Bug 651948 – dev-lang/ruby-2.3.7 update installs only docs to system tree

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description G.Wolfe Woodbury 2018-03-29 20:02:43 UTC]

Updating dev-lang/ruby:2.3 to -2.3.7 (from -2.3.6) with command:

.    emerge --update dev-lang/ruby:2.3

completes without apparent error, but....

The log clearly shows that ONLY the doc files are propagated to the system. It is not clear if they even really get places in the /image tree within the emerge process.

Attaching:
$  emerge --info =dev-lang/ruby-2.3.7
< build logs>
< eclass files that may be relevant>
< fragment of ls(1) output for /usr/bin/ruby* >

[Comment 1 G.Wolfe Woodbury 2018-03-29 20:05:50 UTC]

Created attachment 526116 [details]
emerge --info =dev-lang/ruby-2.3.7

[Comment 2 G.Wolfe Woodbury 2018-03-29 20:10:31 UTC]

Created attachment 526118 [details]
primary build log for update of dev-lang/ruby:2.3

Note at the end that the only things it claims are merged into the system are the "doc" files.  Specifically, it does NOT report that /usr/bin/ruby23 gets merged.
<see the ls output fragments also attached>

[Comment 3 G.Wolfe Woodbury 2018-03-29 20:13:42 UTC]

Created attachment 526120 [details]
ebuild portage is using to build dev-lang/ruby-2.3.7

vanilla ebuild file from /usr/portage/dev-lang/ruby/.....

[Comment 4 G.Wolfe Woodbury 2018-03-29 20:21:28 UTC]

Created attachment 526122 [details]
directory listing of /usr/bin/ruby*

Note that the date on ruby23 is still from last year following the "successful" completion of the 'emerge --update' process.

[Comment 5 G.Wolfe Woodbury 2018-03-29 20:25:13 UTC]

Created attachment 526124 [details]
ruby-ng.eclass from /usr/portage/eclass

[Comment 6 G.Wolfe Woodbury 2018-03-29 20:26:15 UTC]

Created attachment 526126 [details]
ruby-single.eclass from /usr/portage/eclass

[Comment 7 G.Wolfe Woodbury 2018-03-29 20:27:53 UTC]

Created attachment 526128 [details]
ruby-utils.eclass from /usr/portage

[Comment 8 G.Wolfe Woodbury 2018-03-30 08:06:29 UTC]

The title change prior omits a critical aspect of the error in that it is the update (and initial install BTW) of ruby is failing to properly install anything *except* the docs. This falls out to several other Ruby situations (rubygems, rdoc, etc...) when the initial installation fails during a system install.

[Comment 9 Hans de Graaff 2018-04-02 06:14:22 UTC]

*** This bug has been marked as a duplicate of bug 594206 ***