Comment # 3 on bug 1046197 from Ralf Friedl

I modified the Summary to better reflect the problem and to make it easier to
find.

This is not a problem of rsync version 3.1.2, it is a problem of the
configuration options. You just need to change zlib to
--with-included-zlib=yes, and of course not delete the included zlib in the
spec file. I have done exactly that and my rsync works again, so my problem is
solved at the moment, but I would prefer it if I didn't have to compile it
myself every time there is an update.

To add to the motivation for enabling the compress option:
If the option -z is given to the rsync on the client side, it will ignore the
option and send uncompressed data. This is not good, as in some cases the data
can be compressed quite well, which can lead to additional time and cost, as
mentioned before:

This rsync lacks old-style --compress due to its external zlib.  Try -zz.
Continuing without compression.

But if a client with zlib enabled passes the option -z to a new rsync on the
server side, it will just abort and close the connection. That means that the
transfer will not take longer of be more expensive, it will not happen at all:

rsync: This rsync lacks old-style --compress due to its external zlib.  Try
-zz.
rsync error: syntax or usage error (code 1) at main.c(1582) [server=3.1.2]
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(235)
[Receiver=3.1.0]

So I could either modify all scripts doing rsync with my server, and some of
them are not even on my computers, or I could enable the zlib again, which is
of course what I did.