On Friday, April 4, 2014 12:40:44 PM UTC-7, Tom Poulton wrote: > > I was running into this problem as well so I ran: > > *sudo cp -r /usr/lib/ruby/site_ruby/1.8/* > /usr/local/share/ruby/site_ruby/2.0/* > > /usr/local/share/ruby/site_ruby/2.0/ is part of the $LOAD_PATH so I > figured why not stick the files in there and see what happens, now I can > run *puppet --version* plus *facter ipaddress* etc. That's all I've run > so far so there might be some weirdness down the line, but it's a start!? > > It would be better if it was a symlink or something so you wouldn't have > to run this again after a yum update, but hopefully puppetlabs will ralease > a new RPM soon that works, I'm guessing they will now that AWS are running > ruby 2.0.0 as default!? >
The Puppet Labs EL 6 repos are designed to be compatible with RHEL 6.x and CentOS 6.x which will remain on Ruby 1.8.7 for the rest of their lifetimes. By upgrading the default Ruby to 2.0, Amazon Linux has broken compatibility with EL 6. Puppet Labs probably won't be able to compensate for this in the EL 6 repos due to the need to stay compatible with systems running 1.8.7. Renaming the site_ruby directory may bring varying degrees of success, but the puppet package has at least two dependencies, ruby-augeas and ruby-shadow, that contain extensions that have been compiled against the Ruby 1.8.7 libraries. The only way to achieve compatibility in these cases is to re-build the packages against Ruby 2.0.0. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1b2c7286-b8c9-4234-afc9-8903ec188b68%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
