On Wed, 22 Jul 2020 16:17:29 +1000, Adam Carter wrote:

> > Are you running stable or testing? Do you have anything rust-related
> > in package.accept_keywords?
> >  
> 
> No, nothing in /etc/portage/* System is testing/~amd64.
> 
> However, qlop shows the last rust-bin installed was actually 1.38,
> whereas my memory was that it was 1.44, so i have mixed up two
> different systems. I can't see anything in roots history that would
> have caused the issue.
> 
> FWIW if i mask dev-lang/rust-bin it wants to
> [ebuild     UD ] dev-lang/rust-1.44.1:stable/1.44::gentoo
> [1.45.0:stable/1.45::gentoo] USE="-clippy -debug -doc -libressl (-miri)
> -nightly -parallel-compiler -rls -rustfmt -system-bootstrap -system-llvm
> -wasm" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="sse2"
> LLVM_TARGETS="AMDGPU (X86) -AArch64 -ARM -BPF -Hexagon -Lanai -MSP430
> -Mips -NVPTX -PowerPC -RISCV -Sparc -SystemZ -WebAssembly -XCore" 0 KiB
> [ebuild     UD ] virtual/rust-1.44.1::gentoo [1.45.0::gentoo]
> ABI_X86="(64) -32 (-x32)" 0 KiB
> 
> No idea what's pulling in rust-1.44.1

Have you tried adding --tree to your emerge command?


-- 
Neil Bothwick

Processor: (n.) a device for converting sense to nonsense at the speed
           of electricity, or (rarely) the reverse.

Attachment: pgpwbMtwqkKYF.pgp
Description: OpenPGP digital signature

Reply via email to