Thank you!

Thanks!! :)

Danke!

Thanks

Kiitos!

Thanks!

How do I turn off notifications?

@rkh
Account settings => Notification center => Comments after me on gists [disable]

I guess you can't - so thanks everybody for thanking! (but please stop, no more saying thanks, thank you! ;)

@GAMEZ: thanks.

HURRA!! thank you ! tak!

Thanks body, I was totally **ck up!

thanks dude!

Thanks!

Thanks a lot :D

Thanks :)

I'm receiving this error:

$ gem install rails rspec --pre --verbose
GET http://rubygems.org/prerelease_specs.4.8.gz
302 Moved Temporarily
GET http://production.s3.rubygems.org/prerelease_specs.4.8.gz
302 Moved Temporarily
GET http://guide.opendns.com/?url=production.s3.rubygems.org%2Fprerelease_specs.4.8.gz
200 OK
ERROR: While executing gem ... (Zlib::GzipFile::Error)
not in gzip format

I'm getting this error :

Fetching source index from http://gemcutter.org/
/usr/local/lib/site_ruby/1.8/rubygems/remote_fetcher.rb:359:in `request': too many connection resets (http://gemcutter.org/specs.4.8.gz) (Gem::RemoteFetcher::FetchError)
from /usr/local/lib/site_ruby/1.8/rubygems/remote_fetcher.rb:285:in `open_uri_or_path'
from /usr/local/lib/site_ruby/1.8/rubygems/remote_fetcher.rb:170:in `fetch_path'
from /usr/local/lib/site_ruby/1.8/rubygems/spec_fetcher.rb:219:in `load_specs'
from /usr/local/lib/site_ruby/1.8/rubygems/spec_fetcher.rb:192:in `list'
from /usr/local/lib/site_ruby/1.8/rubygems/spec_fetcher.rb:188:in `each'
from /usr/local/lib/site_ruby/1.8/rubygems/spec_fetcher.rb:188:in `list'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/source.rb:75:in `fetch_all_specs'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/source.rb:59:in `fetch_specs'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/source.rb:25:in `specs'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/installer.rb:87:in `remote_index'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/installer.rb:85:in `each'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/installer.rb:85:in `remote_index'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/index.rb:5:in `build'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/installer.rb:74:in `remote_index'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/installer.rb:66:in `resolve_remotely'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/environment.rb:28:in `specs'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/installer.rb:21:in `run'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/installer.rb:6:in `install'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/cli.rb:90:in `install'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/vendor/thor/task.rb:33:in `send'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/vendor/thor/task.rb:33:in `run'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/vendor/thor/invocation.rb:109:in `invoke'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/vendor/thor/invocation.rb:116:in `call'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/vendor/thor/invocation.rb:116:in `invoke'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/vendor/thor.rb:137:in `start'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/vendor/thor/base.rb:378:in `start'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/lib/bundler/vendor/thor.rb:124:in `start'
from /usr/lib/ruby/gems/1.8/gems/bundler-0.9.25/bin/bundle:13
from /usr/bin/bundle:19:in `load'
from /usr/bin/bundle:19

Any ideas ?

Really? Anyone know why this happened?

I have enjoyed using gemcutter. Its like the 3rd iteration of rubygems and is significantly better than previous revs. When this happens though, I always remember that I didn't have this problem with CPAN. Maybe its time to start having some redundancy and mirroring of the rubygems repo.

Thanks,

Ok, rubygems.org seems to work again, so you should not forget to remove the entries...

is anyone thinking about how we can prevent this error from now on?

Make sure to remove this now, these DNS entries are now broken. :)