I'm curious whether this happens in a pre-1.7 version of
RubyGems. The RubyGems API changed and we had to make some
modifications to keep up, but my guess is those changes don't
always work. If you use 1.3.7 (gem update --system
1.3.7), does the error still occur?
A conversation has been started with the RubyGems.org staff to resolve this discussion.