engineyard/engineyard — comment on commit ae599b587dff37e8bc81c0e31c603bfb085437aa
File:  line 0
By martinemde:

This is just a problem I've run into many times depending on how the ruby on that particular machine was built. rvm hasn't always built correctly to prevent this issue, and with the many various machines with different versions of ruby it's easy to mistakenly release a broken gem.

I didn't mean for this to be passive aggressive. It's a problem that's been easy to cause lately. It's just unfortunate that there was ever a version of rubygems that resulted in this error, even if newer versions don't. I assume it will clear up as we get all our development machines running good versions of rubygems. (I found the issue in the rubygems repo that talks about this problem, Evan thinks he has it fixed once and for all. This has been my experience with my last 1.9.3 releases with the newest rubygems.)