1: from /usr/lib64/ruby/2.7.0/rubygems.rb:16:in `<top (required)>' /usr/lib64/ruby/2.7.0/rubygems.rb:16:in `require': cannot load such file -- rubygems/compatibility (LoadError) * ERROR: dev-ruby/xmlrpc-0.3.0::gentoo failed (install phase): * Unable to generate gemspec file. * * Call stack: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop-20210314-100157 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-10.2.0 * clang version 11.1.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/11/bin /usr/lib/llvm/11 11.1.0 Python 3.8.8 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) * Available Rust versions: [1] rust-1.50.0 * The following VMs are available for generation-2: *) AdoptOpenJDK 8.282_p08 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Tue Mar 16 00:52:58 UTC 2021 emerge -qpvO dev-ruby/xmlrpc [ebuild N ] dev-ruby/xmlrpc-0.3.0 USE="-doc -test" RUBY_TARGETS="ruby26 ruby27 -ruby25"
Created attachment 691737 [details] emerge-info.txt
Created attachment 691740 [details] dev-ruby:xmlrpc-0.3.0:20210316-062044.log
Created attachment 691743 [details] emerge-history.txt
Created attachment 691746 [details] environment
Created attachment 691749 [details] etc.portage.tar.bz2
FWIW much more ruby packages are failing at various different images here at the tinderbox with the same error - what was changed in the last few days here is: */* RUBY_TARGETS: ruby27 into */* RUBY_TARGETS: ruby27 within package.use/90common
(In reply to Toralf Förster from comment #6) > FWIW much more ruby packages are failing at various different images here at > the tinderbox with the same error - what was changed in the last few days > here is: > */* RUBY_TARGETS: ruby27 > into > */* RUBY_TARGETS: ruby27 > within package.use/90common These two lines look identical to me? I'm guessing one of them should not be ruby27 but another version? Note that switching like that won't work because your ruby will be partially in one and partially in another version and that breaks things. Add the new target, update, then remove the old one.
(In reply to Hans de Graaff from comment #7) > (In reply to Toralf Förster from comment #6) > > FWIW much more ruby packages are failing at various different images here at > > the tinderbox with the same error - what was changed in the last few days > > here is: > > */* RUBY_TARGETS: ruby27 > > into > > */* RUBY_TARGETS: ruby27 > > within package.use/90common > > These two lines look identical to me? I'm guessing one of them should not be > ruby27 Indeed, for tinderbox images I had "ruby27 ruby30" before and removed ruby30. But this is made only during setup of new images. Existing images (TTL of about 12 days) will never be changed wrt to USE flags.
Had the same issue trying to add ruby27 to a running system with just ruby30. I really have no idea what the error messages mean. So I just gave up (for now) trying to install 2.7. Any ideas or tips for (clearly) uninformed folks like me? Cheers
(In reply to Rémi Cardona from comment #9) > Had the same issue trying to add ruby27 to a running system with just > ruby30. I really have no idea what the error messages mean. So I just gave > up (for now) trying to install 2.7. Any ideas or tips for (clearly) > uninformed folks like me? Cheers These messages usually mean a mismatch between RUBY_TARGETS and the eselected ruby version. I'll see if I can add some safeguards to the eclasses to better identify this and propose remedies.
