make[1]: Nothing to be done for install. make[1]: Leaving directory /var/tmp/portage/x11-terms/aterm-1.0.1-r3/work/aterm-1.0.1/src/graphics chown: cannot access /var/tmp/portage/x11-terms/aterm-1.0.1-r3/image/usr/bin/aterm: No such file or directory * ERROR: x11-terms/aterm-1.0.1-r3::gentoo failed (install phase): * fowners failed * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl-20200311-204810 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-gentoo-linux-musl-9.2.0 * [2] x86_64-gentoo-linux-musl-9.3.0 clang version 10.0.0 Target: x86_64-gentoo-linux-musl Thread model: posix InstalledDir: /usr/lib/llvm/10/bin /usr/lib/llvm/10 10.0.0 Available Python interpreters, in order of preference: [1] python3.8 [2] python3.7 [3] python3.6 [4] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-bin-1.41.1 [2] rust-1.41.1 * The following VMs are available for generation-2: repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Mon, 16 Mar 2020 13:38:33 +0000 emerge -qpvO x11-terms/aterm [ebuild N ] x11-terms/aterm-1.0.1-r3 USE="(-background) -cjk -xgetdefault"
Created attachment 620686 [details] emerge-info.txt
Created attachment 620688 [details] emerge-history.txt
Created attachment 620690 [details] environment
Created attachment 620692 [details] etc.portage.tbz2
Created attachment 620694 [details] logs.tbz2
Created attachment 620696 [details] temp.tbz2
Created attachment 620698 [details] x11-terms:aterm-1.0.1-r3:20200316-142442.log
The first attempt to tinderbox a musl image failed at all. I'll mass close therefore all filed bug reports of the last days related to this tinderbox image. Please feel free to re-open if you think that the bug is real in musl and not fixed by the musl overlay.
tinderbox_musl has reproduced this issue with version 1.0.1-r5 - Updating summary.
tinderbox_musl has reproduced this issue with version 1.0.1-r6 - Updating summary.