Bug#908826: [DRE-maint] Bug#908826: vagrant/stable is incompatible with virtualbox/stretch-backports (now 5.2)
On 17/09/18 at 11:51 -0700, Antonio Terceiro wrote: > Right - I noticed there was one missing bit. Can you grab the .deb from > the above URL and try again? Hi, I can confirm that it works fine now, thanks! > sorry for making you test it for me, but I don't have an easy way to > get a VirtualBox-capable system running stretch No problem, thanks for fixing this :) Lucas signature.asc Description: PGP signature
Bug#908826: vagrant/stable is incompatible with virtualbox/stretch-backports (now 5.2)
On Mon, Sep 17, 2018 at 03:16:05PM +0200, Lucas Nussbaum wrote: > On 15/09/18 at 09:46 -0300, Antonio Terceiro wrote: > > On Fri, Sep 14, 2018 at 05:10:48PM +0200, Lucas Nussbaum wrote: > > > Package: vagrant > > > Version: 1.9.1+dfsg-1+deb9u1 > > > Severity: normal > > > > > > Hi, > > > > > > vagrant 1.9.1+dfsg-1+deb9u1 is now incompatible with virtualbox from > > > stretch-backports (version 5.2.18-dfsg-1~bpo9+1). It worked fine with > > > virtualbox 5.1.30-dfsg-1~bpo9+1. > > > > > > vagrant from stretch-backports works fine with virtualbox from > > > stretch-backports. > > > > > > When starting vagrant, I get: > > > $ vagrant up > > > No usable default provider could be found for your system. > > > > > > Vagrant relies on interactions with 3rd party systems, known as > > > "providers", to provide Vagrant with resources to run development > > > environments. Examples are VirtualBox, VMware, Hyper-V. > > > > > > The easiest solution to this message is to install VirtualBox, which > > > is available for free on all major platforms. > > > > > > If you believe you already have a provider available, make sure it > > > is properly installed and configured. You can see more details about > > > why a particular provider isn't working by forcing usage with > > > `vagrant up --provider=PROVIDER`, which should give you a more specific > > > error message for that particular provider. > > > > > > (while of course virtualbox is available, and works fine outside of > > > Vagrant) > > > > Can you please test the .deb from > > https://people.debian.org/~terceiro/tmp/vagrant-stretch/ > > ? > > Sorry for the delay. > > It doesn't work. It doesn't find the virtualbox provider (it uses > libvirt), and when forced, it says that it doesn't support 5.2. Right - I noticed there was one missing bit. Can you grab the .deb from the above URL and try again? sorry for making you test it for me, but I don't have an easy way to get a VirtualBox-capable system running stretch signature.asc Description: PGP signature
Bug#908826: vagrant/stable is incompatible with virtualbox/stretch-backports (now 5.2)
On 15/09/18 at 09:46 -0300, Antonio Terceiro wrote: > On Fri, Sep 14, 2018 at 05:10:48PM +0200, Lucas Nussbaum wrote: > > Package: vagrant > > Version: 1.9.1+dfsg-1+deb9u1 > > Severity: normal > > > > Hi, > > > > vagrant 1.9.1+dfsg-1+deb9u1 is now incompatible with virtualbox from > > stretch-backports (version 5.2.18-dfsg-1~bpo9+1). It worked fine with > > virtualbox 5.1.30-dfsg-1~bpo9+1. > > > > vagrant from stretch-backports works fine with virtualbox from > > stretch-backports. > > > > When starting vagrant, I get: > > $ vagrant up > > No usable default provider could be found for your system. > > > > Vagrant relies on interactions with 3rd party systems, known as > > "providers", to provide Vagrant with resources to run development > > environments. Examples are VirtualBox, VMware, Hyper-V. > > > > The easiest solution to this message is to install VirtualBox, which > > is available for free on all major platforms. > > > > If you believe you already have a provider available, make sure it > > is properly installed and configured. You can see more details about > > why a particular provider isn't working by forcing usage with > > `vagrant up --provider=PROVIDER`, which should give you a more specific > > error message for that particular provider. > > > > (while of course virtualbox is available, and works fine outside of > > Vagrant) > > Can you please test the .deb from > https://people.debian.org/~terceiro/tmp/vagrant-stretch/ > ? Sorry for the delay. It doesn't work. It doesn't find the virtualbox provider (it uses libvirt), and when forced, it says that it doesn't support 5.2. *** lucas@grr:/tmp/tEEQ$ vagrant up Bringing machine 'default' up with 'libvirt' provider... Error while connecting to libvirt: Error making a connection to libvirt URI qemu:///system?no_verify=1&keyfile=/home/lucas/.ssh/id_rsa: Call to virConnectOpen failed: authentication cancelled: user cancelled authentication process *** lucas@grr:/tmp/tEEQ$ vagrant up --provider=virtualbox The provider 'virtualbox' that was requested to back the machine 'default' is reporting that it isn't usable on this system. The reason is shown below: Vagrant has detected that you have a version of VirtualBox installed that is not supported by this version of Vagrant. Please install one of the supported versions listed below to use Vagrant: 4.0, 4.1, 4.2, 4.3, 5.0, 5.1 A Vagrant update may also be available that adds support for the version you specified. Please check www.vagrantup.com/downloads.html to download the latest version. *** lucas@grr:/tmp/tEEQ$ dpkg -l |grep vagrant ii vagrant 1.9.1+dfsg-1+deb9u2all Tool for building and distributing virtualized development environments Lucas signature.asc Description: PGP signature
Bug#908826: vagrant/stable is incompatible with virtualbox/stretch-backports (now 5.2)
On Fri, Sep 14, 2018 at 05:10:48PM +0200, Lucas Nussbaum wrote: > Package: vagrant > Version: 1.9.1+dfsg-1+deb9u1 > Severity: normal > > Hi, > > vagrant 1.9.1+dfsg-1+deb9u1 is now incompatible with virtualbox from > stretch-backports (version 5.2.18-dfsg-1~bpo9+1). It worked fine with > virtualbox 5.1.30-dfsg-1~bpo9+1. > > vagrant from stretch-backports works fine with virtualbox from > stretch-backports. > > When starting vagrant, I get: > $ vagrant up > No usable default provider could be found for your system. > > Vagrant relies on interactions with 3rd party systems, known as > "providers", to provide Vagrant with resources to run development > environments. Examples are VirtualBox, VMware, Hyper-V. > > The easiest solution to this message is to install VirtualBox, which > is available for free on all major platforms. > > If you believe you already have a provider available, make sure it > is properly installed and configured. You can see more details about > why a particular provider isn't working by forcing usage with > `vagrant up --provider=PROVIDER`, which should give you a more specific > error message for that particular provider. > > (while of course virtualbox is available, and works fine outside of > Vagrant) Can you please test the .deb from https://people.debian.org/~terceiro/tmp/vagrant-stretch/ ? signature.asc Description: PGP signature
Bug#908826: vagrant/stable is incompatible with virtualbox/stretch-backports (now 5.2)
Package: vagrant Version: 1.9.1+dfsg-1+deb9u1 Severity: normal Hi, vagrant 1.9.1+dfsg-1+deb9u1 is now incompatible with virtualbox from stretch-backports (version 5.2.18-dfsg-1~bpo9+1). It worked fine with virtualbox 5.1.30-dfsg-1~bpo9+1. vagrant from stretch-backports works fine with virtualbox from stretch-backports. When starting vagrant, I get: $ vagrant up No usable default provider could be found for your system. Vagrant relies on interactions with 3rd party systems, known as "providers", to provide Vagrant with resources to run development environments. Examples are VirtualBox, VMware, Hyper-V. The easiest solution to this message is to install VirtualBox, which is available for free on all major platforms. If you believe you already have a provider available, make sure it is properly installed and configured. You can see more details about why a particular provider isn't working by forcing usage with `vagrant up --provider=PROVIDER`, which should give you a more specific error message for that particular provider. (while of course virtualbox is available, and works fine outside of Vagrant) Lucas -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (400, 'testing'), (300, 'unstable'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vagrant depends on: ii bsdtar 3.2.2-2 ii curl 7.52.1-5+deb9u6 ii openssh-client 1:7.4p1-10+deb9u3 ii ruby 1:2.3.3 ii ruby-bundler 1.16.1-2 ii ruby-childprocess 0.5.9-1 ii ruby-erubis2.7.0-3 ii ruby-i18n 0.7.0-2 ii ruby-listen3.0.3-3 ii ruby-log4r 1.1.10-4 ii ruby-net-scp 1.2.1-4 ii ruby-net-sftp 1:2.1.2-3 ii ruby-net-ssh 1:4.2.0-2 ii ruby-nokogiri 1.6.8.1-1 ii ruby-rb-inotify0.9.7-1 ii ruby-rest-client 1.8.0-3 vagrant recommends no packages. Versions of packages vagrant suggests: ii virtualbox 5.2.18-dfsg-1~bpo9+1 -- no debconf information
