Comment 2 for bug 1416344

Sorry, should have said librsync 0.9.7, which is available in most
repositories as librsync1.

librsync 1.0.0 has an incompatible file format and will break current
backup chains.

On Fri, Jan 30, 2015 at 6:39 AM, Kenneth Loafman <email address hidden>
wrote:

> Duplicity is not ready for librsync v1.0.0. Please continue to use the
> older 0.9.0 version.
>
>
> On Fri, Jan 30, 2015 at 4:32 AM, Roman Tereshonkov <
> <email address hidden>> wrote:
>
>> Public bug reported:
>>
>> librsync version 1.0.0 changes rs_sig_begin function API as
>> -rs_job_t *rs_sig_begin(size_t new_block_len, size_t strong_sum_len);
>> +rs_job_t *rs_sig_begin(size_t new_block_len, size_t strong_sum_len,
>> + rs_long_t sig_magic);
>>
>>
>> This makes the problem to compile duplicity/_librsyncmodule.c file.
>> It uses the old rs_sig_begin format:
>> sm->sig_job = rs_sig_begin((size_t)blocklen,
>> (size_t)RS_DEFAULT_STRONG_LEN);
>>
>> ** Affects: duplicity
>> Importance: Undecided
>> Status: New
>>
>> --
>> You received this bug notification because you are subscribed to
>> Duplicity.
>> https://bugs.launchpad.net/bugs/1416344
>>
>> Title:
>> librsync 1.0.0 breaks duplicity/_librsyncmodule.c compilation
>>
>> Status in Duplicity - Bandwidth Efficient Encrypted Backup:
>> New
>>
>> Bug description:
>> librsync version 1.0.0 changes rs_sig_begin function API as
>> -rs_job_t *rs_sig_begin(size_t new_block_len, size_t strong_sum_len);
>> +rs_job_t *rs_sig_begin(size_t new_block_len, size_t strong_sum_len,
>> + rs_long_t sig_magic);
>>
>>
>> This makes the problem to compile duplicity/_librsyncmodule.c file.
>> It uses the old rs_sig_begin format:
>> sm->sig_job = rs_sig_begin((size_t)blocklen,
>> (size_t)RS_DEFAULT_STRONG_LEN);
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/duplicity/+bug/1416344/+subscriptions
>>
>
>