Bug 2348676

Summary: Please branch and build python-pyforgejo in epel10
Product: [Fedora] Fedora Reporter: mmassari
Component: python-pyforgejoAssignee: Gwyn Ciesla <gwync>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: gwync
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: python-pyforgejo-2.0.0-1.el10_1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-03-09 03:00: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: 2334951    
Bug Blocks:    

Description mmassari 2025-02-27 08:13:57 UTC
Please branch and build python-pyforgejo in epel10.
packit will soon use it.

If you do not wish to maintain python-pyforgejo 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 mmassari;
please add me through https://src.fedoraproject.org/rpms/<package>/adduser

Thank you

Reproducible: Always

Comment 1 Fedora Update System 2025-02-28 16:25:15 UTC
FEDORA-EPEL-2025-7382ebb30b (python-pyforgejo-2.0.0-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7382ebb30b

Comment 2 Fedora Update System 2025-03-01 02:09:54 UTC
FEDORA-EPEL-2025-7382ebb30b 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-7382ebb30b

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

Comment 3 Fedora Update System 2025-03-09 03:00:52 UTC
FEDORA-EPEL-2025-7382ebb30b (python-pyforgejo-2.0.0-1.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.