On Fri, 03 Nov 2017 18:00:28 +1000 Alexander Zangerl wrote: [...] > 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.
Or maybe because the error was sent to stderr, but I only redirected
the stdout with
$ duplicity -v9 --archive-dir foo_archive --encrypt-key
XXXXXXXXXXXXXXXX \
--full-if-older-than 30D foo_dir/ file://foo_backup \
| tee duplicity.out
I didn't think about stderr, unfortunately.
If there was anything sent there, I believe it ended up mixed with
stdout, but not to file duplicity.out ...
>
> in the meantime i've started up a blank unstable chroot, and i can
> reproduce the issue on incremental backups.
Perfect, so the issue is reproducible on one of your setups.
Thanks a lot for taking the time to test it!
>
> 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").
Awkward...
>
> i'll raise a bug with upstream to improve the logging for this situation.
Thank you so much!
Looking forward to seeing this whole issue solved/clarified for the
best.
Now I have to figure out why "gpg --sign bar.txt" does not work for me
outside X... :-/
--
http://www.inventati.org/frx/
There's not a second to spare! To the laboratory!
..................................................... Francesco Poli .
GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpd_zpBCiwLL.pgp
Description: PGP signature
