Bug 2324160 - Please branch and build python-cherrypy in epel10
Summary: Please branch and build python-cherrypy in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-cherrypy
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Radez
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2315446 2324169 2324170
Blocks: EPELPackagersSIG 2338452
TreeView+ depends on / blocked
 
Reported: 2024-11-06 12:25 UTC by Kaleb KEITHLEY
Modified: 2025-01-22 02:07 UTC (History)
7 users (show)

Fixed In Version: python-cherrypy-18.10.0-4.el10_0
Clone Of:
Environment:
Last Closed: 2025-01-22 02:07:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kaleb KEITHLEY 2024-11-06 12:25:16 UTC
Please branch and build python-cherrypy in epel10.

If you do not wish to maintain python-cherrypy in epel10,
or do not think you will be able to do this in a timely manner,
the EPEL Packagers SIG would be happy to be a co-maintainer of the package;
please add the epel-packagers-sig group through
https://src.fedoraproject.org/rpms/python-cherrypy/addgroup
and grant it commit access, or collaborator access on epel* branches.

I would also be happy to be a co-maintainer (FAS: kkeithle);
please add me through https://src.fedoraproject.org/rpms/python-cherrypy/adduser

Comment 1 Kaleb KEITHLEY 2024-11-06 12:31:38 UTC
this is a runtime requirement for Ceph

Comment 2 Dan Radez 2024-11-06 13:22:21 UTC
Could you help make sure there are BZs existing and set as blocking this bug for the missing dependencies of this package?
python3-zc-lockfile
python3dist(cheroot)
python3dist(jaraco-collections)
python3dist(pytest-cov)

Comment 3 Kaleb KEITHLEY 2024-11-06 15:21:29 UTC
(In reply to Dan Radez from comment #2)
> Could you help make sure there are BZs existing and set as blocking this bug
> for the missing dependencies of this package?
> python3-zc-lockfile
> python3dist(cheroot)
> python3dist(jaraco-collections)
> python3dist(pytest-cov)

They are (already) in the Depends On:

Comment 4 Dan Radez 2024-11-06 19:32:27 UTC
(In reply to Kaleb KEITHLEY from comment #3)
> (In reply to Dan Radez from comment #2)
> > Could you help make sure there are BZs existing and set as blocking this bug
> > for the missing dependencies of this package?
> > python3-zc-lockfile
> > python3dist(cheroot)
> > python3dist(jaraco-collections)
> > python3dist(pytest-cov)
> 
> They are (already) in the Depends On:

That's excellent. Thank you for filing those.

Comment 5 Orion Poplawski 2024-11-11 15:43:58 UTC
I'll note that Fedora packages really shouldn't depend on pytest-cov - coverage tests should be disabled for Fedora packages.

Comment 6 Kaleb KEITHLEY 2024-11-11 18:21:08 UTC
(In reply to Kaleb KEITHLEY from comment #0)> 
> I would also be happy to be a co-maintainer (FAS: kkeithle);
> please add me through
> https://src.fedoraproject.org/rpms/python-cherrypy/adduser

s/co-maintainer/collaborator or committer/

Comment 7 Kaleb KEITHLEY 2025-01-20 16:04:03 UTC
bump

Comment 8 Kaleb KEITHLEY 2025-01-20 16:21:02 UTC
scratch build https://koji.fedoraproject.org/koji/taskinfo?taskID=128214605

Comment 9 Fedora Update System 2025-01-20 19:24:03 UTC
FEDORA-EPEL-2025-e527ee17f6 (python-cherrypy-18.10.0-4.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-e527ee17f6

Comment 10 Fedora Update System 2025-01-21 03:55:30 UTC
FEDORA-EPEL-2025-e527ee17f6 has been pushed to the Fedora EPEL 10.0 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-e527ee17f6

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

Comment 11 Fedora Update System 2025-01-22 02:07:35 UTC
FEDORA-EPEL-2025-e527ee17f6 (python-cherrypy-18.10.0-4.el10_0) has been pushed to the Fedora EPEL 10.0 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.