Rainer,
On Tue, 4 Jun 2024 04:36:41 -0500 you wrote:
...
I read the thread linked to by the OP. I just wonder if waiting a
little longer would have helped.
Did nobody of ye all ever read news item 48, dated 2024-05-09? It laid
out a three-step approach which surely caused at least some packages to
be built twice or even three times, but it JUST WORKED (tm), at least
here. It only required creating and later updating a file in "/etc/por-
tage/package.use/" and then running
emerge --depclean ; emerge -UD @world
for each of the three steps.
Those steps do not just work.
The news item actually specifically states that portage will "just do
the update" if you have not set any python_targets stuff.
I have those not set, but it fails on ALL my systems.
There are also still over 280 packages that are STILL not supporting
python 3.12 according to bugs.gentoo.org.
Several of them are critical for my systems with active upstream development.
Instead of forcing this now, the gentoo devs could have easily waited
a little longer to ensure all the packages with active upstream have a
stabilised version for python 3.12.
Dale, in a previous post you shared a rather long list of packages which
you classified not to be Python 3.12 ready. This list contained "sys-
apps/portage"! This just can't be! From my 1060 installed packages ex-
actly ONE package required the "python_targets_python3_11" USE flag to
be set in the last step.
I really would suggest to take the trouble and to do the whole upgrade
again as suggested in the news item. Just to be safe.
I would really like to suggest you take the trouble to actually check
the current state of 3.12 support for packages.
This forced update is causing more issues than I have seen in the past
8 years with Gentoo.
--
Joost
