On 18.05.2013 20:04, Antonio Terceiro wrote:
>> 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) t
W dniu 18.05.2013 18:00, Adam Borowski pisze:
>>> I've noticed that virtualbox moved from main to contrib
> It's a major loss.
> 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 contr
[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 v
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.
However, Wa
On 05/18/2013 08:30 PM, Holger Levsen wrote:
> Hi,
>
> I've noticed that virtualbox moved from main to contrib (via
> http://jenkins.debian.net/job/chroot-installation_sid_install_full_desktop/)
> and while I personally don't use virtualbox anymore I think this is news to
> be
> announced (henc
5 matches
Mail list logo