* Running compile phase for all ... ronn -w -s toc -r5 --markdown man/*.ronn /usr/lib64/ruby/2.2.0/x86_64-linux/rbconfig.rb:7:in `<module:RbConfig>': ruby lib version (2.2.7) doesn't match executable version (2.1.10) (RuntimeError) from /usr/lib64/ruby/2.2.0/x86_64-linux/rbconfig.rb:5:in `<top (required)>' from /usr/lib64/ruby/site_ruby/2.2.0/rubygems.rb:9:in `require' from /usr/lib64/ruby/site_ruby/2.2.0/rubygems.rb:9:in `<top (required)>' ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-gnome-systemd_20170815-183537 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python2.7 (fallback) [4] pypy3 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) * [2] ruby22 (with Rubygems) java-config: The following VMs are available for generation-2: emerge -qpv app-text/ronn [ebuild N ] app-text/ronn-0.7.3-r3 USE="{-test}" RUBY_TARGETS="ruby22 -ruby23 -ruby24"
Created attachment 490476 [details] emerge-info.txt
Created attachment 490478 [details] app-text:ronn-0.7.3-r3:20170824-134016.log
Created attachment 490480 [details] emerge-history.txt
Created attachment 490482 [details] environment
Created attachment 490484 [details] etc.portage.tbz2
The problem comes from the eselect configuration to actually point to ruby 2.1 instead of 2.2, the error itself states that. Had the same problem, I solved it by configuring eselect to point to ruby22 instead of 21 in your case would be: eselect ruby set 2
So is this a bug or PEBKAC ? In the later case I do wonder if an ewarn would makes sense ?
I just lunched a world update and I have the same error (with 2.5.8 and 2.4.10 because time has passed). So I think that the ebuild should force the ruby version base on the RUBY_TARGETS variable or something like that.
Also please note that this puts the system in a state where “classical” emerge commands are failing: alarig ~ # emerge --ask --depclean * Always study the list of packages to be cleaned for any obvious * mistakes. Packages that are part of the world set will always * be kept. They can be manually added to this set with * `emerge --noreplace <atom>`. Packages that are listed in * package.provided (see portage(5)) will be removed by * depclean, even if they are part of the world set. * * As a safety measure, depclean will not remove any packages * unless *all* required dependencies have been resolved. As a * consequence of this, it often becomes necessary to run * `emerge --update --newuse --deep @world` prior to depclean. Calculating dependencies... done! * Dependencies could not be completely resolved due to * the following required packages not being installed: * * >=dev-ruby/hpricot-0.8.2[ruby_targets_ruby24(-)] pulled in by: * app-text/ronn-0.7.3-r3 * * >=dev-ruby/rdoc-5.1.0-r1[ruby_targets_ruby24] pulled in by: * dev-lang/ruby-2.4.10 * * >=dev-ruby/json-2.0.2[ruby_targets_ruby24] pulled in by: * dev-lang/ruby-2.4.10 * * >=dev-ruby/test-unit-3.2.3[ruby_targets_ruby24] pulled in by: * dev-lang/ruby-2.4.10 * * >=dev-ruby/rdiscount-1.5.8[ruby_targets_ruby24(-)] pulled in by: * app-text/ronn-0.7.3-r3 * * >=dev-ruby/net-telnet-0.1.1[ruby_targets_ruby24] pulled in by: * dev-lang/ruby-2.4.10 * * >=dev-ruby/rake-12.0.0[ruby_targets_ruby24] pulled in by: * dev-lang/ruby-2.4.10 * * virtual/rubygems[ruby_targets_ruby24(-)] pulled in by: * app-text/ronn-0.7.3-r3 * * >=dev-ruby/mustache-0.7.0[ruby_targets_ruby24(-)] pulled in by: * app-text/ronn-0.7.3-r3 * * >=dev-ruby/power_assert-0.4.1[ruby_targets_ruby24] pulled in by: * dev-lang/ruby-2.4.10 * * >=dev-ruby/xmlrpc-0.2.1[ruby_targets_ruby24] pulled in by: * dev-lang/ruby-2.4.10 * * virtual/rubygems[ruby_targets_ruby24(-)] pulled in by: * dev-ruby/did_you_mean-1.1.2 * * virtual/rubygems[ruby_targets_ruby24] pulled in by: * dev-lang/ruby-2.4.10 * * >=dev-ruby/minitest-5.10.1[ruby_targets_ruby24] pulled in by: * dev-lang/ruby-2.4.10 * * Have you forgotten to do a complete update prior to depclean? The * most comprehensive command for this purpose is as follows: * * emerge --update --newuse --deep --with-bdeps=y @world * * Note that the --with-bdeps=y option is not required in many * situations. Refer to the emerge manual page (run `man emerge`) * for more information about --with-bdeps. * * Also, note that it may be necessary to manually uninstall * packages that no longer exist in the repository, since it may not * be possible to satisfy their dependencies. alarig ~ # emerge -vac =dev-lang/ruby-2.4.10 Calculating dependencies... done! dev-lang/ruby-2.4.10 pulled in by: app-text/ronn-0.7.3-r3 requires dev-lang/ruby:2.4 dev-ruby/did_you_mean-1.1.2 requires dev-lang/ruby:2.4 >>> No packages selected for removal by depclean Packages installed: 1398 Packages in world: 203 Packages in system: 43 Required packages: 1398 Number removed: 0
*** Bug 729388 has been marked as a duplicate of this bug. ***
>>> Compiling source in /Users/fabian/Gentoo-11.0i/var/tmp/portage/app-text/ronn-0.7.3-r3/work ... * Running compile phase for all ... NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4 Gem::Specification#has_rdoc= called from (eval):92. ronn -w -s toc -r5 --markdown man/*.ronn Traceback (most recent call last): 5: from <internal:gem_prelude>:2:in `<internal:gem_prelude>' 4: from <internal:gem_prelude>:2:in `require' 3: from /Users/fabian/Gentoo-11.0i/usr/lib/ruby/site_ruby/2.6.0/rubygems.rb:8:in `<top (required)>' 2: from /Users/fabian/Gentoo-11.0i/usr/lib/ruby/site_ruby/2.6.0/rubygems.rb:8:in `require' 1: from /Users/fabian/Gentoo-11.0i/usr/lib/ruby/2.6.0/x86_64-darwin20/rbconfig.rb:11:in `<top (required)>' /Users/fabian/Gentoo-11.0i/usr/lib/ruby/2.6.0/x86_64-darwin20/rbconfig.rb:13:in `<module:RbConfig>': ruby lib version (2.6.6) doesn't match executable version (2.5.8) (RuntimeError) rake aborted! Command failed with status (1): [ronn -w -s toc -r5 --markdown man/*.ronn...] /Users/fabian/Gentoo-11.0i/var/tmp/portage/app-text/ronn-0.7.3-r3/work/all/ronn-0.7.3/Rakefile:50:in `block in <top (required)>' Tasks: TOP => man (See full trace by running task with --trace) * ERROR: app-text/ronn-0.7.3-r3::gentoo_prefix failed (compile phase): * (no error message)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3f8b37bcc2fa62a29b40c199bc2d5ac9e33451dc commit 3f8b37bcc2fa62a29b40c199bc2d5ac9e33451dc Author: David Seifert <soap@gentoo.org> AuthorDate: 2023-04-30 10:06:10 +0000 Commit: David Seifert <soap@gentoo.org> CommitDate: 2023-04-30 10:06:10 +0000 app-text/ronn: treeclean Closes: https://bugs.gentoo.org/628838 Closes: https://bugs.gentoo.org/743956 Closes: https://bugs.gentoo.org/770907 Closes: https://bugs.gentoo.org/863965 Signed-off-by: David Seifert <soap@gentoo.org> app-text/ronn/Manifest | 1 - app-text/ronn/metadata.xml | 11 -------- app-text/ronn/ronn-0.7.3-r4.ebuild | 51 -------------------------------------- profiles/package.mask | 6 ----- 4 files changed, 69 deletions(-)
