What's the corruption scenario that manifest comparison should protect against?
The manifest contains volume checksums, but those aren't checked against the volumes. Eventually the remote manifest is just a copy of the local one. Multiple duplicity instances writing to the same remote should be ruled out as well. The only thing that seems possible is an incomplete backup, but FWIW duplicitly only renames a local temp manifest and uploads it to the remote once the full backup is done. -- https://code.launchpad.net/~dawgfoto/duplicity/fixup1252/+merge/343816 Your team duplicity-team is requested to review the proposed merge of lp:~dawgfoto/duplicity/fixup1252 into lp: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
