When I try to install @preserved-rebuild, I get this: !!! The ebuild selected to satisfy "~dev-lang/rust-bin-1.74.1[rustfmt?,abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?]" has unmet requirements. - dev-lang/rust-bin-1.74.1::gentoo USE="(-big-endian) -clippy -doc (-prefix) -rust-analyzer -rust-src -rustfmt -verify-sig" CPU_FLAGS_X86="-sse2" The following REQUIRED_USE flag constraints are unsatisfied: x86? ( cpu_flags_x86_sse2 ) (dependency required by "virtual/rust-1.74.1::gentoo" [ebuild]) (dependency required by "dev-python/setuptools-rust-1.8.1::gentoo" [ebuild]) (dependency required by "dev-python/cryptography-41.0.7::gentoo" [ebuild]) (dependency required by "@preserved-rebuild" [argument]) So apparently I won't be able to install it without SSE2... Why is even the bad version of cryptography pulled in? Reproducible: Always Steps to Reproduce: 1. Own vintage hardware 2. Install Gentoo on it and get cozy 3. Wait until someone deprecates your sand castle Actual Results: I can't update my system anymore Expected Results: I should be able to update my system
> So apparently I won't be able to install it without SSE2... Why is even the bad version of cryptography pulled in? There isn't an explicit no-SSE2 profile yet, there will be in 23.0 which makes this easier. *** This bug has been marked as a duplicate of bug 741708 ***
