On Friday, 20 August 2021 17:11:59 BST Andrea Conti wrote: > >> This may help: > >> > >> https://wiki.gentoo.org/wiki/Project:Portage/Fixing_broken_portage > > It will not help in this case, since what's broken is python and not > portage. > > If that won't work for whatever reason, chroot into your system after you > > boot with the latest Live-USB and try to update @system. Alternatively, > > reinstall. > Neither will this, as you won't be able to execute python (i.e. run portage) > inside the chroot.
Right, my bad. I meant to write what Neil suggested - copy over binaries to get whatever parts of your toolchain are broken working again - but didn't obviously didn't write so. :-) I can't recall coming come across this problem myself, probably because I tend to leave emerge updates to finish, or resume from where I had stopped an update. Is this a an error portage should be able to deal with itself when an update is interrupted, then restarted?
signature.asc
Description: This is a digitally signed message part.
