Bug 2187587

Summary: file tool / library returns the wrong mimetype for certain gzip files
Product: Red Hat Enterprise Linux 8 Reporter: Daniel Alley <dalley>
Component: fileAssignee: Vincent Mihalkovič <vmihalko>
Status: CLOSED MIGRATED QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.8CC: kdudka, lzaoral
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-20 23:25:47 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:
Attachments:
Description Flags
gzip file none

Description Daniel Alley 2023-04-18 04:25:58 UTC 
Created attachment 1957931 [details]
gzip file

Description of problem:

When using the `file -i` command or the file library (more details on that case here: [0]), for some gzip files and not others, the result seems to be incorrect, even though the gzip file has a valid "magic number" identifier value just like any other.

[0] https://github.com/rpm-software-management/createrepo_c/issues/353

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

From RHEL 8 until recent versions of Fedora.  I haven't tested RHEL 7 or 9 specifically.

How reproducible: Very

Steps to Reproduce:

Take the attached gzip file, run file -i af12533499469117e3824bc938bfc3208539deb44bbf56ec2612fc383b28a1f4-primary.xml.gz

Actual results:

The response "application/octet-stream; charset=binary" is incorrect.  A second person tried to reproduce this on Fedora 39 (rawhide) and got a different incorrect result: 

$ file af12533499469117e3824bc938bfc3208539deb44bbf56ec2612fc383b28a1f4-primary.xml.gz 
af12533499469117e3824bc938bfc3208539deb44bbf56ec2612fc383b28a1f4-primary.xml.gz: DOS/MBR boot sector; partition 1 : ID=0x4b, active 0xd0, start-CHS (0x63,239,44), end-CHS (0x33d,134,0), startsector 316955931, 1708404748 sectors; partition 3 : ID=0x53, active 0xaa, start-CHS (0x33a,156,2), end-CHS (0x22c,176,51), startsector 1315648692, 2595702924 sectors; partition 4 : ID=0x3a, active 0xca, start-CHS (0x1d5,97,37), end-CHS (0x28b,241,55), startsector 2173204403, 2875341233 sectors
$ rpm -q file-libs
file-libs-5.44-3.fc39.x86_64



Expected results:

"application/gzip; charset=binary"
Comment 1 RHEL Program Management 2023-09-20 23:25:13 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 2 RHEL Program Management 2023-09-20 23:25:47 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.