On 5/11/25 9:26 AM, Philip Webb wrote: > I noticed others reporting Python update problems & didn't follow it, > but in my regular Sat update today encountered a big mess. > 'setuptools-scm' offered 13 screens of conflicts, > which were reduced to 10 by ' --backtrack=60 '. > I tried a 'quickpkg' + 'emerge -k', but was refused as the ebuild was missing. > Finally, I did a few 'emerge -C' brute-forces on some listed pkgs, > which allowed a straightforward 'emerge' of 18 Python pkgs. > The underlying problem seemed to be a jump to Python 3.13 .
I doubt the problem was that package specifically, as it supports all python versions already. Probably, it was just set by the default upgrade changes to 3.13, but some other package was stuck on 3.12. This in turn prevented updating setuptools-scm at all, which meant other packages which required setuptools-scm, couldn't be rebuilt for 3.13 The "safe" approach solves that, fwiw. (You may not be able to do the second stage and remove 3.12, ddepending.) Please consider emerge -c --with-bdeps=n before something as dangerous as -C. If the former works, then you're guaranteed a correct system dependency graph and will just have to freshly emerge build dependencies, which is a valid and supported scenario, whereas emerge -C is *not*. As you say, "that solution is risky"... but -c --with-bdeps=n would mean you aren't doing risky things at all... -- Eli Schwartz
OpenPGP_signature.asc
Description: OpenPGP digital signature
