Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflict with latest version of Vagrant #28

Open
daddyschmack opened this issue Jan 6, 2016 · 3 comments
Open

Conflict with latest version of Vagrant #28

daddyschmack opened this issue Jan 6, 2016 · 3 comments

Comments

@daddyschmack
Copy link

Hello, I'm trying to install this plugin with the version of vagrant I just downloaded and installed, and I receive the below message, what information can I provide to help solve this issue? I just upgraded after receiving a similar message with net-ssh 3.02, and no luck.

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 "net-ssh":
In Gemfile:
vagrant (= 1.8.1) ruby depends on
net-ssh (~> 3.0.1) ruby

vagrant (= 1.8.1) ruby depends on
  net-scp (~> 1.1.0) ruby depends on
    net-ssh (>= 2.6.5) ruby

vagrant (= 1.8.1) ruby depends on
  net-scp (~> 1.1.0) ruby depends on
    net-ssh (>= 2.6.5) ruby

vagrant-librarian-chef (>= 0) ruby depends on
  librarian-chef (>= 0) ruby depends on
    chef (>= 0.10) ruby depends on
      net-ssh (~> 2.1.3) ruby
@dskvr
Copy link

dskvr commented Jan 21, 2016

Have the same issue.

@djvdorp
Copy link

djvdorp commented Feb 10, 2016

Same here, downgraded back to Vagrant 1.7.4 for now

@jimmycuadra
Copy link
Owner

Sorry for the trouble, but this plugin is not maintained anymore. I'd recommend looking into Berkshelf as a replacement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants