Comment 20 for bug 394629

Kenneth Loafman a écrit :
> Cristian KLEIN wrote:
>> Kenneth Loafman a écrit :
>>> I just pushed the fix to this bug to the trunk. Thanks Peter for the
>>> initial analysis. The bug was caused by the early out in
>>> GPG/GZIPWriteFile() that stops at a certain volume size. I had removed
>>> the size = sys.maxint args in to_remote() and to_final() after the
>>> change to block size. My mistake. GZipWriteFile() was taking an early
>>> out at 5MB and never finishing the iteration.
>>>
>>> ** Changed in: duplicity
>>> Status: Confirmed => Fix Committed
>> Hello,
>>
>> I'm sorry to tell you, but I still experience this bug even with the
>> last duplicity from bzr #553. I make sure that all previous traces of
>> duplicity were erased and that the patch in dup_temp.py was correctly
>> applied.
>
> I just pushed another release with, I hope, the final fix. Turns out
> that this one was not findable with a debugger, in fact, it would pass
> completely when run under a debugger. AArgh!
>
> If you could please test this out in your environment, I could get a
> release out soon.

Good work! I downloaded the latest bzr and the hang does not occur any
more. Thank you for your patience!