epel-announce July 2025

epel-announce@lists.fedoraproject.org

2 participants
3 discussions

EPEL-ANNOUNCEUpdating uv from 0.6.17 to 0.7.x in all Fedora releases and in EPEL10 leading branch
by Ben Beasley 09 Aug '25

09 Aug '25

In one week, 2025-05-18, or slightly later, I plan to update the uv package from 0.6.17 to 0.7.3 or a later 0.7.x release[1] in Fedora Rawhide, 42, and 41. (Fedora 40 will have reached its end-of-life by then.) I also plan to ship the same update to the EPEL10 leading branch, currently EPEL 10.1. In upstream’s words, “This release contains various changes that improve correctness and user experience, but could break some workflows; many changes have been marked as breaking out of an abundance of caution. We expect most users to be able to upgrade without making changes.” The exact changes are documented in the release notes for 0.7.0[2]. For stable releases Fedora 42 and 41, this update is permitted under a permanent exception to the Updates Policy[3]; for the EPEL10 leading branch, it is permitted under a semi-permanent exception for versions up to 1.0[4]. For EPEL “stable” branches (epel10.0), current policy does not allow SemVer-breaking updates of uv or of the library-only Rust packages upon which it depends, so uv 0.6.17[5] will be the final uv release in EPEL10.0 for the foreseeable future. Four packages in Fedora now depend on uv: fawltydeps, hatch, python-build, and python-tox-uv. A quick impact check using local mock builds did not reveal any incompatibilities. Additionally, a new dependency from translate-toolkit was found to be spurious, and I opened a PR to remove it[6]. I will also update python-uv-build[7], the new uv-based build backend, to the same version as uv. This package is still Rawhide-only for now. As long as nothing yet depends on it, I prefer to allow a little time for the ecosystem to work out any kinks before locking us into a particular minor release in stable branches. – Ben Beasley (FAS: music) [1] https://src.fedoraproject.org/rpms/uv/pull-request/54 [2] https://github.com/astral-sh/uv/releases/tag/0.7.0 [3] https://pagure.io/fesco/issue/3262 [4] https://pagure.io/epel/issue/317#comment-958123 [5] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-445cab085a [6] https://src.fedoraproject.org/rpms/translate-toolkit/pull-request/13 [7] https://src.fedoraproject.org/rpms/python-uv-build/pull-request/6

1 4

EPEL-ANNOUNCEnetplan Incompatible Upgrade in EPEL 9
by Jonathan Wright 06 Aug '25

06 Aug '25

The update contains a soname bump but no known breaking changes - but many bug fixes. I've not found anything in EPEL that relies on or builds against netplan. In its current state, netplan in EPEL9 is pretty unmaintainable as upstream has diverged (and matured) a lot since the release we're on (0.105). In order to get it to a more maintainable state I'd like to get it updated to the current release (1.1.2). netplan moves much slower these days and it's a much more mature project and this update should set us up well for the rest of the EL9 lifecycle. I'll push this to stable next week per the incompatible updates policy <https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades…> . -- Jonathan Wright AlmaLinux OS Foundation Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan>

1 1

EPEL-ANNOUNCEUpdating uv from 0.7.22 to 0.8.x in all Fedora releases and in EPEL10 leading branch
by Ben Beasley 22 Jul '25

22 Jul '25

In one week, 2025-07-29, or slightly later, I plan to update the uv package from 0.7.22 to 0.8.0 or a later 0.8.x release[1] in Fedora Rawhide, 42, and 41. I also plan to ship the same update to the EPEL10 leading branch, currently EPEL 10.1. In upstream’s words, “Since we released uv 0.7.0 in April, we've accumulated various changes that improve correctness and user experience, but could break some workflows. This release contains those changes; many have been marked as breaking out of an abundance of caution. We expect most users to be able to upgrade without making changes.” The exact changes are documented in the release notes for 0.8.0[2]. For stable releases Fedora 42 and 41, this update is permitted under a permanent exception to the Updates Policy[3]; for the EPEL10 leading branch, it is permitted under a semi-permanent exception for versions up to 1.0[4]. For EPEL “stable” branches (epel10.0), current policy does not allow SemVer-breaking updates of uv or of the library-only Rust packages upon which it depends, so uv 0.6.17 will continue to be the final uv release in EPEL10.0 for the foreseeable future. Four packages in Fedora now depend on uv: fawltydeps, hatch, python-build, and python-tox-uv. A quick impact check using local mock builds did not reveal any incompatibilities. I will also update python-uv-build[5], the new uv-based build backend, to the same version as uv. This package is still Rawhide-only for now. As long as nothing yet depends on it, I prefer to allow a little time for the ecosystem to work out any kinks before locking us into a particular minor release in stable branches. – Ben Beasley (FAS: music) [1] https://src.fedoraproject.org/rpms/uv/pull-request/67 [2] https://github.com/astral-sh/uv/releases/tag/0.8.0 [3] https://pagure.io/fesco/issue/3262 [4] https://pagure.io/epel/issue/317#comment-958123 [5] https://src.fedoraproject.org/rpms/python-uv-build/pull-request/6

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

epel-announce July 2025