On Friday, April 4, 2014 9:50:59 PM UTC+2, Nick Cammorato wrote:
>
> Did anyone try using the EL7 RPM? I've had success with testing with it
> in the RHEL7 beta, so if amazon has moved closer to RHEL7, it should be
> worth a shot.
>
Using the EL7 RPM does not work on the 2014 Amazon Linux AMI
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 stic
Did anyone try using the EL7 RPM? I've had success with testing with it in
the RHEL7 beta, so if amazon has moved closer to RHEL7, it should be worth
a shot.
--Nick
On Fri, Apr 4, 2014 at 3:40 PM, Tom Poulton wrote:
> I was running into this problem as well so I ran:
>
> *sudo cp -r /usr/lib/
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*
I ran into the same issue this weekend, and discovered that the Amazon yum
repo's latest Puppet package (2.7.25) has ruby1.8 "shebang'd". With that
puppet release, you can have ruby2.0 on the system as the default and still
have puppet running correctly. If your hosts are running the puppet ag
ok. So for anyone else digging for this issue:
Amazon Linux just did an update to be closer to what RHEL7 will look like,
which means they dropped a default install of ruby 1.8.x
The Puppet RPM package is compiled against RHEL5/6 which has ruby 1.8.x.
So it drops a ton of its dependencies into /
