Bug 1705413

Summary:	gzexe unable to (auto)decompress
Product:	Red Hat Enterprise Linux 8	Reporter:	Jakub Martisko <jamartis>
Component:	gzip	Assignee:	Jakub Martisko <jamartis>
Status:	CLOSED ERRATA	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.1	CC:	fsumsal, jamartis, kdudka, pasik, pstodulk, vvitek
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	gzip-1.9-5.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1690825	Environment:
Last Closed:	2019-11-05 22:16:14 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:
Embargoed:
Bug Depends On:	1690825
Bug Blocks:	1693126

Description Jakub Martisko 2019-05-02 09:04:55 UTC

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

Description of problem:

Gzexe is unable to decompress the file it creates.

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

gzexe (gzip) 1.9 from package gzip-1.9-3.fc28.x86_64
and system up to date.

How reproducible:
Always

Steps to Reproduce:
1. gzexe a file
2. try to uncompress: gzexe -d or execute the auto-extractible file 


Actual results:

gzip: stdin: not in gzip format
/usr/bin/gzexe: test.txt probably not in gzexe format, file unchanged.

Expected results:
The orignal file uncompressed.

Additional info:

The bug come from a modification in the instructions include at the beginning of the generated file (header) (between line 147 and 195 in gzexe script). The script suppose a header of 44 lines long (skip=44, line 148), but currently, the header is 49 lines long.
Changing the skip value from 44 to 49 fixed the problem.

Comment 2 Jakub Martisko 2019-05-02 11:40:20 UTC

Removing users from CC cloned from the fedora bug

Comment 6 errata-xmlrpc 2019-11-05 22:16:14 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-2019:3562