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