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

[Sean OMeara < >]

I'm gonna go ahead and point out that it's considered best practice to
maintain a private package repository for exactly these reasons.


-s


On Fri, Sep 17, 2010 at 7:33 AM, Jonathan Matthews
<
 >
 wrote:
> On 16 September 2010 21:34, Matthew Kent 
> <
 >
>  wrote:
>> On Thu, 2010-09-16 at 01:42 -0500, Leinartas, Michael wrote:
>>> This is half a warning and half a note to Matthew Kent who so
>>> graciously packages up Chef for Redhat/CentOS systems.
>>>
>>> Today an update went out to EPEL to add rubygem-json 1.4.3.  For those
>>> of us using the combination of EPEL and ELFF (mkent's repo)
>>> repositories, this updates rubygem-json from 1.1.9 (from ELFF).
>>>  Unfortunately, Chef and Ohai need versions less than or equal to
>>> 1.4.2, so Rubygems will refuse to load the chef and ohai gems.
>>
>> Thanks! I'll certainly look at updating the packages shortly and likely
>> just carry the working version of rubygem-json in ELFF.
>
> Given a basic installation of EPEL+ELFF, will the presence of <1.4.3
> in ELFF alongside the current 1.4.3 in EPEL not result in 1.4.3 being
> used?
>
> [I'm aware of the repo prioritisation and yum cli parameters that
> could be used to help with this; I'm just interested in the
> non-customised situation which might be reasonable/expected given a
> pre-chef-install environment]
>
> Jonathan
> --
> Jonathan Matthews
> London, UK
> http://www.jpluscplusm.com/contact.html
>