| 1 |
On Monday, 14 October 2019 15:47:53 BST Grant Edwards wrote: |
| 2 |
> On 2019-10-12, Daniel Frey <djqfrey@×××××.com> wrote: |
| 3 |
> > I've run into this many times, whenever portage asks me to update itself |
| 4 |
> > after a sync I always run `emerge -a portage gentoolkit` to merge them |
| 5 |
> > both so this error doesn't happen. |
| 6 |
> |
| 7 |
> I ran into this for the first time last week, and I tinkered for an |
| 8 |
> embarassingly long time before it dawned on me that simply emerging |
| 9 |
> portage and gentoolkit together was the answer. It does seem like a |
| 10 |
> bit of a bug when emerge tells you to run command "whatever", and when |
| 11 |
> you do emerge tells you it can't do "whatever". |
| 12 |
|
| 13 |
You did better than me then. I unmerged gentoolkit, then updated portage then |
| 14 |
remerged gentoolkit. Bare minimum of thought. :) |
| 15 |
|
| 16 |
-- |
| 17 |
Regards, |
| 18 |
Peter. |
Archives