retitle 880111 duplicity should log a warning (not error) for encrypted manifest severity 880111 minor tags 880111 - moreinfo thanks
On Wed, 01 Nov 2017 20:19:31 +0100, Francesco Poli writes: >> 2. could you run another backup invocation with -v9 and attach the output? ... >Attached as duplicity.out thanks for your diagnostic data. >I cannot spot the error there, though... :-| yes, there is no problem in that run. in the meantime i've started up a blank unstable chroot, and i can reproduce the issue on incremental backups. exec summary: please ignore that error message. i've checked the source, and this is actually working as designed: upstream changed the handling of remote manifests in 0.7.14 to more-or-less blindly attempt to access an encrypted remote manifest and if unsuccessful, log that as a nonfatal 'error'. http://bazaar.launchpad.net/~duplicity-team/duplicity/0.8-series/revision/1252/duplicity/collections.py as far as i can tell duplicity doesn't even attempt to fully interact with gpg in this situation, and that's why you see the error message - which is utterly benign: duplicity doesn't even NEED the remote manifest in that situation (earlier on it's logged that "local and remote are in sync"). i'll raise a bug with upstream to improve the logging for this situation. regards az -- Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/ "There are only two industries that refer to their customers as 'users'." -- Edward Tufte
signature.asc
Description: Digital Signature
