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).
