Summary: | sys-apps/systemd-utils-252.7::gentoo -- python3 jinja2 missing | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gary E. Miller <gem> |
Component: | Current packages | Assignee: | Gentoo systemd Team <systemd> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gem, ionen |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Gary E. Miller
2023-03-05 01:48:14 UTC
Created attachment 856136 [details]
build.log
build.log
The jinja dependency is there but this doesn't seem to run python-any-r1_pkg_setup and so python_check_deps is never ran. So I guess it just happened to use the wrong python here. For reference in case there's more to this, also came up on the forums from another user: https://forums.gentoo.org/viewtopic-t-1162146.html The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=220b04352f5151b15575b0fd06874c1037013e80 commit 220b04352f5151b15575b0fd06874c1037013e80 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2023-03-05 03:22:13 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2023-03-05 03:24:21 +0000 sys-apps/systemd-utils: call python_setup Closes: https://bugs.gentoo.org/899622 Signed-off-by: Mike Gilbert <floppym@gentoo.org> sys-apps/systemd-utils/systemd-utils-251.10-r1.ebuild | 5 +++++ sys-apps/systemd-utils/systemd-utils-252.6.ebuild | 5 +++++ sys-apps/systemd-utils/systemd-utils-252.7.ebuild | 5 +++++ 3 files changed, 15 insertions(+) I had python 11 selected, but jinja only installed for python 10. Switching my default python to 10, then this succeeded. Seems like emerge should have known that since it was running under python 11 that it needed jinja[python_targets_python3_11]. (In reply to Gary E. Miller from comment #5) > I had python 11 selected, but jinja only installed for python 10. > Switching my default python to 10, then this succeeded. > > Seems like emerge should have known that since it was running under python > 11 that it needed jinja[python_targets_python3_11]. It's fixed by the above commit. |