Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Hi,
Specifically for the upcoming RHEL 8.5, I'd like to ask whether it is possible to have rpm rebased on an upstream version >= 4.16.0?
In particular, rpm-ostree started to benefit from the new logic in 'rpmver.h' introduced in https://github.com/rpm-software-management/rpm/pull/1221.
As such it would be helpful to have those APIs available in RHEL 8.5 by the time it gets to GA.
If a rebase is not possible/planned, can the referenced PR be considered for a backport maybe?
Thanks in advance!
Rebasing to a new major version of rpm is out of the question (in rpm versions, the first number denotes the file format and the second is the major version within that).
The introduction of rpmver.h API involves all manner of refactoring such as moving symbols across libraries which is not acceptable within a released RHEL version either. What specifically does rpm-ostree use from that? I fail to see any references to the new API in rpm-ostree codebase.
> Scoping this a bit more, I think the relevant parts are just the new bits in this rpmio commit[1] (plus dependency on previous ones in the PR).
We don't generally backport API additions or other new features because they tend to come with too many strings attached. Like here, the patch is on the large side already, but it's the dependencies that are the real killer - we can't move symbols between libraries.
Generally speaking, rpm is best considered frozen in any RHEL release, and plan ahead accordingly wrt compatibility.