ffmpeg in EPEL 9 Next (for CentOS Stream) is being updated from 5 to 7.
There is a compat package (ffmpeg5) that will have the libraries and
headers for ffmpeg5, due to some packages not being able to work with
ffmpeg7.
It will be in testing for a week before going out.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2026-fa14ff518d
The majority of packages just needed a rebuild, but some needed a patch or
an update.
The following packages are part of the update.
ffmpeg-7.1.5-2.el9.next
ffmpeg5-5.1.9-2.el9.next
audacious-plugins-4.4.2-1.el9.next
baresip-4.9.0-1.el9.next
chromium-151.0.7922.137-1.el9.next
digikam-8.5.0-4.el9.next
ffmpegthumbs-22.12.0-1.el9.next
guacamole-server-1.6.0-1.el9.next
guvcview-2.2.2-2.el9.next
haruna-0.12.3-2.el9.next
k3b-23.08.5-2.el9.next
kf5-kfilemetadata-5.116.0-2.el9.next
kpipewire-5.27.12-2.el9.next
libavif-1.1.1-2.el9.next
libopenshot-0.3.3-1.el9.next
minidlna-1.3.3-13.el9.next
mlt-7.24.0-1.el9.next
mpv-0.39.0-4.el9.next
neatvnc-0.9.0-1.el9.next
obs-studio-30.0.0-2.1.el9.next
qt6-qtmultimedia-6.6.2-2.el9.next
svt-av1-2.3.0-2.el9.next
unpaper-7.0.0-6.el9.next
vlc-3.0.23-2.el9.next
xine-lib-1.2.13-17.el9.next
xpra-5.0.10-3.el9.next
If anyone finds any problems with these, or related packages, please let me
know as soon as possible so we can get things fixed.
Troy
Howdy EPEL packagers,
Release Engineering will branch epel10.3 from epel10 on 2026-08-24
(one week from today), 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.
We will send announcements when the branching is starting and when it
is completed.
--
Carl George
This update is now on its way to the testing repositories for the EPEL10
leading branch (10.3)[1]. Most users should not need to change anything,
but see [2] and [3] as well as the email quoted below. This update also
brings python-uv-build to EPEL10.
[1] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-3661338d0d
[2]
https://github.com/astral-sh/uv/blob/0.12.3/CHANGELOG.md#breaking-changes
[3] https://astral.sh/blog/ruff-v0.16.0
On 05/08/2026 10:58 am, Ben Beasley wrote:
> In approximately one week, 2026-08-12, I plan to update the uv package
> to version 0.12.x in stable branches F44 and F43. This includes some
> relatively minor breaking changes[1]; most users will not need to
> change anything. Similarly, I will update ruff to 0.16.x, also with
> minor breaking changes[2], and ty to at least 0.0.66. These updates
> are permitted under existing permanent exceptions to the Updates
> Policy in Fedora[3]. The uv updates are already in Rawhide; the
> updates for ruff, ty, and their dependencies will be built
> simultaneously in Rawhide and in stable branches.
>
> At around the same time, I will update uv to 0.12.x and ruff to 0.16.x
> in the EPEL10 leading branch (currently EPEL10.3), as allowed by
> corresponding exceptions for EPEL[4], limited to leading branches and
> to versions through 1.0. No further approvals are needed for these
> updates, but I do plan to follow the usual announcement and testing
> procedures for incompatible upgrades in EPEL[5]. I will also upgrade
> python-uv-build to 0.12.x. This package doesn’t have an Updates Policy
> exception, but upstream has confirmed that 0.12.0 has no breaking
> changes from 0.11.0, and the apparent SemVer break is only to keep in
> lockstep with uv, so it’s safe to ship in stable releases as long as I
> ensure that any conflicting upper bounds in dependencies on uv-build
> are resolved, as is already done in Rawhide.
>
> For the first time, I will also branch python-uv-build into EPEL10[6].
> The ty package remains Fedora-only for now; I am tentatively planning
> to wait for a 0.1.0 release before branching it to EPEL10.
>
> All of these updates have been (or are being) test-built in COPR[7],
> and I will use the coming week to finish fully impact-checking them.
>
> [1]
> https://github.com/astral-sh/uv/blob/0.12.1/CHANGELOG.md#breaking-changes
>
> [2] https://astral.sh/blog/ruff-v0.16.0
>
> [3] https://pagure.io/fesco/issue/3262,
> https://pagure.io/fesco/issue/3197, https://pagure.io/fesco/issue/3564
>
> [4] https://pagure.io/epel/issue/317, https://pagure.io/epel/issue/350
>
> [5]
> https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades…
>
> [6] https://bugzilla.redhat.com/show_bug.cgi?id=2501300
>
> [7] https://copr.fedorainfracloud.org/coprs/music/uv/packages/