Re: Python 3.13 and massive USE flag changes.

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.

-- 
Regards,
Peter.