patches - Re: new release 3.4.0 - critical security release
Madhu
enometh at meer.net
Sun Jan 19 04:38:57 UTC 2025
* "rsync.project via rsync" <CAJnOL=pWrPBEdwFTMY7mnKkgt997QG7s+5JRg=f8zXgDcA0ESg at mail.gmail.com> :
Wrote on Wed, 15 Jan 2025 09:34:10 +1100:
> sorry about the prefix changes in rsync-patches. We're going to be dropping
> the whole rsync-patches system soon anyway, as it really isn't working
> well. It was supposed to be a staging area where users would test the
> patches before being considered for the main release, but we haven't really
> received any feedback on the patches, so not serving a useful purpose now.
> I'll probably stop updating it for the next release.
There had been no commits on the github site
https://github.com/WayneD/rsync-patches.git since 04-2024, so I
thought it was already defunct, maybe the development happens
elswewhere? I was surprised to hear of the tarball.
fwiw I've been a staple consumer of clone-dest direct-io downdate
omit-dir-changes, at least until 3.3.0.
> On Wed, 15 Jan 2025 at 08:57, Ryan Carsten Schmidt <rsync at ryandesign.com>
> wrote:
>
>> The patches within the rsync-patches-3.4.0.tar.gz archive seem to contain
>> new unnecessary hunks that change the prefix from /usr to /usr/local. This
>> was not the case in 3.3.0.
More information about the rsync
mailing list