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