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

Vagrant JSON Gem Dependency Conflict with Chef #326

Closed
thrillcall opened this Issue Mar 15, 2011 · 1 comment

Comments

Projects
None yet
2 participants
@thrillcall

thrillcall commented Mar 15, 2011

Please see the thread at :

http://groups.google.com/group/vagrant-up/browse_thread/thread/2efcdd37aedb9123

I tried to use a Bundler Gemfile to specify the gems I wanted
installed in the RVM gemset for my Vagrant machine. I build up the
Vagrant machine using Chef.

However, it seems that the latest Vagrant and Chef gems are specifying
conflicting versions of the JSON gem which prevents bundler from being
able to install the gems.

$ bundle install 
Fetching source index for http://rubygems.org/ 
Bundler could not find compatible versions for gem "json": 
  In Gemfile: 
    chef (= 0.9.12) depends on 
      json (>= 1.4.4, <= 1.4.6) 
    vagrant (= 0.7.2) depends on 
      json (1.5.1) 

Can you more flexibly specify a version >= 1.4.4 in the Vagrant
gemspec or do you really require JSON 1.5.1 only.

@mitchellh

This comment has been minimized.

Show comment
Hide comment
@mitchellh

mitchellh Mar 15, 2011

Member

Hello,

This has been brought up many times. The reason I lock onto 1.5.1 only is because thats the only JSON gem version that is working with Ruby 1.9 on Windows. So I must lock on specifically to that gem. :(

The chef guys are aware of it and I think there is an ongoing discussion of what to do about Chef's json dependency, which is the outdated one.

Mitchell

Member

mitchellh commented Mar 15, 2011

Hello,

This has been brought up many times. The reason I lock onto 1.5.1 only is because thats the only JSON gem version that is working with Ruby 1.9 on Windows. So I must lock on specifically to that gem. :(

The chef guys are aware of it and I think there is an ongoing discussion of what to do about Chef's json dependency, which is the outdated one.

Mitchell

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment