Fedora Account System
Red Hat Associate
Red Hat Customer
Many projects are switching to uv as the build system. So also EPEL needs the support for it. Reproducible: Always
As with uv, branching python-uv-build to EPEL9 is not possible unless maturin can be branched, which in turn would require someone to successfully prepare a working python-setuptools_rust package for EPEL9. See bug 2317152. I’m happy to work on branching python-uv-build and uv to EPEL9 if these prerequisites can be met. The python-setuptools_rust blocker has been known for years now, it’s not something I am prepared to invest a lot of time in solving, and nobody else has stepped up, so at this point I suspect that maturin-based packages are just not happening in EPEL9. For EPEL10, python-uv-build can be branched at any time, and this has been true for quite a while. The catch is that every minor-version update is potentially incompatible. (There are always potentially-breaking changes in a new uv minor release, but occasionally upstream declares that there aren’t any in uv-build.) While uv has an Updates Policy exception for the EPEL10 leading branch, python-uv-build doesn’t, and I don’t plan to request one since the packaged python-uv-build is useful primarily for building other packages (vs. uv which is useful primarily for interactive use by humans). So I can, for example, branch python-uv-build 0.11.28 right now, and then I can keep updating it until uv 0.12.0 comes out, at which point I will likely have to stop updating python-uv-build in EPEL 10 for the rest of the EPEL 10 lifecycle. I’ve therefore been stalling on branching python-uv-build until something actually needs it in order to try to get as mature a version of python-uv-build shipped as possible. What do you think? Is there something you are working on that really benefits from having this right away? Should we wait for 0.12.0, which is in planning, https://github.com/astral-sh/uv/milestone/13, but I am not sure quite when it will arrive?
Rawhide now has python-uv-build 0.12.1. I’m planning to branch it to EPEL10 at the same time I update uv, in roughly a week.
FEDORA-EPEL-2026-3661338d0d (python-cucumber-expressions-20.1.0-1.el10_3, python-uv-build-0.12.3-137.el10_3, and 13 more) has been submitted as an update to Fedora EPEL 10.3. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-3661338d0d
FEDORA-EPEL-2026-3661338d0d 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-3661338d0d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle. Changing version to 45.
FEDORA-EPEL-2026-3661338d0d (python-cucumber-expressions-20.1.0-1.el10_3, python-uv-build-0.12.3-137.el10_3, and 13 more) has been pushed to the Fedora EPEL 10.3 stable repository. If problem still persists, please make note of it in this bug report.