| 1 |
Am Donnerstag, 11. Juni 2020, 09:47:50 EEST schrieb n952162: |
| 2 |
> I haven't clue what to do here. Can somebody supply a good URL or |
| 3 |
> explanation? |
| 4 |
> |
| 5 |
|
| 6 |
In the meantime a new ebuild format version (EAPI) has been introduced; your |
| 7 |
old portage can't process that, and as a result doesnt understand many new |
| 8 |
ebuilds. |
| 9 |
|
| 10 |
Portage disregards ebuilds where it doesnt know the format, but of course if |
| 11 |
these are needed to update Portage itself, you're somewhat screwed. |
| 12 |
|
| 13 |
Luckily there is a very simple workaround. |
| 14 |
|
| 15 |
Download a recent portage (the packager) tarball, or clone git master portage: |
| 16 |
https://anongit.gentoo.org/git/proj/portage.git |
| 17 |
|
| 18 |
Then run the "emerge" command inside that checkout, by giving its full path, |
| 19 |
the same way as you would otherwise run emerge. This updates your system and |
| 20 |
ideally afterwards your system portage is new and shiny, so you can delete the |
| 21 |
git clone again. |
| 22 |
|
| 23 |
-- |
| 24 |
Andreas K. Hüttel |
| 25 |
dilfridge@g.o |
| 26 |
Gentoo Linux developer |
| 27 |
(council, qa, toolchain, base-system, perl, libreoffice) |
Archives