Erroneous Bundler::RubyVersionMismatch #2489

ichilton · 2013-05-30T10:52:09Z

I'm trying to run a rake task on a rails app, and am getting this error:

/home/vagrant/.rbenv/versions/2.0.0-p195/lib/ruby/gems/2.0.0/gems/bundler-1.3.5/lib/bundler/definition.rb:361:in     `validate_ruby!': Your Ruby version is 1.9.3, but your Gemfile specified 2.0.0 (Bundler::RubyVersionMismatch)
    from /home/vagrant/.rbenv/versions/2.0.0-p195/lib/ruby/gems/2.0.0/gems/bundler-1.3.5/lib/bundler.rb:116:in `setup'
    from /home/vagrant/.rbenv/versions/2.0.0-p195/lib/ruby/gems/2.0.0/gems/bundler-1.3.5/lib/bundler/setup.rb:17:in `<top (required)>'
    from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
    from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
rake aborted!

As you can see from the paths in the error though, I am running 2.0.0:

$ ruby -v
ruby 2.0.0p195 (2013-05-14 revision 40734) [x86_64-linux]

$ bundle -v
Bundler version 1.3.5

$ gem env
RubyGems Environment:

RUBYGEMS VERSION: 2.0.3
RUBY VERSION: 2.0.0 (2013-05-14 patchlevel 195) [x86_64-linux]
INSTALLATION DIRECTORY: /home/vagrant/.rbenv/versions/2.0.0-p195/lib/ruby/gems/2.0.0
RUBY EXECUTABLE: /home/vagrant/.rbenv/versions/2.0.0-p195/bin/ruby
EXECUTABLE DIRECTORY: /home/vagrant/.rbenv/versions/2.0.0-p195/bin
RUBYGEMS PLATFORMS:
- ruby
- x86_64-linux
GEM PATHS:
- /home/vagrant/.rbenv/versions/2.0.0-p195/lib/ruby/gems/2.0.0
- /home/vagrant/.gem/ruby/2.0.0
GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :backtrace => false
- :bulk_threshold => 1000
REMOTE SOURCES:
- https://rubygems.org/

The text was updated successfully, but these errors were encountered:

ichilton · 2013-05-30T12:26:30Z

One thought is that it's something to do with rbenv and trying to run something using global ruby (1.9.3) instead of local ruby (2.0.0), but I can't work out why...?

indirect · 2013-05-30T14:39:23Z

You may have a hard-coded shebang in the executable you are running. You can check it with "head which rake" or whatever command you are trying to run.

On Thu, May 30, 2013 at 9:26 PM, Ian Chilton notifications@github.com
wrote:

One thought is that it's something to do with rbenv and trying to run something using global ruby (1.9.3) instead of local ruby (2.0.0), but I can't work out why...?

Reply to this email directly or view it on GitHub:
#2489 (comment)

ichilton · 2013-05-30T14:42:20Z

rake is an rbenv shim (in ~/.rbenv/shims/rake)

and starts with this:

$ head which rake
#!/usr/bin/env bash
set -e
[ -n "$RBENV_DEBUG" ] && set -x

indirect · 2013-05-30T14:57:43Z

Sounds like an rbenv issue, then. Maybe you should ask them?

On Thu, May 30, 2013 at 11:42 PM, Ian Chilton notifications@github.com
wrote:

rake is an rbenv shim (in ~/.rbenv/shims/rake)
and starts with this:
$ head which rake
#!/usr/bin/env bash
set -e

[ -n "$RBENV_DEBUG" ] && set -x

Reply to this email directly or view it on GitHub:
#2489 (comment)

ichilton · 2013-05-30T14:58:23Z

I was wondering that - thanks.

ichilton · 2013-05-31T07:12:36Z

rbenv guys are saying it's bundler's problem: rbenv/rbenv#400

It's not system ruby since the stack trace comes from:

/home/vagrant/.rbenv/versions/2.0.0-p195/lib/ruby/gems/2.0.0/gems/bundler-1.3.5

which clearly indicates that you're running 2.0. I would rather believe this is a bug with Bundler's version check.

indirect · 2013-05-31T07:24:42Z

Well, as you can see from the backtrace you originally posted here, you are somehow loading the Bundler installed into Ruby 2... From the Rubygems installed for 1.9 in /usr/lib. Bundler is correct that you're running it on the wrong version of ruby.

On Fri, May 31, 2013 at 4:12 PM, Ian Chilton notifications@github.com
wrote:

rbenv guys are saying it's bundler's problem: rbenv/rbenv#400
It's not system ruby since the stack trace comes from:
/home/vagrant/.rbenv/versions/2.0.0-p195/lib/ruby/gems/2.0.0/gems/bundler-1.3.5

which clearly indicates that you're running 2.0. I would rather believe this is a bug with Bundler's version check.

Reply to this email directly or view it on GitHub:
#2489 (comment)

ichilton · 2013-05-31T08:45:42Z

Yeah, but is that bundler or rbenv!?

indirect · 2013-05-31T09:18:44Z

Bundler is a .rb file and has absolutely no control or say over what ruby interpreter is reading that file and running the code. Your system environment is what determines that.

On Fri, May 31, 2013 at 5:45 PM, Ian Chilton notifications@github.com
wrote:

Yeah, but is that bundler or rbenv!?

Reply to this email directly or view it on GitHub:
#2489 (comment)

ichilton · 2013-05-31T09:47:33Z

Yes, but it's Bundler that's doing the version check and erroring.

Also, I just removed rbenv and tried chruby and ruby-install - and it's doing the exact same thing as rbenv and ruby-build.

/home/vagrant/.gem/ruby/2.0.0/gems/bundler-1.3.5/lib/bundler/definition.rb:361:in `validate_ruby!': Your Ruby version is 1.9.3, but your Gemfile specified 2.0.0 (Bundler::RubyVersionMismatch)
  from /home/vagrant/.gem/ruby/2.0.0/gems/bundler-1.3.5/lib/bundler.rb:116:in `setup'
  from /home/vagrant/.gem/ruby/2.0.0/gems/bundler-1.3.5/lib/bundler/setup.rb:17:in `<top (required)>'
  from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
  from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
rake aborted!
No such file or directory -

$ ruby -v
ruby 2.0.0p195 (2013-05-14 revision 40734) [x86_64-linux]

$ gem env
RubyGems Environment:

RUBYGEMS VERSION: 2.0.3
RUBY VERSION: 2.0.0 (2013-05-14 patchlevel 195) [x86_64-linux]
INSTALLATION DIRECTORY: /home/vagrant/.gem/ruby/2.0.0
RUBY EXECUTABLE: /home/vagrant/.rubies/ruby-2.0.0-p195/bin/ruby
EXECUTABLE DIRECTORY: /home/vagrant/.gem/ruby/2.0.0/bin
RUBYGEMS PLATFORMS:
- ruby
- x86_64-linux
GEM PATHS:
- /home/vagrant/.gem/ruby/2.0.0
- /home/vagrant/.rubies/ruby-2.0.0-p195/lib/ruby/gems/2.0.0
GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :backtrace => false
- :bulk_threshold => 1000
REMOTE SOURCES:
- https://rubygems.org/

$ echo $PATH
Using ruby-2.0.0
/home/vagrant/.gem/ruby/2.0.0/bin:/home/vagrant/.rubies/ruby-2.0.0-p195/lib/ruby/gems/2.0.0/bin:/home/vagrant/.rubies/ruby-2.0.0-p195/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/opt/vagrant_ruby/bin

$ which ruby
/home/vagrant/.rubies/ruby-2.0.0-p195/bin/ruby

$ which rake
/home/vagrant/.gem/ruby/2.0.0/bin/rake

indirect · 2013-05-31T09:51:16Z

Yes, Bundler is doing the version check and erroring. If you remove the ruby line from your Gemfie, you will notice (sooner or later) that you are actually running on Ruby 1.9. As is clearly demonstrated by the backtrace you just pasted again: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb. Since we seem to have reached an impasse, I'm going to stop replying to this ticket now. You may want to investigate your rake, bundler, and gem executables to try to figure out how you're running rake and (I presume) bundle under 1.9 while running gem and ruby under 2.0.

ichilton · 2013-05-31T10:02:30Z

Ok, thanks for at least replying this far.

ichilton · 2013-05-31T13:26:42Z

Found the problem.... i'm shelling out to the heroku command in the rake task - which comes from Heroku Toolbelt.

However, at the top of /usr/bin/heroku is this shebang:

#!/usr/bin/env ruby1.9.1

and sure enough:

$ruby1.9.1 -v
ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux]

So that makes sense - except why is bundler complaining? - where does bundler come in when a rake task is calling that executable?

What would you advise as the best fix? - I don't want to change /usr/bin/heroku as that's written by their toolbelt installer and will get upgraded from time to time.

Do I need to prefix the call in the rake task with something to send it through rbenv/bundler?

I'm just using backticks (heroku .....) to execute it at the moment.

Thanks,

Ian

fnichol · 2013-05-31T13:35:40Z

For reference sake I suspect this issue is ENV['RUBYOPT'] being propagated to subprocesses that happen to be Ruby.

indirect · 2013-05-31T14:36:47Z

As the docs mention, you need to use Bundler.with_clean_env{ foo } if foo is ruby and you don't want to apply the current bundle. But that won't change the ruby version.

On Fri, May 31, 2013 at 10:35 PM, Fletcher Nichol
notifications@github.com wrote:

For reference sake I suspect this issue is ENV['RUBYOPT'] being propagated to subprocesses that happen to be Ruby.

Reply to this email directly or view it on GitHub:
#2489 (comment)

ichilton · 2013-05-31T15:26:08Z

Yep, that fixed it! :)

Changed the shell out to:
Bundler.with_clean_env { sh "cmd" }

Thanks guys.

jess · 2013-07-22T13:35:18Z

Just in case anyone else is searching this issue. I had the same problem using rvm. I was also running rake tasks and shelling out to heroku toolbelt and getting this error:

Your Ruby version is 1.9.3, but your Gemfile specified 2.0.0

The same fix worked for me, wrapping the shell commands with (example):

Bundler.with_clean_env {sh "heroku run bundle exec rake db:migrate --app #{app}"}

henrik · 2014-01-06T15:36:05Z

I, too, had this issue with rvm and shelling out to Heroku. This fixed it. @ichilton, thanks so much for getting to the bottom of it!

ichilton mentioned this issue May 30, 2013

Your Ruby version is 1.9.3, but your Gemfile specified 2.0.0 rbenv/rbenv#400

Closed

indirect closed this as completed May 31, 2013

sayotte mentioned this issue Jan 5, 2015

Foreman isn't using the current version of Ruby (it's using 1.8.7) ddollar/foreman#257

Closed

Bestra mentioned this issue Mar 23, 2016

Fix/update database import Aperta-project/Aperta#2190

Merged

9 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Erroneous Bundler::RubyVersionMismatch #2489

Erroneous Bundler::RubyVersionMismatch #2489

ichilton commented May 30, 2013

ichilton commented May 30, 2013

indirect commented May 30, 2013

One thought is that it's something to do with rbenv and trying to run something using global ruby (1.9.3) instead of local ruby (2.0.0), but I can't work out why...?

ichilton commented May 30, 2013

indirect commented May 30, 2013

[ -n "$RBENV_DEBUG" ] && set -x

ichilton commented May 30, 2013

ichilton commented May 31, 2013

indirect commented May 31, 2013

which clearly indicates that you're running 2.0. I would rather believe this is a bug with Bundler's version check.

ichilton commented May 31, 2013

indirect commented May 31, 2013

Yeah, but is that bundler or rbenv!?

ichilton commented May 31, 2013

indirect commented May 31, 2013

ichilton commented May 31, 2013

ichilton commented May 31, 2013

fnichol commented May 31, 2013

indirect commented May 31, 2013

For reference sake I suspect this issue is `ENV['RUBYOPT']` being propagated to subprocesses that happen to be Ruby.

ichilton commented May 31, 2013

jess commented Jul 22, 2013

henrik commented Jan 6, 2014

Erroneous Bundler::RubyVersionMismatch #2489

Erroneous Bundler::RubyVersionMismatch #2489

Comments

ichilton commented May 30, 2013

ichilton commented May 30, 2013

indirect commented May 30, 2013

One thought is that it's something to do with rbenv and trying to run something using global ruby (1.9.3) instead of local ruby (2.0.0), but I can't work out why...?

ichilton commented May 30, 2013

indirect commented May 30, 2013

[ -n "$RBENV_DEBUG" ] && set -x

ichilton commented May 30, 2013

ichilton commented May 31, 2013

indirect commented May 31, 2013

which clearly indicates that you're running 2.0. I would rather believe this is a bug with Bundler's version check.

ichilton commented May 31, 2013

indirect commented May 31, 2013

Yeah, but is that bundler or rbenv!?

ichilton commented May 31, 2013

indirect commented May 31, 2013

ichilton commented May 31, 2013

ichilton commented May 31, 2013

fnichol commented May 31, 2013

indirect commented May 31, 2013

For reference sake I suspect this issue is ENV['RUBYOPT'] being propagated to subprocesses that happen to be Ruby.

ichilton commented May 31, 2013

jess commented Jul 22, 2013

henrik commented Jan 6, 2014

For reference sake I suspect this issue is `ENV['RUBYOPT']` being propagated to subprocesses that happen to be Ruby.