[chef] Re: json gem conflict

[Morgan Blackthorne < >]

I think this scenario is the exact type of situation the omnibus installs are trying to prevent.

On Wednesday, May 8, 2013, Sam Darwin  wrote:
> What's interesting here is that the dependency is not for some 3rd
> party package, but for chef itself.    chef-client is using the
> route53 recipe, which is using the fog gem, which is using the json
> gem.   A new json gem does get installed during the chef run.   But at
> the time chef-client started, it wasn't yet there.    Perhaps the
> chef-client's ruby process won't re-read and use new gems during that
> single chef run.    It simply must run a second time.     not sure if
> that's the case.


-- 
--

~*~ StormeRider ~*~

"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."

(from Smallville Season 6x1: "Zod")

On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS