Bug 670154 – www-apache/passenger-5.3.5 : * rake failed

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Toralf Förster 2018-11-02 16:56:34 UTC]

 * ERROR: www-apache/passenger-5.3.5::gentoo failed (install phase):
 *   rake failed
 * 

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

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.0-desktop-gnome-systemd_20181026-172613

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

gcc-config -l:
 [1] x86_64-pc-linux-gnu-7.3.1
 [2] x86_64-pc-linux-gnu-8.2.0 *

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

emerge -qpvO www-apache/passenger
[ebuild  N    ] www-apache/passenger-5.3.5  USE="-apache2 -debug -test" RUBY_TARGETS="ruby23 -ruby24 -ruby25"

[Comment 1 Toralf Förster 2018-11-02 16:56:36 UTC]

Created attachment 553872 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2018-11-02 16:56:39 UTC]

Created attachment 553874 [details]
emerge-history.txt

[Comment 3 Toralf Förster 2018-11-02 16:56:42 UTC]

Created attachment 553876 [details]
environment

[Comment 4 Toralf Förster 2018-11-02 16:56:45 UTC]

Created attachment 553878 [details]
etc.portage.tbz2

[Comment 5 Toralf Förster 2018-11-02 16:56:47 UTC]

Created attachment 553880 [details]
logs.tbz2

[Comment 6 Toralf Förster 2018-11-02 16:56:50 UTC]

Created attachment 553882 [details]
www-apache:passenger-5.3.5:20181102-141906.log

[Comment 7 Hans de Graaff 2018-11-07 18:53:35 UTC]

(In reply to Toralf Förster from comment #0)

> Available Ruby profiles:
>   [1]   ruby23 (with Rubygems)
>   [2]   ruby25 (with Rubygems) *

> RUBY_TARGETS="ruby23 -ruby24 -ruby25"

This is not a supported configuration (use an eselected version that is not in RUBY_TARGETS).

[Comment 8 Toralf Förster 2018-11-08 20:08:16 UTC]

(In reply to Hans de Graaff from comment #7)
This is the tinderbox [¹] - how can I catch this situation which simply happened during "qsearch --all | sort --random-sort | xargs -n 1 emerge --update" ?


[¹] https://zwiebeltoralf.de/tinderbox.html

[Comment 9 Hans de Graaff 2018-11-11 08:42:54 UTC]

Perhaps it would work to set up a mask for ruby versions not matching the RUBY_TARGETS that you want to test? Or alternatively make sure that RUBY_TARGETS matches what you are testing. Especially when testing ~arch this could go wrong easily since RUBY_TARGETS will be ruby23 by default but emerging dev-lang/ruby may pull in ruby:2.5.