Daniel Berger
10/27/2007 4:31:00 AM
Richard Kilmer wrote:
> We've identified the problem and its being fixed as we ... email :-)
I BROKE RUBYFORGE! Briefly.
In fact, the problem was me (unless it was the indexer, but I'm pretty
sure it was me). I uploaded a gem (win32-api 1.0.4) using a beta version
of rubygems, and that wreaked holy havoc.
Just in time for Leopard Day! Woohoo! :|
As luck would have it Tom and I were both on IRC, and the problem was
fixed about an hour after it was discovered. So a big thank you to Tom
Copeland! And also to Tim Pope (also on IRC) who figured out that it was
my gem causing the problem.
SORRY EVERYONE!!!
Hopefully you were all out drinking on a Friday night and never noticed.
Apologies,
Dan
PS - This will mean some discussion on the rubygems-devel list as far as
fixes and/or a release strategy. :)