Bug 414447 – media-libs/lv2core-6.0 stable request

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Vitaly 2012-05-03 07:33:50 UTC]

See build log attachment

Reproducible: Always

Steps to Reproduce:
1. install python2 and python3
2. emerge lv2core
Actual Results:  
Failed to emerge


It seems to me that problem is in python version

When I manually replace
#! /usr/bin/env python
with
#! /usr/bin/env python2
in "/var/tmp/portage/media-libs/lv2core-3.0/work/lv2core-3.0/waf" file, "./waf configure" goes fine

[Comment 1 Vitaly 2012-05-03 07:35:27 UTC]

Created attachment 310665 [details]
build log

[Comment 2 Vitaly 2012-05-03 07:35:47 UTC]

Created attachment 310667 [details]
emerge --info

[Comment 3 Cedric Sodhi 2012-05-15 09:47:31 UTC]

The wscript should explicitly request python 2 . requesting just "python" uses whatever eselect python has. Eselecting python2 also works.

[Comment 4 jannis 2012-12-08 20:52:16 UTC]

If this is still current (not yet fixed) you can try this:

add:
PYTHON_DEPEND="2"
before inherit, add:
python
to the "inherit"-line and add:
pkg_setup() {
        python_set_active_version 2
        python_pkg_setup
}
just before the src_prepare() or src_configure()-functions

[Comment 5 Casey Webster 2015-01-26 03:02:25 UTC]

Created attachment 394908 [details, diff]
patch to fix lv2core-3.0 ebuild on systems with python 3.

This patch fixes the ebuild so that this package can be emerged on systems where python2 is not the system default interpreter.

[Comment 6 Casey Webster 2015-01-26 03:03:41 UTC]

The year is 2015 and this bug still exists...  I have added a patch to the ebuild to fix it, please take a look at it.

[Comment 7 Casey Webster 2015-01-29 21:57:48 UTC]

Created attachment 395178 [details]
ebuild for lv2core-3.0 rewritten for EAPI=4 and current python class

The ebuild for stable lv2core-3.0 is out of date with current standards and does not emerge on systems where python 3 is the default interpreter.  This attachment is a new ebuild uses the current python eclass and will install correctly regardless of the default python interpreter.

[Comment 8 Toralf Förster 2015-08-08 08:28:00 UTC]

happened at stable too:

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

  This is an stable amd64 chroot image (named amd64-13.0-stable_20150802-112257) at a hardened host acting as a tinderbox.

Portage 2.2.20 (python 3.4.1-final-0, default/linux/amd64/13.0, gcc-4.8.4, glibc-2.20-r2, 4.0.8-hardened x86_64)
=================================================================
System uname: Linux-4.0.8-hardened-x86_64-Intel-R-_Core-TM-_i7-3770_CPU_@_3.40GHz-with-gentoo-2.2
KiB Mem:    16164692 total,   1409720 free

[Comment 9 Pacho Ramos 2016-03-07 13:00:01 UTC]

Probably time to stabilize a newer version using current python eclasses

[Comment 10 Agostino Sarubbo 2016-03-14 22:13:22 UTC]

amd64 stable

[Comment 11 Agostino Sarubbo 2016-03-15 15:27:16 UTC]

x86 stable. Closing.