On 5/5/25 11:53 AM, Grant Edwards wrote: >> 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,
It has gotten 3.13 support on Sunday but erroneously did so via a revbump and dropping keywords to ~arch. If it was in world, though, then you would have had to resolve it on the May 1st switch. > then it was bmap-tools (zugiana overla) that wasn't > happy. This is in ::gentoo? There's a handful of packages that you need a *build* dep on 3.12 for, if you're going to do much with python. But unless you upgraded using "--with-bdeps=y" you should not have to have its build dependencies... and bmap-tools hasn't been updated in a year and no other packages have forced it to rebuild, so you shouldn't be having issues. > 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. You may be able to get away with just the list of packages that are dependencies of: - dev-python/setuptools - dev-python/gpep517 Since those are the build tools which most python packages use, which means if you have a single 3.12 package, you'll need the build tools installed for: PYTHON_TARGETS: python3_12 python3_13 -- Eli Schwartz
OpenPGP_signature.asc
Description: OpenPGP digital signature
