Bugs item #29170, was opened at 2011-05-05 20:40 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=29170&group_id=126
Category: `gem install` command Group: None >Status: Closed >Resolution: Out of Date Priority: 3 Submitted By: Nick Klauer (klauern) Assigned to: Ryan Davis (zenspider) Summary: with multiple sources, if one is unavailable, nothing works at all Initial Comment: With the Amazon outage, one of the sources I had added outside of rubygems was down (http://rubygems.torquebox.org). For me, this wasn't a big issue, since it hosts only a few gems that I use and I don't need updated that often. However, when trying to install a gem or update gems, it would shut down entirely, not being able to find specs.4.8.gz for that one source. So in effect, `gem update` was borked because one source wasn't available, regardless of the status of all others. If possible, can this just display a warning or something saying that "can't search ${borked gem server source}, skipping this one" and still try to update, install, etc., from any and all other sources listed? ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2011-06-21 16:18 Message: I'm closing this ticket as we've moved to github issues for all issue tracking. Please refile this ticket there if you think it is still valid. https://github.com/rubygems/rubygems/issues Thanks, The RubyGems Team ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2011-06-07 16:50 Message: Hi! Believe it or not, we're moving to github's issue tracker! The pressure to move has been loud and clear, but for the longest time it didn't support the way we worked. Now that it has freeform labels it can support our workflow adequately. There is just one problem: Your bug is here and we don't want to lose you! What we'd like you to do is fairly painless and should only take a few minutes: Please file the _exact_ same ticket on github and provide a link back to this crufty old ticket so we can refer to any previous discussion that occurred. Once the new ticket is made, put a forwarding link to it here and close this ticket out. In a couple weeks, we'll track down the old tickets that are still open and decide what to do with them. We could have done this fairly automatically, but we really want you to do it so you're attached to the ticket and we can still communicate with you and keep a record of it. https://github.com/rubygems/rubygems/issues Thanks, The RubyGems Team ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=29170&group_id=126 _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
