duplicity-team team mailing list archive

[Michael Terry <michael.terry@xxxxxxxxxxxxx>]

I've updated this branch to use a simpler, more generic approach.

*Any* exception when running patch_seq2ropath should be ignored (though logged) and duplicity should move on.  This covers the two asserts in that function (bug 1155345 and bug 720525) as well as errors that happen during file copying (bug 662442).

This doesn't solve any of those bugs, obviously.  But it makes them less severe.

I'm getting the feeling that all three bugs have the same root cause: a missing sequence object.  662442 can be explained by a missing patch in the sequence, and the other two can be explained by a missing first snapshot...
-- 
https://code.launchpad.net/~mterry/duplicity/catch-seq-copy-error/+merge/186106
Your team duplicity-team is requested to review the proposed merge of lp:~mterry/duplicity/catch-seq-copy-error into lp:duplicity.