Description of problem: python-itsdangerous is a BR for 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-itsdangerous, 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-itsdangerous-2.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=87205165) If you don't wish to build python-itsdangerous 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 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.
If you do not wish to maintain python-itsdangerous in epel9, or do not think you will be able to do this in a timely manner, the EPEL Packagers SIG would be happy to be a co-maintainer of the package; please add the epel-packagers-sig group through https://src.fedoraproject.org/rpms/python-itsdangerous/addgroup and grant it commit access, or collaborator access on epel* branches. I would also be happy to be a co-maintainer (FAS: tdawson). Please add me through https://src.fedoraproject.org/rpms/python-itsdangerous/adduser
Will you be able to branch and build python-itsdangerous in epel9? If you do not wish to maintain python-itsdangerous in epel9, or do not think you will be able to do this in a timely manner, the EPEL Packagers SIG would be happy to be a co-maintainer of the package; please add the epel-packagers-sig group through https://src.fedoraproject.org/rpms/python-itsdangerous/addgroup and grant it commit access, or collaborator access on epel* branches. I would also be happy to be a co-maintainer (FAS: tdawson). Please add me through https://src.fedoraproject.org/rpms/python-itsdangerous/adduser
FEDORA-EPEL-2022-fcc9a7e1fe has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-fcc9a7e1fe
FEDORA-EPEL-2022-fcc9a7e1fe has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-fcc9a7e1fe See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-fcc9a7e1fe has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.