From: Ryan Davis <ryand-ruby@...>
Date: 2009-09-11T05:57:23+09:00
Subject: Re: Ruby 1.9, Rubygems, and .gemspec warnings


On Sep 10, 2009, at 13:50 , Ryan Davis wrote:

>
> On Sep 10, 2009, at 13:42 , Rob Sanheim wrote:
>
>> I don't think so, I can reproduce this without jeweler in the mix  
>> at all.
>> bug:
>> http://rubyforge.org/tracker/index.php?func=detail&aid=27087&group_id=126&atid=575
>>
>> code:
>> http://github.com/rsanheim/ruby19_rubygems_bug/blob/09a9f683fe7848980e10ac7bd2291040ec11ea17/Rakefile
>>
>> failing build against ruby 1.9:
>> http://runcoderun.com/rsanheim/ruby19_rubygems_bug/builds/09a9f683fe7848980e10ac7bd2291040ec11ea17/1/ruby_191
>
> I just repro'd this with:
>
>> % multiruby -rubygems -rrubygems/specification -e 0
>> ...
>> VERSION = 1.9.1-p129
>> CMD     = ~/.multiruby/install/1.9.1-p129/bin/ruby -rubygems - 
>> rrubygems/specification -e 0
>>
>> WARNING:  #<NoMethodError: undefined method `>' for nil:NilClass>
>> ...
>> RESULT = 0
>>
>> TOTAL RESULT = 0 failures out of 4
>>
>> Passed: 1.9.1-p129, 1.8.7-p72, 1.8.7-p160, 1.8.6-p368
>> Failed:
>
> That's easy enough to poke around at. I'll get eric's eyeballs on it.

OK... Just figured it out. Something bad juju with 1.9's gem_prelude  
vs rubygems. Easy fix:

% sudo gem uninstall rubygems-update

then this should work:

% multiruby -rubygems -rrubygems/specification -e 'gem "hoe"'