Bundler fails to find appropriate version, despite installing appropriate version earlier in the build

Build Environment
, ,
41

Had a similar problem where bundle install would fail because it couldn’t find the appropriate version (in my case 1.9.9). To solve the problem I had to uninstall all other versions of bundler (why? I don’t know).

dependencies:
  pre:
    - echo Y | rvm @global do gem uninstall bundler
    - gem install bundler -v '1.9.9'
    - gem uninstall bundler -v '1.13.0'
```
42

I’m cross posting this post from the Bundler issue thread:

One crucial piece of the puzzle appears to be disable_shared_gems which is a setting (.bundle/config) that’s turned on when using --path with bundle install (or --deployment, which is essentially --path vendor/bundle).

I’d love some more feedback to help with this:

Can anyone re-create the problem without disable_shared_gems true? (You can use --no-deployment or bundle config --delete disable_shared_gems to clear the setting).
Can anyone report on behavior with Bundler 1.10.5 and Bundler 1.11.2? (I’ve done some testing, but I’m interested in additional input)
Can anyone provide specifics as to why you need nested bundle execs to work in your case?

There is still an open bug between Bundler and Rubygems, when trying to run a double-nested bundle exec. For anyone who’s using the workaround in this thread, could you try reproducing this bug on a branch of the project where you saw this issue?

If you can specifically answer this question, I think that will impact the priority of this fix.

Can anyone provide specifics as to why you need nested bundle execs to work in your case?

2 Likes