Rubygems issues
Running "bundle install" has just started giving me 503 errors from rubygems.org.
$ bundle install Fetching source index for http://rubygems.org/
/usr/local/rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems/remote_fetcher.rb:215:in
`fetch_http': bad response Service Unavailable 503 (http://production.cf.rubygems.org/quick/Marshal.4.8/packet-0.1.7.ge...)
(Gem::RemoteFetcher::FetchError)
I've seen it failing on different gems: packet-0.1.7, mechanize-1.0.0, jbuilder-0.3.gemspec.rz
Anybody else?
Comments are currently closed for this discussion. You can start a new one.
2 Posted by DaveTsunami on 23 Jan, 2012 11:41 AM
Same problem here!
3 Posted by huerlisi on 23 Jan, 2012 11:46 AM
It happens for some of my newly pushed gems, too. But some other gems like rails-3.2.0 do work.
4 Posted by DaveTsunami on 23 Jan, 2012 11:57 AM
Thanks for giving a hint. Adding git source or specifying lower version of gem allowed me to run bundle without problems. But I wouldn't say it's a problem of newly pushed gems, because also gems that were pushed a while ago also cannot be fetched. E.g. gem pg, rb-fsevent, and more.
5 Posted by beddari on 23 Jan, 2012 12:02 PM
It seems down at the moment to me .. :
6 Posted by Daniel Harrington on 23 Jan, 2012 12:09 PM
Same problem here!
7 Posted by DaveTsunami on 23 Jan, 2012 12:52 PM
Seems fixed!
8 Posted by huerlisi on 23 Jan, 2012 01:03 PM
Fixed over here, too.
9 Posted by Dan on 23 Jan, 2012 02:23 PM
All good here too.
Support Staff 10 Posted by Evan Phoenix on 21 Feb, 2012 01:17 AM
Sounds like it was an issue on rubygems.org. Thanks for your patience everyone.
Evan Phoenix closed this discussion on 21 Feb, 2012 01:17 AM.