From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fragile python update is wedged.
Date: Sun, 11 May 2025 19:06:34 +0100 [thread overview]
Message-ID: <2004384.fIoEIV5pvu@rogueboard> (raw)
In-Reply-To: <719cb474-7f49-48e5-8ba5-4269646b5e73@youngman.org.uk>
[-- Attachment #1: Type: text/plain, Size: 2007 bytes --]
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.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-05-11 18:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 17:07 [gentoo-user] Fragile python update is wedged Alan Mackenzie
2025-05-02 17:22 ` Pramod V U
2025-05-02 17:47 ` [gentoo-user] Fragile rust update is wedged. (Was: Fragile python update is wedged.) Eli Schwartz
2025-05-02 19:07 ` [gentoo-user] Fragile rust update is wedged Alan Mackenzie
2025-05-02 20:07 ` Eli Schwartz
2025-05-02 21:15 ` [gentoo-user] Fragile python update is wedged [Was: Fragile rust update is wedged] Alan Mackenzie
2025-05-02 21:35 ` Wol
2025-05-02 21:44 ` Jay Faulkner
2025-05-02 22:17 ` Alan Mackenzie
2025-05-02 22:21 ` Jay Faulkner
2025-05-02 21:56 ` Eli Schwartz
2025-05-04 16:41 ` Alan Mackenzie
2025-05-04 17:01 ` Eli Schwartz
2025-05-03 3:14 ` [gentoo-user] " Grant Edwards
2025-05-03 4:07 ` [gentoo-user] Fragile rust update is wedged Nate Eldredge
2025-05-11 11:54 ` [gentoo-user] Fragile python " Wol
2025-05-11 12:42 ` Dale
2025-05-11 13:26 ` Philip Webb
2025-05-11 14:52 ` Dale
2025-05-17 7:17 ` Dale
2025-05-18 12:06 ` Michael
2025-05-18 14:26 ` Dale
2025-05-11 15:14 ` Eli Schwartz
2025-05-11 12:43 ` Frank Schletz
2025-05-11 13:37 ` Wol
2025-05-11 14:55 ` Dale
2025-05-11 15:04 ` Eli Schwartz
2025-05-11 17:40 ` Wol
2025-05-11 18:06 ` Michael [this message]
2025-05-11 18:08 ` Eli Schwartz
2025-05-11 19:10 ` Wol
2025-05-11 19:47 ` Eli Schwartz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2004384.fIoEIV5pvu@rogueboard \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox