Bug 2086874

Summary: [python-fasteners][epel]: please build python-fasterners in epel9
Product: [Fedora] Fedora Reporter: Kaleb KEITHLEY <kkeithle>
Component: python-fastenersAssignee: Matthias Runge <mrunge>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: code, fschwarz, mrunge, python-sig, thomas.moschny
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-16 17:54:57 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-16 17:49:01 UTC 
Description of problem:

python-fasternes is a BR for python-oauth2->grpc->libarrow, which in turn is a BR for 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-fasteners , 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 without any changes necessary from rawhide source. See See https://koji.fedoraproject.org/koji/taskinfo?taskID=87038113

If you don't wish to build glog in EPEL yourself, please add the epel-packagers-sig group as collabotor, or (less preferable) add me as a collaborator, just for EPEL9 builds.

Thanks
Comment 1 Kaleb KEITHLEY 2022-05-16 17:54:57 UTC 
already built in epel9
Comment 2 Ben Beasley 2022-05-16 18:30:04 UTC 
I just took over as primary maintainer on this package and completed the EPEL9 backport today. I’m interested in it specifically because of the dependency chain you mentioned. I maintain the grpc package and am trying to get it building in EPEL9.

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