| 1 |
I did an emerge --sync and then "emerge -v1 portage" and it blew up all |
| 2 |
over the place. Log in the attachment. |
| 3 |
|
| 4 |
How can I get things reestablished? Or, does gentoo simply require a |
| 5 |
smarter user than me, and I should go back to ubuntu? |
| 6 |
|
| 7 |
|
| 8 |
On 05/14/20 23:36, Rich Freeman wrote: |
| 9 |
> On Thu, May 14, 2020 at 5:10 PM n952162 <n952162@×××.de> wrote: |
| 10 |
>> On 05/14/20 22:46, Rich Freeman wrote: |
| 11 |
>>> On Thu, May 14, 2020 at 4:13 PM n952162 <n952162@×××.de> wrote: |
| 12 |
>>>> Action: sync for repo: gentoo, returned code = 0 |
| 13 |
>>>> |
| 14 |
>>>> * An update to portage is available. It is _highly_ recommended |
| 15 |
>>>> * that you update portage now, before any other packages are updated. |
| 16 |
>>>> |
| 17 |
>>>> * To update portage, run 'emerge --oneshot portage' now. |
| 18 |
>>> ...and? Did you update portage as it was _highly_ recommended that |
| 19 |
>>> you do so first? What version of portage are you using? This appears |
| 20 |
>>> on the top line of emerge --info. |
| 21 |
>>> |
| 22 |
>> $ emerge --info |
| 23 |
>> Portage 2.3.49 (python 3.6.5-final-0, default/linux/x86/17.0, gcc-7.3.0, |
| 24 |
>> glibc-2.26-r7, 4.14.65-gentoo x86_64) |
| 25 |
> That version of portage has been removed from the repo for over a year. |
| 26 |
> |
| 27 |
> I would update your system so that is current and then try again. I |
| 28 |
> believe that version of portage should still support EAPI 7 but there |
| 29 |
> could be some other issue that is giving it problems with more recent |
| 30 |
> packages in the tree. |
| 31 |
> |
Archives