Post removal log from 7.3.11_p1 from stage3.

build.log (text/plain), 5.09 KB, created by Alfred Wingate on 2023-06-20 10:52:53 UTC

ModuleNotFoundError: No module named 'encodings'
debug: OperationError:
debug:  operror-type: ModuleNotFoundError
debug:  operror-value: No module named 'encodings'
 [31;01m*[0m ERROR: dev-python/pypy3-7.3.11_p1::gentoo failed (postrm phase):
 [31;01m*[0m   filter-bash-environment.py failed
 [31;01m*[0m 
 [31;01m*[0m Call stack:
 [31;01m*[0m            ebuild.sh, line  780:  Called __ebuild_main 'postrm'
 [31;01m*[0m   phase-functions.sh, line 1111:  Called __filter_readonly_variables '--filter-features'
 [31;01m*[0m   phase-functions.sh, line  149:  Called die
 [31;01m*[0m The specific snippet of code:
 [31;01m*[0m   	"${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
 [31;01m*[0m 
 [31;01m*[0m If you need support, post the output of `emerge --info '=dev-python/pypy3-7.3.11_p1::gentoo'`,
 [31;01m*[0m the complete build log and the output of `emerge -pqv '=dev-python/pypy3-7.3.11_p1::gentoo'`.
 [31;01m*[0m The complete build log is located at '/var/tmp/portage/._unmerge_/dev-python/pypy3-7.3.11_p1/temp/build.log'.
 [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/._unmerge_/dev-python/pypy3-7.3.11_p1/temp/environment'.
 [31;01m*[0m Working directory: '/var/tmp/portage/._portage_reinstall_.r5jhaw_p/lib'
 [31;01m*[0m S: '/var/tmp/portage/._unmerge_/dev-python/pypy3-7.3.11_p1/work/pypy3-7.3.11_p1'
ModuleNotFoundError: No module named 'encodings'
debug: OperationError:
debug:  operror-type: ModuleNotFoundError
debug:  operror-value: No module named 'encodings'
[31;01m * [39;49;00mThe ebuild phase 'postrm' has exited unexpectedly. This type of behavior
[31;01m * [39;49;00mis known to be triggered by things such as failed variable assignments
[31;01m * [39;49;00m(bug #190128) or bad substitution errors (bug #200313). Normally, before
[31;01m * [39;49;00mexiting, bash should have displayed an error message above. If bash did
[31;01m * [39;49;00mnot produce an error message above, it's possible that the ebuild has
[31;01m * [39;49;00mcalled `exit` when it should have called `die` instead. This behavior
[31;01m * [39;49;00mmay also be triggered by a corrupt bash binary or a hardware problem
[31;01m * [39;49;00msuch as memory or cpu malfunction. If the problem is not reproducible or
[31;01m * [39;49;00mit appears to occur randomly, then it is likely to be triggered by a
[31;01m * [39;49;00mhardware problem. If you suspect a hardware problem then you should try
[31;01m * [39;49;00msome basic hardware diagnostics such as memtest. Please do not report
[31;01m * [39;49;00mthis as a bug unless it is consistently reproducible and you are sure
[31;01m * [39;49;00mthat your bash binary and hardware are functioning properly.
ModuleNotFoundError: No module named 'encodings'
debug: OperationError:
debug:  operror-type: ModuleNotFoundError
debug:  operror-value: No module named 'encodings'
[31;01m * [39;49;00mThe ebuild phase 'die_hooks' has exited unexpectedly. This type of
[31;01m * [39;49;00mbehavior is known to be triggered by things such as failed variable
[31;01m * [39;49;00massignments (bug #190128) or bad substitution errors (bug #200313).
[31;01m * [39;49;00mNormally, before exiting, bash should have displayed an error message
[31;01m * [39;49;00mabove. If bash did not produce an error message above, it's possible
[31;01m * [39;49;00mthat the ebuild has called `exit` when it should have called `die`
[31;01m * [39;49;00minstead. This behavior may also be triggered by a corrupt bash binary or
[31;01m * [39;49;00ma hardware problem such as memory or cpu malfunction. If the problem is
[31;01m * [39;49;00mnot reproducible or it appears to occur randomly, then it is likely to
[31;01m * [39;49;00mbe triggered by a hardware problem. If you suspect a hardware problem
[31;01m * [39;49;00mthen you should try some basic hardware diagnostics such as memtest.
[31;01m * [39;49;00mPlease do not report this as a bug unless it is consistently
[31;01m * [39;49;00mreproducible and you are sure that your bash binary and hardware are
[31;01m * [39;49;00mfunctioning properly.
!!! FAILED postrm: 1
[31;01m * [39;49;00mThe 'postrm' phase of the 'dev-python/pypy3-7.3.11_p1' package has
[31;01m * [39;49;00mfailed with exit value 1.
[31;01m * [39;49;00m
[31;01m * [39;49;00mThe problem occurred while executing the ebuild file named
[31;01m * [39;49;00m'pypy3-7.3.11_p1.ebuild' located in the '/var/db/pkg/dev-
[31;01m * [39;49;00mpython/pypy3-7.3.11_p1' directory. If necessary, manually remove the
[31;01m * [39;49;00menvironment.bz2 file and/or the ebuild file located in that directory.
[31;01m * [39;49;00m
[31;01m * [39;49;00mRemoval of the environment.bz2 file is preferred since it may allow the
[31;01m * [39;49;00mremoval phases to execute successfully. The ebuild will be sourced and
[31;01m * [39;49;00mthe eclasses from the current ebuild repository will be used when
[31;01m * [39;49;00mnecessary. Removal of the ebuild file will cause the pkg_prerm() and
[31;01m * [39;49;00mpkg_postrm() removal phases to be skipped entirely.