0.7.14: misleading error message for encrypted remote manifest

[az]

this is a forward of debian bug 880111, which lives over there: https://bugs.debian.org/880111

the original submitter uses --encrypt-key <pubkey>, and complains about the 'error processing remote manifest' error, saying that duplicity didn't even ask for a passphrase.

i'm running duplicity also with --encrypt-key and no local private keys whatsoever, and am getting a similarly misleading error message: duplicity claims that 'Local and Remote metadata are synchronized, no sync needed.' but a bit later tries to process (decrypt) the remote manifest,
which cannot work (private key not present).

as far as i can tell this error message is a consequence of revision 1252.

i'd posit that this is not an error at all, and therefore should not be logged, or be logged as warning or otherwise tagged to make it clear that this is benign and pretty much expected.

[Kenneth Loafman (kenneth-loafman)]

Missed the comment... this was fixed in 0.7.14.

[az (az-debian)]

the original reporter disagrees with this having been closed (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880111#63):

"However, this sounds really weird to me: if an error or warning message
is totally harmless and should be ignored by the user, the most sensible
thing to do is to suppress the message, so that it is not shown to the
user at all."

[Martin Nowak (dawgfoto)]

What's the reason to download and process the remote manifest if there is a local one?

[Martin Nowak (dawgfoto)]

Wrote a patch to fix this.
https://code.launchpad.net/~dawgfoto/duplicity/fixup1252/+merge/343816