Karmic has 0.5.18
** Changed in: duplicity (Ubuntu)
Status: Confirmed => Fix Released
--
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.
--
ubunt
This fix was released in 0.5.10.
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
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.
** Changed in: duplicity
Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)
--
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-bu
** Changed in: duplicity
Importance: Undecided => Medium
Status: New => Fix Committed
--
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.
--
ubu
** Changed in: duplicity
Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman)
--
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-bu
** Also affects: duplicity
Importance: Undecided
Status: New
--
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
ubu
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...@localho
You need to quote the target, at least, because it contains a space:
'ssh://User [EMAIL PROTECTED]:/home/username/Backup' - or has this been
cleaned by apport during report?
Anyway, the bug is still valid, because it should not crash, but report a sane
error, if the port cannot get parsed. (I've
** Visibility changed to: Public
--
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://list
