Description of problem: python3-semantic_version is currently in both EPEL 10 and CRB. This is not allowed by EPEL policy. It looks like when it was added to EPEL it was not yet in CRB. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-82beb4b43d https://issues.redhat.com/browse/RHEL-66994 We have automation in place that should detect this scenario and file a bug about retiring the EPEL package. It didn't work this time and we're looking into why. Until then, please do not update the EPEL package any further to avoid the version moving ahead of the CRB package. Please do not retire this package yet either, we'll take care of that for you. Version-Release number of selected component (if applicable): python3-semantic_version-2.10.0-10.el10 (CRB) python3-semantic_version-2.10.0-10.el10_0 (EPEL)
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Iām now the default EPEL assignee for this package. I will continue to do nothing with the EPEL10 branches, as requested.
Verified that package is in RHEL 10.0. Package has been retired from epel10 and epel10.0. It might take a few days before it is cleared from the repositories and mirrors.