+ case "${usergroup_phase}" in
+ local run_cmd
+ run_cmd=run_su
+ shift
+ run_su /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/pkg-1.10.99.7nb1/work.log
+ su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/pkg-1.10.99.7nb1/work.log
=> Checksum BLAKE2s OK for pkg-1.10.99.7.tar.xz
=> Checksum SHA512 OK for pkg-1.10.99.7.tar.xz
===> Installing dependencies for pkg-1.10.99.7nb1
=> Tool dependency cwrappers>=20150314: found cwrappers-20220403
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Full dependency libarchive>=3.3.1: found libarchive-3.7.7
=> Full dependency bzip2>=1.0.1: found bzip2-1.0.8
=> Full dependency xz>=5.0.0: found xz-5.6.3
=> Full dependency zlib>=1.1.4: found zlib-1.3.1
===> Overriding tools for pkg-1.10.99.7nb1
===> Extracting for pkg-1.10.99.7nb1
===> Patching for pkg-1.10.99.7nb1
=> Applying pkgsrc patches for pkg-1.10.99.7nb1
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/pkgtools/pkg/patches/patch-scripts_periodic_411.pkg-backup.in
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/pkgtools/pkg/patches/patch-scripts_periodic_411.pkg-backup.in
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-scripts_periodic_411.pkg-backup.in,v 1.1 2020/04/10 23:28:32 khorben Exp $
|
|Pass the portability test
|
|--- scripts/periodic/411.pkg-backup.in.orig	2020-04-10 23:10:58.674050832 +0000
|+++ scripts/periodic/411.pkg-backup.in
--------------------------
Patching file scripts/periodic/411.pkg-backup.in using Plan A...
Hunk #1 succeeded at 25.
done
===> Creating toolchain wrappers for pkg-1.10.99.7nb1
===> Configuring for pkg-1.10.99.7nb1
=> Update pkg(8) defaults.
=> Direct audit reports to Pkgsrc vuxml
=> 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
ERROR: [check-portability] => Found test ... == ...:
ERROR: [check-portability] scripts/periodic/411.pkg-backup:28: if [ ${i} == 0 ]; then

Explanation:
===========================================================================
The "test" command, as well as the "[" command, are not required to know
the "==" operator. Only a few implementations like bash and some
versions of ksh support it.

When you run "test foo == foo" on a platform that does not support the
"==" operator, the result will be "false" instead of "true". This can
lead to unexpected behavior.

There are two ways to fix this error message. If the file that contains
the "test ==" is needed for building the package, you should create a
patch for it, replacing the "==" operator with "=". If the file is not
needed, add its name to the CHECK_PORTABILITY_SKIP variable in the
package Makefile.
===========================================================================
    
*** Error code 1

Stop.
bmake[1]: stopped making "configure" in /data/jenkins/workspace/pkgsrc-upstream-trunk/pkgtools/pkg
*** Error code 1

Stop.
bmake: stopped making "configure" in /data/jenkins/workspace/pkgsrc-upstream-trunk/pkgtools/pkg