Hi
On Sat, May 26, 2012 at 12:10:38AM -0400, Dwayne C. Litzenberger wrote:
tags 659007 + fixed-upstream patch
thanks
A new versions of Paramiko has been released, which fixes this bug:
http://pypi.python.org/pypi/paramiko/1.7.7.2
Do you think you could upload a new version of
tags 659007 + fixed-upstream patch
thanks
A new versions of Paramiko has been released, which fixes this bug:
http://pypi.python.org/pypi/paramiko/1.7.7.2
Do you think you could upload a new version of python-paramiko soon so that
this bug can be fixed before the wheezy is frozen?
There's a patch for this issue here:
https://github.com/paramiko/paramiko/pull/63
--
Dwayne C. Litzenberger dl...@dlitz.net
OpenPGP: 19E1 1FE8 B3CF F273 ED17 4A24 928C EC13 39C2 5CF7
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
I forwarded the bug upstream
https://bugs.launchpad.net/duplicity/+bug/946992 and afterwards I
managed to trigger it again with -v9, which showed that it is the
same issue as the later reported Debian bug #660378.
It is reported upstream in python-paramiko as
Package: duplicity
Version: 0.6.17-3
Severity: important
I have had a very simple backup script using duplicity runnig for a long time.
Recently (I have noticed it since mid-January, perhaps related to the
introduction of python-paramiko) it frequently (not always) fails with (using
switches
5 matches
Mail list logo
