Seems to me this thing is not completely fix as of duplicity 0.6.21-0ubuntu4.1 in saucy, and I just lost a backup on a remote machine that took 2 days to build up, then was broken/undecryptable with the same messages and symptoms as found in this bug here, and I even unintentionally deleted the whole big data transfer that took two days by trying to repair it somehow with the "cleanup" command.
Let me know if you need any information that helps fixing this thing, or analyzing why it still happens here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/946988 Title: GnuPG passphrase error after failed backup session Status in Duplicity - Bandwidth Efficient Encrypted Backup: Fix Released Status in “duplicity” package in Ubuntu: Fix Released Status in “duplicity” source package in Precise: In Progress Bug description: After a failed backup session, duplicity cannot resume the volume creation, and seems to fail with "bad passphrase". It is, however, the same passphrase that is always used. The backup set thus seems to be unusable, and the only solution I've found is to simply create a new backup set in a new directory, losing incremental history. Full output attached as "duplicity-error-incremental-log-v9". Also reported as Debian bug #659009, but it has gotten no attention for a month. Duplicity 0.6.17 Python 2.7.2+ Debian Sid Linux To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/946988/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
