maturin fails to install 2023-06-28 11:54:14,262 gpep517 INFO Installation complete * Using python3.11 in global scope * python3_11: running distutils-r1_run_phase python_compile_all /var/tmp/portage/dev-util/maturin-1.1.0/temp/environment: line 3561: target/release/maturin: No such file or directory * ERROR: dev-util/maturin-1.1.0::gentoo failed (compile phase): * (no error message) * * Call stack: * ebuild.sh, line 136: Called src_compile * environment, line 4165: Called distutils-r1_src_compile * environment, line 2133: Called _distutils-r1_run_common_phase 'python_compile_all' * environment, line 843: Called multibuild_foreach_variant 'distutils-r1_run_phase' 'python_compile_all' * environment, line 3305: Called _multibuild_run 'distutils-r1_run_phase' 'python_compile_all' * environment, line 3303: Called distutils-r1_run_phase 'python_compile_all' * environment, line 2112: Called python_compile_all * environment, line 3561: Called die * The specific snippet of code: * ${maturin} completions bash > "${T}"/${PN} || die; Many thanks for a hint, Helmut
Please attach the build log and provide emerge --info. Then change the bug status to UNCONFIRMED.
Created attachment 864788 [details] build log
Created attachment 864789 [details] emerge --info
Please share emerge -pvO dev-python/scikit-build-core output.
Yeah that looks like the same thing, hopefully it indeed is still due to scikit-build-core (it's currently masked, and no in-tree packages depend on it so very few people have installed) so don't have to figure out what else is breaking setuptools-rust. Makes me glad that the ebuild checks for the maturin executable, otherwise it'd just install fine *without* the executable. For that reason, it's possible you have broken packages around because most other setuptools-rust packages (like dev-python/cryptography) will emerge fine but without their rust extensions.
(In reply to Sam James from comment #4) > Please share emerge -pvO dev-python/scikit-build-core output. emerge -pvO dev-python/scikit-build-core These are the packages that would be merged, in order: !!! All ebuilds that could satisfy "dev-python/scikit-build-core" have been masked. !!! One of the following masked packages is required to complete your request: - dev-python/scikit-build-core-0.4.7::gentoo (masked by: package.mask) /usr/portage/profiles/package.mask: # MichaŠGórny <mgorny@gentoo.org> (2023-06-24) # Breaks dev-python/setuptools-rust. # https://github.com/scikit-build/scikit-build-core/issues/413 - dev-python/scikit-build-core-0.4.6::gentoo (masked by: package.mask)
I guess I'll backport the patch for it then.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9d347c82d7d8fc2b5fb27f684aed3433220a4e19 commit 9d347c82d7d8fc2b5fb27f684aed3433220a4e19 Author: Sam James <sam@gentoo.org> AuthorDate: 2023-07-02 13:10:24 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-07-02 13:10:38 +0000 dev-python/scikit-build-core: backport setuptools hook breakage fix Bug: https://bugs.gentoo.org/909035 Closes: https://bugs.gentoo.org/909335 Signed-off-by: Sam James <sam@gentoo.org> .../scikit-build-core-0.4.7-setuptools-hooks.patch | 28 ++++++++++++ .../scikit-build-core-0.4.7-r1.ebuild | 52 ++++++++++++++++++++++ 2 files changed, 80 insertions(+)
Hm, wait. The patch did need backporting anyway to help people with it still installed, but it doesn't appear to have been installed for you. Could you attach qlist -ICv 'dev-python/*' output? Does the maturin issue still happen for you?
