too long lines were shrinked: [174/440] /usr/bin/python3.11 /var/tmp/portage/sys-auth/elogind-252.9/work/elogind-252.9/tools/meson-render-jinja2.py config.h version.h ../elogind-252.9/src/libelogind/libelogind.pc.in src/libelogind/libelogind.pc FAILED: src/libelogind/libelogind.pc /usr/bin/python3.11 /var/tmp/portage/sys-auth/elogind-252.9/work/elogind-252.9/tools/meson-render-jinja2.py config.h version.h ../elogind-252.9/src/libelogind/libelogind.pc.in src/libelogind/libelogind.pc Traceback (most recent call last): File "/var/tmp/portage/sys-auth/elogind-252.9/work/elogind-252.9/tools/meson-render-jinja2.py", line 9, in <module> import jinja2 ModuleNotFoundError: No module named 'jinja2' [175/440] x86_64-pc-linux-gnu-gcc -Isrc/shared/libelogind-shared-252.9.a.p -Isrc/shared -I../elogind-252.9/src/shared -Isrc/basic -I../elogind-252.9/src/basic -Isrc/fundamental -I../elogind-252.9/src/fundamental -Isrc/core -I../elogind-252.9/src/core -Isrc/login -I../elogind-252.9/src/login -Isrc/sy [176/440] x86_64-pc-linux-gnu-gcc -Isrc/libelogind/libelogind_static.a.p -Isrc/libelogind -I../elogind-252.9/src/libelogind -Isrc/basic -I../elogind-252.9/src/basic -Isrc/fundamental -I../elogind-252.9/src/fundamental -Isrc/core -I../elogind-252.9/src/core -Isrc/login -I../elogind-252.9/src/login -I ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0-20240601-201002 The attached etc.portage.tar.xz has all details. ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-13 * clang/llvm (if any): Python 3.11.9 Available Rust versions: (none found) php cli (if any): HEAD of ::gentoo commit 452b5164600a6f76d9f63006f20029edfe501fe2 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sat Jun 1 20:03:51 2024 +0000 2024-06-01 20:03:51 UTC emerge -qpvO sys-auth/elogind [ebuild N ] sys-auth/elogind-252.9 USE="acl audit pam policykit -cgroup-hybrid -debug -doc (-selinux) -test"
Created attachment 894903 [details] emerge-info.txt
Created attachment 894904 [details] emerge-history.txt
Created attachment 894905 [details] environment
Created attachment 894906 [details] etc.portage.tar.xz
Created attachment 894907 [details] qlist-info.txt
Created attachment 894908 [details] sys-auth:elogind-252.9:20240601-214344.log
Created attachment 894909 [details] temp.tar.xz
So... ``` * Checking whether python3_12 is suitable ... * dev-lang/python:3.12 ... [ ok ] * python_check_deps ... * dev-python/jinja[python_targets_python3_12(-)] ... [ ok ] * dev-python/lxml[python_targets_python3_12(-)] ... [ ok ] [ ok ] ``` Then it falls it with 3.11: ``` [174/440] /usr/bin/python3.11 /var/tmp/portage/sys-auth/elogind-252.9/work/elogind-252.9/tools/meson-render-jinja2.py config.h version.h ../elogind-252.9/src/libelogind/libelogind.pc.in src/libelogind/libelogind.pc FAILED: src/libelogind/libelogind.pc /usr/bin/python3.11 /var/tmp/portage/sys-auth/elogind-252.9/work/elogind-252.9/tools/meson-render-jinja2.py config.h version.h ../elogind-252.9/src/libelogind/libelogind.pc.in src/libelogind/libelogind.pc Traceback (most recent call last): File "/var/tmp/portage/sys-auth/elogind-252.9/work/elogind-252.9/tools/meson-render-jinja2.py", line 9, in <module> import jinja2 ModuleNotFoundError: No module named 'jinja2' ``` Eli?
That script is executable in the source tree, and is looked up via find_program(). It doesn't make sense that the generated command line should even contain the path to python... It should simply be running the script as a script (and utilizing EPYTHON / the eclass wrapper setup).
Oh, correction, "fixed in 255.*" lol. https://github.com/elogind/elogind/commit/f56b6bfa18b6b582619074135b07ff35a84e6a01 So before then it's taking advantage of / falling prey to the issue that meson, when it sees a script with a shebang but no executable but, attempts some tricks to try running it anyways -- including running with the python impl of meson itself.
This is breaking Python 3.11 -> Python 3.12 update so it would be nice to have it fixed even without the version bump. Thanks
