Dnf update error

Hello team.
I have an issue that arose after updating to the new kernel release 5.14.0-70.22.1.el9_0.x86_64 in my Rocky Linux 9 system.
whenever I run the dnf update command, I get these two errors:

sudo dnf update
[sudo] password for jil:
Rocky Linux 9 - BaseOS 2.2 kB/s | 3.6 kB 00:01
Rocky Linux 9 - AppStream 499 B/s | 3.6 kB 00:07
Rocky Linux 9 - CRB 2.9 kB/s | 3.6 kB 00:01
Rocky Linux 9 - Extras 1.7 kB/s | 2.9 kB 00:01
Error:
Problem 1: cannot install the best update candidate for package kf5-ki18n-5.90.0-1.el9.x86_64

  • nothing provides libQt5Core.so.5(Qt_5.15.3_PRIVATE_API)(64bit) needed by kf5-ki18n-5.96.0-1.el9.next.x86_64
    Problem 2: cannot install the best update candidate for package kf5-kxmlgui-5.90.0-1.el9.x86_64
  • nothing provides qt5-qtbase(x86-64) = 5.15.3 needed by kf5-kxmlgui-5.96.0-1.el9.next.x86_64
  • nothing provides libQt5Core.so.5(Qt_5.15.3_PRIVATE_API)(64bit) needed by kf5-kxmlgui-5.96.0-1.el9.next.x86_64
    (try to add ā€˜ā€“skip-brokenā€™ to skip uninstallable packages or ā€˜ā€“nobestā€™ to use not only best candidate packages)

I am still very new to Rocky Linux 9. Please help out.

Thank you.

Hi, you could try this, I have done it few times and sometimes it does help:

dnf clean all
dnf update
1 Like

el9.next

Isnā€™t that a package that EPEL has build for CentOS Stream 9? Surely those (packages and repos) should not be in EL9 distro, like Rocky 9?

Hello, @iwalker I have run the commands but still canā€™t get to update my dnf repository.
Though 95 files have been removed.
Thank you.

Hello @jlehtone

How do I uninstall this? I truly canā€™t recall installing any CentOS Stream 9 EPEL packages and repos.

Thank you.

First, information about your setup:

dnf repolist
dnf list knf\*

OKey .

dnf repolist
repo id repo name
appstream Rocky Linux 9 - AppStream
baseos Rocky Linux 9 - BaseOS
crb Rocky Linux 9 - CRB
epel Extra Packages for Enterprise Linux 9 - x86_64
epel-next Extra Packages for Enterprise Linux 9 - Next - x86_64
extras Rocky Linux 9 - Extras
google-chrome google-chrome
mongodb-org-5.0 MongoDB Repository
pritunl Pritunl Stable Repository
rpmfusion-free-updates RPM Fusion for EL 9 - Free - Updates

dnf list knf*
Last metadata expiration check: 0:12:25 ago on Wed 17 Aug 2022 06:08:37 PM EAT.
Error: No matching Packages to list

See the information.

@jlehtone

Sir, i have run the command
sudo yum remove epel-release -y

then

dnf repolist
repo id repo name
appstream Rocky Linux 9 - AppStream
baseos Rocky Linux 9 - BaseOS
crb Rocky Linux 9 - CRB
extras Rocky Linux 9 - Extras
google-chrome google-chrome
mongodb-org-5.0 MongoDB Repository
pritunl Pritunl Stable Repository

I think it now looks good.

Thank you sir for shedding light.

If you use epel, it should be set to disabled, then to use it:
dnf --enablerepo ā€œepelā€ search somepackage

I think it is more of a personal preference, rather than a case of should/shouldnā€™t. I have the epel repo enabled all the time and have no issues with it. Some prefer to only enable it for installing packages as and when they need it - in the way you suggested with the --enablerepo command. Both are valid methods.

1 Like

Besides, ā€˜epelā€™ was not the problem. This was:

I did just install package ā€˜epel-releaseā€™ from EPEL and it does not contain definition for repo epel-next.

If the repo did ā€œgo awayā€ by removal of package ā€˜epel-releaseā€™, then that version of ā€˜epel-releaseā€™ was not for EL9.

One could run sudo dnf history list epel-release to get list of transactions that included package epel-release.
sudo dnf history info epel-release would show details from all those transactions, but one could give number of transaction, rather than <package-spec>.
One might be able to tell from those details, where did that package come from.

If dnf does not remember, then perhaps shell does: history | grep epel-release
(Default Bash HISTORYSIZE is quite short though.)

Ps. I apparently had a typo earlier: wrote dnf list knf* when I should have written dnf list kf5*. Not that it matters now.

Thank you so much.

I had earlier tried to install KDE Plasma Desktop Environment on Rocky Linux 9.

I found out in some guide (canā€™t exactly trace it) that the epel-next repo was to be installed for a successful installation.

This must have been the instance I installed epel-next repo in my machine

Thank you for your feedback its a learning curve.