rsync 3.2.2

rsync 3.2.2

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 351 bytes --]

Hi,

now it happened - rsync 3.2.2 is out and running. Earlier then I expected...

Before I do this, I'd rather ask:

Shall I mark the existing patch for 'rsync 3.2.1' as "superseded" and
send a new patch or shall I just send an update for the existing 3.2.1
patch? I want to leave 'zstd 1.4.5' and 'popt 1.18' as they are.

Opinions?

Best,
Matthias

Re: rsync 3.2.2

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]

Hi,

> On 5 Jul 2020, at 17:51, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Hi,
> 
> now it happened - rsync 3.2.2 is out and running. Earlier then I expected...

Well, this happens.

> Before I do this, I'd rather ask:
> 
> Shall I mark the existing patch for 'rsync 3.2.1' as "superseded" and
> send a new patch or shall I just send an update for the existing 3.2.1
> patch? I want to leave 'zstd 1.4.5' and 'popt 1.18' as they are.

However, I would not say that it makes sense to update to this release unless there are some critical fixes in it. If there are aesthetic or other minor fixes in this release, I am sure we can skip one so that we keep enough space in the updates for the bigger stuff (Python, perl, etc.).

I am very happy with your effort, but we basically make every third patch from you land in a release now. That sounds like a lot of work that can be invested into all the other packages that we have maybe?

-Michael

> 
> Opinions?
> 
> Best,
> Matthias

Re: rsync 3.2.2

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]

On 06.07.2020 12:01, Michael Tremer wrote:
> Hi,
> 
>> On 5 Jul 2020, at 17:51, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>> 
>> Hi,
>> 
>> now it happened - rsync 3.2.2 is out and running. Earlier then I expected...
> 
> Well, this happens.
> 
>> Before I do this, I'd rather ask:
>> 
>> Shall I mark the existing patch for 'rsync 3.2.1' as "superseded" and
>> send a new patch or shall I just send an update for the existing 3.2.1
>> patch? I want to leave 'zstd 1.4.5' and 'popt 1.18' as they are.
> 
> However, I would not say that it makes sense to update to this release unless there are some critical fixes in it. If there are aesthetic or other minor fixes in this release, I am sure we can skip one so that we keep enough space in the updates for the bigger stuff (Python, perl, etc.).

IMHO the bug fixes in the changelog for 3.2.2 sound if we could wait:
"Avoid a crash when a daemon module enables transfer logging without
setting a log format value.
Fixed installing rsync-ssl script from an alternate build dir.
Fixed the updating of configure.sh from an alternate build dir.
Apple requires the asm function name to begin with an underscore.
Avoid a test failure in the daemon test when ‑‑atimes is disabled."

> I am very happy with your effort, but we basically make every third patch from you land in a release now. That sounds like a lot of work that can be invested into all the other packages that we have maybe?

Which packages would you have in mind?

Best,
Matthias