From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fragile python update is wedged [Was: Fragile rust update is wedged].
Date: Sun, 4 May 2025 16:41:45 +0000 [thread overview]
Message-ID: <aBeYySAHPS_gJ2pB@MAC.fritz.box> (raw)
In-Reply-To: <8293927b-216a-4608-8ebf-f914214a096d@gentoo.org>
Hello, Eli.
[ Added in some hours after writing the main bit below ]
I've managed to solve my problem. In the error output from emerge there
was a message about having to update some configuration files. Normally
this message just means "we advise you to get around to this sometime"
but this time it meant "your emerge will be broken until you do this".
So a quick dispatch-conf later, which inserted an atom spec into some
config file (I've forgotten which), and emerge was able to run. Just
under two hours later it was complete.
So thanks for all the help!
On Fri, May 02, 2025 at 17:56:46 -0400, Eli Schwartz wrote:
> On 5/2/25 5:15 PM, Alan Mackenzie wrote:
[ .... ]
> > Anyhow, my old machine is now in an unusable state. When I repeat the
> > emerge incantation from the news item, emerge fails with obscure messages
> > about conflicting package versions. These messages take several hours to
> > parse and understand, being basically dumps of the internal state of
> > emerge.
> > One way or another, I'll get that machine back in working order. But I
> > can't help thinking it shouldn't be this difficult, even in Gentoo.
> > I think my first summary of my problem was fair: The python update scheme
> > is fragile. In particular if the emerge is interrupted for any reason,
> > it cannot be restarted, and cannot be reverted to a workable state,
> > without a great deal of time and expert knowledge.
> Maybe it would help to know the exact command you used, and the full
> output? If it's quite long, include it as an email attachment or use a
> pastebin.
The command I used was:
# time emerge -1avUD @world
After a lot of error messages (see below), I got the following obscure
message:
!!! All ebuilds that could satisfy ">=dev-python/installer-0.5.0[python_targets_pypy3_11(-)?,python_targets_python3_13t(-)?,python_targets_python3_11(-)?,python_targets_python3_12(-)?,python_targets_python3_13(-)?]" have been masked.
!!! One of the following masked packages is required to complete your request:
- dev-python/installer-0.7.0::gentoo (masked by: )
(dependency required by "dev-python/gpep517-17::gentoo" [installed])
(dependency required by "dev-python/setuptools-78.1.0::gentoo" [installed])
(dependency required by "dev-python/setuptools-scm-8.2.1::gentoo[-test]" [installed])
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
On the line beginning "!!! All ebuilds ..." I do not understand what has
been written. What do the square brackets mean? What does the several
times repeated incantation "(-)?" mean?
I can't parse the "(masked by: )". Is it saying that installer-0.7.0 is
masked by "(dependency required by ...)". What would that even mean?
There are too few finite verbs in this message.
Where is this output documented? It is not documented in the MASKED
PACKAGES section of the emerge man page, or in the Gentoo Handbook, at
least as far as I could find.
It would appear that dev-python/installer-0.7.0 should satisfy the
dependencies. But it doesn't. It is currently installed.
> I hope you did not use
> ```
> emerge --resume
> ```
> at least. Because that option is far too broken to ever be used, in my
> experience, besides for having no useful purpose.
Yes I did indeed use emerge --resume. It usually works for me when an
emerge operation is interrupted by a sporadic seg fault.
> Also note:
> "emerge fails with obscure messages about conflicting package versions"
> The news item did suggest a "safe" upgrade approach that takes longer
> but is, well, safer.
Safer than what? There was no guidance in the news item as to what the
dangers might be, or when the safer upgrade option is recommended.
> It's also possible to greatly simplify large upgrades using emerge
> --getbinpkg, or, it would if not for the fact that the Gentoo Binhost
> has been working for two days now to finish building the binaries so it
> can publish them. :(
Anyhow, here's the full output of the command
# time emerge -1avUD @world > ~acm/rust-bug.20250504b.txt 2>&1:
#########################################################################
[ Removed, due to me having solved the problem. ]
#########################################################################
> --
> Eli Schwartz
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2025-05-04 16:42 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 [this message]
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
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=aBeYySAHPS_gJ2pB@MAC.fritz.box \
--to=acm@muc.de \
--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