Summary: | dev-util/meson-format-array dev-lang/python-exec failure with unknown system state | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | A. Wilcox (awilfox) <awilfox.gentoo> |
Component: | Current packages | Assignee: | Mike Gilbert <floppym> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | python |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=916498 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
A. Wilcox (awilfox)
2023-11-27 12:34:50 UTC
Another possible option might be to only install meson-format-array for a single python version and update the shebang to point to the exact versioned python. This would avoid going through python-exec for a script that both doesn't care about its python version and doesn't have any dependencies. It doesn't feel like it gets much value out of being multiversioned. meson-format-array should work if any of its enabled targets match a target enabled on python-exec. I suspect the issue is that you had meson-format-array installed with only python3_9 enabled, but you rebuilt python-exec with python3_9 disabled. Given that you say you "hosed" your system, I don't think there is much to be done here unless you can provide more exact steps to reproduce the issue. I think what happened here is what I describe at https://bugs.gentoo.org/916498#c1. |