Date: Fri, 13 Mar 2020 05:25:37 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 244783] Updating a port to go 1.14 has vendor version errors Message-ID: <bug-244783-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244783 Bug ID: 244783 Summary: Updating a port to go 1.14 has vendor version errors Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: hsw@bitmark.com Ff the source repo has a go.mod file containing: go 1.14 There will be lots of errors because go 1.14 does more strict version check= ing Sample errors: golang.org/x/crypto@v0.0.0-20200311171314-f7b00557c8c4: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt golang.org/x/sync@v0.0.0-20190423024810-112230192c58: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt golang.org/x/time@v0.0.0-20191024005414-555d28b269f0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt run 'go mod vendor' to sync, or use -mod=3Dmod or -mod=3Dreadonly to ig= nore the vendor directory *** Error code 1 A workaround is to add a files/patch-go.mod changing the 1.14 to 1.13 to restore the earlier go behaviour. --=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>