- From: Michael Stillwell <
>
- To:
- Subject: [chef] chef, CentOS/RedHat, and rubygem-rest-client updates
- Date: Fri, 25 Mar 2011 12:07:38 +0000
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=FedTq6zML6XKJaFRjz3us7kVbqU+a6UbYtrRpfRGrdac4g0mi3Tx2ZkxpwOaEqH9La aI2pR/X3v90VK/zjdBTE9/w5oJT0FC+6/j1FfD9M8d88cRj0G/CzFnoimGYGwAC8jkKk s4KQJow2q1ptYgxiw+j3dUsa5W/JGv5xO0Dy0=
What's the status of chef on CentOS/RedHat? We've currently installed
chef as described at
http://wiki.opscode.com/display/chef/Installation+on+RHEL+and+CentOS+5+with+RPMs
but I get the feeling that chef isn't very well supported on
CentOS/RedHat. For example, the latest RPM packaged version is 0.9.8,
which is quite old, and isn't packaged by Opscode anyway. (Unlike the
Debian/Ubuntu packages.) One of its dependencies is
rubygem-rest-client (from EPEL), and this was updated to version 1.6.1
in the last day or so, which breaks chef-client 0.9.8:
# chef-client
/usr/lib/ruby/site_ruby/1.8/rubygems.rb:827:in
`report_activate_error': RubyGem version error: rest-client(1.6.1 not
>
= 1.0.4, <= 1.5.1) (Gem::LoadError)
from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:261:in `activate'
from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:296:in `activate'
from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:295:in `each'
from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:295:in `activate'
from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:68:in `gem'
from /usr/bin/chef-client:18
Will chef + CentOS be a viable combination in the future, or should I
look to moving to a different distribution? (Or figure out how to
install/package chef myself, which might be about as much work...)
Cheers,
Michael
--
http://beebo.org
- [chef] chef, CentOS/RedHat, and rubygem-rest-client updates, Michael Stillwell, 03/25/2011
Archive powered by MHonArc 2.6.16.