Description of problem: python-sphinx-issues is a BR for python-werkzeug->python-flask->python-opentelemetry->python-xds-protos->grpc->libarrow, which in turn is a BR ceph quincy (17.2.x). While ceph itself will not (ever) be built in EPEL, there are Ceph developers who want to use CentOS Stream or RHEL with EPEL. Note: libarrow and all its dependencies, including python-sphinx-issues, are already available from the CentOS Storage SIG. I'm told though that many Ceph devs prefer to use EPEL over the CentOS Storage SIG. Version-Release number of selected component (if applicable): python-sphinx-issues-3.0.1 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: It builds as is from the rawhide sources (see https://koji.fedoraproject.org/koji/taskinfo?taskID=87207361 ) If you don't wish to build python-sphinx-issues in EPEL yourself, please add the epel-packagers-sig group as collaborator for epel* branches, or (less preferable) add me (FAS: kkeithle) as a collaborator for epel* branches. Thanks
I don't, so I've added the group.
I am the package maintainer for grpc, python-xds-protos, and python-opentelemetry. It may be useful to build this for EPEL9, but it should not be required for grpc. I am able to build python-opentelemetry for EPEL9 in a COPR[1] by disabling certain subpackages with missing dependencies. I already have a bootstrap build of grpc, and I expect to complete a non-bootstrap build shortly. At that point, I am just waiting on a couple of repository branch requests to go through before I can start real builds in a side tag. [1] https://copr.fedorainfracloud.org/coprs/music/grpc-epel9/packages/
I'd like to have it as it is a requirement for python-flask for which i have opened bz 2089764.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle. Changing version to 37.
(In reply to Ulrik Haugen from comment #3) > I'd like to have it as it is a requirement for python-flask for which i have > opened bz 2089764. Or presumably not as python-flask has now been built for epel9 without needing this.