[chef] Re: Re: Re: Re: chef-client gem install --pre doesn't find second level dependencies?

[KC Braunschweig < >]

What version of rubygems is required?

ERROR:  While executing gem ... (RuntimeError)
    gem update --system is disabled on Debian. RubyGems can be updated
using the official Debian repositories by aptitude or apt-get.


On Wed, Apr 20, 2011 at 2:28 PM, Adam Jacob 
<
 >
 wrote:
> I believe you need to upgrade rubygems - can you tell me what happens
> if you do a gem update --system?
>
> On Wed, Apr 20, 2011 at 12:07 PM, KC Braunschweig
> <
 >
>  wrote:
>> 
 :~$
>>  ruby -v
>> ruby 1.8.7 (2010-01-10 patchlevel 249) [x86_64-linux]
>>
>> 
 :~$
>>  gem -v
>> 1.3.5
>>
>>
>> On Tue, Apr 19, 2011 at 5:17 PM, Mark J. Reed 
>> <
 >
>>  wrote:
>>> That might make sense on RHEL <= 5, but Ubuntu 10.04 comes with a
>>> pretty recent ruby - your choice of 1.8.7 or 1.9.2, IIRC.
>>>
>>> On Tuesday, April 19, 2011, Adam Jacob 
>>> <
 >
>>>  wrote:
>>>> What version of ruby are you using, KC? I think this is actually
>>>> caused by Rubygems no longer supporting particular versions of ruby.
>>>>
>>>> Adam
>>>>
>>>> On Tue, Apr 19, 2011 at 4:41 PM, KC Braunschweig
>>>> <
 >
>>>>  wrote:
>>>>> Am I missing something here? I've tried a few times now doing a clean
>>>>> install of chef only for client install purposes on both RHEL and
>>>>> ubuntu (10.04) using rubygems. It seems that it when installing a
>>>>> prerelease version, you can't find second level dependencies or
>>>>> something like that?
>>>>>
>>>>> Specifically you get things like:
>>>>>
>>>>> 
 :~$
>>>>>  sudo gem install chef --pre -y
>>>>> INFO:  `gem install -y` is now default and will be removed
>>>>> INFO:  use --ignore-dependencies to install only the gems you list
>>>>> ERROR:  Error installing chef:
>>>>>        mixlib-authentication requires mixlib-log (>= 0, runtime)
>>>>>
>>>>> Clearly it resolved that chef needs mixlib-authentication but then it
>>>>> couldn't find mixlib-log ?? But that is there and you can install it
>>>>> explicitly, but only if you don't pass --pre
>>>>>
>>>>> 
 :~$
>>>>>  sudo gem install mixlib-log --pre
>>>>> ERROR:  could not find gem mixlib-log locally or in a repository
>>>>>
>>>>> 
 :~$
>>>>>  sudo gem install mixlib-log
>>>>> Successfully installed mixlib-log-1.3.0
>>>>> 1 gem installed
>>>>> Installing ri documentation for mixlib-log-1.3.0...
>>>>> Installing RDoc documentation for mixlib-log-1.3.0...
>>>>>
>>>>> Maybe most folks upgraded from chef 0.9x so they didn't notice, but
>>>>> this is irritating. Seems like I have to manually specify all the
>>>>> dependencies that don't have a prerelease version first and then I can
>>>>> install chef --pre? I know this will go away once all the chef bits
>>>>> aren't in prerelease anymore, but if this is a gem weirdness, it'll
>>>>> just keep happening. On the other hand, I might just be missing
>>>>> something that would make this a non-issue.
>>>>>
>>>>> KC
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Opscode, Inc.
>>>> Adam Jacob, Chief Product Officer
>>>> T: (206) 619-7151 E: 
>>>> 
 
>>>>
>>>
>>> --
>>> Mark J. Reed 
>>> <
 >
>>>
>>
>
>
>
> --
> Opscode, Inc.
> Adam Jacob, Chief Product Officer
> T: (206) 619-7151 E: 
> 
 
>