Eli Schwartz wrote: > On 5/3/25 11:49 PM, Dale wrote: >> Howdy, >> >> I decided to go the safer route with the python upgrade. I do my >> compiles in a chroot and then copy packages over and emerge with -k on >> the main OS. I did the first step in chroot, copied over and installed >> on main OS. I then did the same again with the second step. That all >> went well enough. The last step tho, it spits out a lot of things that >> are not pleased with the update. I'm thinking if I leave my package.use >> at step two until next week, those packages may catch up. It seems some >> packages I have installed don't support the new default python yet. >> This is the error part. >> >> >> WARNING: One or more updates/rebuilds have been skipped due to a >> dependency conflict: >> >> <<<< SNIP >>>> > Most of these packages are "interconnected core infrastructure, that is, > they are the packages you need in order to build *other* python > software. The exception here is: > > - boost, which is a major runtime package -- and a dependency of kicad. > > - cython -- used to build other packages, in theory packages can run it > as either an importable python library or as a command line tool, in > both cases as part of building a package but obviously in the latter > case you don't necessarily need to build it for python 3.12 > > For the most part, as long as you have a single package on your system > using python 3.12 you will need to build this whole set of packages for > python 3.12 > > >> As you can tell, it wants to continue with some packages which is fine. > Yup, for the packages which it doesn't complain about it can do a > consistent and safe update without issues (one of the benefits of doing > it in the safe two-stage upgrade! :) :) :)) > > >> I'm just concerned about the ones where it says it is skipping. Should >> I go back to this setting in package.use which is step two and stay >> there for now, which means both old 3.12 and 3.13 are supported? >> >> >> >> */* PYTHON_TARGETS: -* python3_12 python3_13 >> */* PYTHON_SINGLE_TARGET: -* python3_13 >> >> >> This is the one that causes the error. >> >> >> */* PYTHON_TARGETS: -* python3_13 >> */* PYTHON_SINGLE_TARGET: -* python3_13 >> >> >> I'm thinking it is safe to leave at step two since it will use whichever >> is the latest python the package supports but want to be sure. > Setting both python targets is "easy", vs managing exactly which > packages are a dependency of some 3.12-only package like kicad. But > there's nothing wrong with setting them per-package as well, and setting > them per-package can in some cases result in spending much less time > building compiled packages for versions of python that you don't > actually need (because no apps actually use that library for the old > version of python). > > > > -- Eli Schwartz
So I can either leave it with it set to use both or do individual packages settings, which can be quite a few packages? My thinking is this. Leave it with it set to both and only have two lines in packages.use. Then I can comment out those lines to see if everything has caught up so I can just remove those lines, until the next big upgrade. Two lines with emerge/portage managing what is used might be safer and more stable than me trying to force it one way or the other given I might forget. I don't mind having both python 3.12 and 3.13 on here at the same time. It should be a temporary thing. I'd like to have a easy way to manage this but at the same time, make sure I have a stable system. KDE and some other stuff has enough quirks already, adding a mixed up python won't likely help much. LOL Just so I'm clear on where my live OS stands, this is the current package.use setting. */* PYTHON_TARGETS: -* python3_12 python3_13 */* PYTHON_SINGLE_TARGET: -* python3_13 This is the output of my normal emerge update with the above setting. root@Gentoo-1 / # emerge -aukDN world These are the packages that would be merged, in order: Calculating dependencies... done! Dependency resolution took 45.20 s (backtrack: 0/500). Total: 0 packages, Size of downloads: 0 KiB !!! The following installed packages are masked: - sys-kernel/gentoo-sources-6.14.0::gentoo (masked by: package.mask) /etc/portage/package.mask/package.mask: # =media-libs/opencv-4.10.0 For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. Nothing to merge; quitting. root@Gentoo-1 / # So at the moment, my main OS is happy with that setting, no skipping anything. I figure in a week or so, most other packages will catch up, due to the bug reports being filed, and then when the number of packages get small, I can then do individual packages in package.use or unmerge those packages if I don't need them. I figure --depclean will take care of python when it is all clear. I'm planning to logout and back in shortly. I figure at the moment, emerge is happy so it should be safe to do so. Dale :-) :-)
