Bug 2343587 - Please build python-gitlab for EPEL10
Summary: Please build python-gitlab for EPEL10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-gitlab
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Steve Traylen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2321255 2334951 2345825 2345855
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-03 19:06 UTC by Steve Traylen
Modified: 2025-04-30 01:56 UTC (History)
1 user (show)

Fixed In Version: python-gitlab-5.6.0-3.el10_1
Clone Of:
Environment:
Last Closed: 2025-04-30 01:56:35 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Steve Traylen 2025-02-03 19:06:53 UTC 
Version 4 of python gitlab in rawhide depends on 

* python-responses Bug #2321255
Comment 1 Steve Traylen 2025-02-03 19:13:15 UTC 
Note that gitlab version 5 is currently blocked in rawhide on python-gql bug #2315554. 

If gitlab5 makes it into rawhide then gitlab 5 in epel 10 will also block on  python-vcrpy bug #2333516
Comment 2 Steve Traylen 2025-02-14 21:15:29 UTC 
EPEL 10 branch of python-gql bug # 2345825
Comment 3 Fedora Update System 2025-04-21 11:06:00 UTC 
FEDORA-EPEL-2025-e40f7e2af0 (python-gitlab-5.6.0-3.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-e40f7e2af0
Comment 4 Fedora Update System 2025-04-22 02:37:57 UTC 
FEDORA-EPEL-2025-e40f7e2af0 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-e40f7e2af0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Fedora Update System 2025-04-30 01:56:35 UTC 
FEDORA-EPEL-2025-e40f7e2af0 (python-gitlab-5.6.0-3.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.