As usual, this is a tracker, so no talking.
*** Bug 693546 has been marked as a duplicate of this bug. ***
Breaking the talking rule because I think this might apply to everything this depends on. I've been seeing these fixed by people deleting the go.mod: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=98af196037b6d7968f5ffb60bc74997c8f59055a https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=47e78e715f170ce2cfc48d7568cc83b597663c2d Actually, though, there's a cleaner way of getting the pre-1.13 behavior to keep these packages building: `export GO111MODULE=off`, which is what I did here: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1c659d060363f621c66c816bf41f0bce9be688eb That trick might allow us to quickly fixup all the broken packages in a less invasive manner.
(In reply to Jason A. Donenfeld from comment #2) > I've been seeing these fixed by people deleting the go.mod: Extremely bad idea because it'll result in building package using wrong version of dependencies and this never will be supported by upstream.
I think that generally the path of least resistance (and forward compatibility) is to use GO111MODULE=on together with GOFLAGS=-mod=vendor, like this: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6554a30e6a47756812ab17110bf2a66be55edbe7
All packages that do not build with go 1.13 and that have go.mod and go.sum in their root directory should now inherit go-module instead of golang-*.
Hi, with the help of : https://github.com/williamh/get-ego-vendor can you confirm than my mkcert-1.4.1.ebuild for mkcert is OK? https://bugs.gentoo.org/693998 thanks
Go 1.13 is no longer in the tree. Thanks, William
