+ 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/s-nail-14.9.25/work.log
+ su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/s-nail-14.9.25/work.log
=> Checksum BLAKE2s OK for s-nail-14.9.25.tar.gz
=> Checksum SHA512 OK for s-nail-14.9.25.tar.gz
===> Installing dependencies for s-nail-14.9.25
==========================================================================
The following variables will affect the build process of this package,
s-nail-14.9.25.  Their current value is shown below:

        * SSLBASE (defined)
        * SSLCERTBUNDLE (not defined)
        * SSLCERTS = /etc/opt/pkg/openssl/certs
        * SSLDIR = /etc/opt/pkg/openssl
        * SSLKEYS = /etc/opt/pkg/openssl/private

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 libiconv>=1.9.1nb4: found libiconv-1.17
=> Full dependency libidn2>=2.3.3nb1: found libidn2-2.3.7
=> Full dependency openssl>=3: found openssl-3.3.2
=> Full dependency gettext-lib>=0.22: found gettext-lib-0.22.5
=> Full dependency libunistring>=0.9.3: found libunistring-1.2
===> Overriding tools for s-nail-14.9.25
===> Extracting for s-nail-14.9.25
===> Patching for s-nail-14.9.25
=> Applying pkgsrc patches for s-nail-14.9.25
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/s-nail/patches/patch-mk_make-install.sh
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/s-nail/patches/patch-mk_make-install.sh
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-mk_make-install.sh,v 1.1 2024/01/17 23:43:02 gdt Exp $
|
|Put the default config in EGDIR so we can use CONF_FILES
|
|--- mk/make-install.sh.orig	2022-03-26 15:28:51.000000000 +0000
|+++ mk/make-install.sh
--------------------------
Patching file mk/make-install.sh using Plan A...
Hunk #1 succeeded at 51.
done
===> Creating toolchain wrappers for s-nail-14.9.25
===> Configuring for s-nail-14.9.25
=> Checking for portability problems in extracted files
ERROR: [check-portability] => Found test ... == ...:
ERROR: [check-portability] mx-test.sh:2074: if [ [ $diet == 'yo' ] && [ $curd == 'ho' ] ] && [ $ndefined ]

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] mx-test.sh:2080: if [ [ $diet == 'yo' ] && [ $curd == 'ho' ] ] && [ $ndefined ]

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] mx-test.sh:2168: if [ $diet == 'yo' && $curd == 'ho' ] && $ndefined

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] mx-test.sh:2179: if [ $diet == 'yo' && $curd == 'ho' ] && $ndefined

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] mx-test.sh:2189: if [ [ [ [ [ [ $diet == 'yo' && $curd == 'ho' && $ndefined ] ] ] ] ] ]

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] mx-test.sh:2817: if [ [ $diet == 'yo' ] && [ $curd == 'ho' ] ] && \

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] mx-test.sh:2825: if [ [ $diet == 'yo' ] && [ $curd == 'ho' ] ] && \

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] mx-test.sh:2915: if [ $diet == 'yo' && $curd == 'ho' ] && \

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] mx-test.sh:2922: if [ $diet == 'yo' && $curd == 'ho' && \

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] mx-test.sh:2930: if [ $diet == 'yo' && $curd == 'ho' ] && \

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] mx-test.sh:2942: if [ [ [ [ [ [ $diet == 'yo' && $curd == 'ho' && -N ndefined ] ] ] ] ] ]

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] mx-test.sh:3453: if [ $# > 1 ] || [ $ignerr == '' ]

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] mx-test.sh:8405: if [ "$t_remove" == "" ]

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] mx-test.sh:8526: if [ "$t_remove" == "" ]

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] mx-test.sh:8745: if [ "$t_remove" == "" ]

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/mail/s-nail
*** Error code 1

Stop.
bmake: stopped making "configure" in /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/s-nail