+ case "${usergroup_phase}" in + local run_cmd + run_cmd=run_su + shift + run_su /usr/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent PYTHON_VERSION_REQD=312 WRKLOG=/tmp/bulklog/py312-u2f-0.1.5nb1/work.log + su pbulk -c '"$@"' make /usr/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent PYTHON_VERSION_REQD=312 WRKLOG=/tmp/bulklog/py312-u2f-0.1.5nb1/work.log => Bootstrap dependency digest>=20211023: found digest-20220214 => Checksum BLAKE2s OK for pyu2f-0.1.5.tar.gz => Checksum SHA512 OK for pyu2f-0.1.5.tar.gz ===> Installing dependencies for py312-u2f-0.1.5nb1 ========================================================================== The following variables will affect the build process of this package, py312-u2f-0.1.5nb1. Their current value is shown below: * PYTHON_VERSION_DEFAULT = 311 Based on these variables, the following variables have been set: * PYPACKAGE = python312 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/pkg/bin/bmake clean' after the changes. ========================================================================== => Tool dependency py312-setuptools-[0-9]*: found py312-setuptools-69.5.1 => Tool dependency mktools-[0-9]*: found mktools-20220614 => Tool dependency nbpatch-[0-9]*: found nbpatch-20151107 => Tool dependency cwrappers>=20150314: found cwrappers-20220403 => Tool dependency checkperms>=1.1: found checkperms-1.12 => Full dependency py312-six-[0-9]*: found py312-six-1.16.0nb1 => Full dependency python312>=3.12: found python312-3.12.3 ===> Overriding tools for py312-u2f-0.1.5nb1 ===> Extracting for py312-u2f-0.1.5nb1 ===> Patching for py312-u2f-0.1.5nb1 => Applying pkgsrc patches for py312-u2f-0.1.5nb1 => Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/py-u2f/patches/patch-pyu2f_hid_____init____.py => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/py-u2f/patches/patch-pyu2f_hid_____init____.py Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-pyu2f_hid_____init____.py,v 1.1 2020/08/17 20:57:44 riastradh Exp $ | |Add NetBSD support. | |--- pyu2f/hid/__init__.py.orig 2020-08-17 20:48:34.101158593 +0000 |+++ pyu2f/hid/__init__.py -------------------------- Patching file pyu2f/hid/__init__.py using Plan A... Hunk #1 succeeded at 41. done => Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/py-u2f/patches/patch-pyu2f_hid_netbsd.py => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/py-u2f/patches/patch-pyu2f_hid_netbsd.py Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-pyu2f_hid_netbsd.py,v 1.1 2020/08/17 20:57:44 riastradh Exp $ | |Add NetBSD support. | |--- pyu2f/hid/netbsd.py.orig 2020-08-17 20:43:03.167593821 +0000 |+++ pyu2f/hid/netbsd.py -------------------------- (Creating file pyu2f/hid/netbsd.py...) Patching file pyu2f/hid/netbsd.py using Plan A... Empty context always matches. Hunk #1 succeeded at 1. done => Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/py-u2f/patches/patch-setup.py => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/py-u2f/patches/patch-setup.py Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-setup.py,v 1.2 2022/01/27 10:39:53 wiz Exp $ | |Seems unused. |https://github.com/google/pyu2f/issues/33 | |--- setup.py.orig 2020-10-30 20:02:44.000000000 +0000 |+++ setup.py -------------------------- Patching file setup.py using Plan A... Hunk #1 succeeded at 40. done ===> Creating toolchain wrappers for py312-u2f-0.1.5nb1 ===> Configuring for py312-u2f-0.1.5nb1 => Checking for portability problems in extracted files