Comment # 3 on bug 1204275 from Klaus Braun

Hello,

here are the outputs of rpm -q kernel-default and rpm -q kernel-devel. As far
as I can see there is nothing spectacular:

rpm -q kernel-default

kernel-default-5.3.18-150300.59.93.1.x86_64
kernel-default-5.3.18-150300.59.81.1.x86_64
kernel-default-5.3.18-150300.59.98.1.x86_64
kernel-default-5.3.18-150300.59.76.1.x86_64
kernel-default-5.3.18-150300.59.87.1.x86_64
kernel-default-5.3.18-150300.59.90.1.x86_64

rpm -q kernel-devel

kernel-devel-5.3.18-150300.59.98.1.noarch
kernel-devel-5.3.18-150300.59.81.1.noarch
kernel-devel-5.3.18-150300.59.87.1.noarch
kernel-devel-5.3.18-150300.59.76.1.noarch
kernel-devel-5.3.18-150300.59.90.1.noarch
kernel-devel-5.3.18-150300.59.93.1.noarch


What i'm talking about is the output of yast2 concerning "Update if newer
version available" (Packages / All Packages / Update if newer version
available) where the entries for kerne-devel and kernel-default-devel show up
in red, meaning the installed packages are newer than the available ones (s.
attached screenshot). 

This only happens when the nvidia repo is enabled, meaning obviously the nvidia
drivers need kernel-devel version 5.3.18-57.3 which is a quite old one compared
with the actually installed version 5.3.18-150300.59.98.1. And I have no idea
waht will happen if I downgrade kernel-devel and kernel-default-devel, then
compile the nvidia drivers and load them with the actual kernel.  Is this
behaviour it really intended? There was a discussion about nvidia and kernel
versions but this should be fixed, see bug 1202116.

Best

Klaus