Bug 2089367 - [python-typing-extensions][epel]: please build python-typing-extensions in epel9
Summary: [python-typing-extensions][epel]: please build python-typing-extensions in epel9
Keywords:
Status: CLOSED DUPLICATE of bug 2043761
Alias: None
Product: Fedora
Classification: Fedora
Component: python-typing-extensions
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jonny Heggheim
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-23 14:05 UTC by Kaleb KEITHLEY
Modified: 2022-05-23 14:23 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-05-23 14:23:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.