Bug 2428239

On AlmaLinux 10.1 (x86_64_v2) with EPEL 10 enabled, system updates fail because plasma5support from EPEL requires libgps.so.30()(64bit), but DNF cannot complete the transaction when the distro repository offers gpsd with an Obsoletes relationship against gpsd-libs.My system has:
plasma5support-6.4.5-2.el10_1.alma_altarch.x86_64_v2 installed from EPEL
gpsd-libs-1:3.25-17.el10_0.alma_altarch.x86_64_v2 installed from EPEL
gpsd-1:3.26.1-1.el10.x86_64_v2 available from AppStream
dnf repoquery --whatprovides 'libgps.so.30()(64bit)' shows that only gpsd-libs-1:3.25-17... provides libgps.so.30 in this repository set. During dnf update, DNF tries to move forward due to gpsd (AppStream) obsoleting gpsd-libs < 1:3.26.1-1.el10, but then plasma5support still requires libgps.so.30, and the solver cannot find an installable provider, causing the update to fail.This blocks not only CLI updates (dnf update) but also GUI updates (Discover/PackageKit), since the transaction never resolves.Steps to Reproduce
Install AlmaLinux 10.1 (x86_64_v2).
Enable EPEL 10 repository.
Install KDE/Plasma stack including plasma5support from EPEL.
Run: dnf update
Actual Resultsdnf update fails with a dependency resolution error similar to:
plasma5support requires libgps.so.30()(64bit)
gpsd from AppStream obsoletes gpsd-libs < 1:3.26.1-1.el10
DNF cannot install a consistent set of packages satisfying both constraints
(Full command outputs included below.)Expected Resultsdnf update should complete successfully with EPEL enabled, without requiring transaction flags like --allowerasing, --skip-broken, or --nobest.Installed PackagesOutput of dnf list --installed plasma5support 'gpsd*':
gpsd-libs.x86_64_v2 1:3.25-17.el10_0.alma_altarch @epel
plasma5support.x86_64_v2 6.4.5-2.el10_1.alma_altarch @epel
Enabled RepositoriesOutput of dnf repolist --enabled:
appstream (AlmaLinux 10 - AppStream)
baseos (AlmaLinux 10 - BaseOS)
crb (AlmaLinux 10 - CRB)
extras (AlmaLinux 10 - Extras)
epel (Extra Packages for Enterprise Linux 10 from AlmaLinux - x86_64_v2)
Provider Check for the Required SONAMEOutput of dnf repoquery --whatprovides 'libgps.so.30()(64bit)':
gpsd-libs-1:3.25-17.el10_0.alma_altarch.x86_64_v2
Package Info (available versions)Output of dnf repoquery --info gpsd gpsd-libs (relevant fields):

gpsd

Epoch: 1
Version: 3.26.1
Release: 1.el10
Repo: appstream



gpsd-libs

Epoch: 1
Version: 3.25
Release: 17.el10_0.alma_altarch
Repo: epel



gpsd-libs

Epoch: 1
Version: 3.26.1
Release: 1.el10_1.alma_altarch
Repo: epel


Notes / ImpactThis appears to be a cross-repo dependency/obsoletes interaction where:
EPEL plasma5support depends on libgps.so.30
AppStream gpsd introduces an obsoletes rule against older gpsd-libs
The transaction becomes unsatisfiable, blocking updates
Please advise whether plasma5support should be rebuilt/adjusted to depend on the newer SONAME (if applicable), or whether a compatibility provider for libgps.so.30 is expected in EPEL for EL10 environments.