Ruby Gems Update- Rubyforge to Gemcutter

[fusionman]

Hello,

I'm following the Simply Rails 2 book but am having an issue with the Ruby Gems aspect. After some research I found out that the place to get gems is now gemcutter.org, NOT rubyforge.org. I am running Leopard, so I'm not sure if the gems release was already on here or if it was installed by following the book instructions.

I ran the following commands as instructed by page 27 of the book.

curl -L http://rubyforge.org/frs/download.ph...gems-1.0.1.tgz | tar xz

cd rubygems-1.0.1

sudo ruby setup.rb

cd ..


Currently, if I execute

gem -v

The computer returns 1.0.1

This appears that the gem install was successful. However, if I run

sudo gem update --system

The computer returns the following.

Updating RubyGems...
ERROR: While executing gem ... (Gem::RemoteSourceException)
HTTP Response 403 fetching http://gems.rubyforge.org/yaml

When I try to run

$ ruby script/server
Rails requires RubyGems >= 1.3.1 (you have 1.0.1). Please `gem update --system` and try again.

So, after a little research, I found that Gemcutter is where I should be fetching gems from at this point. I attempted the following.

sudo gem sources list

The computer only returned rubyforge, so I attempted to add gemcutter with the following command.

$ sudo gem sources -a http://gemcutter.org/
ERROR: While executing gem ... (Gem::RemoteSourceException)
HTTP Response 403 fetching http://gemcutter.org/yaml

In other words, I can't get the gem update command to work, and I can't get the add gemcutter command to work. I am getting the same error for both.

Mac OSX Leopard 10.5.8
$ ruby -v
ruby 1.8.6 (2008-08-11 patchlevel 287) [universal-darwin9.0]

I would really appreciate any help. Thanks so much.

[ReggieB]

GemCutter is a new resource and has only become prominant fairly recently. Certainly well after the SitePoint book was published. However, it hasn't replaced RubyForge, but rather it has taken over some of RubyForge's preeminance as the main gem repository. More information here:

http://www.rubyinside.com/gemcutter-...host-2659.html

In other words: gem update should work for RubyForge. You just might not get some of the very latest versions of some gems.

Therefore, I don't think your problem is with the site but your system. Possibly a bug in your gem install. However, I'd start by checking your firewall rules and that you have external connection rights from the console. Unfortunately my Mac knowledge isn't great so I can't tell you where to look for these.

[fusionman]

So, it was bugging me so much I just kept at it and finally got something to work. I kept reading that there was possibly a bug somewhere in the gems version installed on this flavor of OS X. I ended up going and getting the latest version of rubygems from rubyforge and put the folder in the same directory as the version that wasn't working. I ran the same commands from the book but referenced the new folder and version. The install went fine.

gem -v is returning 3.5.4 as it should.

I also set my rails config to start looking at gemcutter for new gem updates. Everything seems to be working great now.

Thanks for the help and suggestion.

[ReggieB]

Well done.