dnf update
Last metadata expiration check: 1:13:16 ago on Thu 16 Jul 2026 09:40:35 PM EEST.
Error:
Problem: cannot install the best update candidate for package python-unversioned-command-3.12.13-2.el10_2.noarch
nothing provides python3 = 3.12.13-2.el10_2.1 needed by python-unversioned-command-3.12.13-2.el10_2.1.noarch from appstream
(try to add ‘–skip-broken’ to skip uninstallable packages or ‘–nobest’ to use not only best candidate packages)
This is most likely because you’re getting different mirrors for baseos and appstream. Your appstream metadata is up-to-date, while your baseos metadata is out of date.
You can try running dnf --refresh update and see if that works.
Thank you .
This is result:
dnf update --refresh
Extra Packages for Enterprise Linux 10 - x86_64 66 kB/s | 16 kB 00:00
Extra Packages for Enterprise Linux 10 - x86_64 5.3 MB/s | 6.6 MB 00:01
Rocky Linux 10 - BaseOS 15 kB/s | 4.3 kB 00:00
Rocky Linux 10 - BaseOS 5.7 MB/s | 3.1 MB 00:00
Rocky Linux 10 - AppStream 16 kB/s | 4.3 kB 00:00
Rocky Linux 10 - CRB 16 kB/s | 4.3 kB 00:00
Rocky Linux 10 - Extras 11 kB/s | 3.1 kB 00:00
Error:
Problem: cannot install the best update candidate for package python-unversioned-command-3.12.13-2.el10_2.noarch
nothing provides python3 = 3.12.13-2.el10_2.1 needed by python-unversioned-command-3.12.13-2.el10_2.1.noarch from appstream
(try to add ‘–skip-broken’ to skip uninstallable packages or ‘–nobest’ to use not only best candidate packages)
My nearest mirror does (now) have version 3.12.13-2.el10_2.1 of both packages.
If the mirror servers are different and metadata does come from servers, then
the mirror that did not yet have the el10_2.1 would still supply the metadata
that does not know about the el10_2.1 packages?
Do the
dnf repoinfo baseos
dnf repoinfo appstream
list different host in ‘Repo-baseurl’?
I do usually:
dnf clean all
It might make dnf select different mirrors.
To show the package versions that dnf sees now:
dnf list --showduplicates python3 python-unversioned-command
If we browse https://rockylinux.netforce.hosting/rocky/ (that you do now use), then we see that latest timestamps there seem to be 2026-06-05 (more than a month old).
The other mirror, https://distrohub.kyiv.ua/rockylinux/ has timestamps up to 2026-07-16 (yesterday).
The rockylinux.netforce.hosting is not a good mirror, because it is not in sync with Rocky.
You do not see issues in “dnf update”, because it now consistently sees only old packages.
You do have the issue that you cannot update your Rocky (because dnf chose a stale mirror).
For 2: The installer does not know better. The assumption is that all mirrors are up to date.
If a mirror is not syncing, then its maintainer and/or Rocky’s mirror service maintainers should be contacted in order to fix the sync or to remove the server from the list of mirrors.