duplicity-team team mailing list archive

[edso <edgar.soldin@xxxxxx>]

You should probably check for a plausible size as well. We had a report that some volume had zero sizes. see
http://lists.gnu.org/archive/html/duplicity-talk/2011-08/msg00013.html

Maybe it'd make sense to list/check directly after every volume is finished with the backend, as long as the temporary file/meta data is still there to compare sizes?

ede/duply.net

On 23.08.2011 19:32, Michael Terry wrote:
> Michael Terry has proposed merging lp:~mterry/duplicity/early-catch-498933 into lp:duplicity.
> 
> Requested reviews:
>   duplicity-team (duplicity-team)
> 
> For more details, see:
> https://code.launchpad.net/~mterry/duplicity/early-catch-498933/+merge/72607
> 
> This is a stop-gap measure for bug 498933.  Since we can't reproduce, and most people that normally discover the bug do it months or years after the actual bug happened, it seems wise to add code to detect the bug as it happens.
> 
> This way, users won't mistakenly think their backup is safe, and hopefully we can get some good data in the bug from users that are able to actually hit the bug itself, not just the symptoms.
> 
> 

-- 
https://code.launchpad.net/~mterry/duplicity/early-catch-498933/+merge/72607
Your team duplicity-team is requested to review the proposed merge of lp:~mterry/duplicity/early-catch-498933 into lp:duplicity.