Rsync allows building against its bundled zlib or the system zlib via the --with(out)-included-zlib flag to configure. This hasn't been done previously as rsync has a customized zlib bundled to aid in its stream compression. However, since rsync-3.1.1, it has been able to use the bundled zlib (by way of --old-compress) or system zlib (by way of --new-compress) to allow syncing with rsyncd that was built with the opposite zlib choice of the client.
When using system zlib, PORTAGE_RSYNC_EXTRA_OPTS should include "--new-compress" to allow syncing against gentoo's rsync servers. Otherwise, emerge --sync will fail.
Thank you for your contribution.
The base-system team is currently discussing the potential negative influence on our portage rsync mirrors.
Once we have come to a positive conclusion we might apply this change.
Adding the portage team to the CC list
Given the incompatibility system zlib would cause, I would suggest disabling it by default for a lengthy period.
Maybe we could enable system zlib by default several years after new compression becomes the default option in rsync.
The bug has been referenced in the following commit(s):
Author: Lars Wendler <firstname.lastname@example.org>
AuthorDate: 2020-06-16 10:15:16 +0000
Commit: Lars Wendler <email@example.com>
CommitDate: 2020-06-16 10:15:32 +0000
net-misc/rsync: Bump to version 3.2.0_pre2
Added support for system-zlib
Package-Manager: Portage-2.3.101, Repoman-2.3.22
Signed-off-by: Lars Wendler <firstname.lastname@example.org>
net-misc/rsync/Manifest | 1 +
net-misc/rsync/metadata.xml | 2 +
net-misc/rsync/rsync-3.2.0_pre2.ebuild | 114 +++++++++++++++++++++++++++++++++
3 files changed, 117 insertions(+)