Little to say besides the description. Likely an ebuild bug, but I'm not really familiar with the relevant eclasses.
Including `emerge --info sys-libs/libnvme` and the build.log from the build would be helpful. I don't observe such behaviour but I guess it *could* be a case of the initial meson build picking an unexpected python to build against.
One way to reproduce is to set your EPYTHON to a python implementation that you have installed but not enabled PYTHON_TARGETS for the package. This is due to the first iteration the meson compile phases including $(meson_feature python), this is unnecessary as these would be built later and in this case leads to unexpected results depending on what python is preferred in the users environment.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ba65982faccd363da37bc8953ee51b4475727876 commit ba65982faccd363da37bc8953ee51b4475727876 Author: Sam James <sam@gentoo.org> AuthorDate: 2024-02-06 02:56:06 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-02-06 02:56:06 +0000 sys-libs/libnvme: fix Python configuration Clearly an error, as we already disable it at the beginning of the array, even. The generic build should have no Python involved. The later builds handle Python per-impl. Closes: https://bugs.gentoo.org/923853 Signed-off-by: Sam James <sam@gentoo.org> sys-libs/libnvme/libnvme-1.6-r1.ebuild | 3 +-- sys-libs/libnvme/libnvme-1.6-r2.ebuild | 3 +-- sys-libs/libnvme/libnvme-1.6.ebuild | 3 +-- sys-libs/libnvme/libnvme-1.7.1.ebuild | 1 - 4 files changed, 3 insertions(+), 7 deletions(-)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=27f17b985f46015bd296d11976cac73e11532655 commit 27f17b985f46015bd296d11976cac73e11532655 Author: Sam James <sam@gentoo.org> AuthorDate: 2024-02-06 03:03:34 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-02-06 03:03:34 +0000 sys-libs/libnvme: revbump for Python fix Followup to ba65982faccd363da37bc8953ee51b4475727876. parona made a fair point that a revbump is technically warranted given that with USE=python, we may get an additional impl installed outside of what PYTHON_TARGETS covered (e.g. if configure picks up Python 3.12, builds & installs that, then the proper Python impl builds do Python 3.11). Revbump for correctness accordingly. After he said it, I realised it wasn't just a technicality, but actually pretty plausible as well. Bug: https://bugs.gentoo.org/923853 Signed-off-by: Sam James <sam@gentoo.org> sys-libs/libnvme/{libnvme-1.7.1.ebuild => libnvme-1.7.1-r1.ebuild} | 0 1 file changed, 0 insertions(+), 0 deletions(-)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=18c086594f0a3ba9109b8d61c38c766db43e8bcd commit 18c086594f0a3ba9109b8d61c38c766db43e8bcd Author: Sam James <sam@gentoo.org> AuthorDate: 2024-02-06 05:36:10 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-02-06 05:36:14 +0000 sys-libs/libnvme: fix disable-python value Closes: https://bugs.gentoo.org/923859 Bug: https://bugs.gentoo.org/923853 Signed-off-by: Sam James <sam@gentoo.org> sys-libs/libnvme/libnvme-1.7.1-r1.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)