On Fri, 30 Sep 2011 11:55:11 +0100, Steve Crook writes: >This upgrade seems to have introduced a requirement >to supply a passphrase during backup jobs.
not quite: running with -v9 would show that there's a cache desynchronization the resurfaced with 0.6.14 (see #572792) where duplicity doesn't remove some old files from the backend but only from the local archive. on the next backup run it then sees the apparently missing file, tries to copy it over from the backend and asks for the passphrase because files on the backend are encrypted but files in the local archive dir are not. the problem is that i stuffed up the relevant patch in 0.6.14. that's just been fixed in 0.6.15 which will be uploaded within the hour. after installing 0.6.15 you'll need to get the cache back in sync with the backend, which duplicity will attempt to fix on the first backup or any other op that accesses backup contents (= anything but collection-status). for this purpose i'd recommend running "duplicity list-current-files" with the appropriate passphrase once. regards az -- + Alexander Zangerl + DSA 42BD645D + (RSA 5B586291) "Die Bandbreite steigt in Gasblasen aus der Sargassosee und wird von dort in Ethernetkabel gefüllt." -- Dirk Moebius
signature.asc
Description: Digital Signature
