← Back to team overview

duplicity-team team mailing list archive

Re: 0.6.01 picking up too many diffs; incorrectly detects 0 volume increment

 

Peter Schuller wrote:
>> I have an almost complete solution committed:
>>
>>   http://bazaar.launchpad.net/~scode/duplicity/archive-sync-removelocal/revision/553
>>
>> The problem is that the "resolution" of base name into local + remote
> 
> So hopefully I fixed it:
> 
>    http://bazaar.launchpad.net/~scode/duplicity/archive-sync-removelocal/revision/555
> 
> It now takes the compressed/encrypted flags and passes on to
> get_suffix() instead of making assumptions based on whether or not
> it's a manifest or not.
> 
> This seems to work better in the case of removals. However, I'm not
> entirely sure whether I just broke something else here; in particular
> in the regular copy_to_local() case it is now using gpg.GzipWriteFile
> based on pr.compressed (and copy_raw() if false). I am not sure this
> is a correct transcribation of the previous version whichi called
> copy_raw() if the file was a manifest.

In the normal course of processing the difference between manifest and
sigtar are necessary in the local side.  The manifest is not compressed
and the sigtar is, so the way I had it was correct.

On the remote side, it's either encrypted or gzipped.  I'll review your
 changes and see if there are any problems.



Follow ups

References