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.
Description of problem:
$ rpm -qP python3.11-pybind11-devel
cmake(pybind11) = 2.10.3
pkgconfig(pybind11) = 2.10.3
pybind11-devel = 2.10.3-2.el9
pybind11-static = 2.10.3-2.el9
python3.11-pybind11-devel = 2.10.3-2.el9
python3.11-pybind11-devel(x86-64) = 2.10.3-2.el9
python3.11-pybind11-static = 2.10.3-2.el9
(Almost) all of the provides without the python3.11- prefix are clashing with pybind11-devel (for Python 3.9):
$ rpm -qP pybind11-devel
cmake(pybind11) = 2.6.2
pybind11-devel = 2.6.2-4.el9
pybind11-devel(x86-64) = 2.6.2-4.el9
pybind11-static = 2.6.2-4.el9
EPEL 9 packages that have:
BuildRequires: pybind11-static
will now fetch the Python 3.11 version of the package.
This breaks assumptions. Adding a new Python stack to RHEL should not break existing packages using an older (and in this case even the default) Python stack.
I believe the package should not provide pybind11-devel, pybind11-static. ABout the cmake and pkgconfig provides, I am not sure. Better to filter them out as well I suppose.
Fixing this by removing the provides is technically backwards incompatible because some users could already expect this faulty behavior, but this package is in CRB, so I guess we can do the right thing and fix it.
Version-Release number of selected component: 2.10.3-2.el9
How reproducible: always
Steps to Reproduce:
$ mock -r centos-stream-9-x86_64 install pybind11-static
Actual results:
Installing:
python3.11-pybind11-devel
Expected results:
Installing:
pybind11-devel
Additional info:
Let's fix this by removing the 2 following provides:
pybind11-devel = 2.10.3-2.el9
pybind11-static = 2.10.3-2.el9
Let's fix this both on RHEL 8 & 9 to be consistent.
I realized pybind11-devel is used for explicit Conflicts. This will still work for now but we would need to figure out how to properly handle Conflicts between python3.11-pybind11-devel and python3.X-pybind11-devel for future Python versions.
It is possible to explicitly conflict with python3.11-pybind11-devel from python3.X-pybind11-devel, but it was certainly easier to just conflict with pybind11-devel.
Comment 3RHEL Program Management
2023-09-20 17:06:24 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 4RHEL Program Management
2023-09-20 17:08:22 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.