[Rpm-maint] [rpm-software-management/rpm] Enhance requires with version information from the build root. (PR #4081)

Florian Weimer notifications at github.com
Thu Jan 8 10:15:06 UTC 2026


fweimer-rh left a comment (rpm-software-management/rpm#4081)

Note that we received some rather strongly worded complaints when some applications built on RHEL 9.7 could no longer be installed on RHEL 9.6 and earlier because they automatically picked up the use of `GLIBC_2.35` symbols we backported in RHEL 9.7. If I understand this proposal here, this change would make this behavior unconditional, for all applications (but only for the RPM metadata). Based on our experience, some developers really do not want that.

This change would also make more RPMs non-portable across CentOS Stream and RHEL y-stream because the RHEL build dist tag sometimes contains a minor release number, while the CentOS Stream builds never will. This discrepancy can make the RHEL NVR either greater than or less  than the CentOS Stream NVR, depending on what follows in the `Release:` tag. Currently, this doesn't matter for ELF dependencies.

On the other hand, for Fedora rawhide, we have some logic that looks for the symbol version under development and adds versioned requires, which is similar to what is proposed here. But we are only doing this for very new symbols on rawhide.

Debian solves this issue with symbol versioning files that contain manually curated version numbers. It cannot accurately represent parallel branches; no approach with just a single version can.  ALT Linux has a hash-based approach which I don't quite understand, but which doesn't seem to need manual maintenance apparently.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/4081#issuecomment-3723166240
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/pull/4081/c3723166240 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20260108/e445ab1c/attachment.htm>


More information about the Rpm-maint mailing list