Re: Python 3.13 and massive USE flag changes.

On 6/7/26 5:42 AM, Peter Humphrey wrote:
> On Sunday, 7 June 2026 11:23:06 British Summer Time Peter Humphrey wrote:
>> On Sunday, 7 June 2026 09:00:46 British Summer Time Dale wrote:
>>> 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 had the same experience on a couple of machines, not using a chroot.
> Come to think of it, I doubt that emerging portage before starting will help.
> I imagine that the portage failure occurs after some of the python modules it
> uses have been upgraded.
>

That is possible but it might pull in some packages before installing 
the portage package.  So you have a point that it might but it depends 
on what else it pulls in.  I wish I could go back somehow and test that 
just to see if it fails or not.  Kinda hard to put the toothpaste back 
in the tube now tho.  LOL

I mostly wanted to mention that so one can say, 'well the other guy had 
it install on its own so let's try that'.  As we know, if emerge stops 
working, fixing things gets tricky and time consuming really fast.  So, 
anytime the portage package goes sideways or emerge won't run, it causes 
a person to have to swallow real hard.

I'm just glad this is done.  Now we just wait for it to be updated again 
so we can rinse and repeat.  Oh crap, forgot to make a note in 
package.use that I can do the complete upgrade in a chroot.  I was so 
focused on updating in previous reply that I forgot.  :/

Dale

:-)  :-)