Caused by: failed to merge config value from `/var/tmp/portage/dev-python/mitmproxy_wireguard-0.1.20/work/cargo_home/config.toml` into `/var/tmp/portage/dev-python/mitmproxy_wireguard-0.1.20/work/mitmproxy_wireguard-0.1.20/.cargo/config.toml`: expected array, but found string 💥 maturin failed Caused by: Cargo metadata failed. Does your crate compile with `cargo build`? Caused by: `cargo metadata` exited with an error: Error: command ['maturin', 'pep517', 'build-wheel', '-i', '/usr/bin/python3.12', '--compatibility', 'off', '--jobs=4', '--skip-auditwheel'] returned non-zero exit status 1 * ERROR: dev-python/mitmproxy_wireguard-0.1.20::gentoo failed (compile phase): * Wheel build failed ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_no_multilib_systemd-20240801-081001 UNMASKED: Requested by sam ~dev-libs/icu-75.1 ~dev-libs/icu-layoutex-75.1 The attached etc.portage.tar.xz has all details. ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-14 * clang/llvm (if any): clang version 18.1.8 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/18/bin Configuration file: /etc/clang/x86_64-pc-linux-gnu-clang.cfg /usr/lib/llvm/18 18.1.8 Python 3.12.4 Available Rust versions: [1] rust-bin-1.79.0 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 11.0.24_p8 [openjdk-bin-11] *) Eclipse Temurin JDK 17.0.12_p7 [openjdk-bin-17] 3) Eclipse Temurin JDK 21.0.4_p7 [openjdk-bin-21] 4) Eclipse Temurin JDK 8.422_p05 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-11 [3] openjdk-bin-17 system-vm [4] openjdk-bin-21 The Glorious Glasgow Haskell Compilation System, version 9.2.8 php cli (if any): (none found) go version go1.22.5 linux/amd64 HEAD of ::gentoo commit 8577aafb7679c6beebe779017e29c48e8828fa59 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Tue Aug 6 11:19:22 2024 +0000 2024-08-06 11:19:21 UTC emerge -qpvO dev-python/mitmproxy_wireguard [ebuild N ] dev-python/mitmproxy_wireguard-0.1.20 USE="-debug" PYTHON_TARGETS="python3_12 -python3_10 -python3_11"
Created attachment 899286 [details] emerge-info.txt
Created attachment 899287 [details] dev-python:mitmproxy_wireguard-0.1.20:20240806-120308.log
Created attachment 899288 [details] emerge-history.txt.xz
Created attachment 899289 [details] environment
Created attachment 899290 [details] etc.clang.tar.xz
Created attachment 899291 [details] etc.portage.tar.xz
Created attachment 899292 [details] qlist-info.txt.xz
Created attachment 899293 [details] temp.tar.xz
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=27d469a2114b4ad0b3e682854c50c806753eb472 commit 27d469a2114b4ad0b3e682854c50c806753eb472 Author: James Le Cuirot <chewi@gentoo.org> AuthorDate: 2024-08-07 14:27:36 +0000 Commit: James Le Cuirot <chewi@gentoo.org> CommitDate: 2024-08-08 09:00:08 +0000 cargo.eclass: Change RUSTFLAGS approach following recent build failures Cargo turned out to be even worse at handling flags than I thought. Target-specific flags set by projects were overriding our own, and Cargo was bailing out when faced with merging a string of flags with an array of flags. After weighing up the poor set of options, I've found that it is better to always set flags via a target-specific environment variable for reasons set out in comments added here. This approach was previously just used for cross-compiling, but now we do it unconditionally. It has the downside of overriding generic [build] flags set by projects, but these were already being overridden by users and ebuilds setting RUSTFLAGS themselves. Closes: https://bugs.gentoo.org/937453 Closes: https://bugs.gentoo.org/937470 Signed-off-by: James Le Cuirot <chewi@gentoo.org> eclass/cargo.eclass | 65 ++++++++++++++++++++++++++++++++--------------------- 1 file changed, 39 insertions(+), 26 deletions(-)
