Question #183711 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/183711
Cristian Măgherușan-Stanciu posted a new comment: The issue is still there in 0.6.22, and I also confirm the workaround shown in comment #11 solved my problem. It would be nice to be able to optionally ignore that check, to me it's more important that(especially full) backups are always resume-able and I know for sure the passphrase is the same one I used when first creating the backup. -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity. _______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
