Summary: | sys-auth/elogind-252.9 - ModuleNotFoundError: No module named jinja2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Andreas Sturmlechner <asturm> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | eschwartz, mail, sam |
Priority: | Normal | Keywords: | PullRequest |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://github.com/gentoo/gentoo/pull/36968 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info.txt
emerge-history.txt environment etc.portage.tar.xz qlist-info.txt sys-auth:elogind-252.9:20240601-214344.log temp.tar.xz |
Description
Toralf Förster
2024-06-02 08:12:05 UTC
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 |