Bug 2369000 - Please branch and build python-apt in epel10.1
Summary: Please branch and build python-apt in epel10.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-apt
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Terje Rosten
QA Contact:
URL:
Whiteboard:
Depends On: 2369004 2447737
Blocks: EPELPackagersSIG
TreeView+ depends on / blocked
 
Reported: 2025-05-28 16:33 UTC by Jonathan Wright
Modified: 2026-04-02 01:54 UTC (History)
2 users (show)

Fixed In Version: python-apt-3.1.0-2.el10_1
Clone Of:
Environment:
Last Closed: 2026-04-02 01:54:29 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Jonathan Wright 2025-05-28 16:33:39 UTC 
Please branch and build python-apt in epel10.0.

If you do not wish to maintain python-apt in epel10.0,
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: jonathanspw);
please add me through https://src.fedoraproject.org/rpms/python-apt/adduser
Comment 1 Terje Rosten 2026-03-15 17:28:47 UTC 
epel10.0 is frozen, moving request to epel10.1
Comment 2 Fedora Update System 2026-03-24 18:45:25 UTC 
FEDORA-EPEL-2026-7f15c367e3 (python-apt-3.1.0-2.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-7f15c367e3
Comment 3 Fedora Update System 2026-03-25 02:23:24 UTC 
FEDORA-EPEL-2026-7f15c367e3 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-2026-7f15c367e3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Fedora Update System 2026-04-02 01:54:29 UTC 
FEDORA-EPEL-2026-7f15c367e3 (python-apt-3.1.0-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.
Note You need to log in before you can comment on or make changes to this bug.