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.

Regards,

Peter

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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.1.2-10
ii  bundler            1.7.4-1
ii  curl               7.38.0-4
ii  openssh-client     1:6.7p1-3
ii  ruby               1:2.1.0.4
ii  ruby-childprocess  0.5.5-1
ii  ruby-erubis        2.7.0-3
ii  ruby-i18n          0.6.9-2
ii  ruby-listen        2.4.0-4
ii  ruby-log4r         1.1.10-4
ii  ruby-net-scp       1.2.1-1
ii  ruby-net-ssh       1:2.9.1-1
ii  ruby-nokogiri      1.6.3.1+ds-1
ii  ruby-rb-inotify    0.9.5-1

vagrant recommends no packages.

Versions of packages vagrant suggests:
ii  virtualbox  4.3.18-dfsg-2

-- no debconf information


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to