# Problem with RubyForge and gems **URL:** \ **Category:** Ruby\ **Created:** [October 27, 2007, 5:58am UTC](https://www.ruby-forum.com/t/problem-with-rubyforge-and-gems/118459 "2007-10-27T05:58:32Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![rkoskela](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/ce73a5/32.png) [@rkoskela](https://www.ruby-forum.com/u/rkoskela)\ **Post date:** [October 27, 2007, 5:58am UTC](https://www.ruby-forum.com/t/problem-with-rubyforge-and-gems/118459/1 "2007-10-27T05:58:32Z")
All, Just to let you know there is an unknown problem right now with the gems service on RubyForge that folks thought was Leopard related but its not…I get the same thing in Tiger (and other OSes may get the same): gem search --remote jabber \*\*\* REMOTE GEMS \*\*\* Bulk updating Gem source index for: [http://gems.rubyforge.org](http://gems.rubyforge.org) ERROR: While executing gem … (TypeError) can’t instantiate uninitialized class We will identify the problem as soon as is possible and fix it…just want to let folks know so you can know that your shinny new OS is OK 😉 Best, Rich ---
**Author:** ![rkoskela](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/ce73a5/32.png) [@rkoskela](https://www.ruby-forum.com/u/rkoskela)\ **Post date:** [October 27, 2007, 6:04am UTC](https://www.ruby-forum.com/t/problem-with-rubyforge-and-gems/118459/2 "2007-10-27T06:04:57Z")
We’ve identified the problem and its being fixed as we … email 🙂 Go Tom! -rich ---
**Author:** ![rkoskela](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/ce73a5/32.png) [@rkoskela](https://www.ruby-forum.com/u/rkoskela)\ **Post date:** [October 27, 2007, 6:31am UTC](https://www.ruby-forum.com/t/problem-with-rubyforge-and-gems/118459/3 "2007-10-27T06:31:14Z")
Richard K. 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. 🙂 ---
**Author:** ![rkoskela](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/ce73a5/32.png) [@rkoskela](https://www.ruby-forum.com/u/rkoskela)\ **Post date:** [October 27, 2007, 6:33am UTC](https://www.ruby-forum.com/t/problem-with-rubyforge-and-gems/118459/4 "2007-10-27T06:33:00Z")
On Oct 26, 2007, at 10:04 PM, Richard K. wrote: > We’ve identified the problem and its being fixed as we … email 🙂 thanks a million guys - you are heros. a @ [http://codeforpeople.com/](http://codeforpeople.com/) ---
**Author:** ![rkoskela](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/ce73a5/32.png) [@rkoskela](https://www.ruby-forum.com/u/rkoskela)\ **Post date:** [October 27, 2007, 6:38am UTC](https://www.ruby-forum.com/t/problem-with-rubyforge-and-gems/118459/5 "2007-10-27T06:38:50Z")
From: Daniel B. [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] # I BROKE RUBYFORGE! Briefly. that is interesting. how could one gem bring down the whole repository?? (dangerous, so to speak) thanks and kind regards -botp ---
**Author:** ![rkoskela](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/ce73a5/32.png) [@rkoskela](https://www.ruby-forum.com/u/rkoskela)\ **Post date:** [October 27, 2007, 6:54am UTC](https://www.ruby-forum.com/t/problem-with-rubyforge-and-gems/118459/6 "2007-10-27T06:54:36Z")
Peña wrote: > From: Daniel B. [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] > > # I BROKE RUBYFORGE! Briefly. > > that is interesting. how could one gem bring down the whole repository?? (dangerous, so to speak) > > thanks and kind regards -botp I’m not entirely sure yet. It may have been because I used a new constant (Gem::Platform::CURRENT I think) for the gem.platform, which isn’t supported by 0.9.4 afaik. We’ll have to discuss this on the list and keep everyone posted. In the meantime, the RF gem indexer won’t run for 24 hours, just to make sure no one else does the same thing and has time to see this message and/or the one on rubygems-devel. Regards, Dan