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:
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:
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:
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
with the help of :
can you confirm than my mkcert-1.4.1.ebuild for mkcert is OK?