Bug 2088012 - [python-sphinxcontrib-log-cabinet][epel]: please build python-sphinxcontrib-log-cabinet in epel9
Summary: [python-sphinxcontrib-log-cabinet][epel]: please build python-sphinxcontrib-l...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-sphinxcontrib-log-cabinet
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Thomas Moschny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-18 16:23 UTC by Kaleb KEITHLEY
Modified: 2022-06-17 00:33 UTC (History)
3 users (show)

Fixed In Version: python-sphinxcontrib-log-cabinet-1.0.1-9.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-17 00:33:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kaleb KEITHLEY 2022-05-18 16:23:23 UTC
Description of problem:

python-sphinxcontrib-log-cabinet is a BR for python-werkzeug->python-flask->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-sphinxcontrib-log-cabinet, 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):

python-sphinxcontrib-log-cabinet-1.0.1

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=87207280)

If you don't wish to build python-sphinxcontrib-log-cabinet 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:15:55 UTC
I am the package maintainer for grpc, python-xds-protos, and python-opentelemetry. It may 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 Ulrik Haugen 2022-05-30 13:28:29 UTC
I'd like to have it as it is a requirement for python-flask for which i have opened bz 2089764.

Comment 3 Fedora Update System 2022-06-08 08:09:38 UTC
FEDORA-EPEL-2022-697ec3be12 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-697ec3be12

Comment 4 Fedora Update System 2022-06-09 00:23:12 UTC
FEDORA-EPEL-2022-697ec3be12 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-697ec3be12

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

Comment 5 Fedora Update System 2022-06-17 00:33:07 UTC
FEDORA-EPEL-2022-697ec3be12 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.


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