Need help in Installing Rails 3.0.3

This is my gem env RubyGems Environment:   - RUBYGEMS VERSION: 1.3.7   - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [i686-linux]   - INSTALLATION DIRECTORY: /home/arjunkishore/.rvm/gems/ruby-1.9.2-p136   - RUBY EXECUTABLE: /home/arjunkishore/.rvm/rubies/ruby-1.9.2-p136/bin/ruby   - EXECUTABLE DIRECTORY: /home/arjunkishore/.rvm/gems/ruby-1.9.2-p136/bin   - RUBYGEMS PLATFORMS:     - ruby     - x86-linux   - GEM PATHS:      - /home/arjunkishore/.rvm/gems/ruby-1.9.2-p136      - /home/arjunkishore/.rvm/gems/ruby-1.9.2-p136@global   - GEM CONFIGURATION:      - :update_sources => true      - :verbose => true      - :benchmark => false      - :backtrace => false      - :bulk_threshold => 1000   - REMOTE SOURCES:      -

I want to install rails 3.0.3 and sqlite3 gems.

i am getting this error message.. Some of our users posted this problem in our group, but not the solution

gem install rails ERROR: does not appear to be a repository ERROR: Could not find a valid gem 'rails' (>= 0) in any repository

can anyone please explain how to fix this problem step by step please ..?? like step 1: type so and so in terminal step 2: ... .. ..

Thanks in advance :slight_smile:

The reference to is out of date. Here's what my gem env (or `gem sources --list`) returns:

  - REMOTE SOURCES:      -      -

You can add them (and remove the no longer operative one) from the command line; for more info

gem help sources


Hassan, is (again) the definitive source: redirects to

Ah, crap. Guess I missed that memo :slight_smile:

Never mind, then, and sorry for the noise.

I know that sounds trivial, and the thread is two weeks old, but are you sure you are connected to the Internet during that tests? It took me yesterday 2 hours to find that problem on my local staging environment. Due to configuration problems I could connect via ssh and remote control, but my network did not route requests from the staging to the Internet, the just got lost.

Actually it wasn't trivial. It helped me :0)

After the RubyGem/Bundler update mess yesterday, I was afraid there was yet another problem with my set up. Turns out my Time Machine's 5 GHz network was insanely unstable and caused the error. If it weren't for your post, I would have spent hours searching for the problem (as I'm a Rails newbie). A big thank you to you Mr. Melzer is in order, so "Thank you!"

It seems the problem is already solved, as noted in the external source:

It was a network problem.