On 5/5/25 10:39 AM, Grant Edwards wrote: > What's annoying about the Python upgrade this time is that the switch > to 3.13 apparently happened. Then an update or two later, emerge > starts balking because it wants to update packages that don't support > 3.13. Now to get a normal daily update to "go" I have to switch _back_ > to 3.12. That means about 250 packages have to be reinstalled after > disabling 3.13 in package.use. > > Isn't there any sort of check that emerge can run _before_ the switch > happens to find out whether the switch is going to cause problems for > installed packages?
Yes, emerge ran that check when you did the original switch. Did you do the original switch without using @world? Did you have packages installed that aren't in world, and you are now trying to update? Which packages is it trying to update that don't support 3.13? There is very little we can do to help without details of the problem you are encountering. :) -- Eli Schwartz
OpenPGP_signature.asc
Description: OpenPGP digital signature
