* [ruby-core:91398] [Ruby trunk Bug#15586] Requiring `bundler/setup` gets wrong version
[not found] <redmine.issue-15586.20190204200452@ruby-lang.org>
@ 2019-02-04 20:04 ` markjreed
2019-02-04 23:29 ` [ruby-core:91401] " mame
1 sibling, 0 replies; 2+ messages in thread
From: markjreed @ 2019-02-04 20:04 UTC (permalink / raw
To: ruby-core
Issue #15586 has been reported by MarkTheStrange (Mark Reed).
----------------------------------------
Bug #15586: Requiring `bundler/setup` gets wrong version
https://bugs.ruby-lang.org/issues/15586
* Author: MarkTheStrange (Mark Reed)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.1p33 (2019-01-30 revision 66950) [x86_64-darwin18]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
The statement 'require "bundler/setup"' always loads the version that ships with ruby (Bundler 1.17.2 as of Ruby 2.6.1), even if a newer version of Bundler is installed via RubyGems. On the other hand, requiring plain "bundler" gets the gem-installed version.
Demo:
$ ruby -rbundler -e 'puts Bundler::VERSION'
2.0.1
$ ruby -rbundler/setup -e 'puts Bundler::VERSION'
1.17.2
This breaks pretty much all my bundled applications, which start by requiring `bundler/setup`, which fails when the Gemfile.lock was created by Bundler 2.x and the loaded Bundler is 1.x.
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
* [ruby-core:91401] [Ruby trunk Bug#15586] Requiring `bundler/setup` gets wrong version
[not found] <redmine.issue-15586.20190204200452@ruby-lang.org>
2019-02-04 20:04 ` [ruby-core:91398] [Ruby trunk Bug#15586] Requiring `bundler/setup` gets wrong version markjreed
@ 2019-02-04 23:29 ` mame
1 sibling, 0 replies; 2+ messages in thread
From: mame @ 2019-02-04 23:29 UTC (permalink / raw
To: ruby-core
Issue #15586 has been updated by mame (Yusuke Endoh).
Status changed from Open to Closed
Sorry for the inconvenience. This is a duplicate of #15582, and it has been already fixed at trunk. You can also workaround the issue with this patch: https://bugs.ruby-lang.org/issues/15582#note-2
----------------------------------------
Bug #15586: Requiring `bundler/setup` gets wrong version
https://bugs.ruby-lang.org/issues/15586#change-76657
* Author: MarkTheStrange (Mark Reed)
* Status: Closed
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.1p33 (2019-01-30 revision 66950) [x86_64-darwin18]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
The statement 'require "bundler/setup"' always loads the version that ships with ruby (Bundler 1.17.2 as of Ruby 2.6.1), even if a newer version of Bundler is installed via RubyGems. On the other hand, requiring plain "bundler" gets the gem-installed version.
Demo:
$ ruby -rbundler -e 'puts Bundler::VERSION'
2.0.1
$ ruby -rbundler/setup -e 'puts Bundler::VERSION'
1.17.2
This breaks pretty much all my bundled applications, which start by requiring `bundler/setup`, which fails when the Gemfile.lock was created by Bundler 2.x and the loaded Bundler is 1.x.
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-02-04 23:29 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <redmine.issue-15586.20190204200452@ruby-lang.org>
2019-02-04 20:04 ` [ruby-core:91398] [Ruby trunk Bug#15586] Requiring `bundler/setup` gets wrong version markjreed
2019-02-04 23:29 ` [ruby-core:91401] " mame
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).