| Summary: | dev-ruby/test-unit-3.0.9-r1 - /usr/bin/yard:9:in `load': cannot load such file -- /usr/lib64/ruby/gems/2.2.0/gems/yard-0.8.7.6/bin/yard (LoadError) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
| Component: | Current packages | Assignee: | Gentoo Ruby Team <ruby> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build.log | ||
|
Description
Juergen Rose
2015-02-15 19:01:07 UTC
BTW., I do not have any /usr/lib64/ruby/gems/2.2.0/gems/yard* subdirectory, although yard-0.8.7.6 is installed:
root@lynx:/root(18)# ll /usr/lib64/ruby/gems/2.2.0/gems/
total 24
drwxr-xr-x 3 root root 4096 Jan 11 09:11 json-1.8.2/
drwxr-xr-x 3 root root 4096 Feb 15 17:04 minitest-5.5.1/
drwxr-xr-x 3 root root 4096 Feb 15 17:04 power_assert-0.2.2/
drwxr-xr-x 4 root root 4096 Dec 29 10:23 racc-1.4.12/
drwxr-xr-x 4 root root 4096 Dec 29 10:22 rake-10.4.2/
drwxr-xr-x 4 root root 4096 Dec 29 10:24 rdoc-4.1.2/
root@lynx:/root(19)# qlist -Iv yard
dev-ruby/yard-0.8.7.6
root@lynx:/root(20)# emerge -pvD ruby yard
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] dev-lang/ruby-2.2.0-r1:2.2::gentoo USE="berkdb doc examples gdbm ipv6 ncurses rdoc readline ssl -debug -jemalloc -rubytests -socks5 -xemacs" 0 KiB
[ebuild N ] dev-ruby/test-unit-3.0.9-r1:2::gentoo USE="doc {-test}" RUBY_TARGETS="ruby19 ruby20 ruby22 -ruby21" 0 KiB
[ebuild R ] dev-ruby/yard-0.8.7.6::gentoo USE="doc {-test}" RUBY_TARGETS="ruby19 ruby20 -ruby21" 0 KiB
Could it be, that yard does not know ruby_targets_ruby22? https://github.com/lsegal/yard/issues/825 seems to be related. Switching back to ruby20 ('eselect ruby set ruby20') I was able to install test-unit-3.0.9-r1.
(In reply to Juergen Rose from comment #3) > https://github.com/lsegal/yard/issues/825 seems to be related. Related in the sense that this blocks us from adding ruby22 to yard. But the real issue here from a Gentoo perspective is bug 424339 where the eclass let's you try to install a ruby package that lacks the RUBY_TARGET of the currently eselected ruby. I hit this issue again. Is there not any patch? (In reply to Juergen Rose from comment #6) > I hit this issue again. Is there not any patch? I'm surprised that you are still seeing this since yard-0.8.7.6 has a ruby22 target. Which version of yard did you have installed when you saw this again? (In reply to Hans de Graaff from comment #7) > (In reply to Juergen Rose from comment #6) > > I hit this issue again. Is there not any patch? > > I'm surprised that you are still seeing this since yard-0.8.7.6 has a ruby22 > target. Which version of yard did you have installed when you saw this again? I just checked once more. I have yard-0.8.7.6: root@caiman:/root(11)# eselect ruby list Available Ruby profiles: [1] ruby19 (with Rubygems) [2] ruby20 (with Rubygems) [3] ruby22 (with Rubygems) * root@caiman:/root(12)# emerge -v1 test-unit These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] dev-ruby/test-unit-3.1.1:2::gentoo USE="doc {-test}" RUBY_TARGETS="ruby19 ruby20 ruby22 -ruby21" 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiB >>> Verifying ebuild manifests >>> Emerging (1 of 1) dev-ruby/test-unit-3.1.1::gentoo * test-unit-3.1.1.gem SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] >>> Unpacking source... * Running unpack phase for all ... * Unpacking .gem file... ... [ ok ] * Uncompressing metadata ... [ ok ] * Unpacking data.tar.gz ... [ ok ] >>> Source unpacked in /var/tmp/portage/dev-ruby/test-unit-3.1.1/work >>> Preparing source in /var/tmp/portage/dev-ruby/test-unit-3.1.1/work ... * Running prepare phase for all ... * Running source copy phase for ruby19 ... * Running source copy phase for ruby20 ... * Running source copy phase for ruby22 ... * Running prepare phase for ruby19 ... * Running prepare phase for ruby20 ... * Running prepare phase for ruby22 ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-ruby/test-unit-3.1.1/work ... >>> Source configured. >>> Compiling source in /var/tmp/portage/dev-ruby/test-unit-3.1.1/work ... * Running compile phase for all ... /usr/bin/yard:9:in `load': cannot load such file -- /usr/lib64/ruby/gems/2.2.0/gems/yard-0.8.7.6/bin/yard (LoadError) from /usr/bin/yard:9:in `<main>' * ERROR: dev-ruby/test-unit-3.1.1::gentoo failed (compile phase): * (no error message) * * Call stack: * ebuild.sh, line 93: Called src_compile * environment, line 4425: Called ruby-ng_src_compile * environment, line 4116: Called _ruby_invoke_environment 'all' 'all_ruby_compile' * environment, line 686: Called all_ruby_compile * environment, line 772: Called die * The specific snippet of code: * yard doc --title ${PN} || die; * * If you need support, post the output of `emerge --info '=dev-ruby/test-unit-3.1.1::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-ruby/test-unit-3.1.1::gentoo'`. !!! When you file a bug report, please include the following information: GENTOO_VM= CLASSPATH="/usr/libexec/ccp4/bin:" JAVA_HOME="/etc/java-config-2/current-system-vm" JAVACFLAGS="" COMPILER="" and of course, the output of emerge --info =test-unit-3.1.1 * The complete build log is located at '/var/tmp/portage/dev-ruby/test-unit-3.1.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-ruby/test-unit-3.1.1/temp/environment'. * Working directory: '/var/tmp/portage/dev-ruby/test-unit-3.1.1/work/all/test-unit-3.1.1' * S: '/var/tmp/portage/dev-ruby/test-unit-3.1.1/work/all/test-unit-3.1.1' >>> Failed to emerge dev-ruby/test-unit-3.1.1, Log file: >>> '/var/tmp/portage/dev-ruby/test-unit-3.1.1/temp/build.log' root@caiman:/root(13)# qlist -Iv yard dev-ruby/yard-0.8.7.6 (In reply to Hans de Graaff from comment #7) > (In reply to Juergen Rose from comment #6) > > I hit this issue again. Is there not any patch? > > I'm surprised that you are still seeing this since yard-0.8.7.6 has a ruby22 > target. Which version of yard did you have installed when you saw this again? Also reinstalling of yard does not help. There is not any /usr/lib64/ruby/gems/2.2.0/gems/yard-* directory after reinstalling of yard: root@caiman:/root(16)# ll /usr/lib64/ruby/gems/2.2.0/gems/ total 28 drwxr-xr-x 3 root root 4096 Jan 12 01:10 json-1.8.2/ drwxr-xr-x 3 root root 4096 May 10 10:27 minitest-5.6.1/ drwxr-xr-x 3 root root 4096 Mar 7 14:32 power_assert-0.2.3/ drwxr-xr-x 4 root root 4096 Dec 28 13:06 racc-1.4.12/ drwxr-xr-x 4 root root 4096 Dec 28 13:05 rake-10.4.2/ drwxr-xr-x 4 root root 4096 Dec 28 13:07 rdoc-4.1.2/ drwxr-xr-x 3 root root 4096 May 30 09:40 test-unit-3.1.1/ (In reply to Juergen Rose from comment #9) > Also reinstalling of yard does not help. There is not any > /usr/lib64/ruby/gems/2.2.0/gems/yard-* directory after reinstalling of yard: Did you verify that yard's ruby22 target was enabled when reinstalling? (In reply to Hans de Graaff from comment #10) > (In reply to Juergen Rose from comment #9) > > > Also reinstalling of yard does not help. There is not any > > /usr/lib64/ruby/gems/2.2.0/gems/yard-* directory after reinstalling of yard: > > Did you verify that yard's ruby22 target was enabled when reinstalling? It was not explicitly enabled. I had only ruby22 eselected and so far as I see I did not set a USE flag -ruby22. root@caiman:/root(24)# eselect ruby list Available Ruby profiles: [1] ruby19 (with Rubygems) [2] ruby20 (with Rubygems) [3] ruby22 (with Rubygems) * root@caiman:/root(25)# grep ruby22 /etc/portage/package.use >=dev-ruby/json-1.8.1 ruby_targets_ruby22 >=dev-ruby/minitest-5.5.1 ruby_targets_ruby22 >=dev-ruby/power_assert-0.2.3 ruby_targets_ruby22 >=dev-ruby/racc-1.4.10 ruby_targets_ruby22 >=dev-ruby/rake-0.9.6-r1 ruby_targets_ruby22 >=dev-ruby/rdoc-4.0.1-r2 ruby_targets_ruby22 >=dev-ruby/rubygems-2.0.14 ruby_targets_ruby22 >=dev-ruby/test-unit-3.0.9-r1 ruby_targets_ruby22 >=virtual/rubygems-6 ruby_targets_ruby22 root@caiman:/root(26)# emerge -pv1 yard These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] dev-ruby/yard-0.8.7.6::gentoo USE="doc {-test}" RUBY_TARGETS="ruby19 ruby20 -ruby21 -ruby22" 0 KiB What I have to do? Set ruby22 or ruby_targets_ruby22 for yard? (In reply to Juergen Rose from comment #11) > What I have to do? Set ruby22 or ruby_targets_ruby22 for yard? It is probably not a good idea to eselect a ruby version that you do not also have selected in RUBY_TARGETS so you might want to match these two. (In reply to Hans de Graaff from comment #12) > It is probably not a good idea to eselect a ruby version that you do not > also have selected in RUBY_TARGETS so you might want to match these two. I have now filed bug 551432 for this. (In reply to Hans de Graaff from comment #12) > (In reply to Juergen Rose from comment #11) > > > What I have to do? Set ruby22 or ruby_targets_ruby22 for yard? > > It is probably not a good idea to eselect a ruby version that you do not > also have selected in RUBY_TARGETS so you might want to match these two. That means, that I should explicitly set RUBY_TARGETS="ruby22" in /etc/make.conf? I don't have any RUBY_TARGETS in /etc/make.conf. I would expect, that this target is set, if I eselect ruby22. |
