On Sunday, 11 May 2025 18:40:44 British Summer Time Wol wrote: > Found it. I will investigate, but to the best of my memory I have no > "targets" settings whatsoever. I will take a look, but at the moment I'm > running the emerge. So from what the news item says, it looks like > everything should have "just worked" - except it didn't.
This won't help you, but I have updated 4 systems so far and a 4th somewhat abandoned waiting for my time, with no problems so far whatsoever. I do understand and it was explained, it is a matter of which packages may be installed in a system if you may face a failed update. > And I can see what happened now. It doesn't help that I didn't have my > glasses, but the news item says: > > "At this point, you have a few configuration options to choose from:" > > I jumped straight to option 4, so I didn't read option 1 - why should I? > Especially if I'm having difficulty reading. Perhaps because a numbered list is meant to be followed in the numbered order? I started with option 1 and had no problems, but others sooner or later run aground and had to consider subsequent options depending on their individual situation. > First, enable both Python 3.12 and Python 3.13, and then run the upgrade > commands: > > */* PYTHON_TARGETS: -* python3_12 python3_13 > */* PYTHON_SINGLE_TARGET: -* python3_12" > > It says "run the upgrade commands - COLON". As I understand English, > that says that what follows is a list of COMMANDS. And "*/*" looks like > a weird comment marker. Why would I assume it's a declaration snippet? Because an asterisk "*" is a special character treated as a wildcard when parsed by a Unix shell. It will match any number of unknown characters. The "*/*" statement at the start of a file under /etc/portage/ can be interpreted as a filter matching: any category/any package with the next "-*" statement interpreted as: disable any python targets and then finally set only the python target(s) that follow.
signature.asc
Description: This is a digitally signed message part.
