[Rubygems-developers] 'gem update' Fails, but 'gem update X' Works

Eric Hodel drbrain at segment7.net
Thu Jul 23 18:00:15 EDT 2009


On Jul 23, 2009, at 07:01, Randy Parker wrote:

>> Eric wrote:
>> Looks like you have some kind of network issue
> I've had the same update behavior
> 100% of the time for almost a month using 2 different connections
> located 10 miles apart.  One is Comcast, the other is a CBeyond
> T1.   And don't forget that 3 out of 4 of the guys in the Atlanta Ruby
> Users Group that responded to my IRC request for confirmation reported
> the exact same problem.  The probability of a network problem whose
> sole manifestation is "gem update" is very low.

At the same time, only four people out of thousands (or more?) are  
reporting this issue...

>> Can you run:  $ sudo gem update -V --debug
>
> ~ $ gem --version
> 1.3.5
>
>
> ~ $ sudo gem update -V --debug
> Password:
> Exception `NameError' at
> /Library/Ruby/Site/1.8/rubygems/command_manager.rb:161 - uninitialized
> constant Gem::Commands::UpdateCommand
> Exception `Gem::LoadError' at /Library/Ruby/Site/1.8/rubygems.rb:827  
> - Could
> not find RubyGem test-unit (>= 0)
>
> Updating installed gems
> GET 200 OK: http://gems.rubyforge.org/latest_specs.4.8.gz
> GET 200 OK: http://gems.github.com/latest_specs.4.8.gz
> Updating crack
> Exception `Errno::EPIPE' at
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/ 
> 1.8/net/protocol.rb:175
> - Broken pipe
> Exception `Gem::RemoteFetcher::FetchError' at
> /Library/Ruby/Site/1.8/rubygems/remote_fetcher.rb:172 -  
> Errno::EPIPE: Broken
> pipe (http://gems.rubyforge.org/quick/Marshal.4.8/crack-0.1.4.gemspec.rz 
> )

Does adding Errno::EPIPE to line 340 of lib/rubygems/remote_fetcher.rb  
in #request help?  Looks like somebody is closing the connection on  
you early...


More information about the Rubygems-developers mailing list