From owner-freebsd-ports@freebsd.org  Tue Nov  5 00:28:03 2019
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id 22D741B5300
 for <freebsd-ports@mailman.nyi.freebsd.org>;
 Tue,  5 Nov 2019 00:28:03 +0000 (UTC)
 (envelope-from meta@FreeBSD.org)
Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3])
 by mx1.freebsd.org (Postfix) with ESMTP id 476Vr300Z3z4XrJ
 for <freebsd-ports@freebsd.org>; Tue,  5 Nov 2019 00:28:03 +0000 (UTC)
 (envelope-from meta@FreeBSD.org)
Received: by mailman.nyi.freebsd.org (Postfix)
 id F3FB11B52FF; Tue,  5 Nov 2019 00:28:02 +0000 (UTC)
Delivered-To: ports@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id F39C51B52FE
 for <ports@mailman.nyi.freebsd.org>; Tue,  5 Nov 2019 00:28:02 +0000 (UTC)
 (envelope-from meta@FreeBSD.org)
Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 server-signature RSA-PSS (4096 bits)
 client-signature RSA-PSS (4096 bits) client-digest SHA256)
 (Client CN "smtp.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 476Vr24pDBz4XrH;
 Tue,  5 Nov 2019 00:28:02 +0000 (UTC)
 (envelope-from meta@FreeBSD.org)
Received: from icepick.vmeta.jp (unknown
 [IPv6:2405:6586:2280:1200:e167:a57f:fd78:5fc9])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 (Authenticated sender: meta/mail)
 by smtp.freebsd.org (Postfix) with ESMTPSA id B9E3729E1C;
 Tue,  5 Nov 2019 00:28:01 +0000 (UTC)
 (envelope-from meta@FreeBSD.org)
Date: Tue, 5 Nov 2019 09:27:58 +0900
From: Koichiro Iwao <meta@FreeBSD.org>
To: ports@FreeBSD.org
Subject: golang apps try to use network during build and build erro on
Message-ID: <20191105002758.mawurxi63vb5gydz@icepick.vmeta.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
User-Agent: NeoMutt/20180716
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2019 00:28:03 -0000

poudriere
Reply-To:
X-Operating-System: FreeBSD 12.1-STABLE amd64


Hi,

I recently noticed some golang apps (recent vewsion?) try to use network
during build.  As we know, this causes build error on poudriere.

I'm not familiar with golang build system. I'm not sure why this happens
and the differences between golang apps use network and don't. I'd
appreciate if you give me some advice how do golang folks avoid using
network during build?

===>  Building cli53 from ./cmd/cli53
go: github.com/aws/aws-sdk-go@v1.13.34: Get
https://proxy.golang.org/github.com/aws/aws-sdk-go/@v/v1.13.34.mod: dial tcp
: lookup proxy.golang.org on 192.168.24.1:53: write udp 127.0.0.1:52854->192.168.24.1:53: write: permission denied

-- 
meta <meta@FreeBSD.org>