+ 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/maradns-2.0.17/work.log
+ su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/maradns-2.0.17/work.log
=> Checksum BLAKE2s OK for maradns-2.0.17.tar.bz2
=> Checksum SHA512 OK for maradns-2.0.17.tar.bz2
===> Installing dependencies for maradns-2.0.17
==========================================================================
The supported build options for maradns are:
inet6
The currently selected options are:
inet6
You can select which build options to use by setting PKG_DEFAULT_OPTIONS
or the following variable. Its current value is shown:
PKG_OPTIONS.maradns (not defined)
==========================================================================
=> Tool dependency cwrappers>=20150314: found cwrappers-20220403
=> Tool dependency checkperms>=1.1: found checkperms-1.12
===> Overriding tools for maradns-2.0.17
===> Extracting for maradns-2.0.17
===> Patching for maradns-2.0.17
=> Applying pkgsrc patches for maradns-2.0.17
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/maradns/patches/patch-aa
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/maradns/patches/patch-aa
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-aa,v 1.5 2012/02/28 21:55:28 cheusov Exp $
|
|--- build/install.locations.orig 2011-02-06 02:21:31.000000000 +0000
|+++ build/install.locations
--------------------------
Patching file build/install.locations using Plan A...
Hunk #1 succeeded at 23.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/maradns/patches/patch-ab
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/maradns/patches/patch-ab
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ab,v 1.3 2012/02/28 21:55:28 cheusov Exp $
|
|--- build/install.sh.orig 2011-08-05 11:59:45.000000000 +0000
|+++ build/install.sh
--------------------------
Patching file build/install.sh using Plan A...
Hunk #1 succeeded at 157.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/maradns/patches/patch-ac
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/maradns/patches/patch-ac
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ac,v 1.4 2012/02/28 21:55:28 cheusov Exp $
|
|--- configure.orig 2011-08-05 11:59:45.000000000 +0000
|+++ configure
--------------------------
Patching file configure using Plan A...
Hunk #1 succeeded at 128 (offset 3 lines).
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/maradns/patches/patch-ad
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/maradns/patches/patch-ad
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ad,v 1.5 2012/02/28 21:55:28 cheusov Exp $
|
|--- parse/ParseMaraRc.c.orig 2012-02-12 06:04:12.000000000 +0000
|+++ parse/ParseMaraRc.c
--------------------------
Patching file parse/ParseMaraRc.c using Plan A...
Hunk #1 succeeded at 1043 (offset 6 lines).
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/maradns/patches/patch-ae
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/maradns/patches/patch-ae
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ae,v 1.4 2012/02/28 21:55:28 cheusov Exp $
|
|--- server/Makefile.orig 2010-09-09 20:21:09.000000000 +0000
|+++ server/Makefile
--------------------------
Patching file server/Makefile using Plan A...
Hunk #1 succeeded at 24.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/maradns/patches/patch-am
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/maradns/patches/patch-am
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-am,v 1.3 2012/02/28 21:55:28 cheusov Exp $
|
|--- MaraDns.h.orig 2012-02-14 14:06:44.000000000 +0100
|+++ MaraDns.h 2012-02-14 14:09:52.000000000 +0100
--------------------------
Patching file MaraDns.h using Plan A...
Hunk #1 succeeded at 85 (offset -6 lines).
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/maradns/patches/patch-deadwood-3.2.14_src_DwMain.c
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/maradns/patches/patch-deadwood-3.2.14_src_DwMain.c
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-deadwood-3.2.14_src_DwMain.c,v 1.1 2019/10/06 12:52:20 nia Exp $
|
|Support PKG_SYSCONFDIR.
|
|--- deadwood-3.2.14/src/DwMain.c.orig 2019-01-20 16:22:47.000000000 +0000
|+++ deadwood-3.2.14/src/DwMain.c
--------------------------
Patching file deadwood-3.2.14/src/DwMain.c using Plan A...
Hunk #1 succeeded at 66.
done
===> Creating toolchain wrappers for maradns-2.0.17
===> Configuring for maradns-2.0.17
=> Substituting "sysconf" in parse/ParseMaraRc.c MaraDns.h deadwood-3.2.14/src/DwMain.c
=> Checking for portability problems in extracted files
ERROR: [check-portability] => Found test ... == ...:
ERROR: [check-portability] deadwood-3.2.14/update/3.2.11/3.2.10-to-3.2.11:84: if [ $? == 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: [check-portability] => Found test ... == ...:
ERROR: [check-portability] deadwood-3.2.14/update/3.2.08/3.2.07-to-3.2.08:97: if [ $? == 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: [check-portability] => Found test ... == ...:
ERROR: [check-portability] deadwood-3.2.14/update/3.2.05/3.2.04-to-3.2.05:108: if [ $? == 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: [check-portability] => Found test ... == ...:
ERROR: [check-portability] deadwood-3.2.14/update/3.2.12/3.2.11-to-3.2.12:91: if [ $? == 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: [check-portability] => Found test ... == ...:
ERROR: [check-portability] deadwood-3.2.14/update/3.2.06/3.2.05-to-3.2.06:106: if [ $? == 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: [check-portability] => Found test ... == ...:
ERROR: [check-portability] deadwood-3.2.14/update/3.2.04/3.2.03-to-3.2.04:146: if [ $? == 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: [check-portability] => Found test ... == ...:
ERROR: [check-portability] deadwood-3.2.14/update/3.2.03/3.2.02-to-3.2.03:140: if [ $? == 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: [check-portability] => Found test ... == ...:
ERROR: [check-portability] deadwood-3.2.14/update/3.2.09/3.2.08-to-3.2.09:92: if [ $? == 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: [check-portability] => Found test ... == ...:
ERROR: [check-portability] deadwood-3.2.14/update/3.2.10/3.2.09-to-3.2.10:99: if [ $? == 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: [check-portability] => Found test ... == ...:
ERROR: [check-portability] deadwood-3.2.14/update/3.2.14/3.2.13-to-3.2.14:84: if [ $? == 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: [check-portability] => Found test ... == ...:
ERROR: [check-portability] deadwood-3.2.14/update/3.2.07/3.2.06-to-3.2.07:80: if [ $? == 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: [check-portability] => Found test ... == ...:
ERROR: [check-portability] deadwood-3.2.14/update/3.2.13/3.2.12-to-3.2.13:84: if [ $? == 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/net/maradns
*** Error code 1
Stop.
bmake: stopped making "configure" in /data/jenkins/workspace/pkgsrc-upstream-trunk/net/maradns