install portage first due to bug in env vars not being passed when portage installs itself and re-inits Found it as part of https://review.opendev.org/#/c/717177 Reproducible: Always Steps to Reproduce: change python versions, run through this as a test https://github.com/openstack/diskimage-builder/blob/f1d7e902e39264a0dd9584d7da11e7e62339d0a6/diskimage_builder/elements/gentoo/pre-install.d/02-gentoo-04-install-desired-python the review linked above has a fix within that same file
Would be nice to have some more context around this error pasted in #gentoo-dev: > 2020-04-03 05:47:48.493 | /var/tmp/portage/._portage_reinstall_.4b7qcxim/bin/ebuild.sh: line 609: /var/tmp/portage/dev-python/lxml-4.5.0/build-info/lxml-4.5.0.ebuild: No such file or directory Like what ebuild phase was it? This code can possibly run in more than one phase, the condition in ebuild.sh looks like this: > if [[ $EBUILD_PHASE = setup && $EMERGE_FROM = ebuild ]] || \ > [[ $EBUILD_PHASE = depend || ! -f $T/environment || \ > -f $PORTAGE_BUILDDIR/.ebuild_changed || \ > " ${FEATURES} " == *" noauto "* ]] ; then
If /var/tmp/portage/dev-python/lxml-4.5.0/build-info/lxml-4.5.0.ebuild is unexpectedly missing, it could be an indication that the build directory lock did not function as expected, which could have the same cause as bug 714480.
maybe, this is all within a tmpfs