cp Coro/RWLock.pm blib/lib/Coro/RWLock.pm cp Coro/LWP.pm blib/lib/Coro/LWP.pm cp Coro/AnyEvent.pm blib/lib/Coro/AnyEvent.pm chmod 644 "State.bs" cp Coro/Select.pm blib/lib/Coro/Select.pm !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ERROR: Cannot copy 'Select.pm' to '../blib/lib/Coro/Select.pm': Permission denied !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! at -e line 1. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no_multilib-20230717-140510 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-13 * clang/llvm (if any): clang version 16.0.6 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/16/bin Configuration file: /etc/clang/clang.cfg /usr/lib/llvm/16 16.0.6 Python 3.11.4 Available Ruby profiles: [1] ruby31 (with Rubygems) * Available Rust versions: [1] rust-1.70.0 * The following VMs are available for generation-2: *) Eclipse Temurin JDK 17.0.7_p7 [openjdk-bin-17] 2) Eclipse Temurin JDK 8.372_p07 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-17 system-vm php cli (if any): go version go1.20.6 linux/amd64 HEAD of ::gentoo commit 2a2510ba7fd2362ef72e2ba1e8d90245ec11b470 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Tue Jul 18 07:47:16 2023 +0000 2023-07-18 07:47:16 UTC emerge -qpvO dev-perl/Coro [ebuild N ] dev-perl/Coro-6.570.0 USE="ev examples -event (-valgrind)"
Created attachment 865732 [details] emerge-info.txt
Created attachment 865733 [details] dev-perl:Coro-6.570.0:20230718-101642.log
Created attachment 865734 [details] emerge-history.txt
Created attachment 865735 [details] environment
Created attachment 865736 [details] etc.clang.tar.xz
Created attachment 865737 [details] etc.portage.tar.xz
Created attachment 865738 [details] temp.tar.xz
I got this with a different file today with the big perl update. Could this be a parallel build issue?
(In reply to Michael Cook from comment #8) > I got this with a different file today with the big perl update. Could this > be a parallel build issue? Forgot to add that trying again without changing anything worked (hence thinking parallel build issue)
