On Mar 31, 2009, at 01:10, aslak hellesoy wrote:
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.
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).
A better solution would be to patch Rubygems so it doesn't choke
just because you have a broken gem - or at least tell you which one
it is.
Without details about how your gems were broken this can't be fixed.
PS: Don't send HTML email to lists, it sucks.
_______________________________________________
Rubygems-developers mailing list
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers
