Bug 2513643
| Summary: | file 5.47 misclassifies systemd unit files as application/x-wine-extension-ini | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Petr Sklenar <psklenar> |
| Component: | file | Assignee: | Vincent Mihalkovič <vmihalko> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 45 | CC: | lzaoral, pbrobinson, vmihalko |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | file-5.48-3.fc46 file-5.48-3.fc45 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2026-09-01 04:04:46 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Petr Sklenar
2026-08-10 20:03:50 UTC
I won't speak for the maintainer since this is regression that should be fixed. Nonetheless, isn't there a different tool that you could use for the brp-mangle-shebangs script? One that only detects text/* mime types? file, in general, is very brittle and every major release causes some regressions due to the way the detection is implemented so it's output is more or less informative but nothing more. (In reply to Lukáš Zaoral from comment #1) > I won't speak for the maintainer since this is regression that should be > fixed. > > Nonetheless, isn't there a different tool that you could use for the > brp-mangle-shebangs script? One that only detects text/* mime types? file, > in general, is very brittle and every major release causes some regressions > due to the way the detection is implemented so it's output is more or less > informative but nothing more. I have created now : https://bugzilla.redhat.com/show_bug.cgi?id=2513837 From mailing list discussion: "This was so problematic that it was reverted in commit f37cc42c on March 25, 2026, explicitly because it “matches too many unix stanza files.” What appears to have happened, is commit 7a1ada9c landed Sept 6,2025. File-5.47 was released Feb 27. Complaints and it was reverted in March as noted. Then June 8, 2026 file 5.48 was released. If we just update to the latest, this problem goes away." Steve Grubb I'm working on an update to 5.48 right now. It appears you did an update in the past to 5.48 in the past and it was unpushed because of problems: https://bodhi.fedoraproject.org/updates/FEDORA-2026-f218bce1f9 https://bodhi.fedoraproject.org/updates/FEDORA-2026-412ea7bd7b https://bodhi.fedoraproject.org/updates/FEDORA-2026-24396f548e Please make sure you take that feedback into account as well. Yes, waiting for upstream to merge the regression fix. FEDORA-2026-49eaa2233d (file-5.48-3.fc46) has been submitted as an update to Fedora 46. https://bodhi.fedoraproject.org/updates/FEDORA-2026-49eaa2233d FEDORA-2026-f218bce1f9 (file-5.48-2.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-f218bce1f9 FEDORA-2026-24396f548e (file-5.48-2.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-24396f548e FEDORA-2026-412ea7bd7b (file-5.48-3.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-412ea7bd7b FEDORA-2026-412ea7bd7b has been pushed to the Fedora 45 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-412ea7bd7b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-412ea7bd7b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2026-24396f548e has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-24396f548e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-24396f548e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2026-f218bce1f9 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-f218bce1f9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-f218bce1f9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2026-49eaa2233d (file-5.48-3.fc46) has been pushed to the Fedora 46 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2026-412ea7bd7b (file-5.48-3.fc45) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report. |