The gemspec file, which is parsed when vagrant is started to load the dependencies, states: s.add_runtime_dependency(%q<json>, ["< 1.8.0", ">= 1.5.1"]) which translates to: >=dev-ruby/json-1.5.1 <dev-ruby/json-1.8.0 The ebuild should enforce this to prevent the installation with json-1.8.0, which causes vagrant to be unusable. Reproducible: Always Steps to Reproduce: 1. Install Vagrant with dev-ruby/json-1.8.0 2. Type `vagrant` in a terminal Actual Results: /usr/lib64/ruby/site_ruby/1.9.1/rubygems/dependency.rb:296:in `to_specs': Could not find 'json' (< 1.8.0, >= 1.5.1) - did find: [json-1.8.0] (Gem::LoadError) from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/specification.rb:1196:in `block in activate_dependencies' from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/specification.rb:1185:in `each' from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/specification.rb:1185:in `activate_dependencies' from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/specification.rb:1167:in `activate' from /usr/lib64/ruby/site_ruby/1.9.1/rubygems.rb:181:in `rescue in try_activate' from /usr/lib64/ruby/site_ruby/1.9.1/rubygems.rb:178:in `try_activate' from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:109:in `rescue in require' from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:35:in `require' from /usr/lib64/ruby/gems/1.9.1/gems/vagrant-1.2.2/bin/vagrant:9:in `<top (required)>' from /usr/bin/vagrant:8:in `load' from /usr/bin/vagrant:8:in `<main>' Expected Results: No immediate crash
Created attachment 352788 [details] cave info vagrant json ruby rubygems output of `cave info vagrant json ruby rubygems`
Forgot to state that adding <dev-ruby/json-1.8.0 to the ebuild fixes this for me. A patch will be there in a second.
Created attachment 352794 [details, diff] Adds <dev-ruby/json-1.8.0 to rdepend
Fixed in 1.2.2-r1.
:)