+ case "${usergroup_phase}" in
+ local run_cmd
+ run_cmd=run_su
+ shift
+ run_su /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent PYTHON_VERSION_REQD=27 WRKLOG=/tmp/bulklog/py27-pqueue-0.2nb1/work.log
+ su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent PYTHON_VERSION_REQD=27 WRKLOG=/tmp/bulklog/py27-pqueue-0.2nb1/work.log
=> Checksum BLAKE2s OK for PQueue-0.2.tar.bz2
=> Checksum SHA512 OK for PQueue-0.2.tar.bz2
===> Installing dependencies for py27-pqueue-0.2nb1
==========================================================================
The following variables will affect the build process of this package,
py27-pqueue-0.2nb1.  Their current value is shown below:

        * PYTHON_VERSION_DEFAULT = 312

Based on these variables, the following variables have been set:

        * PYPACKAGE = python27

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
`/opt/pkg/bin/bmake clean' after the changes.
==========================================================================
=> Tool dependency cwrappers>=20150314: found cwrappers-20220403
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Full dependency python27>=2.7.1nb2: found python27-2.7.18nb21
=> Full dependency gettext-lib>=0.22: found gettext-lib-0.22.5
=> Full dependency libiconv>=1.9.1: found libiconv-1.17nb1
===> Overriding tools for py27-pqueue-0.2nb1
===> Extracting for py27-pqueue-0.2nb1
===> Patching for py27-pqueue-0.2nb1
=> Applying pkgsrc patches for py27-pqueue-0.2nb1
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/py-pqueue/patches/patch-aa
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/py-pqueue/patches/patch-aa
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-aa,v 1.1 2009/02/11 19:19:00 joerg Exp $
|
|--- Makefile.pre.in.orig	1999-07-09 12:18:20.000000000 +0200
|+++ Makefile.pre.in
--------------------------
Patching file Makefile.pre.in using Plan A...
Hunk #1 succeeded at 118.
Hunk #2 succeeded at 171.
Hunk #3 succeeded at 182.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/py-pqueue/patches/patch-ab
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/py-pqueue/patches/patch-ab
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ab,v 1.1 2009/02/11 19:19:00 joerg Exp $
|
|--- configure.orig	1999-07-13 15:12:30.000000000 +0200
|+++ configure
--------------------------
Patching file configure using Plan A...
Hunk #1 succeeded at 700.
Hunk #2 succeeded at 726.
Hunk #3 succeeded at 1230.
done
===> Creating toolchain wrappers for py27-pqueue-0.2nb1
===> Configuring for py27-pqueue-0.2nb1
=> Modifying GNU configure scripts to avoid --recheck
=> Replacing config-guess with pkgsrc versions
=> Replacing config-sub with pkgsrc versions
=> Replacing install-sh with pkgsrc version
=> Checking for portability problems in extracted files
creating cache ./config.cache
checking for python... /opt/pkg/bin/python2.7
checking python version... 2.7
checking python installation prefix... /opt/pkg
checking python installation exec_prefix... /opt/pkg
checking definitions in Python library makefile... done
checking location of python library... $(prefix)/lib/python2.7/site-packages
checking location of python shared modules... $(exec_prefix)/lib/python2.7/site-packages
checking for inline... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... no
updating cache ./config.cache
creating ./config.status
creating Setup
creating Makefile.pre
creating pqueuemodule-config.h
creating Makefile