[Duplicity-talk] Empty signature or manifest files created in local cache if gpg fails

[Roy Badami]

If you delete the local cache, and then type an incorrect passphrase, 
the first file that duplicity tries to sync results in an empty file (or 
a gzipped file that unpacks to an empty file) in the local cache.

Duplicity *does* detect the gpg failure, and aborts, but only after it 
has already created a (possibly compressed) empty file.  The presence of 
this file prevents any further attempts to resync that file.

I'm guessing this coudl be related to bug  #676042 ?

This is on 0.6.13 on CentOS 5

roy

--
Roy Badami
Roboreus Ltd
1 New Oxford Street
London WC1A 1NU