[ ok ] * Loading proc-macro2-1.0.46.crate into Cargo registry ... [ ok ] * Loading pyo3-build-config-0.15.2.crate into Cargo registry ... tar: /var/tmp/portage/dev-python/bcrypt-4.0.1/distdir/pyo3-build-config-0.15.2.crate: Cannot open: No such file or directory tar: Error is not recoverable: exiting now * ERROR: dev-python/bcrypt-4.0.1::gentoo failed (unpack phase): * (no error message) * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no_multilib_hardened-20231023-085514 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-13 * clang/llvm (if any): /usr/lib/llvm/17 17.0.3 Python 3.11.6 Available Ruby profiles: [1] ruby31 (with Rubygems) * Available Rust versions: [1] rust-bin-1.73.0 * php cli (if any): [1] php8.2 * go version go1.21.3 linux/amd64 HEAD of ::gentoo commit 94fc822a01c40e65fcaf09c348f069eb1cb38dbc Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Mon Oct 23 23:16:57 2023 +0000 2023-10-23 23:16:56 UTC emerge -qpvO dev-python/bcrypt [ebuild N ] dev-python/bcrypt-4.0.1 USE="-debug -test" PYTHON_TARGETS="python3_11 -pypy3 -python3_10 -python3_12"
Created attachment 873381 [details] emerge-info.txt
Created attachment 873382 [details] dev-python:bcrypt-4.0.1:20231023-235934.log
Created attachment 873383 [details] emerge-history.txt
Created attachment 873384 [details] environment
Created attachment 873385 [details] etc.portage.tar.xz
Created attachment 873386 [details] logs.tar.xz
Created attachment 873387 [details] qlist-info.txt
This looks like a Portage bug. The package has `pyo3-build-config-0.15.2.crate` in SRC_URI, and when I try, it definitely gets fetched into DISTDIR. Is there any chance you may have accidentally removed files from DISTDIR between fetching and src_unpack?
