duplicity-team team mailing list archive

Thread
Date

Re: [Question #141176]: Resuming a failed backup with Assertion errors

To: duplicity-team@xxxxxxxxxxxxxxxxxxx
From: edso <question141176@xxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 26 Jan 2011 16:45:42 -0000
Reply-to: question141176@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

Question #141176 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/141176

    Status: Open => Answered

edso proposed the following answer:
On 26.01.2011 16:35, vergueishon wrote:
> Question #141176 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/141176
> 
> vergueishon posted a new comment:
> bump ... anyone?
> 

Best bet for now would be to start a new chain. Resuming interrupted
backups is still a very new feature and the assertion coming up looks
unpromising to resume to me.

@ken: could you please have a look at the error stack from above and
http://bazaar.launchpad.net/~duplicity-team/duplicity/0.6-series/view/head:/duplicity/collections.py#L117
and shed some light on what this assertion is for? I see it get's a filename. Shouldn't that suffice?

ede/duply.net

-- 
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.