Re: [gentoo-user] Re: Can't upgrade portage or update/install ebuilds

[Wol <antlists@youngman.org.uk>]

On 09/06/2023 21:16, Grant Edwards wrote:
> On 2023-06-09, Daniel Pielmeier <billie@gentoo.org> wrote:
> 
>> If it is only about gemato then temporary disable the rsync-verify flag
>> which pulls it in.
>>
>> # USE="-rsync-verify" emerge sys-apps/portage
> 
> The problem I ran into is that you never know how many issues there
> are standing in the way of upgrading. The one time I decided to muscle
> my way through updating an "obsolete" Gentoo install, I spent a very
> long day fixing "one more problem" and trying again.  It took many
> more hours than a scratch install would have taken, but at some point
> I decided to keep going just to see if I could make it all the way
> through the process. I did. Then I promised myself never to try that
> again.
> 
> You do learn alot about how portage/emerge works...
> 
Learning that is a good idea maybe :-)

But last time I had a well-out-of-date system, it was a long and messy 
process ...

What I did was, every time portage said "giving up" or "conflict found" 
or whatever, I just took a note of as many of the packages I could 
remember that portage said it could emerge, and then manually updated 
them "emerge --update --one-shot".

And any conflicts, if I dared, I simply deleted then "emerge -C --one-shot".

And once I managed to get the system to complete an update, I then did a 
--deep --new-use. The idea is to update the absolute minimum possible to 
get your system up-to-date, so you probably only want to update @system 
not @world. If @system is up-to-date, it's not major if you break other 
stuff.

Cheers,
Wol