Re: Python 3.13 and massive USE flag changes.

On 6/6/26 10:24 AM, Michael Orlitzky wrote:
> On 2026-06-06 02:50:26, Dale wrote:
>> I'm trying to do my weekend updates. At first, I got one or two
>> packages that wanted me to put in the package.use file to use Python
>> 3.13, some only want one to be used so I had to also disable other
>> python versions.
> This happens every time. If some packages don't add python-3.14
> support before 3.14 is made default, portage will tell you to do
> outrageous things to fix it, and they won't work. Overlay packages
> are especially bad in this regard.
>
> The first thing I would try is to remove any python-related settings
> from your package.use and make.conf (just comment them out). Remove
> any packages that are from overlays, and try a -uDN @world update. If
> that doesn't work... wait a week and try again. If that doesn't
> work... then maybe it's worthwhile to investigate what portage is
> trying to tell you.
>
> If you don't have any packages stuck on python-3.13, the upgrade
> should work with no hassle. If you do, portage will spit out something
> insane, and you have to try to ignore it :)
>


Actually, the problem was that I didn't do the upgrade like the news 
item said too.  I recall seeing it but I guess I didn't think I needed 
to do anything until the June 1st date, which is kinda true I guess.  
Then I forgot about the news item until I went and looked. I wish we 
could mark a news item unread, like most email clients do.  I'm not 
aware of that ability with a news item tho.

The first package I ran into this with is a exception tho.  The package 
elogviewer doesn't support python 3.14, yet anyway.  So, I had to add 
that exception to package.use.  Generally tho, I don't set those in 
package.use if I can avoid it, at least not versioned anyway.  It leads 
to problems down the road when a outdated package gets removed from the 
tree since I often forget about adding such a thing.

Right now, I'm on step two of the safer upgrade process in a chroot.

Thanks for the reply tho.

Dale

:-)  :-)