On 2025-05-05, Eli Schwartz <eschwa...@gentoo.org> wrote:
> On 5/5/25 10:39 AM, Grant Edwards wrote:
>
>> 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?
No, I did my normal update:
emerge --sync
emerge -auvND world
> Did you have packages installed that aren't in world, and you are
> now trying to update?
No, I don't think so.
> Which packages is it trying to update that don't support 3.13?
A coupled days after the May 1st switch, 'emerge -auvND world' refused
to run because libftdi didn't support 3.13.
I removed libftdi, then it was bmap-tools (zugiana overla) that wasn't
happy.
Since I have no idea how many packages are going to need to be
uninstalled or fixed with use-flags, I decided to try to "defer" the
update by putting these lines at the top of /etc/portage/package.use
*/* PYTHON_TARGETS: -* python3_12
*/* PYTHON_SINGLE_TARGET: -* python3_12
Now I'm about half-way through an "update" that is reinstalling 225
packages.
--
Grant
