Bug 2047511 - Please branch and build python-sphinx-testing for EPEL 9
Summary: Please branch and build python-sphinx-testing for EPEL 9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-sphinx-testing
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Justin Caratzas
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2047509
TreeView+ depends on / blocked
 
Reported: 2022-01-27 23:43 UTC by Michel Lind
Modified: 2022-02-17 11:56 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-02-10 16:55:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Michel Lind 2022-01-27 23:43:19 UTC
Please branch and build python-sphinx-testing for EPEL 9 (it is a dependency for python-sphinx-removed-in, which is needed by python-pillow).

If you do not wish to maintain python-sphinx-testing epel9,
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 to
https://src.fedoraproject.org/rpms/python-sphinx-testing/settings#usersgroups-tab 
and grant it commit access, or collaborator access on epel* branches.

I'd be happy to comaintain too (FAS: salimma)

Comment 1 Jerry James 2022-01-27 23:48:28 UTC
Justin Caratzas <jcaratza> is managing the EPEL branch, I believe.  It makes sense to me to have you and epel-packagers-sig as maintainers as well, so I have added you, but maybe ping Justin to see if he has any plans for this package.

Comment 2 Justin Caratzas 2022-01-28 13:15:00 UTC
I can take care of it since I'm doing several packages today

Comment 4 Miro Hrončok 2022-02-17 11:56:06 UTC
I've just retired this package in Fedora 36+. You might want to do the same in EPEL 9. It is dead upstream. See https://src.fedoraproject.org/rpms/python-sphinx-removed-in/pull-request/4 which should be applicable to EPEL 9 as well.


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