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 . > > That solution is risky, but it has always worked before + today. > I don't understand why Python can't do it automatically, > but am tired of complaining & remain a strong fan of Gentoo. > > PS I've never done 'emerge World' without '-pv' since 2003 : > I always pick/choose which pkgs to update a few at a time. >
I think a lot of it depends on what packages we have installed. For me, it was Kicad and a couple others, plus all their friends. It became a lengthy list tho. You may have a completely different set of packages installed but with the same problem as me, doesn't support 3.13 yet. I think Eli said that as long as a version of python is installed for emerge, one can fix most problems if we remove something by mistake. We just need to make sure emerge stays happy. I started using Gentoo in about 2003 as well. Over the years, I've put some options that are always wanted in make.conf and then I put others, depending on what I'm doing, on the command line. I have backtrack set to 500. It rarely goes higher than 4 or 5 tho. Still, it has it if it needs it. I have build deps turned on as well. Over the years tho, I've found settings and methods that result in a very stable system. I always sync, do a emerge -auDN world and then look at any USE flag changes, or any other changes, before letting it go. Sometimes a new USE flag pops up that I know I need or don't need. I adjust and then rerun emerge -auDN world. I've found that letting emerge figure it out is usually the best and most stable. It may result in a little more compiling but it's rare that anything crashes on my system. That's important to me. We all have our own ways tho. If it works, why do it differently??? Oh, tried to do the last step on my main rig, emerge spit out a nice loud and hard to miss, NO!!!. There's still a lot of packages not ready for python 3.13 yet. Maybe next week. If I don't forget. Again. Dale :-) :-)
