Virtualbox should depend on virtualbox-ose-modules (kernel module)

Crud, that wasn't clear.

The main issue is that since Virtualbox requires the modules to function they should be a dependency and not a recommends. The easiest way to do that is like the kernels are handled, they are virtual packages that just point to the latest real package.

There are other bugs where this issue is mentioned but I felt it was best to get a new bug that clearly states the problem and a potential solution.

I tend to reject this bug as invalid:
1. Recommends should get installed automatically (in most cases, e.g. with aptitude).
2. virtualbox-ose can be used without virtualbox-ose-modules, if you just want to edit a virtual machine.

Please see bug 152406, where I'll provide a patch to clarify the error message.

Does this sound reasonable?

I see your point however Synaptics doesn't install Recommends by default which is a common method of installing apps. Does Add/Remove install recommends by default (I haven't tried that yet)? I do feel that people who install virtualbox without the modules are going to be rare.

Even if we leave it as recommends what about the second part regarding a virtual package so that the modules are upgrades automatically? It can be a bit of a pain that it isn't done automatically.

Thanks!

The virtual/meta package is bug 152015.

In response to daniel's comment:

1. The most used install methods in Ubuntu (synaptic, add/remove programs and apt-get) don't install recommends by default at the moment.

2. The debian packaging manual states that: "The Depends field should be used if the depended-on package is required for the depending package to provide a significant amount of functionality." I think being able to actually run a virtual machine is a significant amount of functionality.

So I think it should depend on the -modules package. I hope this can be fixed before the archive freeze tomorrow!

Added the fix to the debdiff attached to bug 152406.

virtualbox-ose (1.5.0-dfsg2-1ubuntu3) gutsy; urgency=low

  * Move the virtualbox-ose-modules from Recommends to Depends. (LP: #152405)

 -- Steve Kowalik <email address hidden> Mon, 15 Oct 2007 22:22:30 +1000

I'm reopening this bug, because I had to revert this change (bug 188579).

I can see no way to fix this currently, but there may be a solution once apt's dependency resolution gets improved (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471771)

I'd like to see this virtual package too

just adding a point really no further updates.

but every time there's a new kernel released, suddently my VM doesn't work anymore undervirtualbox, I've migrated most of my VM's to vmware now, which although has a similar issue, I have a script for that to sort it for me, but not on Virtualbox, so the latest kernel modules not being installed with a kernel update could push people away from virtual box.

also note that I already had virtualbox installed (through aptitude) the kernel updates came throught the update-manager GUI - and I do not have the latest modules for my kernel, I had to manually add them in.

Jason

It's getting quite annoying that Virtualbox breaks EVERY TIME a new kernel is released. Since Hardy was released, we've had quite a few kernel updates, and everytime, Virtualbox is broken for a week, maybe more.

Why is this classed as "Wishlist" if it breaks everytime there is a kernel update, then surely it's not a wish, it's bug...?

This bug is blocking VirtualBox from operating correctly with system updates, and I for one have started to use VMWare Server simply because I don't have to constantly reconfigure it everytime I change my kernel.

Jason.

I just installed Intrepid; virtualbox-ose-source is recommended by virtualbox-ose and they work wonderfully together! :-)

So this bug can be closed, right?

No, a fix should be released for Gutsy and Hardy. It's great that it works in Intrepid but it doesn't in the other two just mentioned.

Actually this can be closed beacuse it is fixed. If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "How to request new packages" at https://help.ubuntu.com/community/UbuntuBackports#request-new-packages