On 5/11/25 3:10 PM, Wol wrote: > But anyway - a bit more - the actual targets ... > >> You didn't post full output so it's difficult to say for sure. But, >> "requires just one of" sounds like this: >> >> $ PYTHON_SINGLE_TARGET='python3_13 python3_12' emerge -1a glib-utils > > That's basically what I got, except it was demanding python 11 or 12.
... but you originally said, "I followed the instructions at the end - depclean, -1uVD, and it just fails completely with "requires just one of 3_11 or 3_12". Including important stuff like most of kde, systemd-dbus, and so on." You should definitely not have only 3.11 and 3.12 as options for "most of kde, systemd-dbus, and so on". Here's a list of packages that only have 3.11 and 3.12 support: https://qa-reports.gentoo.org/output/gpyutils/312-to-313.txt Courtesy of the dashboard at https://qa-reports.gentoo.org/ A mere 269 packages, out of numerous thousands of packages in gentoo. And "most of KDE" was certainly ready. A common theme of those that weren't is that they are usually not well maintained or popular. sci-*/ packages are quite a chunk. Either way, that goes back to the general discussion about "not all packages were ready yet", and that is a topic of discussion every single year. As the news item said, it's possible to take a slower approach and defer the whole thing. > Given that I have absolutely no mention that I can find of python, in > either make.conf or package.use (other than the snippet I've just added > to force the upgrade), it looks to me like option 1 should have "just > worked". So why didn't it? Where else would there be stuff that tells my > system that Python 13 is "persona non grata"? Full portage output could no doubt shed a light on which package is missing support for 3.13 entirely. -- Eli Schwartz
OpenPGP_signature.asc
Description: OpenPGP digital signature
