[Bug 289891] net-mgmt/netdata: Update 2.6.3 => 2.7.1

From: <bugzilla-noreply_at_freebsd.org>
Date: Wed, 01 Oct 2025 09:24:20 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289891

--- Comment #10 from Jordan Ostreff <jordan@ostreff.info> ---
(In reply to Namkhai B. from comment #9)
 # setenv | grep -i proxy
http_proxy=http://proxy:3128
https_proxy=http://proxy:3128
ftp_proxy=http://proxy:3128

Using this environment many other go based ports are build. Only netdata port
has issues.


The output looks like this:

# portmaster netdata

===>>> Currently installed version: netdata-2.6.3
===>>> Port directory: /usr/ports/net-mgmt/netdata

===>>> Gathering distinfo list for installed ports

===>>> Launching 'make checksum' for net-mgmt/netdata in background
===>>> Gathering dependency list for net-mgmt/netdata from ports
===>>> Initial dependency check complete for net-mgmt/netdata


===>>> Starting build for net-mgmt/netdata <<<===

===>>> All dependencies are up to date

===>  Cleaning for netdata-2.6.3_1
===>>> Waiting on fetch & checksum for net-mgmt/netdata <<<===
# get
https://proxy.golang.org/sigs.k8s.io/structured-merge-diff/v4/@v/v4.6.0.mod:
Get
"https://proxy.golang.org/sigs.k8s.io/structured-merge-diff/v4/@v/v4.6.0.mod":
dial tcp: lookup proxy.golang.org on 127.0.0.1:53: read udp
127.0.0.1:59000->127.0.0.1:53: read: connection refused
# get https://proxy.golang.org/k8s.io/klog/v2/@v/v2.130.1.mod: Get
"https://proxy.golang.org/k8s.io/klog/v2/@v/v2.130.1.mod": dial tcp: lookup
proxy.golang.org on 127.0.0.1:53: read udp 127.0.0.1:59000->127.0.0.1:53: read:
connection refused
# get
https://proxy.golang.org/github.com/%21d%21a%21t%21a-%21d%21o%21g/go-sqlmock/@v/v1.5.2.info
# get
https://proxy.golang.org/github.com/%21azure/go-ansiterm/@v/v0.0.0-20210617225240-d185dfc1b5a1.info
# get
https://proxy.golang.org/github.com/%21azure/go-ntlmssp/@v/v0.0.0-20221128193559-754e69321358.info
# get
https://proxy.golang.org/github.com/%21masterminds/sprig/v3/@v/v3.3.0.info
# get https://proxy.golang.org/dario.cat/mergo/@v/v1.0.1.info
# get
https://proxy.golang.org/github.com/%21masterminds/semver/v3/@v/v3.3.0.info
# get https://proxy.golang.org/github.com/%21masterminds/goutils/@v/v1.1.1.info
# get https://proxy.golang.org/filippo.io/edwards25519/@v/v1.1.0.info


===>>> Waiting on fetch & checksum for net-mgmt/netdata <<<===
# get https://proxy.golang.org/gopkg.in/ini.v1/@v/v1.67.0.info: Get
"https://proxy.golang.org/gopkg.in/ini.v1/@v/v1.67.0.info": dial tcp: lookup
proxy.golang.org on 127.0.0.1:53: read udp 127.0.0.1:54059->127.0.0.1:53: read:
connection refused
# get https://proxy.golang.org/gopkg.in/inf.v0/@v/v0.9.1.info: Get
"https://proxy.golang.org/gopkg.in/inf.v0/@v/v0.9.1.info": dial tcp: lookup
proxy.golang.org on 127.0.0.1:53: read udp 127.0.0.1:54059->127.0.0.1:53: read:
connection refused
# get
https://proxy.golang.org/k8s.io/utils/@v/v0.0.0-20241104100929-3ea5e8cea738.info
# get https://proxy.golang.org/gopkg.in/cenkalti/backoff.v2/@v/v2.2.1.info: Get
"https://proxy.golang.org/gopkg.in/cenkalti/backoff.v2/@v/v2.2.1.info": dial
tcp: lookup proxy.golang.org on 127.0.0.1:53: read udp
127.0.0.1:54059->127.0.0.1:53: read: connection refused
# get https://proxy.golang.org/k8s.io/client-go/@v/v0.33.2.info
# get
https://proxy.golang.org/sigs.k8s.io/json/@v/v0.0.0-20241010143419-9aa6b5e7a4b3.info
# get https://proxy.golang.org/k8s.io/klog/v2/@v/v2.130.1.info
# get
https://proxy.golang.org/k8s.io/kube-openapi/@v/v0.0.0-20250318190949-c8a335a9a2ff.info
# get https://proxy.golang.org/k8s.io/apimachinery/@v/v0.33.2.info
# get
https://proxy.golang.org/layeh.com/radius/@v/v0.0.0-20190322222518-890bc1058917.info


^C
===>>> Build/Install for net-mgmt/netdata exiting due to signal


the only possibility to build port on such machine is to transfer content of
/usr/ports/distfiles/go/net-mgmt_netdata/ directory from other machine which
has direct connectivity to internet.

But as I'm telling you - it looks like that for GO some parameters or something
like that is provided and it ignores environment variables. And this is
strongly specific for netdata port. That's why I'm still challenging you to try
to fix the port.

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