I’m trying to understand the kernel versions shown below:
dnf repoquery kernel.x86_64
kernel-0:4.18.0-372.13.1.el8_6.x86_64
kernel-0:4.18.0-372.16.1.el8_6.0.1.x86_64 (<- what?)
kernel-0:4.18.0-372.16.1.el8_6.x86_64
kernel-0:4.18.0-372.9.1.el8.x86_64
Indeed. My nearest mirror does not even have it yet. On the main site:
kernel-4.18.0-372.9.1.el8.x86_64.rpm 10-May-2022 22:01 8420412
kernel-4.18.0-372.13.1.el8_6.x86_64.rpm 29-Jun-2022 23:34 8426636
kernel-4.18.0-372.16.1.el8_6.x86_64.rpm 13-Jul-2022 21:44 8435540
kernel-4.18.0-372.16.1.el8_6.0.1.x86_64.rpm 15-Jul-2022 01:50 8435564
https://errata.rockylinux.org/ does not have entry for it either (yet?)
So kernel “16.1” is shown twice, I’m not used to seeing that. I guess in a real dnf upgrade, it wuld just ignore the first one and only install “el8_6.0.1”
I’ve just checked again and it now says
kernel-0:4.18.0-372.16.1.el8_6.x86_64
The “0.1” suffix in the original list has gone?
Still appears on my list:
[root@rocky8 ~]# dnf repoquery kernel.x86_64
Last metadata expiration check: 3:27:43 ago on Sat 23 Jul 2022 10:12:39 CEST.
kernel-0:4.18.0-372.13.1.el8_6.x86_64
kernel-0:4.18.0-372.16.1.el8_6.0.1.x86_64
kernel-0:4.18.0-372.16.1.el8_6.x86_64
kernel-0:4.18.0-372.9.1.el8.x86_64
also still available here: Index of /pub/rocky/8.6/BaseOS/x86_64/os/Packages/k/
Maybe you are connecting with mirrors that haven’t got a full sync of all files. Also, doing a:
dnf update
on my system, brought in the latest kernel, and I have it:
[root@rocky8 ~]# uname -r
4.18.0-372.16.1.el8_6.0.1.x86_64
Package release are made, whether it is el8_6, or el8_6.1 or el8_6.2.3 doesn’t really matter. It will happen, and it’s nothing unusual. Especially if el8_6 is released, and later they fix it, so that is how you see here, so similar scenario. They won’t commit it to the same version because other people might have the older one installed, and they won’t get the bugfix.
Here another scenario:
[root@rocky8 ~]# cat /etc/rocky-release
Rocky Linux release 8.6 (Green Obsidian)
So I’m running Rocky 8.6, but wait I have Rocky 8.4 packages:
[root@rocky8 ~]# rpm -qa | grep el8_4
libdb-5.3.28-42.el8_4.x86_64
libdb-utils-5.3.28-42.el8_4.x86_64
lz4-libs-1.8.3-3.el8_4.x86_64
ca-certificates-2021.2.50-80.0.el8_4.noarch
and I have Rocky 8.5 packages:
[root@rocky8 ~]# rpm -qa | grep el8_5
libarchive-3.3.3-3.el8_5.x86_64
openssl-1.1.1k-6.el8_5.x86_64
gzip-1.9-13.el8_5.x86_64
zlib-1.2.11-18.el8_5.x86_64
cyrus-sasl-lib-2.1.27-6.el8_5.x86_64
openssl-libs-1.1.1k-6.el8_5.x86_64
polkit-libs-0.115-13.el8_5.2.x86_64
polkit-0.115-13.el8_5.2.x86_64
I asked about this once here, it basically means those packages that were installed when I was on Rocky 8.4 or 8.5 haven’t updated yet, but in time they will when a package is released with a higher one than I have installed. Incidently, I could probably uninstall one of them, and it would then show el8 or el8_6 as it would then pull from the Rocky 8.6 repos.
OK, it makes sense about the mirrors; I just tried again and it’s back. I now see
kernel-0:4.18.0-372.16.1.el8_6.0.1.x86_64
maybe each time I tested this, it was using a different mirror and got a different result…
Yep, most likely since the repos by default use mirrorlist for performance.