Bug 2314525 - Please branch and build python-repoze-sphinx-autointerface in epel10
Summary: Please branch and build python-repoze-sphinx-autointerface in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-repoze-sphinx-autointerface
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kaleb KEITHLEY
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2311680
Blocks: EPELPackagersSIG 2314524 2339002
TreeView+ depends on / blocked
 
Reported: 2024-09-24 21:23 UTC by Michel Lind
Modified: 2025-01-20 14:21 UTC (History)
5 users (show)

Fixed In Version: python-repoze-sphinx-autointerface-1.0.0-0.el10_0
Clone Of:
Environment:
Last Closed: 2025-01-09 02:38:06 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Package Sources python-repoze-sphinx-autointerface pull-request 5 0 None None None 2024-09-24 22:14:34 UTC

Description Michel Lind 2024-09-24 21:23:38 UTC 
Please branch and build python-repoze-sphinx-autointerface in epel10.
Comment 1 Fedora Update System 2024-12-31 18:26:29 UTC 
FEDORA-EPEL-2024-66d362b6fa (python-repoze-sphinx-autointerface-1.0.0-0.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-66d362b6fa
Comment 2 Fedora Update System 2025-01-01 03:23:06 UTC 
FEDORA-EPEL-2024-66d362b6fa 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-2024-66d362b6fa

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 3 Fedora Update System 2025-01-09 02:38:06 UTC 
FEDORA-EPEL-2024-66d362b6fa (python-repoze-sphinx-autointerface-1.0.0-0.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.