Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
gzip -l shows nonsense for archives > 4GB. It showing negative compression ratio.
This is nowadays a big problem.
We should either say something like "Sorry, too big archive" or (better) fix this bug so that gzip -l works regardless of the file size.
See manual:
-- 8< --
The gzip format represents the input size modulo 2^32, so the --list
option reports incorrect uncompressed sizes and compression ratios for
uncompressed files 4 GB and larger. To work around this problem, you
can use the following command to discover a large uncompressed file's
true size:
zcat file.gz | wc -c
The --list option reports sizes as -1 and crc as ffffffff if the com‐
pressed file is on a non seekable media.
-- >8 --
This will never be fixed.
*** This bug has been marked as a duplicate of bug 752040 ***