chef includes the following dependencies. >=dev-ruby/net-ssh-2.1.3 <dev-ruby/net-ssh-2.2 >=dev-ruby/net-ssh-multi-1.1 <dev-ruby/net-ssh-multi-1.2 net-ssh-multi depends on ">=dev-ruby/net-ssh-2.1.4" so 2.1.4 is the only version of net-ssh that can satisfy both of these. Except that graaff culled this version from the tree a little while ago. I think he actually meant to remove 2.1.3, which is still in the tree. It's also worth noting that it's impossible to install this version of chef together with dev-ruby/capistrano-2.9.0 if the latter has ruby19 enabled. It also depends on net-ssh but only the ebuilds for 2.2 and later include ruby19. It may be worth adding ruby19 to 2.1.4, if indeed it does work with this version of Ruby.
I did mean to remove 2.1.4. 2.1.3 can't be removed since it is the latest stable version for most arches. chef should fix its dependencies to match the slots we use within Gentoo, or bugs should be filed to create new slots. From the ruby side we'll only support that if it is really needed, i.e. if there are actual compatibility issues.
these are the dependencies require by the gemspec. please fix the ruby mess yourself
Created attachment 302633 [details, diff] chef-0.10.8.ebuild patch Patch from flameeyes that works for me. It looks like the deps from the gems are incorrect. 99.999% positive this all works without issue.
for the sake of making this work vs. using the correct dependencies, i've commited your patch. still the ruby team should fix their mess :-(
(In reply to comment #4) > for the sake of making this work vs. using the correct dependencies, i've > commited your patch. still the ruby team should fix their mess :-( There is nothing to fix, the real mess is with rubygems itself which considers each individual version a slot and then happily overwrites files in them. In Gentoo we have chosen to create slots only for API-incompatible versions, but obviously this may require changes in gemspec files. So if chef exposes an API incompatibility in a package that we haven't slotted then we can fix that. In this case it looks like chef has put in premature guards against newer versions. We see that in more gems and usually these are wrong.
