Bug 488102 – sys-libs/libselinux-2.1.13-r4 fails with USE="-ruby" if RUBY_TARGETS does not include any of the supported targets

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Jaakko Perttilä 2013-10-15 09:03:29 UTC]

Looks like the USE="-ruby" is not respected and one of the supported ruby versions is required.


Reproducible: Always

Steps to Reproduce:
1. USE="-ruby"
2. RUBY_TARGETS="ruby20"
3. emerge sys-libs/libselinux
Actual Results:  
# USE="-ruby" RUBY_TARGETS="ruby20" emerge sys-libs/libselinux -v1

sys-libs/libselinux-2.1.13-r4  USE="(python) static-libs -ruby" PYTHON_TARGETS="python2_7 python3_2" RUBY_TARGETS="-ruby18 -ruby19*" 0 kB

Total: 1 package (1 reinstall), Size of downloads: 0 kB


>>> Verifying ebuild manifests

>>> Emerging (1 of 1) sys-libs/libselinux-2.1.13-r4
 * libselinux-2.1.13.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ...                                                              [ ok ]
 * patchbundle-libselinux-2.1.13-r3.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ...                                               [ ok ]
 * You need to select at least one compatible Ruby installation target via RUBY_TARGETS in make.conf.
 * Compatible targets for this package are: ruby18 ruby19
 * 
 * See http://www.gentoo.org/proj/en/prog_lang/ruby/index.xml#doc_chap3 for more information.
 * 
 * ERROR: sys-libs/libselinux-2.1.13-r4::gentoo failed (setup phase):
 *   No compatible Ruby target selected.
 * 
 * Call stack:
 *        ebuild.sh, line  93:  Called pkg_setup
 *        ebuild.sh, line 317:  Called ruby-ng_pkg_setup
 *   ruby-ng.eclass, line 413:  Called _ruby_each_implementation
 *   ruby-ng.eclass, line 402:  Called die
 * The specific snippet of code:
 *              die "No compatible Ruby target selected."
 * 
 * If you need support, post the output of `emerge --info '=sys-libs/libselinux-2.1.13-r4::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-libs/libselinux-2.1.13-r4::gentoo'`.
!!! When you file a bug report, please include the following information:
GENTOO_VM=  CLASSPATH="" JAVA_HOME=""
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info =libselinux-2.1.13
 * The complete build log is located at '/var/tmp/portage/sys-libs/libselinux-2.1.13-r4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-libs/libselinux-2.1.13-r4/temp/die.env'.
 * Working directory: '/usr/lib64/portage/pym'
 * S: '/var/tmp/portage/sys-libs/libselinux-2.1.13-r4/work/libselinux-2.1.13'

>>> Failed to emerge sys-libs/libselinux-2.1.13-r4, Log file:

>>>  '/var/tmp/portage/sys-libs/libselinux-2.1.13-r4/temp/build.log'

[Comment 1 Sven Vermeulen (RETIRED) 2013-10-27 18:10:10 UTC]

Indeed; the "inherit ruby-ng.eclass" pulls in the ruby-ng_pkg_setup() phase (in our pkg_setup()) which does not honor the RUBY_OPTIONAL variable.

I'll call ruby-ng_pkg_setup optionally myself in the ebuild.

[Comment 2 Sven Vermeulen (RETIRED) 2013-10-27 18:26:06 UTC]

Committed.

Also created bug #489608 as a feature request to update ruby-ng_pkg_setup() to honor the RUBY_OPTIONAL parameter.