Bug 1382054 - /usr/bin/zforce does not work
Summary: /usr/bin/zforce does not work
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gzip
Version: 7.4
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Petr Stodulka
QA Contact: Robin Hack
URL:
Whiteboard:
Depends On:
Blocks: 1380361 1393867
TreeView+ depends on / blocked
 
Reported: 2016-10-05 15:34 UTC by Petr Stodulka
Modified: 2017-08-01 18:41 UTC (History)
7 users (show)

Fixed In Version: gzip-1.5-9.el7
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of: 880084
Environment:
Last Closed: 2017-08-01 18:41:49 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
CentOS 6096 0 None None None 2016-10-05 15:34:28 UTC
Red Hat Bugzilla 880084 0 unspecified CLOSED /usr/bin/zforce does not work 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2017:2003 0 normal SHIPPED_LIVE gzip bug fix update 2017-08-01 18:11:35 UTC

Internal Links: 880084

Description Petr Stodulka 2016-10-05 15:34:28 UTC
+++ This bug was initially created as a clone of Bug #880084 +++

+++ This bug was initially created as a clone of Bug #880081 +++

Description of problem:
/usr/bin/zforce fails to identify and rename valid gzipped files

Version-Release number of selected component (if applicable):

gzip-1.3.12-18.el6

How reproducible:
always

Steps to Reproduce:
1.	touch /tmp/test
2. gzip /tmp/test
3. mv /tmp/test.gz /tmp/test
4. zforce /tmp/test
  
Actual results:
Nothing happens

Expected results:
/tmp/test should be renamed to /tmp/test.gz

Additional info:

The /usr/bin/zforce utility is a script. Line 61

if gzip -l < "$i" 2>/dev/null | grep '^compressed' > /dev/null; then

is incorrect. The output of gzip -l /tmp/file (see above) is

         compressed uncompressed ratio uncompressed_name
                 25 0 0.0% /tmp/file

so '^compressed' fails because of the spaces printed in front of "compressed"

Comment 5 errata-xmlrpc 2017-08-01 18:41:49 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, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2017:2003


Note You need to log in before you can comment on or make changes to this bug.