Hello, Gentoo.

While updating my old machine (a 1st generation Ryzen), I was 42 minutes through the emerge of rust when it crashed. This is probably due to the
known hardware error in early Ryzen chips.

So I tried

# emerge --resume

, which gave me a few lines of emerge messages followed by:

* Error: Circular Dependencies

(dev-lang/rust-1.84.1-r1:1.84.1/1.84.1::gentoo, ebuild scheduled for merge) depends on
(dev-lang/rust-1.84.1-r1:1.84.1/1.84.1::gentoo, ebuild scheduled for merge (build time)

[ Message copied by hand from old machine to new machine running email ]

I'm not happy about this. I tried to unmerge that partial version of
rust, but just got further error messages.

How can I unwedge portage in this situation?

Thanks!

--
Alan Mackenzie (Nuremberg, Germany).

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, Mar 30, 2025 at 16:04:04 +0000, Alan Mackenzie wrote:

Hello, Gentoo.

While updating my old machine (a 1st generation Ryzen), I was 42 minutes through the emerge of rust when it crashed. This is probably due to the known hardware error in early Ryzen chips.

So I tried

# emerge --resume

, which gave me a few lines of emerge messages followed by:

* Error: Circular Dependencies

(dev-lang/rust-1.84.1-r1:1.84.1/1.84.1::gentoo, ebuild scheduled for merge) depends on
(dev-lang/rust-1.84.1-r1:1.84.1/1.84.1::gentoo, ebuild scheduled for merge (build time)

[ Message copied by hand from old machine to new machine running email ]

I'm not happy about this. I tried to unmerge that partial version of
rust, but just got further error messages.

How can I unwedge portage in this situation?

Well, I tried

# emerge -auND @world

again, and it seems to be working, including attempting to build rust
again.

I'd still be interested to find out what caused the bug in emerge
--resume.

Thanks!

--
Alan Mackenzie (Nuremberg, Germany).

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)