so here is example when i tried to install qbittorrent
matija@RockyLinux ~> sudo dnf install qbittorrent
[sudo] password for matija:
Last metadata expiration check: 0:32:26 ago on Mon 25 May 2026 11:01:10 CEST.
Error:
Problem: conflicting requests
- nothing provides libQt6Core.so.6(Qt_6.10)(64bit) needed by qbittorrent-1:5.1.4-4.el1
0_2.x86_64 from epel
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only
best candidate packages)
Because you are pulling packages from EPEL that are based on RHEL 10.2 and Rocky 10.2 hasnāt been released yet.
so what should i do next in order to manage updates normally?
For now just wait until 10.2 is released.
This happens every time RHEL releases a new version, EPEL matches it, and until Rocky releases the same version and people have EPEL enabled, it blocks it from updating because you have 10.1 and EPEL expects 10.2. Once Rocky 10.2 releases, the problem disappears.
ok i understand..ill wait, and thank you for your help.
This is not āupdateā. It is an āinstallā. You could try:
sudo dnf --releasever=10.1 install qbittorrent
It might force dnf to explicitly look for Rocky 10.1 and EPEL 10.1 repos.
matija@RockyLinux ~> sudo dnf --releasever=10.1 install qbittorrent
[sudo] password for matija:
Extra Packages for Enterprise Linux 10.1 - x86_64 8.3 MB/s | 5.7 MB 00:00
Rocky Linux 10.1 - BaseOS 16 MB/s | 21 MB 00:01
Rocky Linux 10.1 - AppStream 4.8 MB/s | 2.4 MB 00:00
Rocky Linux 10.1 - CRB 491 kB/s | 541 kB 00:01
Rocky Linux 10.1 - Extras 16 kB/s | 6.0 kB 00:00
No match for argument: qbittorrent
Error: Unable to find a match: qbittorrent
I installed flatpak version..it works..
Apparently the qbittorrent package was added to EPEL 10 only recently and then only for 10.2 and 10.3, not for 10.1 nor for 10.0: https://bodhi.fedoraproject.org/updates/?search=EPEL&packages=qbittorrent
EPEL 8 and EPEL 9 have had it way longer.
That is a valid option. You can re-evaluate the flatpak vs EPEL when Rocky 10.2 is released.
Ok, so how i do regular updates till 10.2 version comes out? Or i just ignore them? Maybe using Discover app or disabling epel?
Updates of what?
Red Hat will not make any updates for RHEL 10.1 now that RHEL 10.2 is out. (They have done updates for RHEL 10.0 after release of 10.1, but only for extended update support clients.)
Since there will be no new updates for RHEL 10.1, there is no need to replicate them for Rocky 10.1. The only exception would be critical security hotfixes (like in recent weeks), but why divert resources to such task now when getting the Rocky 10.2 (and 9.8) ready does probably solve the issue too?
Likewise it is quite unlikely that EPEL (or any other third-party repo) releases updates built for 10.1 now.
I understand you well so i did: sudo dnf config-manager --set-disabled epel and: sudo dnf update --exclude=āgpsd*ā -y and it pulled out tons of updates, after reboot it says finally nothing to do/complete.. i meant updates of a system since it refuses to do so with regular dnf update
i get it, there should be no updates till Rocky 10.2 is out. It refuses to do so like you said there are no updates for 10.1 but discover shows that updates are available maybe some nonsystem related updates) so i did manual update
My bad.
I did assume that the (Rocky 10) system was up to date when RHEL 10.2 was released.
Directories of my nearest Rocky 10.1 mirror seem to have timestamp: 2026-05-19.
That is, no new updated packages released for Rocky 10.1 since 2026-05-19.
If your previous dnf up was on 2026-05-19 or 2026-05-20 (before EPEL made their 10.2 a default), then there would be no new updates.
If your previous dnf up had been before 2026-05-19, then Rocky 10.1 repos did indeed have ānew packagesā for your system.
The dnf --releasever=10.1 up ought to have succeeded.
The dnf config-manager --set-disabled epel modifies repo config file. Convenient, but one can
also dnf --disablerepo=epel up --exclude=gpsd\* without persistent change to repo config.
I usually do not add that -y to dnf commands. It is as easy to say āYā interactively and get opportunity to see what Iām saying yes to.
dnf check-update and the dnf history (e.g. sudo dnf history info last) commands should show from which repositories the packages are/did come from.
No problem:D ok i get it. Now i reverted back to defaults. Epel enabled again. So when 10.2 comes out should i upgrade normal with sudo dnf update/upgrade, or i have to disable Epel again to do upgrade?
Should work.
Note: dnf update and dnf up are both aliases for dnf upgradeā all three the same command.
Hence I prefer to type the dnf up ā¦
One can define more aliases for dnf. I have dnf cup for saving typing dnf check-update
Yes, but thereās also the concept of code comprehension, avoiding acronyms and making it easy to understand e.g. for someone who is reading it for the first time.
since 10.2 is out it all works perfectly now..