Errors during update

Hi,

I’m new in this forum, so I can’t join for the moment files describing my problems.

I’ve installed Almalinux 10.0 KDE Plasma 6 months ago.

But now, I have a problem during last update.

last week, some packages essentially concerning qt6 on the epel repo don’t want to install.

I thought that epel repo wasn’t updated yet.

So, I waited one week.

And today, the problem persists.

my pc configuration :

Operating System: AlmaLinux 10.0
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.1
Kernel Version: 6.12.0-55.43.1.el10_0.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i7-12700
Memory: 15.1 Gio of RAM
Graphics Processor: Mesa Intel® UHD Graphics 770
Manufacturer: Dell Inc.
Product Name: OptiPlex 5000

dnf repolist
id du dépôt nom du dépôt
appstream AlmaLinux 10 - AppStream
baseos AlmaLinux 10 - BaseOS
crb AlmaLinux 10 - CRB
epel Extra Packages for Enterprise Linux 10 - x86_64
extras AlmaLinux 10 - Extras

dnf repolist all
id du dépôt nom du dépôt état
appstream AlmaLinux 10 - AppStream activé
appstream-debuginfo AlmaLinux 10 - AppStream - Debug désactivé
appstream-source AlmaLinux 10 - AppStream - Source désactivé
baseos AlmaLinux 10 - BaseOS activé
baseos-debuginfo AlmaLinux 10 - BaseOS - Debug désactivé
baseos-source AlmaLinux 10 - BaseOS - Source désactivé
crb AlmaLinux 10 - CRB activé
crb-debuginfo AlmaLinux 10 - CRB - Debug désactivé
crb-source AlmaLinux 10 - CRB - Source désactivé
epel Extra Packages for Enterprise Linux 10 - x8 activé
epel-debuginfo Extra Packages for Enterprise Linux 10 - x8 désactivé
epel-source Extra Packages for Enterprise Linux 10 - x8 désactivé
epel-testing Extra Packages for Enterprise Linux 10 - Te désactivé
epel-testing-debuginfo Extra Packages for Enterprise Linux 10 - Te désactivé
epel-testing-source Extra Packages for Enterprise Linux 10 - Te désactivé
extras AlmaLinux 10 - Extras activé
extras-debuginfo AlmaLinux 10 - Extras - Debug désactivé
extras-source AlmaLinux 10 - Extras - Source désactivé
highavailability AlmaLinux 10 - HighAvailability désactivé
highavailability-debuginfo AlmaLinux 10 - HighAvailability - Debug désactivé
highavailability-source AlmaLinux 10 - HighAvailability - Source désactivé
nfv AlmaLinux 10 - NFV désactivé
nfv-debuginfo AlmaLinux 10 - NFV - Debug désactivé
nfv-source AlmaLinux 10 - NFV - Source désactivé
rt AlmaLinux 10 - RT désactivé
rt-debuginfo AlmaLinux 10 - RT - Debug désactivé
rt-source AlmaLinux 10 - RT - Source désactivé
sap AlmaLinux 10 - SAP désactivé
sap-debuginfo AlmaLinux 10 - SAP - Debug désactivé
sap-source AlmaLinux 10 - SAP - Source désactivé
saphana AlmaLinux 10 - SAPHANA désactivé
saphana-debuginfo AlmaLinux 10 - SAPHANA - Debug désactivé
saphana-source AlmaLinux 10 - SAPHANA - Source désactivé

EPEL has more than one repo for the el10: 10.0, 10.1, …

RHEL 10 and AlmaLinux 10 systems request URL for a repo with id “epel-z-10” and in the Summer that did direct to the “10.0” repo as it should.

On 2025-11-12 RHEL 10.1 was released and EPEL updated the “epel-z-10” to resolve to “10.1”. This allows the upgraded RHEL 10 systems to get packages that are built for 10.1.

AlmaLinux 10 ought to release 10.1 next week. Hence it is still a 10.0.
(EPEL) packages built for 10.1 will fail to install, if they depend on 10.1 versions of base distro packages. (Mostly libraries).


There are two trivial options:

  • Wait until AlmaLinux 10.1 is available
  • Give dnf option --releasever=10.0
    That will explicitly request 10.0, which should work with base repos and EPEL.

PS. These posts can be formatted. There is code tags button </> that makes pasted text (from terminal) bit easier to read. I did just press it and got what is below:

type or paste code here

I choosed the 2nd option (updating with 10.0 release)

Perfect !

I will wait the 10.1 release for a new update.

Thanks !