+ case "${usergroup_phase}" in
+ local run_cmd
+ run_cmd=run_su
+ shift
+ run_su /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent LUA_VERSION_REQD=54 WRKLOG=/tmp/bulklog/lua54-socket-3.0rc1nb5/work.log
+ su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent LUA_VERSION_REQD=54 WRKLOG=/tmp/bulklog/lua54-socket-3.0rc1nb5/work.log
=> Checksum BLAKE2s OK for luasocket-3.0-rc1.tar.gz
=> Checksum SHA512 OK for luasocket-3.0-rc1.tar.gz
===> Installing dependencies for lua54-socket-3.0rc1nb5
==========================================================================
The following variables will affect the build process of this package,
lua54-socket-3.0rc1nb5.  Their current value is shown below:

        * CURSES_DEFAULT = ncurses
        * LUA_VERSION_DEFAULT = 54
        * READLINE_DEFAULT = readline

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

        * CURSES_TYPE = ncurses
        * LUA_PACKAGE = lua54
        * READLINE_TYPE = readline
        * TERMCAP_TYPE = curses

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 lua54>=5.4.0<5.5: found lua54-5.4.7
=> Full dependency ncurses>=5.3nb1: found ncurses-6.5
=> Full dependency readline>=2.2: found readline-8.2nb2
===> Overriding tools for lua54-socket-3.0rc1nb5
===> Extracting for lua54-socket-3.0rc1nb5
===> Patching for lua54-socket-3.0rc1nb5
=> Applying pkgsrc patches for lua54-socket-3.0rc1nb5
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/lua-socket/patches/patch-makefile
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/lua-socket/patches/patch-makefile
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-makefile,v 1.2 2024/02/05 13:23:16 tm Exp $
|
|Pass our LDFLAGS.
|
|--- makefile.orig	2013-06-14 11:27:32.000000000 +0000
|+++ makefile
--------------------------
Patching file makefile using Plan A...
Hunk #1 succeeded at 15.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/lua-socket/patches/patch-src_makefile
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/lua-socket/patches/patch-src_makefile
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_makefile,v 1.3 2024/02/05 13:23:16 tm Exp $
|
|Pass our LDFLAGS.
|Build unix.so, serial.so and install them always.
|
|--- src/makefile.orig	2013-06-14 11:27:32.000000000 +0000
|+++ src/makefile
--------------------------
Patching file src/makefile using Plan A...
Hunk #1 succeeded at 145.
Hunk #2 succeeded at 307.
Hunk #3 succeeded at 332.
done
===> Creating toolchain wrappers for lua54-socket-3.0rc1nb5
===> Configuring for lua54-socket-3.0rc1nb5
=> Checking for portability problems in extracted files
ERROR: [check-portability] => Found test ... == ...:
ERROR: [check-portability] gem/myps2pdf:42: if [ $best == 1 ]

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] gem/myps2pdf:76: if [ $rot == 1 ]

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] gem/myps2pdf:81: if [ $eps == 1 ]

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] gem/myps2pdf:88: if [ $a4 == 1 ]

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] gem/myps2pdf:107: if [ $do_opt == 1 ]

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/net/lua-socket
*** Error code 1

Stop.
bmake: stopped making "configure" in /data/jenkins/workspace/pkgsrc-upstream-trunk/net/lua-socket