Bug 2089319

Summary: [python-mock][epel]: please build python-mock in epel9
Product: [Fedora] Fedora EPEL Reporter: Kaleb KEITHLEY <kkeithle>
Component: python-mockAssignee: Orphan Owner <extras-orphan>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: code, extras-orphan, mhroncok, python-sig, TicoTimo
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:55:54 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 12:35:35 UTC 
Description of problem:

python-mock is a BR for python-pymemcache->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-mock, 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 (see https://koji.fedoraproject.org/koji/taskinfo?taskID=87403079)


If you don't wish to build python-mock 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 Ben Beasley 2022-05-23 14:55:54 UTC 
Since python-mock has been deprecated since Fedora 34[1], it should not be branched for EPEL9. Instead, packages that still require it should be patched before branching.

In this specific case: I am the package maintainer for both grpc and python-opentelemetry. I am able to build python-opentelemetry for EPEL9 in a COPR[2] 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://fedoraproject.org/wiki/Changes/DeprecatePythonMock
[2] https://copr.fedorainfracloud.org/coprs/music/grpc-epel9/packages/
Comment 2 Miro Hrončok 2022-05-23 15:27:29 UTC 
Indeed.

https://src.fedoraproject.org/rpms/python-pymemcache/pull-request/6

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