What were you trying to do that didn't work?

Build packages in EPEL that have a build time dependency on python3-semantic_version

What is the impact of this issue to you?

This affects the availability of multiple packages in EPEL 9 and EPEL 10. So far we've identified python3-setuptools-rust, matrix-synapse, breezy, and python-bcrypt as packages that have already been requested in EPEL but can't be built. There are a half dozen more Fedora packages that would also be blocked if they end up being requested for EPEL.

This package is already part of the buildroot, but no subpackages are shipped in BaseOS, AppStream, or CRB. That means it is eligible to be added to EPEL itself, however it would be easier for everyone if the existing build could just be moved from the buildroot to CRB. For reference, it was requested for EPEL 9 in rhbz#2173215, and for EPEL 10 in rhbz#2316989. In those bugs there was some general indication from RHEL maintainers that this is feasible for CRB.

Please provide the package NVR for which the bug is seen:

python3-semantic_version-2.10.0-8.el10