Bug 1816528

Summary: Defaults for --skip-compress are not working, everything is being compressed
Product: Red Hat Enterprise Linux 8 Reporter: Simon Matter <simon.matter>
Component: rsyncAssignee: Michal Ruprich <mruprich>
Status: CLOSED ERRATA QA Contact: Ondrej Mejzlik <omejzlik>
Severity: medium Docs Contact:
Priority: low    
Version: 8.1CC: omejzlik, simon.matter
Target Milestone: rcKeywords: AutoVerified, EasyFix, Patch, Reproducer, TestCaseProvided, Triaged
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: rsync-3.1.3-12.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-18 14:55:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
Patch none

Description Simon Matter 2020-03-24 08:43:04 UTC
Description of problem:
When syncing with compression (-z), certain file types should not be compress during the transfer because they are already compressed. The file types which are not to be compressed can be seen in the man page.

Version-Release number of selected component (if applicable):
All versions since 3.1.0

How reproducible:

Steps to Reproduce:
1. run 'rm -f Z ; rsync -azv alpha:z.gz Z'

Actual results:
Transferred data was compressed during the transfer:
sent 43 bytes  received 63,873 bytes  25,566.40 bytes/sec
total size is 628,952  speedup is 9.84

Expected results:
No compression should happen.

Additional info:
Note that the source file 'z.gz' was an ascii text file to show clearly that compression took place.

Comment 3 Michal Ruprich 2020-08-26 10:45:34 UTC
Created attachment 1712666 [details]

Comment 15 errata-xmlrpc 2021-05-18 14:55:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (rsync bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.