| 1 |
On 8/6/21 11:07 PM, antlists wrote: |
| 2 |
> On 06/08/2021 19:41, n952162 wrote: |
| 3 |
>>> It might not hurt if that error message included the suggestion to run |
| 4 |
>>> "emerge -u portage" to update it. It does say that the solution is to |
| 5 |
>>> update portage - it just doesn't explicitly tell you how to do so. |
| 6 |
>> |
| 7 |
>> |
| 8 |
>> The way out of my dilema would be first to emerge portage and then |
| 9 |
>> emerge @world? |
| 10 |
> |
| 11 |
> Probably. If you've left it that long you might find you still have a |
| 12 |
> few problems. |
| 13 |
|
| 14 |
|
| 15 |
That long! |
| 16 |
|
| 17 |
|
| 18 |
> |
| 19 |
> If you find you have trouble once portage is updated, I've found that |
| 20 |
> the following often works ... |
| 21 |
> |
| 22 |
> First do a --update @system (NO deep, no changed use, no nothing like |
| 23 |
> that). If that succeeds, the remaining steps will be hassle but |
| 24 |
> nothing serious. |
| 25 |
> |
| 26 |
> Then try the same with @world. |
| 27 |
> |
| 28 |
> Finally update @world with deep, newuse etc. |
| 29 |
> |
| 30 |
> If emerge keeps giving up with too many blocks, just do a oneshot |
| 31 |
> emerge of a bunch of stuff it says it *can* emerge, and you'll likely |
| 32 |
> find after a couple of shots of that that it suddenly works. The other |
| 33 |
> trick I try is, IFF @system was successful, just do a oneshot delete |
| 34 |
> of any blocking packages and again it should suddenly start working. |
| 35 |
> |
| 36 |
> |
| 37 |
|
| 38 |
Yes, this last is the step I've finally accepted is the way out of a |
| 39 |
dead-end. |
Archives