https://bugzilla.novell.com/show_bug.cgi?id=802624
https://bugzilla.novell.com/show_bug.cgi?id=802624#c28
--- Comment #28 from Stefan Dirsch
First of all, I'm sorry for the delay.
(In reply to comment #22)
For some reason I don't see the issues when just updating nvidia-gfxG03-kmp-desktop package. I would have expected the same issue when looking at the %preun/%postun scripts.
Did you test with the kernel that the KMP was built against?
No, the kernel has been updated meanwhile. IIRC updating the kernel was necessary to reproduce the issue.
In this case the module is installed below /lib/modules/.../extra or .../updates and this is handled by rpm. Admittedly, rpm is lot smarter than the weak-modules2 script.
Michal, could it be that wm2 removes the symlink although the kernel module still exists, but only does that if it belongs to a different package? This would explain the behaviour.
Yes. weak-modules2 --remove-kmp always removes all the symlinks, and then looks for the newest among other versions of the kmp to create new symlinks. I.e. package renames are not handled. I will change it to also consider packages that contain the same set modules, which should handle the nvidia case. It will not handle the case when you rename a KMP _and_ add or remove modules at the same time.
Thanks. That would be great and covers perfectly this issue only containing one kernel module called "nvidia.ko". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.