Chef 10.28.0 adds ruby and rubygems 2.0 support, release info: http://www.getchef.com/blog/2013/09/03/chef-10-28-0-released/ I did not experiment with having both ruby19 and ruby20, but both may work. I believe this will also fix a couple other outstanding bugs related to chef: https://bugs.gentoo.org/show_bug.cgi?id=489916 https://bugs.gentoo.org/show_bug.cgi?id=484348 Reproducible: Always diff -u /usr/portage/app-admin/chef/chef-10.24.0.ebuild /usr/local/portage/vagrant/app-admin/chef/chef-10.28.0.ebuild --- /usr/portage/app-admin/chef/chef-10.24.0.ebuild 2013-03-01 11:17:14.000000000 -0800 +++ /usr/local/portage/vagrant/app-admin/chef/chef-10.28.0.ebuild 2014-04-14 11:49:55.630002253 -0700 @@ -3,7 +3,7 @@ # $Header: /var/cvsroot/gentoo-x86/app-admin/chef/chef-10.24.0.ebuild,v 1.1 2013/03/01 19:17:14 hollow Exp $ EAPI=4 -USE_RUBY="ruby19" +USE_RUBY="ruby20" RUBY_FAKEGEM_TASK_DOC="" RUBY_FAKEGEM_TASK_TEST="spec" @@ -30,7 +30,6 @@ dev-ruby/erubis >=dev-ruby/highline-1.6.9 >=dev-ruby/json-1.4.4 - <=dev-ruby/json-1.7.7 >=dev-ruby/mixlib-authentication-1.3.0 >=dev-ruby/mixlib-cli-1.1.0 >=dev-ruby/mixlib-config-1.1.2 @@ -38,7 +37,6 @@ dev-ruby/mixlib-shellout <dev-ruby/moneta-0.7.0 >=dev-ruby/net-ssh-2.6 - <dev-ruby/net-ssh-2.7 >=dev-ruby/net-ssh-multi-1.1 <dev-ruby/net-ssh-multi-1.2 >=dev-ruby/ohai-0.6.0
Just realized when I tested this I had some other custom ebuilds which let ruby20 work for chef's dependencies. Specifically, I added ruby20 to: dev-ruby/mixlib-authentication dev-ruby/mixlib-log dev-ruby/mixlib-config dev-ruby/moneta dev-ruby/rest-client dev-ruby/net-ssh-multi dev-ruby/ohai dev-ruby/ipaddress The ebuilds I am using can all be found at https://github.com/jcline/vagrant-1.5.2-overlay I'm not sure if it's better to make a new bug for each of those, or just use this one?
At this point, chef-11 should be the version we try to get stabilized. Especially with 12 coming soon and with it the deprecation of 10. Once 10 is deprecated, I would hope that it would shortly after be removed from the tree. Just my 2¢, ignore me if I'm insane.
My thinking was we might have chef-10 in a slot and chef-11 in a slot for people who are still using chef-10 for compatibility reasons. Maybe chef-11 is fully backwards compatible, though? I haven't tried it yet. I mainly did this because I needed to be able to upgrade to vagrant-1.4.2-r2 (the built-in docker plugin is broken on ruby19, it seems), which requires ruby20. This seemed like the quickest way to get chef working with that.
vagrant-1.4.3-r2*
*** This bug has been marked as a duplicate of bug 505992 ***
