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