Package: duplicity Version: 0.5.16-1~bpo50+1 For quite a while, duplicity has failed for me with:
GPGError: GPG Failed, see log below: ===== Begin GnuPG log ===== gpg: CAST5 encrypted data gpg: encrypted with 1 passphrase gpg: [don't know]: invalid packet (ctb=00) gpg: [don't know]: invalid packet (ctb=00) gpg: mdc_packet with invalid encoding gpg: decryption failed: invalid packet gpg: [don't know]: invalid packet (ctb=00) ===== End GnuPG log ===== http://217.69.76.57/pipermail/gnupg-devel/2006-September/023181.html and the rest of that patch series fixes this, but it's not applied to GPGv1, just GPGv2. Could duplicity switch to using GPGv2 instead? It's a one-line change at GnuPGInterface.py, line 272. Change self.call = 'gpg' into self.call = 'gpg2' (Just applying the patch to gpg succeeds, but makes the GPG test suite fail.) -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
