[Bug 244783] lang/go: Updating ports to go 1.14 can cause vendor version errors (eg: net-p2p/bitmark)

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Mar 13 13:27:55 UTC 2020


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244783

Dmitri Goutnik <dmgk at freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dmgk at freebsd.org

--- Comment #4 from Dmitri Goutnik <dmgk at freebsd.org> ---
This looks like it could be a serious issue as more upstreams will be updating
go.mod to require go1.14:

"When -mod=vendor 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=vendor is the only mode that works for ports due to restricted
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

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list