Date: Thu, 04 Dec 2025 09:02:44 +0000 From: bugzilla-noreply@freebsd.org To: go@FreeBSD.org Subject: [Bug 291375] Mk/Uses/go.mk: how not to use a GOPROXY? (GOPROXY=direct) Message-ID: <bug-291375-42334-qnNIPNnILP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-291375-42334@https.bugs.freebsd.org/bugzilla/> References: <bug-291375-42334@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=291375 --- Comment #3 from Benjamin Takacs <nimaje+fbz@bureaucracy.de> --- I tested that idea just now, most golang ports I have in my package list build fine like that. But security/snowflake-tor failed, seems like a dependency of it (lyft/protoc-gen-validate) got deleted from github. That is exactly why I don't like the GOPROXY idea of golang, as it hides these problems. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-291375-42334-qnNIPNnILP>