Bug 2089367

Summary: [python-typing-extensions][epel]: please build python-typing-extensions in epel9
Product: [Fedora] Fedora Reporter: Kaleb KEITHLEY <kkeithle>
Component: python-typing-extensionsAssignee: Jonny Heggheim <hegjon>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: code, epel-packagers-sig, hegjon, mail, michel
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-23 14:23:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kaleb KEITHLEY 2022-05-23 14:05:50 UTC 
Description of problem:

python-typing-extensions is a BR for python-twisted->python-tblib->->python-python-django->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-typing-extenions, 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):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

It builds as is from the rawhide sources (https://koji.fedoraproject.org/koji/taskinfo?taskID=87406597)

If you don't wish to build python-typing-extensions 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
Comment 1 Jonny Heggheim 2022-05-23 14:23:05 UTC 

*** This bug has been marked as a duplicate of bug 2043761 ***