Date: Wed, 19 Jul 2023 14:38:26 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 272601] net-mgmt/bind_exporter: please bump version to 0.5.0 Message-ID: <bug-272601-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272601 Bug ID: 272601 Summary: net-mgmt/bind_exporter: please bump version to 0.5.0 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: gert@greenie.muc.de CC: matt@mattmoriarity.com CC: matt@mattmoriarity.com Flags: maintainer-feedback?(matt@mattmoriarity.com) FreeBSD currently ships bind_exporter 0.4.0, which fails to read bind statistics if there are unavailable zones (and bind returns <serial>-1</serial>). The fix is in 0.5.0, released over a year ago. Please bump the port accordingly. I would append a patch, but I am not a Go person, and a "simple" substituti= on of 0.4.0 by 0.5.0 leads to strange error messages =3D=3D=3D> Building bind_exporter from github.com/prometheus-community/bin= d_exporter go: finding module for package github.com/go-kit/log/level go: finding module for package github.com/prometheus/client_golang/prometheus/collectors bind_exporter.go:26:2: cannot query module due to -mod=3Dvendor bind_exporter.go:32:2: cannot query module due to -mod=3Dvendor ... which is all gibberish to me. So there is a bit more understanding nee= ded. For reference, here's the upstream ticket about the bind interop issue, fix= ed in 0.5.0 https://github.com/prometheus-community/bind_exporter/pull/97 thanks, gert --=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-272601-7788>