Package: duplicity Version: 0.6.15-2 Severity: normal My nightly backups started to fail with 0.6.15 since they relied on the behaviour described in the following way in the duplicity manual: """ .... , if SIGN_PASSPHRASE is not set but PASSPHRASE is set, the latter will be used. """ This functionality broke in 0.6.15, but has been restored in upstream revision 780 ( http://bazaar.launchpad.net/~duplicity- team/duplicity/0.6-series/revision/780 ), on its way for 0.6.16.
Since it made my cron jobs silently prompt for a passphrase, not much was done. The bug was severe in that it made my backups fail, but it was easily discovered and fixed by also setting SIGN_PASSPHRASE in my script, after the abovementioned revision information was found. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.39-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages duplicity depends on: ii libc6 2.13-21 ii librsync1 0.9.7-8 ii python 2.7.2-7 ii python-gnupginterface 0.3.2-9.1 ii python-pexpect 2.3-1 ii python2.7 2.7.2-5 duplicity recommends no packages. Versions of packages duplicity suggests: pn ncftp 2:3.2.5-1 pn python-boto <none> pn rsync 3.0.8-1 pn ssh <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
