> The module already depends on a kernel version, which causes already other problems (bug 226960)
The package "virtualbox-ose-modules-2.6.24-17-generic" depends on "linux-image-2.6.24-17-generic" but because the package "linux- image-2.6.24-17-generic" is retained when a kernel update is ditributed, the kernel gets updated and the dependencies are still met. So, for APT, all is well! Making "virtualbox-ose-modules-2.6.24-17-generic" dependent on "linux- image-generic" with the exact version of 2.6.24-17 would hold back the kernel update until the correct virtualbox modules are available? Making "virtualbox-ose-modules-generic" dependent on any "virtualbox- ose-modules-xxxxxx-generic" package (an OR statement), would always install the correct modules for the installed kernel, when "virtualbox- ose-modules-generic" is installed? Only downside would be that people could be running a vulnerable kernel if the virtualbox modules are not updated fast enough... But for me personally, I wouldn't mind running a "vulnerable" kernel a day or two... Not being able to run virtualbox hampers me a lot more! I think you can't force end users to a terminal each time they receive a kernel update... Hmm, difficult issue... -- virtualbox don't run when update-manager change the linux-kernel https://bugs.launchpad.net/bugs/237278 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
