Today I updated the Gentoo repository and a surprise awaited me. Now the default variables in profiles/base/make.defaults are written like this: PYTHON_TARGETS="python3_12" PYTHON_SINGLE_TARGET="python3_12" But many stable ebuilds have not been rewritten for python-3.12. Examples of such packages: app-emulation/virtualbox dev-util/devhelp And much more. I had to fix this in make.conf. At the moment, the transition to python-3.12 is premature, since many ebuilds have not been tested under python-3.12. I can’t describe it as anything other than deliberate damage to a normal Gentoo build. Reproducible: Always
Yes, there was a news item about the Python 3.12 migration. It's always a bit bumpy at first but gets straightened out after a day or two. The news item tells you how you can roll back to 3.11 either proactively or when the change hits. > I can’t describe it as anything other than deliberate damage to a normal Gentoo build. Statements like this are never going to be helpful and are best left out, thank you.
>Statements like this are never going to be helpful and are best left out, thank you. This is my personal opinion, you can disagree with it, but in order to switch to python-3.12, ebuilds had to be tested with the new version. The news does not indicate that this is still a transition process. Therefore, it is assumed that all steps to switch to python-3.12 have been completed. At this point, it just makes things more complicated. Unfortunately, I cannot call this the right decision. Although the news would say that this is still a transition process. Of course, I understand that all this can be fixed in make.conf, but now the average user will need to keep track of all the changes. Moreover, searching for uncorrected ebuilds is quite simple: grep -R "\.\.11" <path> It’s good if all this really gets fixed quickly, then there really is no problem here.
(In reply to Roman from comment #2) > >Statements like this are never going to be helpful and are best left out, thank you. > > This is my personal opinion, you can disagree with it, but in order to > switch to python-3.12, ebuilds had to be tested with the new version. The > news does not indicate that this is still a transition process. Therefore, > it is assumed that all steps to switch to python-3.12 have been completed. > At this point, it just makes things more complicated. Unfortunately, I > cannot call this the right decision. Although the news would say that this > is still a transition process. That's OK and a reasonable position. Just please don't call it deliberate damage. That implies malice. With regard to the news item: I think you're right that we should include something about likely disruption at the point of the switch. Maybe reformat it to just say "if you're having issues, please do XXX and retry in ...". It's hard because I've tried to make it verbose to explain options but then stuff gets buried.
(In reply to Sam James from comment #3) > With regard to the news item: I think you're right that we should include > something about likely disruption at the point of the switch. Maybe reformat > it to just say "if you're having issues, please do XXX and retry in ...". > It's hard because I've tried to make it verbose to explain options but then > stuff gets buried. In my case, this implies outrage. Even for me, the transition to TDE-14.1.2 was much smoother. Therefore, this is a rather unpleasant bug for a Gentoo maintainer. Of course, I understand that everyone can make mistakes, but for a Gentoo developer to make more mistakes than me, this is not a pleasant moment. Such errors would be more typical for me, but not for a Gentoo developer, since professionalism should come into play here. The Gentoo developers should be like gods to us mere mortals, but when the gods make mistakes it's disappointing... It’s just that when a person has been involved in support for quite a long time, he is more critical of everything.
I changed the summary, it’s strange that it wasn’t added. It seems like I added it when creating it, but it wasn’t there. In general, the name reflects the problem, since the stable ebuilds were not translated to python-3.12. This change does not seem stable, as it adds problems with building stable packages, and requires redefining variables in make.conf. More than eight hundred ebuilds that have not been translated into python-3.12 are quite a large number.
