google.golang.org/protobuf/reflect/protoregistry tested by google.golang.org/protobuf/reflect/protoregistry.test imports github.com/google/go-cmp/cmp/cmpopts: github.com/google/go-cmp@v0.5.1: reading file:///var/tmp/portage/dev-vcs/lab-0.19.0/temp/go-proxy/github.com/google/go-cmp/@v/v0.5.1.zip: no such file or directory * ERROR: dev-vcs/lab-0.19.0::gentoo failed (unpack phase): * go mod tidy failed * * Call stack: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma-j4-20220228-233411 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.3.1 [2] x86_64-pc-linux-gnu-11.2.1 * clang/llvm (if any): /usr/lib/llvm/13 13.0.1 Python 3.9.10 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) [3] ruby30 (with Rubygems) * Available Rust versions: [1] rust-bin-1.59.0 [2] rust-1.59.0 * The following VMs are available for generation-2: *) Eclipse Temurin JDK 11.0.14_p9 [openjdk-bin-11] 2) Eclipse Temurin JDK 8.322_p06 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-11 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 php cli: HEAD of ::gentoo commit a867e949293900e0f6198557b94d060afa6f17f7 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Mon Mar 7 22:36:59 2022 +0000 2022-03-07 22:36:58 UTC emerge -qpvO dev-vcs/lab [ebuild N ] dev-vcs/lab-0.19.0
Created attachment 766552 [details] emerge-info.txt
Created attachment 766553 [details] dev-vcs:lab-0.19.0:20220308-010350.log
Created attachment 766554 [details] emerge-history.txt.bz2
Created attachment 766555 [details] environment.bz2
Created attachment 766556 [details] etc.portage.tar.bz2
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2ad9100728886b7a73ed2eba0710e3ab29622f52 commit 2ad9100728886b7a73ed2eba0710e3ab29622f52 Author: Florian Schmaus <flow@gentoo.org> AuthorDate: 2022-03-07 08:43:52 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-03-08 13:27:18 +0000 go-module.eclass: invoke "ego mod tidy" with nonfatal We previously invoked "mod tidy" without the ego helper function in a non-fatal way. This was switched to using the ego helper in f9ee55e698f8 ("go-module.eclass: use ego helper function") but without prefixing the call with nonfatal. Hence the semantic of the eclass changes: a previously non-fatal invocation became fatal, causing e.g., bug #834695. [sam: fixes semantic change which wasn't advertised/seemingly intentional, so let's get this in now to avoid a significant number of ebuilds being broken. We can introduce this change if desired at a later point. Fixes: f9ee55e698f8 ("go-module.eclass: use ego helper function") Closes: https://bugs.gentoo.org/834758 Closes: https://bugs.gentoo.org/834762 Closes: https://bugs.gentoo.org/834607 Closes: https://bugs.gentoo.org/834608 Closes: https://bugs.gentoo.org/834625 Closes: https://bugs.gentoo.org/834626 Closes: https://bugs.gentoo.org/834630 Closes: https://bugs.gentoo.org/834669 Closes: https://bugs.gentoo.org/834603 Closes: https://bugs.gentoo.org/834610 Closes: https://bugs.gentoo.org/834711 Closes: https://bugs.gentoo.org/834763 Signed-off-by: Florian Schmaus <flow@gentoo.org> Closes: https://github.com/gentoo/gentoo/pull/24437 Signed-off-by: Sam James <sam@gentoo.org> eclass/go-module.eclass | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
