Hi, during stage3 bootstrapping from bootstrap-prefix.sh I get a QA notice which should NOT be a fatal error: Creating directory /auto/vestec1-elixir/projects/biocev/mmokrejs/gentoo/usr/share/man Creating directory /auto/vestec1-elixir/projects/biocev/mmokrejs/gentoo/usr/share/man/man1 /usr/bin/install -c -m 644 ./Misc/python.man \ /auto/vestec1-elixir/projects/biocev/mmokrejs/tmp/portage/dev-lang/python-3.12.0_beta4_p1/image/auto/vestec1-elixir/projects/biocev/mmokrejs/gentoo/usr/share/man/man1/python3.12.1 if test "xno" != "xno" ; then \ case no in \ upgrade) ensurepip="--altinstall --upgrade" ;; \ install|*) ensurepip="--altinstall" ;; \ esac; \ LD_LIBRARY_PATH=/auto/vestec1-elixir/projects/biocev/mmokrejs/tmp/portage/dev-lang/python-3.12.0_beta4_p1/work/Python-3.12.0b4 ./python -E -m ensurepip \ $ensurepip --root=/auto/vestec1-elixir/projects/biocev/mmokrejs/tmp/portage/dev-lang/python-3.12.0_beta4_p1/image/ ; \ fi >>> Completed installing dev-lang/python-3.12.0_beta4_p1 into /auto/vestec1-elixir/projects/biocev/mmokrejs/tmp/portage/dev-lang/python-3.12.0_beta4_p1/image * Final size of build directory: 161206 KiB (157.4 MiB) * Final size of installed tree: 48521 KiB ( 47.3 MiB) * eprefixing shebang of auto/vestec1-elixir/projects/biocev/mmokrejs/gentoo/usr/bin/python3.12-config * QA Notice: the following files use invalid (possible non-prefixed) shebangs: * /auto/vestec1-elixir/projects/biocev/mmokrejs/gentoo/etc/init.d/pydoc-3.12:/sbin/openrc-run (script pydoc-3.12 installed in PATH but interpreter /sbin/openrc-run not found) * ERROR: dev-lang/python-3.12.0_beta4_p1::gentoo failed: * Aborting due to QA concerns: invalid shebangs found * * Call stack: * misc-functions.sh, line 861: Called install_qa_check * misc-functions.sh, line 134: Called source 'install_symlink_html_docs' * 05prefix, line 120: Called install_qa_check_prefix * 05prefix, line 116: Called die * The specific snippet of code: * die "Aborting due to QA concerns: invalid shebangs found" * * If you need support, post the output of `emerge --info '=dev-lang/python-3.12.0_beta4_p1::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-lang/python-3.12.0_beta4_p1::gentoo'`. * The complete build log is located at '/auto/vestec1-elixir/projects/biocev/mmokrejs/tmp/portage/dev-lang/python-3.12.0_beta4_p1/temp/build.log'. * The ebuild environment file is located at '/auto/vestec1-elixir/projects/biocev/mmokrejs/tmp/portage/dev-lang/python-3.12.0_beta4_p1/temp/environment'. * Working directory: '/auto/vestec1-elixir/projects/biocev/mmokrejs/tmp/portage/dev-lang/python-3.12.0_beta4_p1/image' * S: '/auto/vestec1-elixir/projects/biocev/mmokrejs/tmp/portage/dev-lang/python-3.12.0_beta4_p1/work/Python-3.12.0b4' !!! post install failed; exiting. >>> Failed to emerge dev-lang/python-3.12.0_beta4_p1, Log file: >>> '/auto/vestec1-elixir/projects/biocev/mmokrejs/tmp/portage/dev-lang/python-3.12.0_beta4_p1/temp/build.log' There is also OSError: AF_UNIX path too long make: [Makefile:2390: libinstall] Error 1 (ignored) in the build.log.
Created attachment 866802 [details] build.log
This should be fixed already. Specifically, see https://bugs.gentoo.org/640658#c15. *** This bug has been marked as a duplicate of bug 640658 ***
Thank you. For the "OSError: AF_UNIX path too long" issue I know I should have filed a different bugreport. I do not know what could be done to that. It is a pity the error is silent although I understand the process of building stages is shaky and tricks are necessary to forward, even "emerge --nodeps" as I see in bootstrap-prefix.sh .
Still there is a problem IMO. On Gentoo::RAP there will NOT ever be /sbin/openrc-run anyway as it makes no sense to install init.d scripts. So this QA check must be disabled during the bootstrap-prefix.sh stage3 anyway. We get that far because during bootstrap it call "emerge --nodeps" so the QA checks should be disabled too. I searched through manpage emerge.1 and did not find any "QA" hits hoping one can force emerge to ignore the QA checks and just continue.
During bootstrapping I got around by creating an empty file via: touch $PREFIX/sbin/openrc-run After a few more glitches I finally completed the bootstrapping on ~amd64.
I think creating a dummy openrc-run at some stage indeed is going to be the easiest way around this
