Bug 2390254 - Please branch and build python-sphinxcontrib-trio in epel10
Summary: Please branch and build python-sphinxcontrib-trio in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-sphinxcontrib-trio
Version: epel10
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: 2025-08-22 04:51 UTC by fedepell
Modified: 2025-09-10 02:15 UTC (History)
2 users (show)

Fixed In Version: python-sphinxcontrib-trio-1.1.2-25.el10_2 python-sphinxcontrib-trio-1.1.2-25.el10_0 python-sphinxcontrib-trio-1.1.2-25.el10_1
Clone Of:
Environment:
Last Closed: 2025-09-10 00:41:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description fedepell 2025-08-22 04:51:17 UTC
Would it be possible to branch and build python-sphinxcontrib-trio in EPEL10?

I've done some tests locally on 10 and it should be straight forward, a mockbuild of current rawhide succeeded without changes for epel10.


If you do not wish to maintain python-sphinxcontrib-trio in epel10,
or do not think you will be able to do this in a timely manner,
I would be happy to be a co-maintainer of the package (FAS fedepell);
please add me through https://src.fedoraproject.org/rpms/python-sphinxcontrib-trio/adduser

Many thanks!
F.

Comment 1 Fedora Update System 2025-09-01 08:02:56 UTC
FEDORA-EPEL-2025-d5fea8aa24 (python-sphinxcontrib-trio-1.1.2-25.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-d5fea8aa24

Comment 2 Fedora Update System 2025-09-01 08:03:04 UTC
FEDORA-EPEL-2025-a9dcbe3f69 (python-sphinxcontrib-trio-1.1.2-25.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a9dcbe3f69

Comment 3 Fedora Update System 2025-09-01 08:03:04 UTC
FEDORA-EPEL-2025-389f9bd854 (python-sphinxcontrib-trio-1.1.2-25.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-389f9bd854

Comment 4 Fedora Update System 2025-09-02 00:56:54 UTC
FEDORA-EPEL-2025-389f9bd854 has been pushed to the Fedora EPEL 10.2 testing repository.

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

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

Comment 5 Fedora Update System 2025-09-02 01:52:57 UTC
FEDORA-EPEL-2025-d5fea8aa24 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-d5fea8aa24

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

Comment 6 Fedora Update System 2025-09-02 01:58:01 UTC
FEDORA-EPEL-2025-a9dcbe3f69 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-a9dcbe3f69

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

Comment 7 Fedora Update System 2025-09-10 00:41:59 UTC
FEDORA-EPEL-2025-389f9bd854 (python-sphinxcontrib-trio-1.1.2-25.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2025-09-10 02:12:27 UTC
FEDORA-EPEL-2025-d5fea8aa24 (python-sphinxcontrib-trio-1.1.2-25.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.

Comment 9 Fedora Update System 2025-09-10 02:15:55 UTC
FEDORA-EPEL-2025-a9dcbe3f69 (python-sphinxcontrib-trio-1.1.2-25.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.