search

WinRb / vagrant-windows

Other
444 stars 83 forks source link

Why is Vagrant 1.7.4 insisting on having vagrant-windows installed when it's deprecated? #202

Closed pjscopeland closed 9 years ago

pjscopeland commented 9 years ago

Disclaimer: I know this plugin is deprecated. Vagrant, though, apparently doesn't.

Here's what I'm doing, on Ubuntu Trusty:

$ vagrant -v
Vagrant 1.7.4
$ vagrant init -fm opentable/win-7-professional-amd64-nocm
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
$ vagrant up --provider virtualbox
vagrant-windows missing, please install the vagrant-windows plugin!
Run this command in your terminal:
vagrant plugin install vagrant-windows
$ vagrant plugin install vagrant-windows
Installing the 'vagrant-windows' plugin. This can take a few minutes...
The plugin(s) can't be installed due to the version conflicts below.
This means that the plugins depend on a library version that conflicts
with other plugins or Vagrant itself, creating an impossible situation
where Vagrant wouldn't be able to load the plugins.

You can fix the issue by either removing a conflicting plugin or
by contacting a plugin author to see if they can address the conflict.

Vagrant could not find compatible versions for gem "winrm":
  In Gemfile:
    vagrant (= 1.7.4) ruby depends on
      winrm (~> 1.3) ruby

    vagrant (= 1.7.4) ruby depends on
      winrm-fs (~> 0.2.0) ruby depends on
        winrm (~> 1.3.0) ruby

    vagrant-windows (>= 0) ruby depends on
      winrm (~> 1.1.1) ruby
Vagrant could not find compatible versions for gem "vagrant":
  In Gemfile:
    vagrant-windows (>= 0) ruby depends on
      vagrant (~> 1.0.3) ruby

    vagrant (= 1.7.4) ruby

And everything I see on vagrant-windows says it's not needed any more. So why is Vagrant insisting on having it? And more to the point, how do I stand up my VM?

sneal commented 9 years ago

The error message is coming from the Vagrantfile that's embedded in the box. You have 3 options:

  1. Use a different box. One that doesn't check for vagant-windows.
  2. Unpackage the box, remove the offending line in the Vagrantfile and repackage.
  3. Downgrade to an older version of Vagrant and use vagrant-windows.