rust 1.86.0 fails to emerge with an error "die "Unsigned distfiles found"". Reproducible: Always Steps to Reproduce: 1.emerge dev-lang/rust:1.86.0 2. 3. Actual Results: Fails to build. Expected Results: Build succeeds.
Created attachment 919659 [details] build.log
I probably should have put the full version in the bug title: dev-lang/rust-1.86.0_beta20250218
I can't reproduce this, but with a different error: >>> Source configured. >>> Compiling source in /var/tmp/portage/dev-lang/rust-1.86.0_beta20250218/work/rustc-beta-src ... Building bootstrap running: /usr/lib/rust/1.83.0/bin/cargo build --manifest-path /var/tmp/portage/dev-lang/rust-1.86.0_beta20250218/work/rustc-beta-src/src/bootstrap/Cargo.toml -Zroot-dir=/var/tmp/portage/dev-lang/rust-1.86.0_beta20250218/work/rustc-beta-src --verbose --verbose --verbose --locked --frozen error: unknown `-Z` flag specified: root-dir For available unstable features, see https://doc.rust-lang.org/nightly/cargo/reference/unstable.html If you intended to use an unstable rustc feature, try setting `RUSTFLAGS="-Zroot-dir"` Traceback (most recent call last): File "/var/tmp/portage/dev-lang/rust-1.86.0_beta20250218/work/rustc-beta-src/./x.py", line 53, in <module> bootstrap.main() File "/var/tmp/portage/dev-lang/rust-1.86.0_beta20250218/work/rustc-beta-src/src/bootstrap/bootstrap.py", line 1339, in main bootstrap(args) File "/var/tmp/portage/dev-lang/rust-1.86.0_beta20250218/work/rustc-beta-src/src/bootstrap/bootstrap.py", line 1306, in bootstrap build.build_bootstrap() File "/var/tmp/portage/dev-lang/rust-1.86.0_beta20250218/work/rustc-beta-src/src/bootstrap/bootstrap.py", line 1010, in build_bootstrap run(args, env=env, verbose=self.verbose, cwd=self.rust_root) File "/var/tmp/portage/dev-lang/rust-1.86.0_beta20250218/work/rustc-beta-src/src/bootstrap/bootstrap.py", line 236, in run raise RuntimeError(err) RuntimeError: failed to run: /usr/lib/rust/1.83.0/bin/cargo build --manifest-path /var/tmp/portage/dev-lang/rust-1.86.0_beta20250218/work/rustc-beta-src/src/bootstrap/Cargo.toml -Zroot-dir=/var/tmp/portage/dev-lang/rust-1.86.0_beta20250218/work/rustc-beta-src --verbose --verbose --verbose --locked --frozen
(In reply to Zhixu Liu from comment #3) > I can't reproduce this, but with a different error: > > >>> Source configured. please ignore, I thought I've enabled USE="verify-sig", but apparentaly it's not true, sorry for the confusion. I've reproduced this after enable USE="verify-sig".
maybe the patch should be put in ${FILESDIR} instead of ${DISTDIR}?
(In reply to Zhixu Liu from comment #5) > maybe the patch should be put in ${FILESDIR} instead of ${DISTDIR}? The other solution is to explicitly write out the verify-sig commands instead of relying on verify-sig_src_unpack. Would make sense as there is only one upstream archive getting fetched.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=63523556dbd35468f27415b1a9d6f9a3b4015685 commit 63523556dbd35468f27415b1a9d6f9a3b4015685 Author: Matt Jolly <kangie@gentoo.org> AuthorDate: 2025-02-22 22:04:19 +0000 Commit: Matt Jolly <kangie@gentoo.org> CommitDate: 2025-02-22 22:07:07 +0000 dev-lang/rust: add manual verify-sig handling to 1.86.0_beta20250218 As we fetch a patch from GitHub we can't verify that and instead we need to not use the default 'verify everything' logic. Closes: https://bugs.gentoo.org/950098 Signed-off-by: Matt Jolly <kangie@gentoo.org> dev-lang/rust/rust-1.86.0_beta20250218.ebuild | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
