Gems does not skip gem sources it is unable to connect to?

Nick Malnick's Avatar

Nick Malnick

18 Sep, 2010 01:07 PM

I have listed in my .gemrc file 2 internal work gem repositories along with gemcutter and rubyforge. When I am out of the office and try to do a gem install I get the error "http://work_repository_url does not appear to be a repository" and the install fails. The work around is to either vpn into work or remove the two sources from .gemrc (both of which are annoying). I would have assumed that gems would just go through the source list and skip any urls that it is on able to connect to, is this not how it works?


  1. Support Staff 1 Posted by Nick Quaranto on 03 Oct, 2010 04:55 PM

    Nick Quaranto's Avatar

    Sorry about the delay here.

    Yeah, RG isn't too smart about what sources it can't connect to...probably stems back to when there was only ever one source. Maybe you could take the custom one out of the .gemrc and only install custom gems with -s http://work_url ?

  2. 2 Posted by Nick Malnick on 01 Jun, 2011 05:51 PM

    Nick Malnick's Avatar

    You can close this issue. I've discovered that you can specify gem sources in Bundler Gemfiles. So for my work projects I use a Gemfile that specifies our internal repository and for my personal projects I use public sources define in .gemrc.

  3. 3 Posted by Luis Lavena on 03 Jun, 2011 03:33 PM

    Luis Lavena's Avatar

    Hello, closing this out on OP request. Happy to hear you sorted it out.

  4. Luis Lavena closed this discussion on 03 Jun, 2011 03:33 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac