[chef] Re: Re: Gem install on Ubuntu 12

[Ash Berlin < >]

Doing that would change the system ruby to the one installed by omnibus which defeats many of the purposes of installing another non-system ruby for use with chef.

-ash

On 23 Jul 2012, at 05:48, Morgan Blackthorne wrote:

I think the thing is, if you want to run Chef with Ubuntu 12, you want to switch the default version of ruby away from ruby1.8. So you'd want to do "update-alternatives --config ruby" to point the default to ruby1.9 (and associated binaries such as "gem", "ri", "rdoc", etc.).

~*~ StormeRider ~*~

"With hearts immortal, we stand before our lives
A soul against oblivion, forever asking why
This upside down symphony in a paradox called life
Our hearts immortal
What you give to love, will never die"

On Sun, Jul 22, 2012 at 9:29 PM, Steve Bennett < " target="_blank"> > wrote:

Hi all,

  This is a bug report/heads up, not a support request - my issue is solved.

I ran into an issue a couple of days ago with the default (omnibus?) chef-client install on Ubuntu 12.04. Basically, it somehow ends up with two versions of Gems (or just Ruby? - I'm not a Ruby person) installed, in different locations: Gems 1.8 in /var/lib/gems, and 1.9.1 somewhere else (/opt/...something...chef-embedded I think). The upshot of this was that a cookbook that worked on Ubuntu 10.04 didn't work - a postgres gem ("pg") installed, but couldn't be found by a later step that required it. It was present, but not available to the ruby environment in use at the time.

People on IRC helped with a workaround: installing chef-client with the specific distribution, "-d ubuntu12.04".

I'm just mentioning this so the relevant people are aware and can hopefully fix it. The recipe I ran into problems with is here: https://github.com/stevage/mytardis-chef

Steve