Bug 2369001 - Please branch and build python-apt in epel10
Summary: Please branch and build python-apt in epel10
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: 2369005
Blocks: EPELPackagersSIG
TreeView+ depends on / blocked
 
Reported: 2025-05-28 16:33 UTC by Jonathan Wright
Modified: 2026-03-24 02:04 UTC (History)
4 users (show)

Fixed In Version: python-apt-3.1.0-2.el10_2 python-apt-3.1.0-2.el10_3
Clone Of:
Environment:
Last Closed: 2026-03-24 02:03:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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

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

Comment 1 Javier Hernández 2025-06-18 10:14:25 UTC
Any updates on this? I'm working in planning the upgrade of some of our internal services to AlmaLinux 10 and we are missing python-apt.

Comment 2 David Auer 2025-11-17 18:24:59 UTC
python-distutils-extra is now in testing for epel10.2 it should land in stable in a week.

fedpkg --release epel10 mockbuild --enablerepo epel-testing
[...]
No matching package to install: 'apt-devel >= 2.0.0'


My mock build of apt completed without issues, I don't see any further obstacles, you just need someone with access to the apt repository to branch and build apt for epel:

fedpkg --release epel10 mockbuild --enablerepo epel-testing
[...]
Wrote: /builddir/build/RPMS/apt-devel-3.1.8-1.el10.x86_64.rpm
[...]
Finish: rpmbuild apt-3.1.8-1.el10_2.src.rpm
Finish: build phase for apt-3.1.8-1.el10_2.src.rpm
INFO: Done(/home/da/fedora-scm/tmp/apt/apt-3.1.8-1.el10_2.src.rpm) Config(epel-10-x86_64) 6 minutes 6 seconds
INFO: Results and/or logs in: /home/da/fedora-scm/tmp/apt/results_apt/3.1.8/1.el10_2
INFO: Cleaning up build root ('cleanup_on_success=True')
Start: clean chroot
Finish: clean chroot
Finish: run

Comment 3 Terje Rosten 2026-02-16 20:55:08 UTC
apt is coming to epel10 soon: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-a378a98086

python-apt will follow I hope

Comment 4 Terje Rosten 2026-03-15 15:27:17 UTC
What epel10 branches are wanted? 

Branch 10.1 seems to be missing python-distutils-extra package, causing build break. In 10.2 and 10.3 package build fine now.

Comment 5 Fedora Update System 2026-03-15 17:34:22 UTC
FEDORA-EPEL-2026-3c44b28579 (python-apt-3.1.0-2.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-3c44b28579

Comment 6 Fedora Update System 2026-03-16 02:02:47 UTC
FEDORA-EPEL-2026-3c44b28579 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-2026-3c44b28579

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

Comment 7 Fedora Update System 2026-03-16 02:04:58 UTC
FEDORA-EPEL-2026-3a57d72951 has been pushed to the Fedora EPEL 10.3 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-3a57d72951

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

Comment 8 Fedora Update System 2026-03-24 02:03:01 UTC
FEDORA-EPEL-2026-3c44b28579 (python-apt-3.1.0-2.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 9 Fedora Update System 2026-03-24 02:04:54 UTC
FEDORA-EPEL-2026-3a57d72951 (python-apt-3.1.0-2.el10_3) has been pushed to the Fedora EPEL 10.3 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.