Re: [Duplicity-talk] [PATCH 0/2] consume a chain of sigtar files in rdiffdir delta mode

[Laszlo Ersek]

Hi,

On 02/05/13 12:05, T. Prost wrote:
> I just notice that rdiffdir is already on my system, although I never
> installed it intentionally. Thus I assumed dependencies - however could
> not find packages which are actually using rdiffdir ???:-|
> But how are the actual dependencies really between the packages
> discussed here and rdiffdir ?

rdiffdir is just a lower-level CLI to (part of) the machinery inside
duplicity. It's very useful for one's own scripts.

Regarding dependencies, rdiffdir and duplicity both depend of said core,
they don't depend on each other.

Kenneth, is there any chance you could review and pick up this series?

Thanks!
Laszlo

> --
> Greetz
> Thomas
> 
> Am Montag, den 31.12.2012, 16:35 +0100 schrieb Laszlo Ersek: 
>> As blurb, I'm pasting here the proposed modified / new manual sections,
>> formatted as plain text:
>>
>> SYNOPSIS
>>
>>    rdiffdir [options] delta full_sigtar {incr_sigtar} new_dir delta_file
>>
>> DESCRIPTION
>>
>>    Regarding  the  delta  command,  the  full_sigtar  operand  is a signa-
>>    ture_file written by an earlier signature or tar  command  (the  latter
>>    using the --write-sig-to option). The optional incr_sigtar operands are
>>    signature files written by earlier delta commands  using  the  --write-
>>    sig-to  option.  This  way  the Nth invocation of the delta command can
>>    parse (and extend) the signature chain that has  been  founded  by  the
>>    first signature or tar command with a full signature, and then extended
>>    by the subsequent N-1 delta invocations with incremental signatures. It
>>    is  the  responsibility  of  the user to specify the sigtar operands in
>>    logical increment order.
>>
>> I gave the patches some light testing on an example directory with two
>> small files: one full backup and two increments. I looked into each
>> delta and sigtar file produced, and then restored and verified each
>> stage.
>>
>> These patches enable me to use rdiffdir as an independent, recursive
>> rdiff primitive, in combination with lbzip2 (parallel bzip2 compression)
>> and custom (UDPv4 based) uploading of deltas and incremental sigtars.
>>
>> The use case has been raised before:
>> https://answers.launchpad.net/duplicity/+question/103229
>>
>> Thanks for considering.
>>
>> Laszlo Ersek (2):
>>   rdiffdir: allow lower-bounds-only for action operands
>>   rdiffdir delta: support incremental sigtar files
>>
>>  bin/rdiffdir   |   14 +++++++-------
>>  bin/rdiffdir.1 |   34 +++++++++++++++++++++++++++++++++-
>>  2 files changed, 40 insertions(+), 8 deletions(-)
>>
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 
> 
> 
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk