Bug 2089385

Summary:	[python-constantly][epel]: please build python-constantly in epel9
Product:	[Fedora] Fedora	Reporter:	Kaleb KEITHLEY <kkeithle>
Component:	python-constantly	Assignee:	Robert-André Mauchin 🐧 <eclipseo>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	37	CC:	code, eclipseo, nnavneet1001, python-sig
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-constantly-15.1.0-25.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-10-20 16:07:01 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:
Bug Depends On:
Bug Blocks:	2049035

Description Kaleb KEITHLEY 2022-05-23 14:35:30 UTC

Description of problem:

python-constantly 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-constantly, 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=87407408)

If you don't wish to build python-constantly 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 15:02:46 UTC

I am the package maintainer for grpc, python-xds-protos, and python-opentelemetry. It may or may not 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/

Comment 2 Ben Cotton 2022-08-09 13:16:51 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.

Comment 3 Michel Lind 2022-10-10 21:55:35 UTC

*** Bug 2082020 has been marked as a duplicate of this bug. ***

Comment 4 Fedora Update System 2022-10-11 16:23:57 UTC

FEDORA-EPEL-2022-6dbb62e269 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-6dbb62e269

Comment 5 Fedora Update System 2022-10-12 13:13:13 UTC

FEDORA-EPEL-2022-6dbb62e269 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-6dbb62e269

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2022-10-20 16:07:01 UTC

FEDORA-EPEL-2022-6dbb62e269 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.