Hello everybody, I need help:
I try to upgrade the follow Rocky Linux version:
Operating System: Rocky Linux 9.5 (Blue Onyx)
CPE OS Name: cpe:/o:rocky:rocky:9::baseos
Kernel: Linux 5.14.0-503.31.1.el9_5.x86_64
Architecture: x86-64
I obtain many errors like the follow:
sudo dnf -y upgrade
Last metadata expiration check: 0:06:21 ago on Wed 04 Jun 2025 03:16:41 PM UTC.
Error:
Problem: cannot install the best update candidate for package kmod-mptsas-3.04.20-9.el9_5.elrepo.x86_64
nothing provides kernel >= 5.14.0-570.12.1.el9_6 needed by kmod-mptsas-3.04.20-10.el9_6.elrepo.x86_64 from elrepo
nothing provides kernel(module_layout) = 0x4f5671f6 needed by kmod-mptsas-3.04.20-10.el9_6.elrepo.x86_64 from elrepo
If 9.6 has finally been released, then chances are not all the mirrors have synced just yet. Solution is just wait for 24 hours at least. It seems elrepo have released packages too early, before Rocky have had chance to get their mirrors all synced.
The reason for error was (when future reader sees this) that ELRepo released packages for el9_6 before Rocky released el9_6.
The workaround is to exclude the available third-party packages that are not for your system (although at this point Rocky 9.5 should no longer get any updates since RHEL is already at 9.6).
Although, I would not say “too early”. The ELRepo is packages for EL and RHEL is both an EL and was out earlier. It would hardly be fair if ELRepo had waited until all EL 9 distros have released 9.6.
The el9_5 users could exclude the el9_6 packages that already exists, but the el9_6 users cannot install el9_6 packages that are not available yet. Considering that ELRepo (and some other repos) provide drivers, which tend to be essential, it is good that ELRepo did release el9_6 content “ASAP”.
The gstreamer1 has packages in both EPEL and RPM Fusion (third-party) repositories.
The history is that some libraries have/had license that EPEL did not want to have.
Now, a el9_6 version package in EPEL provides not only what the el9_5 version had, but also files that a package in RPM Fusion did provide for el9_5.
The solution is to remove the package that was installed from RPM Fusion. After that the EPEL package can update.
If the new package does not provide everything that the RPM Fusion version did … then you have to figure out a new solution.
It is probably easier to handle individual packages from command-line, with dnf.