I dont have python3 on my system. There doesn't seem to be any python3 depandency in the ebuild, but when in the configure step, libcap-ng fails with ------------------------------------------------------------------ checking whether to create python bindings... testing checking for python version... 2.7 checking for python platform... linux2 checking for python script directory... ${prefix}/lib64/python2.7/site-packages checking for python extension module directory... ${exec_prefix}/lib64/python2.7/site-packages configure: Python bindings will be built checking whether to create python3 bindings... yes checking for python3... no The python3 program was not found in the search path. Please ensure that it is installed and its directory is included in the search path or pass --without-python3 to ./configure. ------------------------------------------------------------------ The emerge looks like this : orzel@berlioz /home/orzel% emerge -1 sys-libs/libcap-ng [ebuild U ] sys-libs/libcap-ng-0.7.7 [0.7.5] USE="python static-libs" PYTHON_TARGETS="python2_7 -python3_3 -python3_4" Reproducible: Always
it's weird that i have 0.7.5 installed, but 0.7.7 doesn't configure : my system hasn't changed (i never had python3), and there's no difference in the ebuilds. I guess the difference comes from eclass.. ?
(In reply to Thomas Capricelli from comment #1) > I guess the difference comes from eclass.. ? Not due to any recent change in eclasses. I can reproduce this bug with a copy of the gentoo repository from ~1 month ago. >cat /usr/portage/metadata/timestamp Wed May 6 18:37:24 UTC 2015 >USE="python" PYTHON_TARGETS="python2_7" ebuild libcap-ng-0.7.5.ebuild configure >>> Source configured. >USE="python" PYTHON_TARGETS="python2_7" ebuild libcap-ng-0.7.7.ebuild configure checking whether to create python3 bindings... yes checking for python3... no [snip] ERROR: sys-libs/libcap-ng-0.7.7::testing failed (configure phase):
Created attachment 404570 [details] libcap-ng-0.7.7-r1.ebuild The bug was in the ebuild. I've rewritten the src_configure() section, now it seems to work properly. >USE="python" PYTHON_TARGETS="python2_7 python3_3" emerge =sys-libs/libcap-ng-0.7.7-r1 Installing (1 of 1) sys-libs/libcap-ng-0.7.7-r1::testing >equery files --filter=dir =sys-libs/libcap-ng-0.7.7-r1 | grep python /usr/lib64/python2.7 /usr/lib64/python2.7/site-packages /usr/lib64/python3.3 /usr/lib64/python3.3/site-packages /usr/lib64/python3.3/site-packages/__pycache__ >USE="python" PYTHON_TARGETS="python2_7" emerge =sys-libs/libcap-ng-0.7.7-r1 Installing (1 of 1) sys-libs/libcap-ng-0.7.7-r1::testing >equery files --filter=dir =sys-libs/libcap-ng-0.7.7-r1 | grep python /usr/lib64/python2.7 /usr/lib64/python2.7/site-packages >USE="python" PYTHON_TARGETS="python3_3" emerge =sys-libs/libcap-ng-0.7.7-r1 Installing (1 of 1) sys-libs/libcap-ng-0.7.7-r1::testing >equery files --filter=dir =sys-libs/libcap-ng-0.7.7-r1 | grep python /usr/lib64/python3.3 /usr/lib64/python3.3/site-packages /usr/lib64/python3.3/site-packages/__pycache__ Note I had to add RESTRICT="test", since something is still borked in the src_test() section.
(In reply to Thomas Capricelli from comment #1) (In reply to Andrew Miller from comment #3) Upstream tells me that they recognize a problem with their new python code which will be fixed with 0.7.8 hopefully. I'll put this ebuild on the tree without a revbump, but I don't recommend that it every go stable. Let's wait until 0.7.8 comes out and see what further changes they've made.
Fine with me, thanks for your work.
