Bug 2231587
| Summary: | Transaction fails when installing openms due to file conflict in /usr/lib/.build-id/ | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | ktsh.tanaka.2020 |
| Component: | openms | Assignee: | Antonio T. sagitter <sagitterghostproton.me> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 42 | CC: | gui1ty |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | openms-3.0.0-2.fc40 openms-3.0.0-2.fc39 openms-3.0.0-2.fc38 openms-3.5.0-1.20260107git91afebf.fc43 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2026-01-17 00:48:13 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: | |||
|
Description
ktsh.tanaka.2020
2023-08-12 07:09:34 UTC
The only time .build-id have a conflict is if two rpms have the same binary file. If we look at /usr/lib/.build-id/8a/c2bf7bd15a5aeb09620726b3f8953a68ad7962 we see that is the case. It is pointing to /usr/lib64/OpenMS/libQt5QuickWidgets.so.5.15.10 If we do a diff between /usr/lib64/OpenMS/libQt5QuickWidgets.so.5.15.10 and /usr/lib64/libQt5QuickWidgets.so.5.15.10 provided by qt5-qtdeclarative-5.15.10-1.fc38.x86_64 we see they are identical. I don't know how or why that happened, but I am not the maintainer of openms, so I will let them get it fixed. FEDORA-2023-9fcd1bb0eb has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-9fcd1bb0eb FEDORA-2023-9fcd1bb0eb has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-e0bbe7c488 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-e0bbe7c488 FEDORA-2023-e0bbe7c488 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. Fedora 38 update: https://bodhi.fedoraproject.org/updates/FEDORA-2023-f8a695d80e This appears to be happening again. Not sure why, though. To reproduce: mock -r fedora-rawhide-x86_64 openms It fails with: Transaction failed: Rpm transaction failed. - file /usr/lib/.build-id/17/9527af97e91eb78760b49f641470d951e73467 from install of openms-1:3.1.0-0.16.pre1.fc42.x86_64 conflicts with file from package qt5-qtdeclarative-5.15.15-1.fc42.x86_64 Querying for the file: $ fedrq pkgs --resolve-packages /usr/lib/.build-id/17/9527af97e91eb78760b49f641470d951e73467 openms-1:3.1.0-0.16.pre1.fc42.x86_64 qt5-qtdeclarative-5.15.15-1.fc42.x86_64 Installing qt5-qtdeclarative by itself, I can see that /usr/lib/.build-id/17/9527af97e91eb78760b49f641470d951e73467 points to /usr/lib64/libQt5QuickWidgets.so.5.15.15 This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42. FEDORA-2026-4d1e0aeb9b (autowrap-0.25.0-2.fc43 and openms-3.5.0-1.20260107git91afebf.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-4d1e0aeb9b FEDORA-2026-4d1e0aeb9b 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-4d1e0aeb9b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-4d1e0aeb9b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2026-4d1e0aeb9b (autowrap-0.25.0-2.fc43 and openms-3.5.0-1.20260107git91afebf.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report. |