Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

On a bundle install: "Git repo <...> is not checked out. Run bundle install." #2059

Closed
mheffner opened this Issue · 5 comments

4 participants

@mheffner

On a fresh RVM install when running a bundle install with the --without flag I'm seeing:

$ bundle install --without=metrics
https://github.com/org/somerepo.git (at v0.15.35) is not checked out. Please run `bundle install`

The repo https://github.com/org/somerepo.git is only listed in the bundle group metrics, so in theory it should not be trying to reference it.

To work around this I've found that you can:

  1. Run bundle install minus the --without flag and let it check out https://github.com/org/somerepo.git.
  2. Running bundle install --without=metrics will now work.
$ bundle --version
Bundler version 1.1.5
$ ruby --version
ruby 1.8.7 (2012-02-08 MBARI 8/0x6770 on patchlevel 358) [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 2012.02
@indirect
Owner

So this is a bug... but it's only a bug in the sense that it should check out the repo even when you try to exclude it using --without. It's only possible to avoid checking out git repos if you already have a complete Gemfile.lock (and you might have to run bundle install with the --deployment flag on top of that).

@hone
Owner

Did you run bundle clean by chance? There was a bug with this that I fixed in bundler 1.2.0.rc.2. See this diff. We haven't backported this to 1-1-stable.

@mheffner

@indirect A complete Gemfile.lock was available, but I did not try the --deployment flag.

@hone I did not run bundle clean. This was the first I had bun bundle install on this project after a full reinstall of RVM + REE.

@radar
Collaborator

@hone, @indirect: I think this bug is fixed now. Correct?

@indirect
Owner

It should be fixed, yes.

@indirect indirect closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.