From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Fischer To: development@lists.ipfire.org Subject: Re: rsync 3.2.2 Date: Mon, 06 Jul 2020 18:40:58 +0200 Message-ID: In-Reply-To: <01E50C03-FAD9-47DA-AE85-F4B7D4DD7175@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7002300095195492237==" List-Id: --===============7002300095195492237== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 06.07.2020 12:01, Michael Tremer wrote: > Hi, >=20 >> On 5 Jul 2020, at 17:51, Matthias Fischer = wrote: >>=20 >> Hi, >>=20 >> now it happened - rsync 3.2.2 is out and running. Earlier then I expected.= .. >=20 > Well, this happens. >=20 >> Before I do this, I'd rather ask: >>=20 >> 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. >=20 > However, I would not say that it makes sense to update to this release unle= ss 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 spac= e 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 =E2=80=91=E2=80=91atimes is disa= bled." > I am very happy with your effort, but we basically make every third patch f= rom you land in a release now. That sounds like a lot of work that can be inv= ested into all the other packages that we have maybe? Which packages would you have in mind? Best, Matthias --===============7002300095195492237==--