Problem with dnf upgrade (gpsd)

Support
1

Hi!

I would appreciate some help with a issue with dnf which prevents me from installing upgrades. Whenever I run dnf upgrade I get this error:
Error:Error:
Problem: package plasma5support-6.6.4-1.el10_2.x86_64 from @System requires libgps.so.31()(64bit), but none of the providers can be installed
- package gpsd-1:3.26.1-3.el10_2.1.x86_64 from appstream obsoletes gpsd-libs < 1:3.26.1-3.el10_2.1 provided by gpsd-libs-1:3.26.1-3.el10_2.x86_64 from @System
- package gpsd-1:3.26.1-3.el10_2.1.x86_64 from appstream obsoletes gpsd-libs < 1:3.26.1-3.el10_2.1 provided by gpsd-libs-1:3.26.1-3.el10_2.x86_64 from epel
- cannot install the best update candidate for package plasma5support-6.6.4-1.el10_2.x86_64
- cannot install the best update candidate for package gpsd-libs-1:3.26.1-3.el10_2.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

I realize that the gpsd package has changed but I am at a loss on how to fix it.

2

try with this:

sudo rpm -e --nodeps gpsd-libs
sudo dnf install gpsd-libs

few days ago someone posted this solution in the chat and it works.

3

Worked like a charm, thank you!

4

This solves the dependency issue, but it breaks the requirement for plasma5support:

# dnf check
plasma5support-6.6.4-1.el10_2.x86_64 has missing requires of libgps.so.31()(64bit)
Error: Check discovered 1 problem(s)

The real solution is probably that either gpsd ships that library, or that plasma5support is recompiled without requiring that library

5

Does this issue also reproduce on CentOS Stream 10 with the same package versions?
If so, this may be an upstream packaging/dependency issue rather than an AlmaLinux-specific problem.

6

These are from v2, but I would presume that Alma’s v2 build of EPEL is no different:

# dnf -q --enablerepo=epel list --showduplicates plasma5support
Available Packages
plasma5support.x86_64_v2    6.5.2-1.el10_2.alma_altarch    epel
plasma5support.x86_64_v2    6.5.4-1.el10_2.alma_altarch    epel
plasma5support.x86_64_v2    6.6.0-1.el10_2.alma_altarch    epel
plasma5support.x86_64_v2    6.6.4-1.el10_2.alma_altarch    epel

# dnf --enablerepo=epel install plasma5support | grep gpsd
 gpsd-libs  x86_64_v2  1:3.26.1-3.el10_2.alma_altarch.1    epel        66 k
n
Operation aborted.

# dnf -q --enablerepo=epel list --showduplicates gpsd
Available Packages
gpsd.x86_64_v2              1:3.26.1-3.el10                appstream
gpsd.x86_64_v2              1:3.26.1-3.el10_2.1            appstream
gpsd.x86_64_v2              1:3.26.1-3.el10_2.2            appstream

# dnf --enablerepo=epel install gpsd | grep gpsd
 gpsd       x86_64_v2       1:3.26.1-3.el10_2.2        appstream        586 k
n
Operation aborted.

# dnf -q --enablerepo=epel list --showduplicates gpsd-libs
Available Packages
gpsd-libs.x86_64_v2         1:3.26.1-1.el10_2.alma_altarch    epel
gpsd-libs.x86_64_v2         1:3.26.1-2.el10_2.alma_altarch    epel
gpsd-libs.x86_64_v2         1:3.26.1-3.el10_2.alma_altarch    epel
gpsd-libs.x86_64_v2         1:3.26.1-3.el10_2.alma_altarch.1  epel

From those we can conclude that:

  • The gpsd-1:3.26.1-3.el10_2.2.x86_64_v2 does not require gpsd-libs, because
    • gpsd is in _appstream
    • gpsd-libs is in EPEL
  • The plasma5support does not require gpsd

However:

# dnf --enablerepo=epel install gpsd-libs
Last metadata expiration check: 0:09:07 ago on Mon 21 Sep 2026 11:15:20 AM EEST.
Dependencies resolved.
=========================================================================
 Package   Architecture   Version                   Repository      Size
=========================================================================
Installing:
 gpsd      x86_64_v2      1:3.26.1-3.el10_2.2       appstream      586 k

Transaction Summary
=========================================================================
Install  1 Package

Total download size: 586 k
Installed size: 2.2 M
Is this ok [y/N]: n
Operation aborted.

The “install gpsd-libs” does install gpsd, probably because the gpsd has “obsoletes gpsd-libs”. Mysteriously, the “install plasma5support” does avoid that, but dnf up will then attempt to replace gpsd-libs @epel with gpsd @appstream

gpsd seems to be mutually exclusive with gpsd-libs.
One can keep the plasma5support (i.e. avoid the gpsd) with:

dnf up --exclude=gpsd

As said, things in appstream repo are most likely an upstream issue.

7

I reported this issue in Red Hat Bugzilla:

8

Hello,
The EPEL maintainer is currently addressing the issue.
Please check the following link for updates: