Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 681886 - dev-ruby/asciidoctor: /.../asciidoctor:9:in load : cannot load such file -- /usr/lib64/ruby/gems/2.6.0/gems/asciidoctor-1.5.8/bin/asciidoctor (LoadError)
Summary: dev-ruby/asciidoctor: /.../asciidoctor:9:in load : cannot load such file -- ...
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Ruby Team
URL:
Whiteboard:
Keywords:
: 681890 681994 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-03-27 22:25 UTC by Toralf Förster
Modified: 2019-04-28 18:16 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge-info.txt (emerge-info.txt,15.96 KB, text/plain)
2019-03-27 22:26 UTC, Toralf Förster
Details
app-backup:btrbk-0.27.2:20190327-175847.log (app-backup:btrbk-0.27.2:20190327-175847.log,2.03 KB, text/plain)
2019-03-27 22:26 UTC, Toralf Förster
Details
emerge-history.txt (emerge-history.txt,96.95 KB, text/plain)
2019-03-27 22:26 UTC, Toralf Förster
Details
environment (environment,56.79 KB, text/plain)
2019-03-27 22:26 UTC, Toralf Förster
Details
etc.portage.tbz2 (etc.portage.tbz2,11.28 KB, application/x-bzip)
2019-03-27 22:26 UTC, Toralf Förster
Details
temp.tbz2 (temp.tbz2,14.93 KB, application/x-bzip)
2019-03-27 22:26 UTC, Toralf Förster
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Toralf Förster gentoo-dev 2019-03-27 22:25:58 UTC
Traceback (most recent call last):
	1: from /usr/bin/asciidoctor:9:in `<main>'
/usr/bin/asciidoctor:9:in `load': cannot load such file -- /usr/lib64/ruby/gems/2.6.0/gems/asciidoctor-1.5.8/bin/asciidoctor (LoadError)
make: *** [Makefile:61: btrbk.1] Error 1
make: Leaving directory '/var/tmp/portage/app-backup/btrbk-0.27.2/work/btrbk-0.27.2/doc'
 * ERROR: app-backup/btrbk-0.27.2::gentoo failed (compile phase):

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.1-desktop_20190325-132027

  -------------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-8.3.0 *

Available Python interpreters, in order of preference:
  [1]   python3.6
  [2]   python2.7 (fallback)
Available Ruby profiles:
  [1]   ruby24 (with Rubygems)
  [2]   ruby25 (with Rubygems)
  [3]   ruby26 (with Rubygems) *
Available Rust versions:
  [1]   rust-1.32.0 *
java-config:
The following VMs are available for generation-2:
*)	IcedTea JDK 3.10.0 [icedtea-bin-8]
Available Java Virtual Machines:
  [1]   icedtea-bin-8  system-vm

emerge -qpvO app-backup/btrbk
[ebuild  N    ] app-backup/btrbk-0.27.2  USE="doc pv"
Comment 1 Toralf Förster gentoo-dev 2019-03-27 22:26:01 UTC
Created attachment 570950 [details]
emerge-info.txt
Comment 2 Toralf Förster gentoo-dev 2019-03-27 22:26:04 UTC
Created attachment 570952 [details]
app-backup:btrbk-0.27.2:20190327-175847.log
Comment 3 Toralf Förster gentoo-dev 2019-03-27 22:26:09 UTC
Created attachment 570954 [details]
emerge-history.txt
Comment 4 Toralf Förster gentoo-dev 2019-03-27 22:26:12 UTC
Created attachment 570956 [details]
environment
Comment 5 Toralf Förster gentoo-dev 2019-03-27 22:26:15 UTC
Created attachment 570958 [details]
etc.portage.tbz2
Comment 6 Toralf Förster gentoo-dev 2019-03-27 22:26:17 UTC
Created attachment 570960 [details]
temp.tbz2
Comment 7 Axel Burri 2019-03-28 10:27:37 UTC
There seems to be a problem with your Ruby setup:

> Attachment: emerge-history.txt:
> /usr/bin/asciidoctor:9:in `load': cannot load such file -- /usr/lib64/ruby/gems/2.6.0/gems/asciidoctor-1.5.8/bin/asciidoctor (LoadError)

For some reason asciidoctor tries to load rubygems from ruby-2.6, but asciidoctor builds only with ruby-2.3 and ruby-2.4 (plus ruby-2.5 for asciidoctor-1.5.8):

  # grep USE_RUBY /usr/portage/dev-ruby/asciidoctor/asciidoctor-1.5.7.1.ebuild
  USE_RUBY="ruby23 ruby24"
  # grep USE_RUBY /usr/portage/dev-ruby/asciidoctor/asciidoctor-1.5.8.ebuild
  USE_RUBY="ruby23 ruby24 ruby25"

From your post I see that you have ruby24 installed (required by asciidoc), and selected ruby26.
I'm not sure how gentoo handles this with the selection of the ruby gems, but for some reasons portage is not able to point to the correct ruby24 gems. Even if dev-lang/ruby-2.6 is masked, this should still work.


It probably works if you run:

  # eselect ruby set ruby24
  # emerge app-backup/btrbk
Comment 8 Toralf Förster gentoo-dev 2019-03-28 20:44:42 UTC
(In reply to Axel Burri from comment #7)
> There seems to be a problem with your Ruby setup:
Well, this is the tinderbox, it doesn nothing special particular to Ruby.

> It probably works if you run:
> 
>   # eselect ruby set ruby24
>   # emerge app-backup/btrbk
yes
Comment 9 Toralf Förster gentoo-dev 2019-03-30 09:15:21 UTC
*** Bug 681890 has been marked as a duplicate of this bug. ***
Comment 10 Toralf Förster gentoo-dev 2019-03-30 09:15:28 UTC
*** Bug 681994 has been marked as a duplicate of this bug. ***
Comment 11 Craig Andrews gentoo-dev 2019-04-17 19:14:21 UTC
Toralf, this seems to be a ruby or asciidoctor problem, and not related to btrbk.

Therefore, I'm assigning to the ruby team.
Comment 12 Toralf Förster gentoo-dev 2019-04-27 07:17:49 UTC
(In reply to Craig Andrews from comment #11)
> Toralf, this seems to be a ruby or asciidoctor problem, and not related to
> btrbk.
> 
> Therefore, I'm assigning to the ruby team.

indeed, happaned again and again:
Traceback (most recent call last):
	1: from /usr/bin/asciidoctor:9:in `<main>'
/usr/bin/asciidoctor:9:in `load': cannot load such file -- /usr/lib64/ruby/gems/2.6.0/gems/asciidoctor-2.0.7/bin/asciidoctor (LoadError)
make: *** [Makefile:52: btrbk.1] Error 1
make: Leaving directory '/var/tmp/portage/app-backup/btrbk-0.28.0/work/btrbk-0.28.0/doc'
 * ERROR: app-backup/btrbk-0.28.0::gentoo failed (compile phase):
Comment 13 Hans de Graaff gentoo-dev 2019-04-28 18:16:54 UTC
You are trying to use a non-ruby26 package with ruby26 eselected. That doesn't work. Unfortunately there is nothing preventing you from doing this (e.g. fancy wrappers or runtime checks) so you'll get these kinds of errors.