Created attachment 681604 [details] dev-libs:volume_key-0.3.12-r2:20210107-031754.log # emerge -1qOpv dev-libs/volume_key [ebuild R ] dev-libs/volume_key-0.3.12-r2 USE="-test" PYTHON_SINGLE_TARGET="python3_8 (-python3_6) -python3_7 -python3_9" # emerge -1q dev-libs/volume_key ... # qlist dev-libs/volume_key | grep python /usr/lib64/python3.6/site-packages/volume_key.py /usr/lib64/python3.6/site-packages/__pycache__/volume_key.cpython-36.pyc /usr/lib64/python3.6/site-packages/__pycache__/volume_key.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/_volume_key.so
Hi Mike, I have trouble to reproduce the problem here: # USE="python_single_target_python3_9 -python_single_target_python3_8" nice ebuild $(portageq get_repo_path / gentoo)/dev-libs/volume_key/volume_key-0.3.12-r2.ebuild clean install ... # find /var/tmp/portage/dev-libs/volume_key-0.3.12-r2/image/ -type d -name "python*" /var/tmp/portage/dev-libs/volume_key-0.3.12-r2/image/usr/lib/python3.9 # USE="-python_single_target_python3_9 python_single_target_python3_8" nice ebuild $(portageq get_repo_path / gentoo)/dev-libs/volume_key/volume_key-0.3.12-r2.ebuild clean install ... # find /var/tmp/portage/dev-libs/volume_key-0.3.12-r2/image/ -type d -name "python*"/var/tmp/portage/dev-libs/volume_key-0.3.12-r2/image/usr/lib/python3.8 can you give me any hints how to reproduce your issue?
from the build.log: checking whether to use Python 3 bindings... testing checking for python3.6... /usr/bin/python3.6 checking whether /usr/bin/python3.6 version is >= 3.5... yes from the configure.ac: AC_MSG_CHECKING([whether to use Python 3 bindings]) ... if test "x$use_python3" = xno; then AC_MSG_RESULT([no]) else AC_MSG_RESULT([testing]) # Try to find Python 3 interpreter: AC_PATH_PROGS([PYTHON3], [python3.6 python3.5 python3 python], [no]) i'm guessing you don't have python3.6 or python3.5 on your system which is why you aren't seeing the problem.
(In reply to SpanKY from comment #2) > from the build.log: > checking whether to use Python 3 bindings... testing > checking for python3.6... /usr/bin/python3.6 > checking whether /usr/bin/python3.6 version is >= 3.5... yes > > from the configure.ac: > AC_MSG_CHECKING([whether to use Python 3 bindings]) > ... > if test "x$use_python3" = xno; then > AC_MSG_RESULT([no]) > else > AC_MSG_RESULT([testing]) > # Try to find Python 3 interpreter: > AC_PATH_PROGS([PYTHON3], [python3.6 python3.5 python3 python], [no]) > > i'm guessing you don't have python3.6 or python3.5 on your system which is > why you aren't seeing the problem. Exactly! Thanks for giving me that hint. Fix incoming.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9ddf1017294aa912660bfbbf52c918bc260ea396 commit 9ddf1017294aa912660bfbbf52c918bc260ea396 Author: Lars Wendler <polynomial-c@gentoo.org> AuthorDate: 2021-01-07 12:30:42 +0000 Commit: Lars Wendler <polynomial-c@gentoo.org> CommitDate: 2021-01-07 12:34:31 +0000 dev-libs/volume_key: Revbump fixing python3 lookup Thanks-to: Mike Frysinger <vapier@gentoo.org> Closes: https://bugs.gentoo.org/764230 Package-Manager: Portage-3.0.12, Repoman-3.0.2 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> .../files/volume_key-0.3.12-find_python3.patch | 27 ++++++++++ dev-libs/volume_key/volume_key-0.3.12-r3.ebuild | 61 ++++++++++++++++++++++ 2 files changed, 88 insertions(+)