On 10/4/15 12:54 AM, Antonio Terceiro wrote: > Control: severity -1 normal >> I have installed the virtualbox-guest-utils, virtualbox-guest-x11 packages >> and still I got this error. > > Those packages need to be installed on Debian guests, not on Debian > hosts.
My bad! Didn't read about the packages before trying to install them :) But installing these packages or not having them installed does nothing to influence this issue. > >> But later when I installed virtualbox-ext-pack package from non-free, vagrant >> worked fine without the above error. So if this is clearly reproducible, >> vagrant package should depend on the virtualbox-ext-package which might >> cause vagrant to be moved to non-free section. > > vagrant does not depend on virtualbox (it can use other virtualization > providers -- e.g. I do not use virtuabox myself), so it does not make > any sense for it to depend on something that virtualbox needs to work. Yes, vagrant is not tied to VirtualBox. But it is used most commonly with VirtualBox. So after installing vagrant, if "vagrant up" command fails with some error, that makes the package unusable for most of those users because that is the command to start a VM from based on a Vagrantfile. While this bug might not be "grave", imho it is definitely more severe than "normal". > I am copying the virtualbox maintainers to see if they have some input. > Maybe virtualbox should recommend virtualbox-ext-pack of something like > that. Ritesh Raj Sarraf has asked for more logs, if any. So I will uninstall virtualbox-ext-pack and then run vagrant up with debug logging enabled and share the logs collected. I am not sure if recommending virtualbox-ext-pack will be of any help because recommended packages do not get installed unless the user explicitly chooses to install them. So unless the user installs virtualbox-ext-pack, vagrant is broken for him/her when using with VirtualBox. Thanks & Regards, Guruprasad
signature.asc
Description: OpenPGP digital signature
