Project

General

Profile

Actions

Bug #15333

closed

make check fails looking for Bundler 2.0

Added by leam (Leam Hall) almost 6 years ago. Updated almost 6 years ago.

Status:
Closed
Target version:
-
ruby -v:
ruby 2.6.0dev (2018-10-17 trunk 65108) [x86_64-linux]
[ruby-core:89992]

Description

Just pulled the latest trunk from github. The log from "make check" seems to indicate a bundler 2.0 missing. Using bundler 1.17.1 installed by gem.

ruby -v: ruby 2.6.0dev (2018-11-23 trunk 65931) [x86_64-linux]
making mjit_build_dir.so
const char MJIT_BUILD_DIR[] = "/usr/local/src/ruby";
/usr/local/src/ruby/lib/rubygems/resolver.rb:231:in search_for': Unable to resolve dependency: use r requested 'bundler (= 2.0.0.pre.1)' (Gem::UnsatisfiableDependencyError) from /usr/local/src/ruby/lib/rubygems/resolver.rb:283:in block in sort_dependencies'


Files

ruby_make_check_20181122_1832.log (14.5 KB) ruby_make_check_20181122_1832.log leam (Leam Hall), 11/22/2018 11:55 PM
ruby_configure_20181122_1832.log (27.5 KB) ruby_configure_20181122_1832.log leam (Leam Hall), 11/22/2018 11:55 PM
ruby_make_20181122_1832.log (96.5 KB) ruby_make_20181122_1832.log leam (Leam Hall), 11/22/2018 11:55 PM

Updated by hsbt (Hiroshi SHIBATA) almost 6 years ago

  • Status changed from Open to Assigned
  • Assignee set to hsbt (Hiroshi SHIBATA)

Updated by hsbt (Hiroshi SHIBATA) almost 6 years ago

  • Status changed from Assigned to Feedback

I couldn't reproduce it.

Updated by leam (Leam Hall) almost 6 years ago

I will build a clean box and try again. Thank you.

Updated by MSP-Greg (Greg L) almost 6 years ago

@hsbt (Hiroshi SHIBATA)

By no means have I looked at how Bundler is used by RG testing, but in trunk, the following line in test_case.rb works in rubygems/rubygems, but not trunk:

# If bundler gemspec exists, add to stubs
bundler_gemspec = File.expand_path("../../../bundler/bundler.gemspec", __FILE__)

https://github.com/rubygems/rubygems/blob/master/lib/rubygems/test_case.rb#L17

JFYI, ruby-loco runs test-all with runner.rb from ruby.exe in the install folder, so...

Updated by leam (Leam Hall) almost 6 years ago

My original failure was on a Fedora 28 box. I am building a CentOS 7 box and still getting the build environment set up for a totally clean build. I apologize for the delay.

Updated by leam (Leam Hall) almost 6 years ago

  • Status changed from Feedback to Closed

Build on a totally clean CentOS 7 box passed without failure. I would attribute this issue to "user's host configuration".

Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0Like0Like0