ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: richard.schneeman+ruby-lang@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:91622] [Ruby trunk Bug#15622] Default version of Bundler incorrectly invoked when using binstubs
Date: Mon, 25 Feb 2019 22:38:49 +0000 (UTC)	[thread overview]
Message-ID: <redmine.issue-15622.20190225223847.2413d939330eeb1a@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15622.20190225223847@ruby-lang.org

Issue #15622 has been reported by schneems (Richard Schneeman).

----------------------------------------
Bug #15622: Default version of Bundler incorrectly invoked when using binstubs 
https://bugs.ruby-lang.org/issues/15622

* Author: schneems (Richard Schneeman)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.6.1p33 (2019-01-30 revision 66950) [x86_64-linux]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
When trying to run a binstub with Ruby 2.6.1 with Bundler 2.0.1 on the system, the wrong version of Bundler gets loaded which then fails when the Gemfile.lock points to a 2.x version (since the default version that ships with Ruby is Bundler 1.x. While this was discovered on Heroku and is discussed in this issue https://github.com/heroku/heroku-buildpack-ruby/issues/856#issuecomment-467205932 I was able to replicate the problem fairly easily with docker. I've provided instructions below.

## Reproduction

Start a docker image with Ruby 2.6.1

```
docker run -it --rm ruby:2.6.1 bash
```

Install bundler, rails, make a new app, and remove the `begin/rescue/end` from the `bin/rake` binstub. To trigger the error run a `rake` command without `bundle exec`:

```
gem install bundler -v 2.0.1
gem install rails -v 6.0.0.beta1
rails new ruby-2-6-bundler-2-issue


cd ruby-2-6-bundler-2-issue

cat <<EOT > bin/rake
#!/usr/bin/env ruby
require_relative '../config/boot'
require 'rake'
Rake.application.run
EOT

rake -T
```

Output:

```
You must use Bundler 2 or greater with this lockfile.
```

Expected:

Bundler 2 is available on the system, and is the latest version, so it should be invoked instead of the default bundler version.





-- 
https://bugs.ruby-lang.org/

       reply	other threads:[~2019-02-25 22:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-15622.20190225223847@ruby-lang.org>
2019-02-25 22:38 ` richard.schneeman+ruby-lang [this message]
2019-02-26  8:22 ` [ruby-core:91623] [Ruby trunk Bug#15622] Default version of Bundler incorrectly invoked when using binstubs mattduszynski
2019-02-26  8:45 ` [ruby-core:91624] " hsbt
2019-02-27  8:44 ` [ruby-core:91629] " deivid.rodriguez
2019-03-08 11:41 ` [ruby-core:91715] " hsbt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.issue-15622.20190225223847.2413d939330eeb1a@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).