On Mon, February 15, 2016 7:17 am, Jérémie Courrèges-Anglas wrote:
>
> We should fix the current situation one way of the other. duplicity
> users on OpenBSD should speak up. Does the default ssh backend,
> paramiko, prevent you from easily using duplicity on OpenBSD-current?
> Looks like para
"trondd" writes:
> Bump to get this in for 5.9 so users aren't confused by the changed
> default and the resulting incorrect manpage.
>
> If no one thinks it should go in for 5.9, I'll wait for unlock to poke again.
Thanks for caring about this, Tim.
We should fix the current situation one way
On Sun, 2016-02-14 at 11:14 -0500, trondd wrote:
> Bump to get this in for 5.9 so users aren't confused by the changed
> default and the resulting incorrect manpage.
I'd be for it, but I can't reliably test as I don't use ssh with
duplicity.
> If no one thinks it should go in for 5.9, I'll wait f
Bump to get this in for 5.9 so users aren't confused by the changed
default and the resulting incorrect manpage.
If no one thinks it should go in for 5.9, I'll wait for unlock to poke again.
Tim.
On Mon, February 8, 2016 6:43 pm, tro...@kagu-tsuchi.com wrote:
> If we would rather restore pexpect
If we would rather restore pexpect as the default ssh backend instead of
paramiko,
this should do it.
Tim.
Index: Makefile
===
RCS file: /cvs/ports/sysutils/duplicity/Makefile,v
retrieving revision 1.35
diff -u -p -r1.35 Makefile
--
