[chef] Re: Re: Re: Re: Re: EPEL repository (Redhat/Centos) breaks chef after 9/15

[Paul Choi < >]

 That's a great idea. I second that.
Another method is to use "yum --downloadonly install chef" to download 
the RPM and its dependencies. Then you can put them in your own 
repository if you are already maintaining your own set of RPMs. I've 
been doing that for 0.8.16 and then 0.9.6. As Sean wrote earlier, it's 
good practice to lock down the libraries you use.

-Paul

On 9/17/10 3:10 PM, Matthew Kent wrote:
> On Fri, 2010-09-17 at 11:14 -0400, Sean OMeara wrote:
> > I'm gonna go ahead and point out that it's considered best practice to
> > maintain a private package repository for exactly these reasons.
> Given the sheer number of packages involved in the chef server setup and
> the potential for breakage like this json issue I'd highly recommend
> anyone using it to rsync a stable copy of the whole repo and use plugins
> like yum priorities to make use of it's contents.
>
> http://elff.viviti.com/packages has links for rsync.
>
> The original issue should be fixed by updated packages I just pushed. I
> patched out the mandatory old json version and built a copy of the
> latest json for ELFF.
>
> I've also filed a ticket for an update in Fedora which should trickle
> down to EPEL later @
> https://bugzilla.redhat.com/show_bug.cgi?id=635034