+ 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/db18-18.1.40/work.log
+ su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/db18-18.1.40/work.log
=> Checksum BLAKE2s OK for db-18.1.40.tar.gz
=> Checksum SHA512 OK for db-18.1.40.tar.gz
===> Installing dependencies for db18-18.1.40
=> Tool dependency libtool-base>=2.4.2nb9: found libtool-base-2.4.7nb1
=> Tool dependency pax>=20040802: found pax-20210219
=> Tool dependency cwrappers>=20150314: found cwrappers-20220403
=> Tool dependency checkperms>=1.1: found checkperms-1.12
===> Overriding tools for db18-18.1.40
===> Extracting for db18-18.1.40
===> Patching for db18-18.1.40
=> Applying pkgsrc patches for db18-18.1.40
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db18/patches/patch-dist_Makefile.in
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db18/patches/patch-dist_Makefile.in
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-dist_Makefile.in,v 1.1 2020/06/29 13:30:35 ryoon Exp $
|
|* Adjust library name to coexist other berkeley DB versions.
|
|--- dist/Makefile.in.orig	2020-05-29 17:58:22.000000000 +0000
|+++ dist/Makefile.in
--------------------------
Patching file dist/Makefile.in using Plan A...
Hunk #1 succeeded at 17.
Hunk #2 succeeded at 54.
Hunk #3 succeeded at 73.
Hunk #4 succeeded at 92.
Hunk #5 succeeded at 167.
Hunk #6 succeeded at 188.
Hunk #7 succeeded at 1109.
Hunk #8 succeeded at 1233.
Hunk #9 succeeded at 1283.
Hunk #10 succeeded at 1296.
Hunk #11 succeeded at 1306.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db18/patches/patch-dist_bumprel
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db18/patches/patch-dist_bumprel
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-dist_bumprel,v 1.1 2020/06/29 13:30:35 ryoon Exp $
|
|--- dist/bumprel.orig	2020-05-29 17:58:22.000000000 +0000
|+++ dist/bumprel
--------------------------
Patching file dist/bumprel using Plan A...
Hunk #1 succeeded at 49.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db18/patches/patch-dist_configure
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db18/patches/patch-dist_configure
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-dist_configure,v 1.1 2020/06/29 13:30:35 ryoon Exp $
|
|--- dist/configure.orig	2020-05-29 17:58:22.000000000 +0000
|+++ dist/configure
--------------------------
Patching file dist/configure using Plan A...
Hunk #1 succeeded at 7044.
Hunk #2 succeeded at 20201.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db18/patches/patch-test_xa_src1_run.sh
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db18/patches/patch-test_xa_src1_run.sh
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-test_xa_src1_run.sh,v 1.1 2020/06/29 13:30:35 ryoon Exp $
|
|--- test/xa/src1/run.sh.orig	2020-05-29 17:58:22.000000000 +0000
|+++ test/xa/src1/run.sh
--------------------------
Patching file test/xa/src1/run.sh using Plan A...
Hunk #1 succeeded at 4.
Hunk #2 succeeded at 29.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db18/patches/patch-test_xa_src3_run.sh
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db18/patches/patch-test_xa_src3_run.sh
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-test_xa_src3_run.sh,v 1.1 2020/06/29 13:30:35 ryoon Exp $
|
|--- test/xa/src3/run.sh.orig	2020-05-29 17:58:22.000000000 +0000
|+++ test/xa/src3/run.sh
--------------------------
Patching file test/xa/src3/run.sh using Plan A...
Hunk #1 succeeded at 4.
Hunk #2 succeeded at 28.
Hunk #3 succeeded at 90.
Hunk #4 succeeded at 115.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db18/patches/patch-test_xa_src4_run.sh
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db18/patches/patch-test_xa_src4_run.sh
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-test_xa_src4_run.sh,v 1.1 2020/06/29 13:30:35 ryoon Exp $
|
|--- test/xa/src4/run.sh.orig	2020-05-29 17:58:22.000000000 +0000
|+++ test/xa/src4/run.sh
--------------------------
Patching file test/xa/src4/run.sh using Plan A...
Hunk #1 succeeded at 4.
Hunk #2 succeeded at 27.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db18/patches/patch-test_xa_src5_run.sh
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db18/patches/patch-test_xa_src5_run.sh
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-test_xa_src5_run.sh,v 1.1 2020/06/29 13:30:35 ryoon Exp $
|
|--- test/xa/src5/run.sh.orig	2020-05-29 17:58:22.000000000 +0000
|+++ test/xa/src5/run.sh
--------------------------
Patching file test/xa/src5/run.sh using Plan A...
Hunk #1 succeeded at 7.
Hunk #2 succeeded at 37.
done
===> Creating toolchain wrappers for db18-18.1.40
===> Configuring for db18-18.1.40
=> 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] dist/s_list_dup_message.sh:20: if [ "$1" == "id" ] ; 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: [check-portability] => Found test ... == ...:
ERROR: [check-portability] dist/validate/s_chk_message_id:32: if [ "$curnum" == "id" ]; 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: [check-portability] => Found test ... == ...:
ERROR: [check-portability] dist/validate/s_chk_message_id:47: if [ "$curnum" == "$lastnum" ]; 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: [check-portability] => Found test ... == ...:
ERROR: [check-portability] dist/validate/s_chk_message_id:48: if [ "$curnum" == "$rep_dup_msg_id" ]; 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/databases/db18
*** Error code 1

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