Control: tag -1 + confirmed

On Sun, Mar 08, 2015 at 10:42:34AM -0500, Peter Gallagher wrote:
> Package: vagrant
> Version: 1.6.5+dfsg1-2
> Severity: important
> 
> Dear Maintainer,
> 
> When attempting to boot a Windows VirtualBox image with Vagrant using 
> `config.vm.communicator = "winrm"` Vagrant exits with the following error:
> 
>     /usr/share/vagrant/plugins/communicators/winrm/shell.rb:9:in `require': 
> cannot load such file -- winrm (LoadError)
>         from /usr/share/vagrant/plugins/communicators/winrm/shell.rb:9:in 
> `block in <top (required)>'
>         from /usr/lib/ruby/vendor_ruby/vagrant/util/silence_warnings.rb:8:in 
> `silence!'
>         from /usr/share/vagrant/plugins/communicators/winrm/shell.rb:8:in 
> `<top (required)>'
>         from 
> /usr/share/vagrant/plugins/communicators/winrm/communicator.rb:6:in 
> `require_relative'
>         from 
> /usr/share/vagrant/plugins/communicators/winrm/communicator.rb:6:in `<top 
> (required)>'
>         from /usr/share/vagrant/plugins/communicators/winrm/plugin.rb:15:in 
> `require'
>         from /usr/share/vagrant/plugins/communicators/winrm/plugin.rb:15:in 
> `block in <class:Plugin>'
>         from /usr/lib/ruby/vendor_ruby/vagrant/registry.rb:27:in `call'
>         from /usr/lib/ruby/vendor_ruby/vagrant/registry.rb:27:in `get'
>         from /usr/lib/ruby/vendor_ruby/vagrant/machine.rb:217:in `communicate'
>         from /usr/lib/ruby/vendor_ruby/vagrant/machine.rb:134:in `initialize'
>         from /usr/lib/ruby/vendor_ruby/vagrant/vagrantfile.rb:75:in `new'
>         from /usr/lib/ruby/vendor_ruby/vagrant/vagrantfile.rb:75:in `machine'
>         from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:503:in `machine'
>         from /usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:168:in 
> `block in with_target_vms'
>         from /usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:192:in 
> `call'
>         from /usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:192:in 
> `block in with_target_vms'
>         from /usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:174:in 
> `each'
>         from /usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:174:in 
> `with_target_vms'
>         from /usr/share/vagrant/plugins/commands/up/command.rb:67:in `block 
> in execute'
>         from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:239:in `block 
> (2 levels) in batch'
>         from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:237:in `tap'
>         from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:237:in `block 
> in batch'
>         from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:236:in 
> `synchronize'
>         from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:236:in `batch'
>         from /usr/share/vagrant/plugins/commands/up/command.rb:58:in `execute'
>         from /usr/lib/ruby/vendor_ruby/vagrant/cli.rb:42:in `execute'
>         from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:258:in `cli'
>         from /usr/bin/vagrant:173:in `<main>'
> 
> Attempting to install the winrm GEM manually does not change the behaviour. 
> The
> DEB package provided at https://www.vagrantup.com/download-archive/v1.6.5.html
> does not display this behaviour and works as expected.

winrm is not packaged in Debian, and since I didn't have interest in
having Windows guests, I didn't go through the trouble of packaging it
and disabled the explicit dependency on it.

When winrm is packaged and in the archive, just let me know and I will
update vagrant to depend on it.

-- 
Antonio Terceiro <terce...@debian.org>

Attachment: signature.asc
Description: Digital signature

Reply via email to