Hi Alexander, Many thanks for your answers.
a) report your full duplicity invocation (without that i have no clue what backend you're using, whether this was a full backup only or incremental or whatever)
duplicity does the full backup normally The issue occurs while trying to do an incremental backup On my setup, the backend is a cifs partition mounted locally
and b) reproduce the problem from a clean state, run duplicity with -v9 and provide the resulting log as well (minus personal/private information).
Well, I hopefully have found a workaround: With the option "--no-encryption" duplicity makes full and incremental backups as usual (except ciphering, which is not really a point in my case. I just need no to lose data) Obviously, duplicity encounters some bad interactions with possible recent updates of gpg...
Best regards Christophe
