Comment # 47 on bug 1182666 from B

> rpm -q --whatrequires kernel-default
    no package requires kernel-default

> rpm -q --whatrequires kernel-default-devel
    nvidia-gfxG05-kmp-default-460.56_k5.10.16_1-35.1.x86_64
    kernel-syms-5.11.4-1.2.x86_64
    kernel-syms-5.11.4-1.3.x86_64

> rpm -q --requires kernel-syms-5.11.4-1.3.x86_64
    kernel-default-devel = 5.11.4-1
    kernel-devel = 5.11.4-1

> rpm -q --requires kernel-default-devel-5.11.4-1.3.x86_64
    kernel-devel = 5.11.4-1


There seems to be no strict requirement for kernel-default to be installed
before kernel-default-devel so it must've been a coincidence that the few times
I looked at the order when installing it was correct.

When kernel-default is uninstalled it cleans out /lib/modules/$kernel/updates/
dir where the modules are.

So if there's a minor patch version bump 5.11.4-1.3 it first needs to remove
the older package 5.11.4-1.2 so if you get unlucky:
1) kernel-default-devel-5.11.4-1.3 is installed
2) kernel-default-5.11.4-1.2 is removed
3) kernel-default-5.11.4-1.3 is installed
you now are left without those extra kernel modules.

Some possible fixes I see:
1) Modify the kernel-default uninstall script to not clean out
/lib/modules/$kernel/updates/. This is probably a lazy and bad idea because it
will junk when you normally uninstall kernels.
2) Modify the kernel-default uninstall script so that it somehow knows that
it's not a regular uninstall happening but a minor patch upgrade and not delete
those kernel modules.
3) Make it that minor patch updates (5.11.4-1.2->5.11.4-1.3) work like regular
updates (for example 5.11.4->5.11.6) where kernels are not replaced but
installed alongside each other and use different directories.

Basically every idea involves modifications to the kernel packages, not Nvidia
and I have no idea how easy it would be to implement those.