On Sat, 29 Nov 2025 07:59:18 -0600, Kenneth Loafman writes: >I have a possible fix for this, see attached patch. Would you mind trying >it? >Seems there was a line deleted that should not have been. AArgh!
with the patch i get different but still broken behaviour. same invocation as last time: duplicity backup --exclude-other-filesystems --volsize 250 \ --encrypt-key 2FCCF66BB963BD5F --archive-dir /var/lib/duplicity \ --name boot --full-if-older-than 7D /boot \ rsync://backup@REDACTED::/backup/REDACTED/boot Local and Remote metadata are synchronized, no sync needed. Last full backup date: Wed Nov 26 01:04:01 2025 Error processing remote file (duplicity-inc.20251129T053415Z.to.20251129T150401Z.manifest.gpg): GPG Failed, see log below: ===== Begin GnuPG log ===== gpg: encrypted with 4096-bit RSA key, ID 0x360EEB3F4F780821, created 2013-11-03 "Alexander Zangerl <[email protected]>" gpg: decryption failed: secret key not available ===== End GnuPG log ===== Manifests not equal because different volume numbers Fatal Error: Remote manifest does not match local one. Either the remote backup set or the local archive directory has been corrupted. -- Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + https://snafu.priv.at/ Hal, open the file Hal, open the damn file, Hal open the, please Hal
signature.asc
Description: Digital Signature
