Seems that with the change to duplicity 0.7, the default sftp backend changed.
The manpage was being patched to say the default was pexpect over paramiko.
This is no longer true. Remove the manpage changes.
Not sure if the REVISION needs to be bumped or not for this.
RCS file: /cvs/ports/sysutils/duplicity/Makefile,v
retrieving revision 1.35
diff -u -p -r1.35 Makefile
--- Makefile 17 Jan 2016 05:30:31 -0000 1.35
+++ Makefile 7 Feb 2016 22:17:35 -0000
@@ -7,6 +7,7 @@ COMMENT = encrypted backup using rsync a
RCS file: /cvs/ports/sysutils/duplicity/patches/patch-bin_duplicity_1,v
retrieving revision 1.3
diff -u -p -r1.3 patch-bin_duplicity_1
--- patches/patch-bin_duplicity_1 17 Jan 2016 05:30:31 -0000 1.3
+++ patches/patch-bin_duplicity_1 7 Feb 2016 22:17:35 -0000
@@ -19,18 +19,6 @@ Document the ssh backend change from par
.BI "--ssl-cacert-file " file
-@@ -1151,9 +1150,9 @@ scp://.. or
--.BR "defaults" " are paramiko+scp:// and paramiko+sftp://"
-+.BR "defaults" " are pexpect+scp://, pexpect+sftp://, lftp+sftp://"
--.BR "alternatively" " try pexpect+scp://, pexpect+sftp://, lftp+sftp://"
-+.BR "alternatively" " try paramiko+scp:// and paramiko+sftp://"
- See also
- .BR --ssh-askpass ,
@@ -1471,7 +1470,7 @@ which aren't followed by 'foo'. However, it wouldn't
if /home/ben/1234567 existed.
@@ -40,39 +28,3 @@ Document the ssh backend change from par
installed on the system.
-@@ -1764,7 +1763,7 @@ about the requirements for a server to support
- .I scp/ssh
- To make it even more confusing the user can choose between several ssh backends via a scheme prefix:
--paramiko+ (default), pexpect+, lftp+... .
-+paramiko+, pexpect+ (default), lftp+... .
- paramiko & pexpect support
- .BR --use-scp ,
-@@ -1776,7 +1775,7 @@ backend allows to define
- .BR --scp-command " and"
- .BR --sftp-command .
--.BR "SSH paramiko backend " "(default)"
-+.BR "SSH paramiko backend"
- is a complete reimplementation of ssh protocols natively in python. Advantages
- are speed and maintainability. Minor disadvantage is that extra packages are
- needed as listed in
-@@ -1789,7 +1788,7 @@ mode (
- .I --use-scp
- ) though scp access is used for put/get operations but listing is done via ssh remote shell.
--.B SSH pexpect backend
-+.BR "SSH pexpect backend" " (selected by default on OpenBSD)"
- is the legacy ssh backend using the command line ssh binaries via pexpect.
- Older versions used
- .I scp
-@@ -2050,7 +2049,7 @@ see pydrive backend
- (Python Cryptography Toolkit)
- - http://www.dlitz.net/software/pycrypto/ - .TP
--.B ssh pexpect backend
-+.BR "ssh pexpect backend" " (default on OpenBSD)"
- .B sftp/scp client binaries
- OpenSSH - http://www.openssh.com/ - .br
> Seems that with the change to duplicity 0.7, the default sftp backend changed.
> The manpage was being patched to say the default was pexpect over paramiko.
> This is no longer true. Remove the manpage changes.
Was there a rationale for changing the default again?
> Not sure if the REVISION needs to be bumped or not for this.
> [hidden email] writes:
>> Seems that with the change to duplicity 0.7, the default sftp backend
>> The manpage was being patched to say the default was pexpect over
>> This is no longer true. Remove the manpage changes.
> Was there a rationale for changing the default again?
Ok, it looks like we used to patch the default in globals.py but that
variable isn't there anymore so the patch went away.
Would we rather change the default (however that would work in 0.7) to
pexpect again? Paramiko doesn't work for me as it doesn't understand
ed25519 ssh keys but I don't know if that is a global problem for all
I think this patch (versus "duplicity restore pexpect as default ssh
backend") is better as I think we should stay as close to upstream as
possible and if paramiko doesn't fit one's needs, adding "+pexpect" to
the scheme to change the back-end is easily done.