[re-adding the package maintainer(s) in Cc:, and adding the vagrant maintainer(s) in the loop]
On Sat, May 18, 2013 at 05:49:38PM +0200, Adam Borowski wrote: > On Sat, May 18, 2013 at 11:38:46PM +0800, Thomas Goirand wrote: > > On 05/18/2013 08:30 PM, Holger Levsen wrote: > > > I've noticed that virtualbox moved from main to contrib > > > FYI, this has been discussed here: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691148 > > It's a major loss. Indeed. Two problems caused by this: - if virtualbox stays in contrib, this will force vagrant to go to contrib as well (at least until we don't have alternative VM providers such as vagrant-kvm in main). - users of unstable main that don't use contrib are now stuck with a buggy version of virtualbox (4.1.18-dfsg-2+deb7u1) whose kernel modules don't build against the default kernel version (3.8) ... > However, Watcom is needed only for 16-bit code, and VirtualBox has an EFI > mode. Would it be possible to restrict it to EFI only in main, unless the > BIOS from contrib is loaded? If that's possible, I would ask the virtualbox maintainer(s) to please consider this alternative so that we can have virtualbox back in main. -- Antonio Terceiro <terce...@debian.org>
signature.asc
Description: Digital signature
