Ruby for Chef (Ruby 1.9.3-p125)


#1

After installing chef-client on CentOS6 system with Ruby 1.9.3-p125, chef-client -v returns the following:

chef-client -v

/usr/lib/ruby/gems/1.9.1/gems/systemu-2.2.0/lib/systemu.rb:29: Use RbConfig instead of obsolete and deprecated Config.
Chef: 0.10.8

Is the “deprecated Config” anything to worry about? How can I suppress this from each chef run?


#2

I believe there is an issue resolved with a patch supplied from one of
my staff: http://tickets.opscode.com/browse/OHAI-314

Next ohai release. :slight_smile:

Cheers,

–AJ

On 23 February 2012 09:25, Van Fossan,Randy vanfossr@oclc.org wrote:

After installing chef-client on CentOS6 system with Ruby 1.9.3-p125, chef-client -v returns the following:

chef-client -v

/usr/lib/ruby/gems/1.9.1/gems/systemu-2.2.0/lib/systemu.rb:29: Use RbConfig instead of obsolete and deprecated Config.
Chef: 0.10.8

Is the “deprecated Config” anything to worry about? How can I suppress this from each chef run?