I know I'm chiming in pretty late here, but this error is not due to spaces. It's because the user entered the target location using a colon at the end of the hostname (which is standard ssh syntax, but not for duplicity according to the man page). Instead of specifying the target as u...@localhost:/path/to/backup, one should use u...@localhost/path/to/backup. Apparently duplicity interprets the colon to mean that a port number follows. Clearly untrue. The issue of whether a sane error message should be printed still stands.
-- duplicity crashed with ValueError in port() https://bugs.launchpad.net/bugs/229826 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
