Bug 2307038
| Summary: | pkgconf-2.1.1 incorrectly orders libraries for linking | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Don Zickus <dzickus> |
| Component: | pkgconf | Assignee: | Neal Gompa <ngompa13> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 40 | CC: | awilliam, igor.raits, ngompa13 |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | pkgconf-2.1.1-2.fc40 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-09-03 05:50:09 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
Don Zickus
2024-08-21 19:37:00 UTC
Can we identify the post-2.1.1 fix for this? We generally prefer to go forwards rather than backwards in Fedora, so it'd be nicer to backport the fix rather than roll back to 2.1.0. Looks like this was reported upstream at https://github.com/pkgconf/pkgconf/issues/361 and the recommendation was "use 2.2.0", but 2.2.0 comes with ABI changes and an soname bump so we really shouldn't do that. The fix was https://github.com/pkgconf/pkgconf/pull/345 , which is a lot of change. Perhaps what we should do is revert https://github.com/pkgconf/pkgconf/pull/339 , which is what broke this, and seems to have been only a performance improvement, not a functionality fix (so reverting it shouldn't *break* anything, just make complex cases slower). Reverting that patch would work for me. There does not seem to be a lot of commits between 2.1.0 and 2.1.1. This seems to be the most likely commit causing the issue: https://github.com/pkgconf/pkgconf/commit/80b5011e697d66065f8aaf88821ce95b3e3d1773 Let me see if I can prepare a build with this reverted... (Oh man, this was stuck due to comment collisions, it's a bit late now...) I see Adam is already on it: https://src.fedoraproject.org/rpms/pkgconf/c/464f5730acc4271233466772932209b6cd0e780a?branch=f40 FEDORA-2024-eae89af680 (pkgconf-2.1.1-2.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-eae89af680 FEDORA-2024-eae89af680 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-eae89af680` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-eae89af680 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-eae89af680 (pkgconf-2.1.1-2.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report. |