+ 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/bash-completion-2.17.0/work.log + su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/bash-completion-2.17.0/work.log => Checksum BLAKE2s OK for bash-completion-2.17.0.tar.xz => Checksum SHA512 OK for bash-completion-2.17.0.tar.xz ===> Installing dependencies for bash-completion-2.17.0 => Tool dependency gmake>=3.81: found gmake-4.4.1 => Tool dependency cwrappers>=20150314: found cwrappers-20220403 => Tool dependency checkperms>=1.1: found checkperms-1.12 ===> Overriding tools for bash-completion-2.17.0 ===> Extracting for bash-completion-2.17.0 ===> Patching for bash-completion-2.17.0 => Applying pkgsrc patches for bash-completion-2.17.0 => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash-completion/patches/patch-Makefile.in => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash-completion/patches/patch-Makefile.in Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-Makefile.in,v 1.2 2026/01/06 20:20:55 adam Exp $ | |Don't install profile.d and bash_completion.d bits. | |--- Makefile.in.orig 2025-10-31 14:07:05.000000000 +0000 |+++ Makefile.in -------------------------- Patching file Makefile.in using Plan A... Hunk #1 succeeded at 329. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash-completion/patches/patch-bash__completion => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash-completion/patches/patch-bash__completion Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-bash__completion,v 1.4 2026/01/06 20:20:55 adam Exp $ | |Added pkgsrc completions | |--- bash_completion.orig 2025-10-31 14:03:32.000000000 +0000 |+++ bash_completion -------------------------- Patching file bash_completion using Plan A... Hunk #1 succeeded at 2611. done ===> Creating toolchain wrappers for bash-completion-2.17.0 ===> Configuring for bash-completion-2.17.0 => 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 checking for a BSD-compatible install... /opt/pkg/bin/bsdinstall -c -o pbulk -g pbulk checking whether sleep supports fractional seconds... yes checking filesystem timestamp resolution... 0.01 checking whether build environment is sane... yes checking for a race-free mkdir -p... mkdir -p checking for gawk... /usr/bin/nawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking xargs -n works... yes checking how to create a pax tar archive... gnutar checking whether ln -s works... yes checking for a sed that does not truncate output... /usr/bin/sed checking for pytest... no checking for pytest-3... no checking build system type... x86_64-sun-solaris2.11 checking host system type... x86_64-sun-solaris2.11 checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating completions/Makefile config.status: creating doc/Makefile config.status: creating helpers/Makefile config.status: creating test/Makefile config.status: creating test/fallback/Makefile config.status: creating test/fallback/completions/Makefile config.status: creating test/t/Makefile config.status: creating test/t/unit/Makefile