Bug 2335575
Summary: | Please branch and build python-sphinx-autobuild in epel10 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Romain Geissler <romain.geissler> |
Component: | python-sphinx-autobuild | Assignee: | Jerry James <loganjerry> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | code, kkeithle, loganjerry |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | python-sphinx-autobuild-2024.10.03-2.el10_1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2025-04-03 02:57:52 UTC | Type: | --- |
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: | 2335460, 2335577, 2335583 | ||
Bug Blocks: | 2336610, 2350146 |
Description
Romain Geissler
2025-01-04 16:27:27 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. 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. This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42. 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). 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. 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 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. 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. |