=> Bootstrap dependency digest>=20010302: found digest-20190127 ===> Skipping vulnerability checks. WARNING: No /var/db/pkg/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /var/db/pkg fetch-pkg-vulnerabilities'. => Checksum SHA1 OK for beats-6.6.2.tar.gz => Checksum RMD160 OK for beats-6.6.2.tar.gz => Checksum SHA512 OK for beats-6.6.2.tar.gz ===> Installing dependencies for beats-6.6.2nb7 => Tool dependency bsdtar-[0-9]*: found bsdtar-3.4.0 => Tool dependency gmake>=3.81: found gmake-4.2.1nb1 => Tool dependency checkperms>=1.1: found checkperms-1.12 => Build dependency go112-1.12.14*: found go112-1.12.14 => Build dependency cwrappers>=20150314: found cwrappers-20180325 ===> Overriding tools for beats-6.6.2nb7 ===> Extracting for beats-6.6.2nb7 ===> Patching for beats-6.6.2nb7 => Applying pkgsrc patches for beats-6.6.2nb7 => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/beats/patches/patch-vendor_github.com_insomniacslk_dhcp_dhcpv4_client.go => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/beats/patches/patch-vendor_github.com_insomniacslk_dhcp_dhcpv4_client.go Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-vendor_github.com_insomniacslk_dhcp_dhcpv4_client.go,v 1.1 2019/03/15 15:03:02 he Exp $ | |BindToInterface is apparently only implemented for Linux and Darwin. |So much for portable software. Since I fail to grasp what dhcp has |to do with shipping logs, just comment out the code to make it build. | |--- vendor/github.com/insomniacslk/dhcp/dhcpv4/client.go.orig 2019-03-06 10:13:10.000000000 +0000 |+++ vendor/github.com/insomniacslk/dhcp/dhcpv4/client.go -------------------------- Patching file vendor/github.com/insomniacslk/dhcp/dhcpv4/client.go using Plan A... Hunk #1 succeeded at 90. Hunk #2 succeeded at 113. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/beats/patches/patch-vendor_github.com_tsg_gopacket_pcap_pcap.go => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/beats/patches/patch-vendor_github.com_tsg_gopacket_pcap_pcap.go Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-vendor_github.com_tsg_gopacket_pcap_pcap.go,v 1.1 2017/01/05 16:43:09 fhajny Exp $ | |Just require pcap, fixes NetBSD. | |--- vendor/github.com/tsg/gopacket/pcap/pcap.go.orig 2016-12-06 07:41:08.000000000 +0000 |+++ vendor/github.com/tsg/gopacket/pcap/pcap.go -------------------------- Patching file vendor/github.com/tsg/gopacket/pcap/pcap.go using Plan A... Hunk #1 succeeded at 8. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/beats/patches/patch-vendor_golang.org_x_crypto_blake2b_blake2bAVX2__amd64.go => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/beats/patches/patch-vendor_golang.org_x_crypto_blake2b_blake2bAVX2__amd64.go Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-vendor_golang.org_x_crypto_blake2b_blake2bAVX2__amd64.go,v 1.1 2019/03/15 15:03:02 he Exp $ | |We get link errors about runtime.support_avx and runtime.support_avx2, so |revert the offending commit from |https://github.com/golang/crypto/commit/b0697eccbea9adec5b7ba8008f4c33d98d733388 |I've not been able to track which version of golang.org/x/crypto is |embedded in the beats package, and frankly am befuddled that this sort |of thing makes it into released code, in this day and age with widespread |use of CI etc. This coupled with the apparent widespread practice of |"vendoring" code (copy a vendor's code and ship it as part of your source |package) makes it difficult to stamp out this sort of bugs. Sigh! | |--- vendor/golang.org/x/crypto/blake2b/blake2bAVX2_amd64.go.orig 2019-03-06 10:13:10.000000000 +0000 |+++ vendor/golang.org/x/crypto/blake2b/blake2bAVX2_amd64.go -------------------------- Patching file vendor/golang.org/x/crypto/blake2b/blake2bAVX2_amd64.go using Plan A... Hunk #1 succeeded at 6. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/beats/patches/patch-vendor_golang.org_x_crypto_blake2b_blake2bAVX2__amd64.s => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/beats/patches/patch-vendor_golang.org_x_crypto_blake2b_blake2bAVX2__amd64.s Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-vendor_golang.org_x_crypto_blake2b_blake2bAVX2__amd64.s,v 1.1 2019/03/15 15:03:03 he Exp $ | |We get link errors about runtime.support_avx and runtime.support_avx2, so |revert the offending commit from |https://github.com/golang/crypto/commit/b0697eccbea9adec5b7ba8008f4c33d98d733388 |I've not been able to track which version of golang.org/x/crypto is |embedded in the beats package, and frankly am befuddled that this sort |of thing makes it into released code, in this day and age with widespread |use of CI etc. This coupled with the apparent widespread practice of |"vendoring" code (copy a vendor's code and ship it as part of your source |package) makes it difficult to stamp out this sort of bugs. Sigh! | |--- vendor/golang.org/x/crypto/blake2b/blake2bAVX2_amd64.s.orig 2019-03-06 10:13:10.000000000 +0000 |+++ vendor/golang.org/x/crypto/blake2b/blake2bAVX2_amd64.s -------------------------- Patching file vendor/golang.org/x/crypto/blake2b/blake2bAVX2_amd64.s using Plan A... Hunk #1 succeeded at 748. done ===> Creating toolchain wrappers for beats-6.6.2nb7 ===> Configuring for beats-6.6.2nb7 => Checking for portability problems in extracted files