Stuck in python 3.12 upgrade I believe.

[tckosvic]

Just an engineer; not IT guy. Short-time gentoo user. Routine upgrades done weeky with emerge line as below:

[freke]

python_single_target nor python_targets belongs in make.conf - at best in package.use.

Only one python_single_target is allowed for an ebuild - it complains about multiple single targets set.

[tckosvic]

@freke, I do not understand your comments. I added "python_single_target_python3_11" to USE as I saw it in emerge output. Was not there before I got these messages.
I guess I am confused about where do I have multiple python targets set.

[logrusx]

[pietinger]

The news from 2024-05-09-python3-12 says:

[figueroa]

pietinger
Mine is a file, by choice, even in my most recent install. I find it much easier to edit a single file with the entries in alphabetic order, especially since sometimes entries are closely related, as when trying to migrate from one python version to another.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi

[pietinger]

[logrusx]

[Josef.95]

tckosvic,

in doubt, best is set nothing.
With this, portage will using the sane defaults from profile - this should work.

[tckosvic]

This is totally confusing issue and I have made no progress. I'll respond to some of the comments I have received.

I put python_single_target_python3_10 python_single_target_python3_11 python_single_target_python3_12 each separately into make.conf USE because emerge very specifically said to. Before that there was no python USE flag at all.

How could anyone know that that any one of the above USE strings was specifying python twice as was stated in the replys.

I did the steps of @pietinger. I created a new file named python.use in /etc/portage/packages.use directory. I entered the python statements supplied. I redid sync. Upon running my emerge@world string, I got the same emerge messages I presented initially. Telling me to install python_single_target_python3_10 python_single_target_python3_11 python_single_target_python3_12 as USE flags.

Along the way I did find out about "ufed" and used that to do some USE flag editing. It did put everything in make.conf in alphabetical order.

I do not think the wording of news item 32 re: python upgrade is very descriptive or useful.

thanks all for help, I will certainly take any additional suggestions.

[logrusx]

[tckosvic]

I have my emerge@world of 179 items running.

I modified the contents of the new python.use from:

[logrusx]

[tckosvic]

As I have stated several times before, python_single_target_python3_10 or python_single_target_python3_11 or python_single_target_python3_12 were NOT in make.conf when I received the emerge errors posted initially regarding python problems. In fact "python" by itself was not in make.conf. I added the above as I thought emerge was telling me to do by clearly saying "REQUIRED USE".

So I still don't know what was the initial problem. The fix was to add suggested code strings into package.use and add python as a USE flag in make.conf.

How is one to know that python is in the profile so as to cause a conflict with a python USE flag reference in make.conf. The error messages give no clue to that happening.

The news item 32 does not clearly state where to put the code snippets it is presenting. It is not clear whether they go into a file or a comandline in a terminal. Also, after 50+ years in unix and linux, I am unaware of what */* means. Must be a gentoo thing.

I do appreciate your help here, don't get me wrong.

I would like to straighten out my USE flags in make.conf. That's why I stumbled on ufed. I did read up on ufed.

Any ref you know of on how to move a large bunch of USE flags easily from make.conf into package.use files? Don't relish going through this package by package to see what USE flags are needed by each.

[Hu]

I accept that you started with none of those listed in make.conf. However, through some as yet unidentified path, you had two "single" targets concurrently set on gedit. The most likely explanation is that python3.12 came from your Gentoo Portage profile (since that one recently switched to preferring python3.12) and that you had a personal override somewhere, such as package.use, that continued to add python3.11. Adding the same target twice is not an error, so you may have had a personal setting of python3.11 for months which, because it coincided with the Gentoo Portage setting of python3.11, produced 2 uses of python3.11, and none of anything else. That would be legal. When Gentoo switched from setting python3.11 to setting python3.12, your personal addition of python3.11 became an error.

To explain the initial problem, we would need to see the state of your Portage configuration when the initial problem happened. You have made changes since that time, so it is difficult to determine what caused the initial problem.

*/* is a Gentoo thing, specifically for use in the package.* files. It applies the setting to all packages.

USE flags that do not apply to a package are ignored. Cleaning them out may make it easier to understand what your configuration does, but leaving it dirty does not hurt Portage.

[tckosvic]

I can accept that somehow I had two references to python. That is the only way to get these error messages It is lost to history now.

A few weeks ago I did the profile upgrade from 17.3 to 23. But I did several successful updates since then.

I hear you saying to leave make.conf alone as dirty and not tinker with it. Right?

One question is will I have to tinker with the strings in my new /etc/portage/package.use/python.use at some time in the future and, if so, what will I have to do?

Emerge still running fine. Will likely take a day or so even with giving it 5 cpus.

thanks again. Guess I'm whole at least for now.

[logrusx]

[Hu]

Part of the fun of Gentoo is tinkering with things. However, if Portage is happy now and you would rather not spend more time on this, leaving the files as-is should be fine for now.

Your settings in package.use/python.use will become a problem when Gentoo moves to Python 3.13 or when Gentoo removes support for an older Python that your file is keeping in use. When that happens, you will need to remove the conflicting settings. You will definitely get error messages from Portage when this becomes a problem. It will not be a silent misbehavior. My advice is to remove the PYTHON_SINGLE_TARGET override, and test to see what breaks. If you are using any packages that need Python 3.11, you may get an error from the Gentoo default of 3.12. If that happens, either (a) restore the override and wait a few weeks for Gentoo to finish the conversion to 3.12 or (b) add package-specific overrides now, and periodically revisit whether they are still needed. Longer term, you will also want to remove the PYTHON_TARGETS override. That is less critical since its presence only means your system supports 2 Python versions even when not needed. When Gentoo fully removes Python 3.11, the PYTHON_TARGETS override should become a harmless no-operation. (When Gentoo switches on Python 3.13, the PYTHON_TARGETS override will become a problem. However, I expect the 3.13 conversion is months in the future, at least.)

[tckosvic]

May as well ask my questions since I have a knowledgeable audience.

[figueroa]

Here is a scenario for you. My /etc/portage/package.use (just a single file containing everything needed) contains a line with:

[tckosvic]

@fugueroa,

Need a clarification.

[tckosvic]

@figueroa, disregard last post. I follow what you are saying.

thanks tom kosvic

[logrusx]

[pietinger]

[tckosvic]

thanks all again. I'm learning gentoo from the comments.

By the way, my emerge@world eventually finished satisfactorily (after about 24 hours) So, mission accomplished.