I guess the modules packages for 2.6.24-10 will be released soon. But still, the original bug remains:
When installing virtualbox-ose (with apt-get or aptitude), to resolve the dependency on the virtual package virtualbox-ose-modules, virtualbox-ose-modules-(version)-386 is installed _and_ the whole -386 kernel. The following packages provide virtualbox-ose-modules: virtualbox-ose-modules-2.6.24-8-386 virtualbox-ose-modules-2.6.24-8-rt virtualbox-ose-modules-2.6.24-8-virtual virtualbox-ose-modules-2.6.24-8-generic virtualbox-ose-modules-2.6.24-8-server Why does apt(itude) chose -386, implying the installation of the whole -386 kernel when it could simply pick the module for the current (-generic) one? And it becomes even stranger: if instead of installing virtualbox-ose, you type aptitude install virtualbox, aptitude suggests to install the -gereic module! (apt-get install virtualbox results as previously in installation of the -386 module and kernel) But there is no such package with the name virtualbox. It is a virtual package, provided by virtualbox-ose. Why doeas aptitude suggest a different 'modules' package? Are there any package priorities, and when yes, how can someone tweak them? -- virtualbox installs for the wrong kernel https://bugs.launchpad.net/bugs/188579 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
