Skip to content
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.

bundler env should show bundler's shebang if it differs from the first found ruby #5616

Closed
nogweii opened this issue Apr 26, 2017 · 1 comment

Comments

@nogweii
Copy link

nogweii commented Apr 26, 2017

I was starting to tear my hair out today in a crazy debugging situation. I ran gem install bundler on OSX, and then trying to install various gems. However, I got ruby version incompatibilities: our rails app specifies ruby 2.3, but bundler reported ruby 2.0.

It turns out that rubygem's had written the bundler binstub with OSX's system ruby for it's shebang, and not the ruby installed with Homebrew. It would have been faster to debug if I had realized the discrepancy earlier.

@segiddins
Copy link
Member

Can you give an example of the relevant shebangs and ruby executable path?

bundlerbot added a commit that referenced this issue Jun 12, 2017
…irect

[Env] Print shebang when it doesnt match Gem.ruby

Closes #5616.

Prints out `Gem.ruby` and the `bundle` binstub shebang when they don't match, which should help us pinpoint when ruby installation shenanigans are the root cause of an issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants