On Mar 31, 2009, at 13:32, Bryan Richardson wrote:
> On 3/31/09, Daniel Berger <djberg96 / gmail.com> wrote:
>> On Mar 31, 8:57 am, Dominic Sisneros <dsisn... / gmail.com> wrote:
>>> the update to mojombo-grit is the problem.  Here is Aslax Hellesoy
>>> response
>>> to my inquiry on the rubygems mailing list
>>>
>>> 2009/3/31 Dominic Sisneros <dsisn... / gmail.com>
>>>
>>>> I did a gem cleanup and since then I have been getting the  
>>>> following
>>>> error
>>>> whenever I try to use a gem
>>>
>>> I had the same problem yesterday, when I upgraded all my gems. It  
>>> turns
>>> out,
>>> this error occurs if you have one broken gem.
>>
>> I've tried to duplicate this but I can't. I installed grit 1.0.0,  
>> then
>> grit 1.1.0, then ran "gem clean", then fired up irb and loaded a gem.
>> I didn't have any problems.
>>
>> I'm curious in what way the gem is broken. The require_paths appears
>> to just be set to 'lib', which is fine.
>>
>>> My solution: Add a puts statement inside gem_path_searcher.rb to  
>>> find out
>>> what gem is broken. Then uninstall it. (For me it was the latest
>>> mojombo-grit).
>>>
>>> And here is the result of the puts
>>>
>>> #<Gem::Specification name=mofo version=0.2.16>
>>> #<Gem::Specification name=mojombo-grit version=1.1.0>
>>> load error: C:/Documents and Settings/dominic e sisneros/.irbrc
>>
>> This is interesting, and might be a clue as to the real problem.  
>> Could
>> spaces in the path name be an issue? I'm not sure. What does
>> your .irbc file look like? Also, do you have any non-ascii characters
>> in the path to the .irbc file?
>>
>>> NoMethodError: undefined method `join' for nil:NilClass
>>
>> Looks like spec.require_paths is returning nil, which is very odd.
>> Like I said, I can't duplicate this, and I'm not sure how that could
>> happen.
>
> I am getting the exact same NoMethodError having to do with calling
> 'join' on a nil class. I'm on a linux machine with no spaces in path
> names. I haven't had a chance to try printing stuff out in Rubygems
> yet...

If you figure out which gem is doing it, please send the gemspec from  
the specifications/ dir and a tarball of the gem from the gems/ dir.