Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 594962 - dev-ruby/rubygems-2.2.5-r1 will not build from source due to error in ebuild/eclass scripts
Summary: dev-ruby/rubygems-2.2.5-r1 will not build from source due to error in ebuild/...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal major (vote)
Assignee: Gentoo Ruby Team
URL:
Whiteboard:
Keywords:
Depends on: 594206
Blocks:
  Show dependency tree
 
Reported: 2016-09-23 20:55 UTC by G.Wolfe Woodbury
Modified: 2016-10-17 11:47 UTC (History)
1 user (show)

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


Attachments
emerge --info file (einfo.txt,16.16 KB, text/plain)
2016-09-23 20:55 UTC, G.Wolfe Woodbury
Details
build log file for dev-ruby/rubygems-2.2.5-r1 (build.log,2.65 KB, text/plain)
2016-09-23 20:56 UTC, G.Wolfe Woodbury
Details
ebuild environment file (environment,154.62 KB, text/plain)
2016-09-23 20:57 UTC, G.Wolfe Woodbury
Details
ebuild file for dev-ruby/rubygems-2.2.5-r1 (rubygems-2.2.5-r1.ebuild,4.26 KB, text/plain)
2016-09-23 20:58 UTC, G.Wolfe Woodbury
Details
latest emerge --info (einfo.txt,16.67 KB, text/plain)
2016-10-02 21:56 UTC, G.Wolfe Woodbury
Details
dev-ruby/rubygems ebuild used (rubygems-2.6.7.ebuild,3.87 KB, text/plain)
2016-10-02 21:58 UTC, G.Wolfe Woodbury
Details
current build log (2.6.7) (rubygems-2.6.7:20161002-214923.log,2.72 KB, text/plain)
2016-10-02 21:58 UTC, G.Wolfe Woodbury
Details
emerge --info for attempt on 2016/10/12 (einfo.txt,16.67 KB, text/plain)
2016-10-13 00:03 UTC, G.Wolfe Woodbury
Details
emerge -pqv output for attempt on 2016/10/12 (einfo-pqv.txt,307 bytes, text/plain)
2016-10-13 00:04 UTC, G.Wolfe Woodbury
Details
environment dump from attempt 2016/10/12 (environment.txt,154.86 KB, text/plain)
2016-10-13 00:05 UTC, G.Wolfe Woodbury
Details
ebuild as recorded on my system 2016/10/12 (rubygems-2.6.7.ebuild,3.87 KB, text/plain)
2016-10-13 00:06 UTC, G.Wolfe Woodbury
Details
portage build log of attempt 2016/10/12 (rubygems-2.6.7:20161012-234425.log,2.72 KB, text/plain)
2016-10-13 00:07 UTC, G.Wolfe Woodbury
Details
screen capture of error 2016/10/12 (screencp.txt,3.33 KB, text/plain)
2016-10-13 00:09 UTC, G.Wolfe Woodbury
Details

Note You need to log in before you can comment on or make changes to this bug.
Description G.Wolfe Woodbury 2016-09-23 20:55:07 UTC
Created attachment 447658 [details]
emerge --info file

Following the failures to install dev-lang/ruby:2.1.9, I hand-crafted an ebuild and got dev-lang/ruby to install; however, rubygems fails to install and kill all the dependencies of dev-lang/ruby.

Will attach "emerge --info' 'build.log' 'environment' and the relevant 'ebuild'
for the failures.

As with dev-lang/ruby, this blocks the installation of kde-plasma/plasma-meta on a fresh install.
Comment 1 G.Wolfe Woodbury 2016-09-23 20:56:29 UTC
Created attachment 447660 [details]
build log file for dev-ruby/rubygems-2.2.5-r1
Comment 2 G.Wolfe Woodbury 2016-09-23 20:57:10 UTC
Created attachment 447662 [details]
ebuild environment file
Comment 3 G.Wolfe Woodbury 2016-09-23 20:58:06 UTC
Created attachment 447664 [details]
ebuild file for dev-ruby/rubygems-2.2.5-r1
Comment 4 G.Wolfe Woodbury 2016-09-30 20:37:03 UTC
dev-ruby/json also fails for the same reason rubygems fails:

The implementation of 'each_ruby_configure' and '_ruby_each_implementation' fails to set/maintaion the {$RUBY} variable and the build fails because of a bad environment.

Do you want a formal new bug for dev-ruby/json filled out?

This is attempting to do the recent updates released to the unstable tree.
Comment 5 Hans de Graaff gentoo-dev 2016-10-02 06:12:09 UTC
(In reply to G.Wolfe Woodbury from comment #4)
> dev-ruby/json also fails for the same reason rubygems fails:
> 
> The implementation of 'each_ruby_configure' and '_ruby_each_implementation'
> fails to set/maintaion the {$RUBY} variable and the build fails because of a
> bad environment.

I think these are the result of your hand-crafted dev-lang/ruby ebuild. I'm inclined to close this as INVALID, but let's see if we can fix the dev-lang/ruby issues first and then retest this.
Comment 6 G.Wolfe Woodbury 2016-10-02 21:31:06 UTC
I am not using a "hand-crafted" ebuild when testing for the bug. The patch is a partial fix for one problem.  I always test against the vanilla ebuilds.
Comment 7 G.Wolfe Woodbury 2016-10-02 21:55:51 UTC
I pulled the latest rubygems (2.6.7) and did an update.  Enclosed are the einfo, ebuild and build log results. No change in status.
Comment 8 G.Wolfe Woodbury 2016-10-02 21:56:42 UTC
Created attachment 448910 [details]
latest emerge --info
Comment 9 G.Wolfe Woodbury 2016-10-02 21:58:12 UTC
Created attachment 448912 [details]
dev-ruby/rubygems ebuild used

just pulled from portage
Comment 10 G.Wolfe Woodbury 2016-10-02 21:58:55 UTC
Created attachment 448914 [details]
current build log (2.6.7)
Comment 11 G.Wolfe Woodbury 2016-10-03 11:27:44 UTC
(In reply to G.Wolfe Woodbury from comment #6)
> I am not using a "hand-crafted" ebuild when testing for the bug. The patch
> is a partial fix for one problem.  I always test against the vanilla ebuilds.

To state it more precisely: I've done enough QA and Testing in my time that when filing a bug, I will present the ebuild and sources "as is". Anything I do in terms of making my own versions is done in a VM and isolated from the stuff I file.  It is hard enough to isolate and figure the precise dynamics of complex software, I would not want to make it any harder for the maintainers by making them deal with my changes as well.
Comment 12 G.Wolfe Woodbury 2016-10-13 00:01:36 UTC
Attaching the full build information from the latest attempt to install/update the  rubygems package while updating kde and qt stuff.  I am almost to the pooint of attempting to install ruby on a stable 64-bit virtualbox vm: if there are problems there (or not!) I will report them here.

attaching:
  einfo.txt
  einfo-pqv.txt
  environment.txt
  rubygems-2.6.7.ebuild
  rubygems-2.6.7:20161012-234425.log
  screencap.txt
Comment 13 G.Wolfe Woodbury 2016-10-13 00:03:46 UTC
Created attachment 450048 [details]
emerge --info for attempt on 2016/10/12

This batch of attachments is the full information for a build attempt on
2016/10/12
Comment 14 G.Wolfe Woodbury 2016-10-13 00:04:46 UTC
Created attachment 450050 [details]
emerge -pqv output for attempt on 2016/10/12
Comment 15 G.Wolfe Woodbury 2016-10-13 00:05:35 UTC
Created attachment 450052 [details]
environment dump from attempt 2016/10/12
Comment 16 G.Wolfe Woodbury 2016-10-13 00:06:25 UTC
Created attachment 450054 [details]
ebuild as recorded on my system 2016/10/12
Comment 17 G.Wolfe Woodbury 2016-10-13 00:07:28 UTC
Created attachment 450056 [details]
portage build log of attempt 2016/10/12
Comment 18 G.Wolfe Woodbury 2016-10-13 00:09:32 UTC
Created attachment 450058 [details]
screen capture of error 2016/10/12

tail end of screen dump and error messages to CLI console doing the emerge.
Comment 19 G.Wolfe Woodbury 2016-10-17 11:47:33 UTC
Actually did a new install of dev-lang/ruby:2.3 on a new machine. ruby23 built and installed, but rubygems et alia did not install; failing the same way as documented. [Full diagnostics available if requested]