[Rubygems-developers] rubygems / http://gems.rubyforge.org/ stability (RubyGems will revert to legacy indexes degrading performance)

Eric Hodel drbrain at segment7.net
Wed Sep 24 02:09:28 EDT 2008

On Sep 23, 2008, at 05:17 AM, Greg Hauptmann wrote:
> Macintosh-2:gems greg$ sudo gem install hobo --debug
> Exception `NameError' at
> /opt/local/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:134 -
> uninitialized constant Gem::Commands::InstallCommand
> Exception `Timeout::Error' at /opt/local/lib/ruby/1.8/timeout.rb:54 -
> execution expired
> Exception `Gem::RemoteFetcher::FetchError' at
> /opt/local/lib/ruby/site_ruby/1.8/rubygems/remote_fetcher.rb:142 -
> timed out (http://gems.rubyforge.org/latest_specs.4.8.gz)
> WARNING:  RubyGems 1.2+ index not found for:
> RubyGems will revert to legacy indexes degrading performance.
> Exception `Net::HTTPBadResponse' at
> /opt/local/lib/ruby/1.8/net/http.rb:2019 - wrong status line:
> "\037\213\b\000bw\330H

This exposed a bug where RubyGems needs to close the socket for timed- 
out requests (in case data arrives after the timeout, like the gzip  
data shown here).

Asside from that, how long does it take to get the WARNING message?

Can you run like:

gem install hobo --debug -V

I'd like to see if there's a particular host you're having a problem  

More information about the Rubygems-developers mailing list