Re: Python 3.13 and massive USE flag changes.

On 6/7/26 3:27 AM, Michael wrote:
> On Sunday, 7 June 2026 09:00:46 British Summer Time Dale wrote:
>> 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.
> Was portage in the chroot system and the main OS in sync, or had you ran
> 'emerge --sync' at different times on each system?
>

When I get ready to update, I sync the tree on my main OS.  Every once 
in a while, it's just a few packages and I just run it in the main OS.  
If it is a lot of packages, then I use the chroot.  If I'm going to use 
the chroot, I then rsync my main OS over to the chroot.  At that point, 
the chroot is identical to the main OS.


>> 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.
> Was portage updated successfully on the main OS using the chrooted
> binary, or was it built afresh from source?


I installed it from the binary.  I think it was updating so much that 
something portage depends on got out of sync somehow, maybe between when 
I ran emerge and when it got to portage itself.  I just switched to 
another tab and updated portage on its own.  No problem at all.  Then I 
switched back to the previous tab and up arrowed and hit return.  It 
finished the rest just fine.

I might add, I've had portage fail to emerge in the past before. I've 
read that when there is a update to portage, it is best to run it first 
and then update everything else.  Thing is, I was focused on python and 
didn't even see portage in the list.  If I had, I likely would have done 
it first.  I usually do since it does sometimes fail when mixed in with 
other packages.

Overall tho, the chroot is a very nice way to do updates.  Before I 
started doing it that way, I'd be part way through a compile and certain 
programs wouldn't open or would start acting weird.  It's understandable 
tho since packages the software depends on may be updated but the 
software I'm actually using has not yet.  It's kinda got lost in the 
shuffle.  Using a chroot, it takes minutes to do a fairly large update 
once the chroot has done all the heavy lifting. Oh, Firefox has this 
nifty new feature.  If it gets updated and you have restarted, it won't 
open new tabs until you restart.  Neat huh?  Riiiiggghhhtt.  :/

Dale

:-)  :-)