From: Eli Schwartz <eschwartz@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fragile python update is wedged.
Date: Sun, 11 May 2025 11:04:25 -0400 [thread overview]
Message-ID: <a59344d9-333e-4684-a7f7-c793a85b3333@gentoo.org> (raw)
In-Reply-To: <5cdb6f3b-8d20-4578-8429-c532b221be16@youngman.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 2168 bytes --]
On 5/11/25 7:54 AM, Wol wrote:
>
>
> On 02/05/2025 18:07, Alan Mackenzie wrote:
>> Hello, Gentoo.
>>
>> I've just been trying the update for python 3.13. It went well on my
>> new machine (well, after unmerging app-portage/unsymlink-lib, which was
>> debris from some 2019 update).
>
> I'm now trying to update my system. And it's not even fragile or wedged,
> it just won't.
>
> I followed the instructions at the end - depclean, -1uVD, and it just
> fails completely with "requires just one of 3_11 or 3_12". Including
> important stuff like most of kde, systemd-dbus, and so on.
>
> I thought I'd try increasing backtrack like I usually do - to 100 - but
> that made no difference.
You must have done something more than just emerge --sync followed by
emerge -uDU @world.
OR you must have had old package.use entries setting duplicate USE flags
already.
> I missed out the stuff at the start of the news item, sorry, but see
> below ...
>
> Giveb that I don't "do" Python, I've got nothing in make.conf that
> mentions python. I guess I have nothing in package.use etc unless the
> system set it for me ...
>
> So I guess I need to do the "safer" upgrade, but it gives me two lines
> that look like comments, and says "use these to blah blah", How do I use
> them? Where do I put them? I don't "do" python - this is double dutch to
> me.
I'm confused and baffled that, when a news item describes some blocks of
code as "the package.use samples provided below", you are totally lost
and declare that you don't "do" python as it's double dutch to you.
And why on earth would you assume they are comments?
You don't need to know python and aren't expected to either. The news
item describes the fact that:
- a group of packages using the python programming language, are
switching their versioned USE flags, here's the correct way to migrate
the USE
- it involves building many packages for the changed USE. Rebuilding
many packages at the same time can sometimes result in complex issues,
these are a USE_EXPAND and can be migrated in stages, which is safer.
--
Eli Schwartz
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2025-05-11 15:05 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 [this message]
2025-05-11 17:40 ` Wol
2025-05-11 18:06 ` Michael
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=a59344d9-333e-4684-a7f7-c793a85b3333@gentoo.org \
--to=eschwartz@gentoo.org \
--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