Package: duplicity Version: 0.6.18-3 Severity: important Dear Maintainer,
When using scp or sftp as a backend with the default SSH-backend it becomes unpossible to use a non-standard port (!=22). If you upgrade to Wheezy the --ssh-options="-o Port 3232" won't be used anymore due to paramiko. In duplicity v0.6.19 ssh_config support was added. So the current packages and configurations break existing backup setups and limits the usability of Backupninja. I see a couple of possible solutions: - add a note to the release notes (and/or other appropriate places) - get the one from Sid (haven't looked at dependencies and such) Obviously the note would be the easiest, but personally I consider the current behavior to be stupid enough to warrant a bigger change. Changing the default backend to pexpect would be another option but that only arrived in Duplicity 0.6.19 - which isn't available in testing. Curious to hear your opinion on how to deal with this, Kwadronaut -- System Information: Debian Release: 7.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages duplicity depends on: ii libc6 2.13-38 ii librsync1 0.9.7-9 ii python 2.7.3-4 ii python-gnupginterface 0.3.2-9.1 Versions of packages duplicity recommends: ii python-paramiko 1.7.7.1-3.1 ii rsync 3.0.9-4 Versions of packages duplicity suggests: pn lftp <none> pn ncftp <none> pn python-boto <none> pn python-cloudfiles <none> pn python-gdata <none> ii python-pexpect 2.4-1 pn tahoe-lafs <none> -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
