Where, oh where has my gem server gone?

August 8, 2010 Alex Chaffee

Uh-oh!

ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
    bad response Moved Permanently 301 (http://gems.rubyforge.org/latest_specs.4.8)

Whew!

gem sources -a http://rubygems.org/
gem sources -r http://gems.rubyforge.org/

Looks like they weren’t kidding when they said to switch from rubyforge to rubygems.org (née gemcutter)!

[Edited to change “http://production.s3.rubygems.org/” to “http://rubygems.org/”. Note that the trailing slash is significant!]

About the Author

Biography

More Content by Alex Chaffee
Previous
Network Issues Today
Network Issues Today

Our managed hosting provider experienced an extended network outage today, which affected a number of appli...

Next
iPhone on blocks: UITextFields
iPhone on blocks: UITextFields

If you've ever used a UITextField in an iPhone project (or, I suppose, an NSTextField in a Cocoa project) y...

How do you measure digital transformation?

Take the Benchmark