duplicity-team team mailing list archive
-
duplicity-team team
-
Mailing list archive
-
Message #01951
Re: Next release
Just went through and found a few more dups. That should be all of them.
I also tried to explain a bit more about the three symptoms and what a user
can do about it in the master bug.
On 23 January 2014 12:33, Michael Terry <mike@xxxxxxxxxxx> wrote:
> (Note that in explaining this to affected users, the fix doesn't actually
> get their data back. That's gone for good. But it helps avoid the bug for
> the future.)
>
> There is a separate but related patch in 0.6.23 that makes the bug less
> severe by letting the user restore the rest of the files that aren't
> affected (rather than aborting restore entirely):
>
> https://code.launchpad.net/~mterry/duplicity/catch-seq-copy-error/+merge/186106
>
> But again, we can't do anything about the files actually affected by the
> chunk-loss bug.
>
> -mt
>
>
> On 23 January 2014 12:30, Michael Terry <mike@xxxxxxxxxxx> wrote:
>
>> Yes. It is the root cause to both those issues (I've marked as dups).
>>
>> Anything that looks like:
>>
>> assert len( patch_seq ) == 1, len( patch_seq )
>> or
>> assert first.difftype != "diff", patch_seq
>> or
>> librsync error 103 while in patch cycle
>>
>> is fixed by this bug.
>>
>>
>>
>> On 23 January 2014 12:21, <edgar.soldin@xxxxxx> wrote:
>>
>>> is this possibly related to these new issues people showed up with on
>>> the list as well?
>>>
>>> 1. https://answers.launchpad.net/duplicity/+question/242530
>>> 2. https://bugs.launchpad.net/duplicity/+bug/1271927
>>>
>>> thx.. ede
>>>
>>> On 23.01.2014 18:09, Michael Terry wrote:
>>> > https://bugs.launchpad.net/duplicity/+bug/1252484
>>> >
>>> >
>>> > On 23 January 2014 11:51, <edgar.soldin@xxxxxx <mailto:
>>> edgar.soldin@xxxxxx>> wrote:
>>> >
>>> > On 23.01.2014 17:46, Michael Terry wrote:
>>> > > Is there an ETA for 0.6.23? I'd like to see that data loss fix
>>> in the wild.
>>> > >
>>> > > (Ubuntu has it patched in as an update, so no pressure from my
>>> side really, but I still see the occasional question or bug filed about it.
>>> The sooner we get the fix out the better.)
>>> > >
>>> >
>>> > which one is that again? is there a ticket?
>>> >
>>> > ..ede
>>> >
>>> > _______________________________________________
>>> > Mailing list: https://launchpad.net/~duplicity-team <
>>> https://launchpad.net/%7Eduplicity-team>
>>> > Post to : duplicity-team@xxxxxxxxxxxxxxxxxxx <mailto:
>>> duplicity-team@xxxxxxxxxxxxxxxxxxx>
>>> > Unsubscribe : https://launchpad.net/~duplicity-team <
>>> https://launchpad.net/%7Eduplicity-team>
>>> > More help : https://help.launchpad.net/ListHelp
>>> >
>>> >
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~duplicity-team
>>> Post to : duplicity-team@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~duplicity-team
>>> More help : https://help.launchpad.net/ListHelp
>>>
>>
>>
>
Follow ups
References