Date: Fri, 13 Mar 2020 13:27:54 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 244783] lang/go: Updating ports to go 1.14 can cause vendor version errors (eg: net-p2p/bitmark) Message-ID: <bug-244783-7788-w50bClFNwp@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-244783-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-244783-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244783 Dmitri Goutnik <dmgk@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmgk@freebsd.org --- Comment #4 from Dmitri Goutnik <dmgk@freebsd.org> --- This looks like it could be a serious issue as more upstreams will be updat= ing go.mod to require go1.14: "When -mod=3Dvendor is set (explicitly or by default), the go command now verifies that the main module's vendor/modules.txt file is consistent with = its go.mod file." [1] Because -mod=3Dvendor is the only mode that works for ports due to restrict= ed network access and there's no way to generate vendor/modules.txt during port build, the options we have seem to be (a) keep generated vendor/modules.txt in files/ and copy it over to ${WRKSRC}/vendor before build (b) patch go.mod go version back to 1.13 (probably could be automated with go.mk) (c) patch lang/go [2] to skip these consistency checks [1] https://golang.org/doc/go1.14#go-command [2] https://github.com/golang/go/blob/9d67a94217c0a46a2b02a1fc67bb3e436dac0c97/= src/cmd/go/internal/modload/vendor.go#L135 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-244783-7788-w50bClFNwp>