title: Bundler and wrong binstubs?
body: <p>I run <code>rails s</code> or <code>bundle exec rails s</code> and I get this warning:</p>
  
  <pre><code>Bundler is using a binstub that was created for a different gem.
  This is deprecated, in future versions you may need to `bundle binstub rails` to work around a system/bundle conflict.
  </code></pre>
  
  <p>What does this mean? From looking around the bundler site, my understanding of binstubs is that you can set executables to them, so instead of running <code>bundle exec blabla</code> you can just do <code>bin/blabla</code>. So this error is saying my <code>bundler</code> isn't set to the right binstub?</p>
  
  <p>When I run the <code>bundle binstub rails</code> I get this output</p>
  
  <pre><code>rails has no executables, but you may want one from a gem it depends on.
    railties has: rails
    bundler has: bundle, bundler
  </code></pre>
  
  <p>I do not understand what my system is trying to tell me, and it's not breaking anything, but I have a hunch this could turn into a  bigger issue if I don't fix it</p>
  
  <pre><code>ruby 2.0.0p247
  </code></pre>
  
  <p>which ruby</p>
  
  <pre><code>/Users/evan/.rvm/rubies/ruby-2.0.0-p247/bin/ruby
  </code></pre>
  
  <p>which bundler</p>
  
  <pre><code>/Users/evan/.rvm/gems/ruby-2.0.0-p247/bin/bundler
  </code></pre>
  
  <p>Rails 4.0.2</p>
  
  <p>Edit:</p>
  
  <p>So, if I run the commands in the nag message:</p>
  
  <pre><code>  bundle config --delete bin    # Turn off Bundler's stub generator
    rake rails:update:bin         # Use the new Rails 4 executables
  </code></pre>
  
  <p>I end up getting <code>uninitialized constant Bundler</code> errors with <code>bundle exec</code> commands and the only way I've found to fix that is to rerun <code>bundle install --binstubs</code> which brings back the nag message at the start of this post.</p>