From: Eric Hodel Date: 2008-06-26T06:08:27+09:00 Subject: Re: [ANN] RubyGems 1.2.0 On Jun 23, 2008, at 13:33 PM, Rick DeNatale wrote: > I'm also having difficulties, it would appear that I can't > successfully > access http://gems.rubyforge.org. I can't find the remote rails gem: > > Macintosh:activerecord rick$ gem list --both rails > > *** LOCAL GEMS *** > > rails (2.0.2, 1.2.5, 1.2.3) > > *** REMOTE GEMS *** > > Bulk updating Gem source index for: http://gems.rubyforge.org/ > > Macintosh:activerecord rick$ > > If I look at that url with firefox, I get a text page with links to > get a > yaml index, look at the gems online, and download ruby gems. If I > click on > the second one, I seem to get randomly redirected to different shadow > servers most of which result in a forbidden error. A sampling: > > http://gemmirror.xaop.net/gems/ gives > Forbiddin > http://gems.rubyforge.vm.bytemark.co.uk/gems/ gets through > http://gems.rubyforge.mmmultiworks.com/gems/ gives Forbidden > http://rubyforge-gems.ruby-forum.com/gems/ gives Forbidden > http://rubyforge.rubyuser.de/gems/ gets > through RubyGems itself never accesses these URLs. Forbidden here is ok. > Here's what happens when I try a system update: > > Macintosh:activerecord rick$ sudo gem update --system > Password: > Updating RubyGems > Bulk updating Gem source index for: http://gems.rubyforge.org/ > Updating rubygems-update > ERROR: While executing gem ... (Gem::GemNotFoundException) > could not find rubygems-update locally or in a repository Can you try again today? There was an incompatibility in trunk before RubyGems 1.2 was released, so gems released were incompatible and broke the index. They've all been cleaned up now, re-released with RubyGems 1.2. There is one other bug with upgrading from RubyGems 1.1.1. If an older rubygems-update is not installed RubyGems may report "nothing to update". As a work-around, run `gem install rubygems-update -v 1.1.1` before `gem update --system`.