Re: Python 3.13 and massive USE flag changes.

On 6/6/26 5:06 AM, Dale wrote:
>
> If I read your reply correctly, that is what you are saying.  I should
> be able to skip from current OS before the switch directly to new python
> after all stages of the upgrade path using binaries from the chroot.
> The key word being should of course.  ;-)
>
> Dale
>
> :-)  :-)


Just in case someone else does their updates in a chroot or similar 
environment.  In the chroot, I did the complete safer upgrade process in 
the news item, except --depclean.  During that I had to remove 
elogviewer as it doesn't seem to have python 3.14 support yet.  I then 
copied the binaries over to my main install and did a emerge -aukDN 
world.  I made sure it had all binaries available, total packages and 
total binaries is the same.  I did get a failure of portage itself 
during the upgrade process.  I updated portage by itself and it updated 
without error.  I guess something was out of sync during the upgrade so 
I'd recommend upgrading portage before doing a emerge -aukDN world just 
to give it a jump start.  Once portage was upgraded, I ran emerge -aukDN 
world again and it completed without error.

So, remove elogviewer if you have it installed and before updating the 
main OS with binaries, update portage first.  Other than that, it worked 
fine.  Now I just need to remember this in a year or two when I need to 
do this again.  Yea, I thought about making a note but then I'll forget 
where I wrote the note most likely.  ROFL Wait, I'll put it in 
package.use right where I keep the python USE flags commented out.  
Maybe I will notice that.  o_O  One can hope, right?

In the end, doing the upgrade in a chroot, or similar environment, is 
possible at least.  It did work for me at least.  This time.

Hope this helps some other poor soul doing this.

Thanks to all.

Dale

:-)  :-)