Description of problem: We can no longer install pybind11-devel from EPEL or Powertools. It seems like it has been removed from EPEL, but put into Code Ready Builder (CBR) for RHEL 8/9 and CentOS Stream 9. But it is not in Powertools for CentOS Stream 8 and the installation fails. Version-Release number of selected component (if applicable): Latest available version How reproducible: Always Steps to Reproduce: $ docker run --platform linux/arm64 --rm -ti --entrypoint bash quay.io/centos/centos:stream8 # dnf install -y epel-release # dnf config-manager --enable powertools # dnf install pybind11-devel Last metadata expiration check: 0:00:18 ago on Wed Dec 7 15:06:20 2022. All matches were filtered out by modular filtering for argument: pybind11-devel Error: Unable to find a match: pybind11-devel Actual results: Installation fails Expected results: Package installed Additional info: It is possible to install python39-pybind11-devel by enabling the python39:3.9 and python39-devel:3.9 modules. This comes with a new python version and requires a full range of testing for something that should not be neccessary. Everyone that is going to use the produced software will also need to depend on the python39 packages and enable the modules.
I don't believe that much can be done here from the RHEL side. This ticket should probably be reassigned to the Fedora/EPEL maintainer (CC'd) for pybind11 so that we can decide what to do to restore Python 3.6 support. Susi, this issue was discussed at the EPEL meeting today. There are some questions about the precise mechanism that actually removed the package, but it was almost certainly related to the new Python 3.9 package arriving in CRB. It was suggested that the first course of action would be to file a releng ticket and try re-adding the package back into epel8. If that proves to be problematic, we may need to stand up a new `python36-pybind11` (or the like) package specifically for supporting EPEL 8.
See also https://pagure.io/releng/issue/9965 and https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/UB7MQ5CM26GVVK4MNJHPANF3T5QIOGRQ/ Guidelines: The relevant guidelines rule [0]: "In EPEL8 or later, it is also permitted to provide an alternative non-modular package to any package found only in a non-default RHEL module." [0] https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#Policy The package was unretired in EPEL8 2 years ago and is *not* retired in dist-git but it seems retired in PDC: https://pdc.fedoraproject.org/rest_api/v1/component-branches/?name=epel8&global_component=pybind11 So the first thing to figure out is why it is retired in PDC in the first place, who or what did it, and how. In the meantime, assigning this to epel8.
I think this needs a releng ticket, not just assigned to epel8 distribution. We have no permissions to look into why an eol was set the way it was. releng will also need to set the eol to a normal date (2029-05-31) and then tag the package back in.