Gem on debian moved permanently

Weirdness on debian
Added by Christoph Kappel about 7 years ago

Debian seems to have big problems with gem and the different versions, you will notice when you see this:

1 > gem list --remote
2 
3 *** REMOTE GEMS ***
4 
5 ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)
6 bad response Moved Permanently 301 (http://gems.rubyforge.org/latest_specs.4.8)

Apparently there is an easy fix, just update the sources of gem:

 1 > gem sources
 2 *** CURRENT SOURCES ***
 3 
 4 http://gems.rubyforge.org/
 5 
 6 > gem sources -r http://gems.rubyforge.org/
 7 http://gems.rubyforge.org/ removed from sources
 8 
 9 > gem sources -a http://production.s3.rubygems.org/
10 http://production.s3.rubygems.org/ added to sources

Comments

Added by arog nasir over 5 years ago

joy to read, I came across this site ages ago but I've only just decided to stop back and have a read of your articles. car insurance