epel-announce

epel-announce@lists.fedoraproject.org

1 participants
196 discussions

Updating uv from 0.6.17 to 0.7.x in all Fedora releases and in EPEL10 leading branch
by Ben Beasley 11 May '25

11 May '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 0

Updating uv from 0.5.31 to 0.6.3 in EPEL10, with some breaking changes
by Ben Beasley 10 Mar '25

10 Mar '25

I have just issued updates for the Python package and project manager uv, from version 0.5.31 to version 0.6.3, in both EPEL10 branches (10.0 and 10.1)[1][2]. This package follows semantic versioning[3], and there are a few breaking changes from 0.5.x to 0.6.x. This update therefore follows the policy for incompatible upgrades[4] and has obtained the approval of the EPEL steering committee[5]. The developers of uv have been very strict about defining and tracking potential breaking changes, and it is likely that most users will not need to change anything at all. Upstream writes: There have been 31 releases and 1135 pull requests since 0.5.0, our last release with breaking changes. As before, 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 upstream changelogs for the 0.6.0 release contain a complete, detailed list of breaking changes and their possible implications for uv users[6]. By policy, these updates will remain in testing for at least one week regardless of karma, and I will send a follow-up announcement when I manually push them to stable. [1] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-978102e56a [2] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-67e00f28cd [3] https://semver.org/ [4] https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/ [5] https://pagure.io/epel/issue/317 [6] https://github.com/astral-sh/uv/blob/0.6.3/CHANGELOG.md#breaking-changes

1 1

EPEL 10.0 mass branching
by Carl George 18 Feb '25

18 Feb '25

Hello EPEL packagers, Later today (2025-02-18), Release Engineering will branch epel10.0 from epel10, in accordance with our overall branching strategy for EPEL 10. https://docs.fedoraproject.org/en-US/epel/branches/#_epel_10 During the branching, we will temporarily disable builds to the epel10-candidate target, which is used when you run `fedpkg build` from the epel10 branch. If you are trying to create a build and receive an error about a target not existing, please try again later in the day. Because this is the first time we are doing an EPEL mass branching, we don't know precisely how long it will take or how long we will need to disable the builds for. Thanks in advance for your patience. -- Carl George

1 1

Re: [EPEL-devel] Planning to retire yt-dlp in epel9
by Maxwell G 20 Jan '25

20 Jan '25

yt-dlp has been retired in epel9. On 1/6/25 3:04 PM, Maxwell G wrote: > Hi everyone, > > > I plan to retire yt-dlp in epel9 in two weeks. It is currently stuck at > an old version due to stable (i.e., outdated) Python libraries in (EP)EL > 9. I envision that keeping up with future yt-dlp update will be > infeasible due to library incompatibilities. Having an old version of > yt-dlp is not very useful, as it needs regular updates to remain > compatible with code changes in the various video platforms that it > interfaces with. For the same reason, I also do not plan to branch the > package for epel10. > > > Users are recommended to install yt-dlp using pipx, which is available > in both EPEL 9 and EPEL 10. > > > Thanks, > > Maxwell > >

1 0

EPEL 10 is now available
by Carl George 12 Dec '24

12 Dec '24

On behalf of the EPEL Steering Committee, I’m happy to announce the availability of EPEL 10. EPEL 10 already contains over 10,000 packages, built from over 3,600 source packages. This is a result of the hard work of over 150 Fedora package maintainers. You can read more about this on the Fedora Community Blog. https://communityblog.fedoraproject.org/epel-10-is-now-available/ -- Carl George

1 0

Incompatible update: dav1d 1.2.1 -> 1.5.0
by Fabio Valentini 19 Nov '24

19 Nov '24

Hi all, EPEL Incompatible updates policy exception ticket: https://pagure.io/epel/issue/299 The update for dav1d 1.5.0 and all necessary package rebuilds will be in "testing" soon: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-398707b664 No actions are necessary to keep using dav1d or any dependent packages - other than applying the linked update. Only software not shipped by EPEL or self-compiled programs that link with dav1d might need to be rebuilt. Fabio

1 1

ABI-incompatible update of re2 in EPEL10
by Ben Beasley 17 Oct '24

17 Oct '24

As previously discussed on the epel-devel list[1] and approved by the EPEL Steering Committee[2], I am preparing to update the re2 package in EPEL10 from version 20220601 to version 20240702[3]. In addition to two years of assorted bugfixes, which are mostly only documented in the commit messages[4], this update will allow us to ship the maintained, official Python bindings[5] as a python3-google-re2 subpackage. Since EPEL10 has not yet officially launched, there should be no impact to end users. However, if you were already testing your software with the re2 package in EPEL10, you will need to rebuild it due to the ABI changes and the SONAME version bump from 9 to 11. I am not aware of significant API changes. When I originally proposed this update, re2 was still a leaf package in EPEL10. In the last few days, grpc and libarrow were branched and built, and both packages will need to be rebuilt as part of the update. I will coordinate these rebuilds in side tag epel10.0-build-side-98656. Since EPEL10 is still in a Rawhide-like state without updates-testing, the testing period normally prescribed for incompatible updates in EPEL will not be possible; this email serves as the sole announcement for the update, and it will be pushed to stable as soon as the builds are all finished. – Ben Beasley (FAS: music) [1] https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraprojec… [2] https://pagure.io/epel/issue/297 [3] https://src.fedoraproject.org/rpms/re2/pull-request/9 [4] https://github.com/google/re2/commits/2024-07-02 [5] https://pypi.org/project/google-re2/

1 0

(new date) Re: EPEL-8 upgrade Clamav from 0.103.11 to 1.0.x LTS
by Sérgio Basto 03 Sep '24

03 Sep '24

Hi, Clamav upgrade will be pushed to updates tommorow, September 4, 2024 Please check if any 3rd party package depends on libclamav.so.9. if yes, it will have to be rebuilt Best regards, On Sat, 2024-07-27 at 14:35 +0100, Sérgio Basto wrote: > Hi, > > As many users requested support for clamav 1.0 LTS , and as clamav > 0.103 goes EOL (Sep-14 2024) > > To fulfill the "EPEL Incompatible upgrades policy" process [1], > we announce that Clamav 1.0.x LTS is on epel-testing for more than 4 > weeks and will lands on EPEL 8 updates stable in one week or so. > > This update changes from libclamav.so.9 to libclamav.so.11. It will > require rebuilding c-icap-modules and librpminspect. > > Happy hacking > > [1] > https://pagure.io/epel/issue/282 > > -- Sérgio M. B.

1 0

(new date) Re: EPEL-8 upgrade Clamav from 0.103.11 to 1.0.x LTS
by sergio＠serjux.com 03 Sep '24

03 Sep '24

The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list.

1 0

Re: EPEL-8 upgrade Clamav from 0.103.11 to 1.0.x LTS
by sergio＠serjux.com 30 Aug '24

30 Aug '24

The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

epel-announce