| 1 |
On 2020-06-14 00:05, n952162 wrote: |
| 2 |
> cool! I'll give that a try tomorrow. |
| 3 |
> |
| 4 |
> Thank you. |
| 5 |
> |
| 6 |
> On 2020-06-13 21:42, Andreas K. Hüttel wrote: |
| 7 |
>> Am Donnerstag, 11. Juni 2020, 09:47:50 EEST schrieb n952162: |
| 8 |
>>> I haven't clue what to do here. Can somebody supply a good URL or |
| 9 |
>>> explanation? |
| 10 |
>>> |
| 11 |
>> In the meantime a new ebuild format version (EAPI) has been |
| 12 |
>> introduced; your |
| 13 |
>> old portage can't process that, and as a result doesnt understand |
| 14 |
>> many new |
| 15 |
>> ebuilds. |
| 16 |
>> |
| 17 |
>> Portage disregards ebuilds where it doesnt know the format, but of |
| 18 |
>> course if |
| 19 |
>> these are needed to update Portage itself, you're somewhat screwed. |
| 20 |
>> |
| 21 |
>> Luckily there is a very simple workaround. |
| 22 |
>> |
| 23 |
>> Download a recent portage (the packager) tarball, or clone git master |
| 24 |
>> portage: |
| 25 |
>> https://anongit.gentoo.org/git/proj/portage.git |
| 26 |
>> |
| 27 |
>> Then run the "emerge" command inside that checkout, by giving its |
| 28 |
>> full path, |
| 29 |
>> the same way as you would otherwise run emerge. This updates your |
| 30 |
>> system and |
| 31 |
>> ideally afterwards your system portage is new and shiny, so you can |
| 32 |
>> delete the |
| 33 |
>> git clone again. |
| 34 |
>> |
| 35 |
> |
| 36 |
|
| 37 |
Unfortunately, I couldn't get that to work, using this command, first |
| 38 |
with tgt=@world, then @system, then portage, I got thousands of lines of |
| 39 |
output before failure to calculate the dependencies. Log files attached |
| 40 |
(world contains both @world and @system). |
| 41 |
|
| 42 |
sudo $HOME/adm/gentoo/src/portage/bin/emerge -vuUD --backtrack=100 |
| 43 |
--with-bdeps=y $tgt |
Archives