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