Bug 539272 – stable version of dev-python/pylibacl doesn't respect PYTHON_TARGETS

• Status: RESOLVED OBSOLETE
• Product: Gentoo Linux

[Description Ivan Labáth 2015-02-07 20:32:55 UTC]

I was trying to emerge app-backup/bup, which is itself an unstable package, so I have keyworded it. It failed to install with its default use flags, as it then depends on a stable package, dev-python/pylibacl-0.5.0, which itself fails to build.

Reproducible: Always

Steps to Reproduce:
1. emerge -1 pylibacl
Actual Results:  
Build fails.

Expected Results:  
Package should build and merge successfully.

The build stops at

 * Building of dev-python/pylibacl-0.5.0 with CPython 3.4...
python3.4 setup.py build -b build-3.4
Traceback (most recent call last):
  File "setup.py", line 4, in <module>
    from setuptools import setup, Extension
ImportError: No module named 'setuptools'

emerge --info:
Portage 2.2.14 (python 2.7.9-final-0, default/linux/x86/13.0/desktop, gcc-4.8.3, glibc-2.19-r1, 3.14.26 i686)
=================================================================
System uname: Linux-3.14.26...
Timestamp of tree: Sat, 07 Feb 2015 00:45:01 +0000
ld GNU ld (Gentoo 2.24 p1.4) 2.24
app-shells/bash:          4.2_p53
dev-java/java-config:     2.2.0
dev-lang/perl:            5.18.2-r2
dev-lang/python:          2.7.9-r1, 3.3.5-r1, 3.4.1
dev-util/cmake:           2.8.12.2-r1
dev-util/pkgconfig:       0.28-r1
sys-apps/baselayout:      2.2
sys-apps/openrc:          0.13.8
sys-apps/sandbox:         2.6-r1
sys-devel/autoconf:       2.13, 2.69
sys-devel/automake:       1.11.6-r1, 1.12.6, 1.13.4
sys-devel/binutils:       2.24-r3
sys-devel/gcc:            4.7.3-r1::local, 4.8.3
sys-devel/gcc-config:     1.7.3
sys-devel/libtool:        2.4.4
sys-devel/make:           4.0-r1
sys-kernel/linux-headers: 3.16 (virtual/os-headers)
sys-libs/glibc:           2.19-r1
Repositories: gentoo local
ACCEPT_KEYWORDS="x86"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -pipe -march=native"
CHOST="i686-pc-linux-gnu"
CXXFLAGS="-O2 -pipe -march=native"
FCFLAGS="-O2 -march=i686 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs protect-owned sandbox sfperms splitdebug strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-O2 -march=i686 -pipe"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,--hash-style=gnu -Wl,--sort-common"
PORTAGE_CONFIGROOT="/"
USE="... xattr" ABI_X86="32" CPU_FLAGS_X86=... ELIBC="glibc" KERNEL="linux" LINGUAS="en sk" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_3" USERLAND="GNU"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, MAKEOPTS, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, SYNC, USE_PYTHON

[Comment 1 Ivan Labáth 2015-02-07 20:36:03 UTC]

Installed python versions and flags:

$ eix ^python$
[I] dev-lang/python
     Available versions:  
     (2.7)  2.7.7 ~2.7.8 2.7.9-r1
     (3.2)  3.2.5-r6
     (3.3)  3.3.5-r1
     (3.4)  ~3.4.0 3.4.1 ~3.4.2
       {-berkdb build doc examples gdbm hardened ipv6 +ncurses +readline sqlite +ssl +threads tk +wide-unicode wininst +xml ELIBC="uclibc"}
     Installed versions:
         2.7.9-r1(2.7)(09:37:18 01/11/15)(gdbm ipv6 ncurses readline sqlite ssl threads tk wide-unicode xml -berkdb -build -doc -examples -hardened -wininst ELIBC="-uclibc")
         3.3.5-r1(3.3)(14:08:39 01/11/15)(gdbm ipv6 ncurses readline sqlite ssl threads tk xml -build -doc -examples -hardened -wininst ELIBC="-uclibc")
         3.4.1(3.4)(02:26:15 10/19/14)(gdbm ipv6 ncurses readline sqlite ssl threads tk xml -build -examples -hardened -wininst ELIBC="-uclibc")
     Homepage:            http://www.python.org/
     Description:         An interpreted, interactive, object-oriented programming language

[Comment 2 Ivan Labáth 2015-02-07 20:37:39 UTC]

Created attachment 395840 [details]
build.log

[Comment 3 Ivan Labáth 2015-02-07 20:42:17 UTC]

Information as suggested in the error message

$ emerge -pqv '=dev-python/pylibacl-0.5.0::gentoo'
[ebuild  N    ] dev-python/pylibacl-0.5.0

[Comment 4 Ivan Labáth 2015-02-26 11:42:41 UTC]

It seems to me, that the stable version of pylibacl (0.5.0) builds the package for eselected version, yet setuptools uses PYTHON_TARGETS.

I had python 2.7, 3.3 and 3.4 installed,
eselected were 2.7 and 3.4,
but PYTHON_TARGETS was automatically set to 2.7 and 3.3,
so setuptools were needed yet not built for 3.4.

I don't know much about gentoo policy, but it would be nice, if the stable version of pylibacl respected PYTHON_TARGETS. Most other packages do.

Perhaps it would suffice to stabilize pylibacl-0.5.0-r1 on architectures where 0.5.0 is stable?

[Comment 5 Justin Lecher (RETIRED) 2015-08-04 13:52:32 UTC]

+  04 Aug 2015; Justin Lecher <[e-mail]> -pylibacl-0.5.0.ebuild:
+  Drop old, obsoletes bug #539272
+