+ 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/u9fs-2.0.3/work.log
+ su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/u9fs-2.0.3/work.log
WARNING: [license.mk] Every package should define a LICENSE.
=> Checksum BLAKE2s OK for u9fs-2.0.3.tar.gz
=> Checksum SHA512 OK for u9fs-2.0.3.tar.gz
===> Installing dependencies for u9fs-2.0.3
=> Tool dependency cwrappers>=20150314: found cwrappers-20220403
=> Tool dependency checkperms>=1.1: found checkperms-1.12
===> Overriding tools for u9fs-2.0.3
===> Extracting for u9fs-2.0.3
===> Patching for u9fs-2.0.3
=> Applying pkgsrc patches for u9fs-2.0.3
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/filesystems/u9fs/patches/patch-aa
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/filesystems/u9fs/patches/patch-aa
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-aa,v 1.4 2014/02/09 17:23:54 wiedi Exp $
|
|--- makefile.orig	2005-06-06 19:26:52.000000000 +0000
|+++ makefile
--------------------------
Patching file makefile using Plan A...
Hunk #1 succeeded at 17.
Hunk #2 succeeded at 49.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/filesystems/u9fs/patches/patch-ab
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/filesystems/u9fs/patches/patch-ab
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ab,v 1.3 2014/02/09 17:23:54 wiedi Exp $
|
|--- u9fs.c.orig	2005-06-06 19:26:52.000000000 +0000
|+++ u9fs.c
--------------------------
Patching file u9fs.c using Plan A...
Hunk #1 succeeded at 28.
Hunk #2 succeeded at 762.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/filesystems/u9fs/patches/patch-ac
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/filesystems/u9fs/patches/patch-ac
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ac,v 1.1.1.1 2007/04/24 19:06:03 agc Exp $
|
|--- plan9.h	2007/04/23 22:30:40	1.1
|+++ plan9.h	2007/04/23 22:06:13
--------------------------
Patching file plan9.h using Plan A...
Hunk #1 succeeded at 1.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/filesystems/u9fs/patches/patch-ad
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/filesystems/u9fs/patches/patch-ad
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ad,v 1.1.1.1 2007/04/24 19:06:03 agc Exp $
|
|--- oldfcall.c	2007/04/24 07:25:17	1.1
|+++ oldfcall.c	2007/04/24 07:26:09
--------------------------
Patching file oldfcall.c using Plan A...
Hunk #1 succeeded at 2.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/filesystems/u9fs/patches/patch-ae
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/filesystems/u9fs/patches/patch-ae
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ae,v 1.1.1.1 2007/04/24 19:06:03 agc Exp $
|
|--- safecpy.c	2007/04/24 07:25:17	1.1
|+++ safecpy.c	2007/04/24 07:26:57
--------------------------
Patching file safecpy.c using Plan A...
Hunk #1 succeeded at 1.
done
===> Creating toolchain wrappers for u9fs-2.0.3
===> Configuring for u9fs-2.0.3
=> Checking for portability problems in extracted files