On 2019/09/13 23:32, Joel Sing wrote:
> On 19-09-13 12:38:19, Stuart Henderson wrote:
> > On 2019/09/10 04:20, Joel Sing wrote:
> > > The following updates lang/go to Go 1.13 and also updates the main
> > > golang.org/x packages to around the Go 1.13 release. This does
> > > not update devel/go-tools, as it introduces new dependencies that
> > > will need to be packaged. Once this lands I can also work towards
> > > enabling Go on arm64.
> > >
> > > The following ports appear to break with this update:
> > >
> > > net/go-ipfs
> > > net/mattermost-server
> > > security/keybase
> > > sysutils/consul
> > > sysutils/restic
> > > sysutils/restic-rest-server
> > > www/hugo
> >
> > net/dnscrypt-proxy now attempts to fetch from the network, this is
> > blocked on the main ports build machines and for anyone using
> > PORTS_PRIVSEP=Yes in mk.conf with the default "block return out log
> > proto {tcp udp} user _pbuild" pf rule. Any advice on how to fix this?
>
> Unfortunately this is going to become more of a problem, since Go is pushing
> towards the use of Go modules and fetching of dependencies at build time,
> rather than vendoring code. We'll have to figure out how we address this
> moving forward.
Same problem everywhere unfortunately. npm, maven, cargo, even "normal"
use of python..
> The following diff should fix this case:
Thanks, confirmed it does. OK.
> Index: Makefile
> ===================================================================
> RCS file: /cvs/ports/net/dnscrypt-proxy/Makefile,v
> retrieving revision 1.44
> diff -u -p -r1.44 Makefile
> --- Makefile 10 Sep 2019 13:19:25 -0000 1.44
> +++ Makefile 13 Sep 2019 13:30:31 -0000
> @@ -19,6 +19,7 @@ WANTLIB = c pthread
>
> MODULES = lang/go
> MODGO_TYPE = bin
> +MAKE_ENV += GO111MODULE=off
> NO_TEST = Yes
>
> INSTDIR = ${PREFIX}/share/examples/dnscrypt-proxy
>
