=> Bootstrap dependency digest>=20211023: found digest-20220214 => Checksum BLAKE2s OK for redo-0.42d.tar.gz => Checksum SHA512 OK for redo-0.42d.tar.gz ===> Installing dependencies for apenwarr-redo-0.42dnb3 ========================================================================== The following variables will affect the build process of this package, apenwarr-redo-0.42dnb3. Their current value is shown below: * PYTHON_VERSION_DEFAULT = 311 Based on these variables, the following variables have been set: * PYPACKAGE = python311 You may want to abort the process now with CTRL-C and change the value of variables in the first group before continuing. Be sure to run `/usr/bin/make clean' after the changes. ========================================================================== => Tool dependency py311-beautifulsoup4-[0-9]*: found py311-beautifulsoup4-4.12.3 => Tool dependency py311-markdown-[0-9]*: found py311-markdown-3.5.2 => Tool dependency mktools-[0-9]*: found mktools-20220614 => Tool dependency cwrappers>=20150314: found cwrappers-20220403 => Tool dependency checkperms>=1.1: found checkperms-1.12 => Full dependency dash-[0-9]*: found dash-0.5.12 => Full dependency py311-setproctitle-[0-9]*: found py311-setproctitle-1.3.3 => Full dependency python311>=3.11.6nb1: found python311-3.11.8 ===> Skipping vulnerability checks. WARNING: No /usr/pkg/pkgdb/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /usr/pkg/pkgdb fetch-pkg-vulnerabilities'. ===> Overriding tools for apenwarr-redo-0.42dnb3 ===> Extracting for apenwarr-redo-0.42dnb3 ===> Patching for apenwarr-redo-0.42dnb3 => Applying pkgsrc patches for apenwarr-redo-0.42dnb3 => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/devel/apenwarr-redo/patches/patch-bin_all.do => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/devel/apenwarr-redo/patches/patch-bin_all.do Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-bin_all.do,v 1.2 2019/11/09 15:00:55 schmonz Exp $ | |Add info to help debug bulk build failures. | |--- bin/all.do.orig 2019-07-24 07:27:12.000000000 +0000 |+++ bin/all.do -------------------------- Patching file bin/all.do using Plan A... Hunk #1 succeeded at 1. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/devel/apenwarr-redo/patches/patch-do => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/devel/apenwarr-redo/patches/patch-do Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-do,v 1.3 2019/09/02 18:20:50 schmonz Exp $ | |Avoid spurious output. |Run self-test verbosely, to try to get more info from failing bulk builds. | |--- do.orig 2019-01-02 19:49:33.000000000 +0000 |+++ do -------------------------- Patching file do using Plan A... Hunk #1 succeeded at 11. Hunk #2 succeeded at 52. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/devel/apenwarr-redo/patches/patch-docs_md2man.py => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/devel/apenwarr-redo/patches/patch-docs_md2man.py Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-docs_md2man.py,v 1.1 2020/03/30 08:02:22 schmonz Exp $ | |Avoid finding older BeautifulSoup. | |--- docs/md2man.py.orig 2020-03-04 20:00:34.000000000 +0000 |+++ docs/md2man.py -------------------------- Patching file docs/md2man.py using Plan A... Hunk #1 succeeded at 1. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/devel/apenwarr-redo/patches/patch-install.do => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/devel/apenwarr-redo/patches/patch-install.do Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-install.do,v 1.1 2020/07/06 15:18:26 schmonz Exp $ | |Avoid CONFLICTS with other redo implementations. | |--- install.do.orig 2020-06-15 06:20:02.000000000 +0000 |+++ install.do -------------------------- Patching file install.do using Plan A... Hunk #1 succeeded at 4. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/devel/apenwarr-redo/patches/patch-redo_sh.do => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/devel/apenwarr-redo/patches/patch-redo_sh.do Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-redo_sh.do,v 1.2 2019/09/02 18:20:50 schmonz Exp $ | |Look for pkgsrc-provided dash only. | |--- redo/sh.do.orig 2019-01-02 19:49:33.000000000 +0000 |+++ redo/sh.do -------------------------- Patching file redo/sh.do using Plan A... Hunk #1 succeeded at 11. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/devel/apenwarr-redo/patches/patch-redo_whichpython.do => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/devel/apenwarr-redo/patches/patch-redo_whichpython.do Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-redo_whichpython.do,v 1.1 2020/03/30 08:02:22 schmonz Exp $ | |Avoid finding pkg_alternatives(8) wrapper, or really any interpreter |besides the one explicitly depended on. | |--- redo/whichpython.do.orig 2020-03-04 20:00:34.000000000 +0000 |+++ redo/whichpython.do -------------------------- Patching file redo/whichpython.do using Plan A... Hunk #1 succeeded at 1. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/devel/apenwarr-redo/patches/patch-t_shelltest.od => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/devel/apenwarr-redo/patches/patch-t_shelltest.od Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-t_shelltest.od,v 1.1 2019/07/20 21:17:11 schmonz Exp $ | |Avoid spurious output. | |--- t/shelltest.od.orig 2019-01-02 19:49:33.000000000 +0000 |+++ t/shelltest.od -------------------------- Patching file t/shelltest.od using Plan A... Hunk #1 succeeded at 14. done ===> Creating toolchain wrappers for apenwarr-redo-0.42dnb3 ===> Configuring for apenwarr-redo-0.42dnb3 => Checking for portability problems in extracted files => Substituting "paths" in redo/whichpython.do