Bug 410385 – app-admin/chef-solr could not start (unsatisfied net-ssh ~> 2.1.3 dependency)

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Julien Sanchez 2012-03-31 20:55:32 UTC]

chef-solr service fails to start with the following error:

# /etc/init.d/chef-solr start
 * Starting Chef SOLR ...
/usr/lib/ruby/site_ruby/1.8/rubygems.rb:779:in `report_activate_error': RubyGem version error: net-ssh(2.2.2 not ~> 2.1.3) (Gem::LoadError)
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:214:in `activate'
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:249:in `activate'
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:248:in `each'
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:248:in `activate'
	from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:35:in `require'
	from /usr/lib/ruby/gems/1.8/gems/chef-solr-0.10.8/lib/chef/solr/application/solr.rb:20
	from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
	from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
	from /usr/lib/ruby/gems/1.8/gems/chef-solr-0.10.8/bin/chef-solr:24
	from /usr/bin/chef-solr:8:in `load'
	from /usr/bin/chef-solr:8
 * start-stop-daemon: failed to start `/usr/bin/chef-solr'                                                                                               [ !! ]
 * ERROR: chef-solr failed to start


Chef gem spec needs net-ssh ~>2.1.3 (<2.2) but ebuild dependencies are:
chef-0.10.8 -> net-ssh-multi-1.1 -> >=net-ssh-2.1.4

As net-ssh-2.1.4 ebuild is not in portage, net-ssh-2.2 should be installed but it is not compatible with chef rubygem dependencies.

[Comment 1 Benedikt Böhm (RETIRED) 2012-04-02 05:04:32 UTC]

*sigh*

[Comment 2 Julien Sanchez 2012-04-02 12:25:48 UTC]

What's the preferred way to solve this sort of conflicts (according to Gentoo ruby project's policy)?

And just for my own curiosity, is there any reason net-ssh-2.1.4 to have been dropped instead of being stabilized?

[Comment 3 Hans de Graaff 2012-04-02 18:13:48 UTC]

(In reply to comment #2)
> What's the preferred way to solve this sort of conflicts (according to
> Gentoo ruby project's policy)?

We can solve this either by providing slots if the package really has incompatible API changes between version numbers, or we fix the dependencies of the requesting package. We do this because the 'every version is a slot' policy of rubygems doesn't work very well with how Gentoo handles packages.

> And just for my own curiosity, is there any reason net-ssh-2.1.4 to have
> been dropped instead of being stabilized?

As far as I can tell all 2.x versions are API compatible, so we aim to stable one of the 2.2.x versions instead.

[Comment 4 Julien Sanchez 2012-04-02 19:50:59 UTC]

(In reply to comment #3)
Thanks for your answer Hans.

I've found that next version of chef-related gems (0.10.10) will depend on net-ssh 2.2.

Until then, perhaps net-ssh-2.1.4 could be reintroduced in portage tree if possible?

[Comment 5 Benedikt Böhm (RETIRED) 2012-04-29 13:23:48 UTC]

chef-solr-0.10.10_beta1 is now in portage which should fix the dependency issues