http://bugzilla.opensuse.org/show_bug.cgi?id=1082704 http://bugzilla.opensuse.org/show_bug.cgi?id=1082704#c11 --- Comment #11 from Peter Sütterlin <P.Suetterlin@royac.iac.es> --- (In reply to Stefan Dirsch from comment #10)
Ok. You're right. I was testing on Leap 42.3. Indeed there we have the rebuild in %post and in the %triggers. On TW only in the %triggers.
one mystery solved :)
I also believe it's correct to install to /lib/modules/$kver/updates instead of the hardcoded path in the trigger scripts for TW.
I think it's wrong in both TW and Leap. kver=$(make -sC /usr/src/linux-obj/$arch/$flavor kernelrelease) will always point to the latest installed kernel. This *can* be the one the modules were compiled for originally. In that case $kver=4.4.76-1-$flavor (in your case). But if it's different, it would overwrite the original one with a 'broken' one. Likely the error doesn't show up in Leap, as that one doesn't really do big kernel jumps. In principle it's easy: If you compile against $kver, then also install in /lib/modules/$kver ..... -- You are receiving this mail because: You are on the CC list for the bug.