On Wed, 26 Aug 2009 17:34:38 +0200, Tollef Fog Heen writes: >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'
i don't think that your proposed workaround is the right action in this case: first, the problem seems to be a gpg bug which should be fixed in gpg. second, duplicity is using python-gnupginterface, so a gpg1->2 switch needs to be made there (duplicity only ships a private GnuPGInterface.py until the patch for #509415 is finally committed). regards az -- + Alexander Zangerl a...@bond.edu.au DSA 0xF860ACF1 + + Bond University IT School phone +61 7 5595 3398 +
signature.asc
Description: Digital Signature
