From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Fragile python update is wedged.
Date: Fri, 2 May 2025 17:07:28 +0000 [thread overview]
Message-ID: <aBT70LRzy1B9Awwt@MAC.fritz.box> (raw)
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).
On my old machine, however, there was a seg fault while merging rust.
This is a known problem in certain first generation Ryzen processors.
However, this left the build wedged: emerge says that there's a circular
dependency from rust to itself. More precisely, the error message looks
like:
#########################################################################
[ebuild NS ] dev-lang/rust-1.85.1:1.85.1::gentoo [1.81.0-r100:1.81.0::gentoo, 1.82.0-r101:1.82.0::gentoo, 1.83.0-r2:1.83.0::gentoo, 1.84.1-r1:1.84.1::gentoo] USE="(-big-endian) -clippy -debug -dist -doc (-llvm-libunwind) -lto -rust-analyzer -rust-src -rustfmt (-system-llvm) -test -verify-sig -wasm (-miri%) (-nightly%) (-parallel-compiler%)" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="sse2" LLVM_SLOT="(19)" LLVM_TARGETS="(X86) -AArch64 -AMDGPU -ARC -ARM -AVR -BPF -CSKY -DirectX -Hexagon -Lanai -LoongArch -M68k -MSP430 -Mips -NVPTX -PowerPC -RISCV -SPIRV -Sparc -SystemZ -VE -WebAssembly -XCore -Xtensa" 0 KiB
Total: 1 package (1 in new slot), Size of downloads: 0 KiB
* Error: circular dependencies:
(dev-lang/rust-1.85.1:1.85.1/1.85.1::gentoo, ebuild scheduled for merge) depends on
(dev-lang/rust-1.85.1:1.85.1/1.85.1::gentoo, ebuild scheduled for merge) (buildtime)
* Note that circular dependencies can often be avoided by temporarily
* disabling USE flags that trigger optional dependencies.
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
dev-python/gpep517:0
#########################################################################
(and so on).
This would appear to be a bug in the rust ebuild - it has set itself as a
builtime dependency before it had been built - or something like that.
How do I best recover from this?
--
Alan Mackenzie (Nuremberg, Germany).
next reply other threads:[~2025-05-02 17:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 17:07 Alan Mackenzie [this message]
2025-05-02 17:22 ` [gentoo-user] Fragile python update is wedged 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
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=aBT70LRzy1B9Awwt@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