Bug 2335575 - Please branch and build python-sphinx-autobuild in epel10
Summary: Please branch and build python-sphinx-autobuild in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-sphinx-autobuild
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jerry James
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2335460 2335577 2335583
Blocks: 2336610 2350146
TreeView+ depends on / blocked
 
Reported: 2025-01-04 16:27 UTC by Romain Geissler
Modified: 2025-04-03 02:57 UTC (History)
3 users (show)

Fixed In Version: python-sphinx-autobuild-2024.10.03-2.el10_1
Clone Of:
Environment:
Last Closed: 2025-04-03 02:57:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Romain Geissler 2025-01-04 16:27:27 UTC
Hi,

Please branch and build python-sphinx-autobuild in epel10.

I know you don't maintain EPEL branches yourself, so I am opening this to track dependencies for now, and later if I enter the packager group I will propose to become a co-maintainer of the EPEL branches to have it done.

Cheers,
Romain

Reproducible: Always

Comment 1 Ben Beasley 2025-01-04 18:18:31 UTC
Some of the dependencies here have pretty significant dependency trees of their own.

There is nothing *wrong* with branching python-sphinx-autobuild for EPEL10, but do you really need it? Or is it just a documentation dependency for the package you actually want? In most cases, disabling generated documentation in the EPEL10 branch makes more sense than branching and maintaining dozens of packages just to build a manual.

Granted, many of these packages are likely to find their way into EPEL10 anyway, but a lot of these “web” packages will become permanently outdated (because they regularly break API and can’t be updated compatibly) almost as soon as they are branched, so it’s worth thinking a little bit about when and whether to bring them to EPEL10.

Comment 2 Romain Geissler 2025-01-04 23:20:31 UTC
Right, I should have figured this out by myself when seeing the number of new EPEL request I was creating, sorry for that.

I did open this https://src.fedoraproject.org/rpms/python-pygraphviz/pull-request/9 to avoid this need for doc packages in my case.

Comment 3 Aoife Moloney 2025-02-26 13:21:08 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 4 Kaleb KEITHLEY 2025-03-25 11:41:52 UTC
scratch build https://koji.fedoraproject.org/koji/taskinfo?taskID=130734168

Comment 5 Kaleb KEITHLEY 2025-03-25 11:42:27 UTC
Will you be able to branch and build <package> in epel10?
I would be happy to be a co-maintainer if you do not wish
to build it on epel10 (FAS: kkeithle).

Comment 6 Jerry James 2025-03-25 14:17:18 UTC
Sorry, Kaleb.  The last comment from Romain indicated this was no longer needed, and I didn't notice you added a blocker bug.  I've added you as maintainer now.

Comment 7 Fedora Update System 2025-03-25 14:39:47 UTC
FEDORA-EPEL-2025-7dbed3b239 (python-sphinx-autobuild-2024.10.03-2.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7dbed3b239

Comment 8 Fedora Update System 2025-03-26 02:16:17 UTC
FEDORA-EPEL-2025-7dbed3b239 has been pushed to the Fedora EPEL 10.1 testing repository.

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

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

Comment 9 Fedora Update System 2025-04-03 02:57:52 UTC
FEDORA-EPEL-2025-7dbed3b239 (python-sphinx-autobuild-2024.10.03-2.el10_1) has been pushed to the Fedora EPEL 10.1 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.