+ case "${usergroup_phase}" in
+ local run_cmd
+ run_cmd=run_su
+ shift
+ run_su /usr/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent PYTHON_VERSION_REQD=310 WRKLOG=/tmp/bulklog/py310-mercurial-6.8.1/work.log
+ su pbulk -c '"$@"' make /usr/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent PYTHON_VERSION_REQD=310 WRKLOG=/tmp/bulklog/py310-mercurial-6.8.1/work.log
=> Bootstrap dependency digest>=20211023: found digest-20220214
=> Checksum BLAKE2s OK for mercurial-6.8.1.tar.gz
=> Checksum SHA512 OK for mercurial-6.8.1.tar.gz
===> Installing dependencies for py310-mercurial-6.8.1
==========================================================================
The following variables will affect the build process of this package,
py310-mercurial-6.8.1.  Their current value is shown below:

        * PYTHON_VERSION_DEFAULT = 312

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

        * PYPACKAGE = python310

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
`/usr/pkg/bin/bmake clean' after the changes.
==========================================================================
=> Tool dependency py310-setuptools-[0-9]*: found py310-setuptools-75.2.0
=> Tool dependency py310-wheel-[0-9]*: found py310-wheel-0.44.0
=> Tool dependency py310-build>=0: found py310-build-1.2.2.post1
=> Tool dependency py310-installer>=0.7.0nb1: found py310-installer-0.7.0nb1
=> Tool dependency mktools-[0-9]*: found mktools-20220614
=> Tool dependency nbpatch-[0-9]*: found nbpatch-20151107
=> Tool dependency cwrappers>=20150314: found cwrappers-20220403
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Full dependency python310>=3.10.13nb1: found python310-3.10.15
===> Overriding tools for py310-mercurial-6.8.1
===> Extracting for py310-mercurial-6.8.1
===> Patching for py310-mercurial-6.8.1
=> Applying pkgsrc patches for py310-mercurial-6.8.1
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/devel/py-mercurial/patches/patch-mercurial_bundle2.py
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/devel/py-mercurial/patches/patch-mercurial_bundle2.py
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-mercurial_bundle2.py,v 1.3 2024/06/20 23:56:45 joerg Exp $
|
|Upstream f28c52a9f7b4
|
|--- mercurial/bundle2.py.orig	2024-03-29 20:37:05.000000000 +0000
|+++ mercurial/bundle2.py
--------------------------
Patching file mercurial/bundle2.py using Plan A...
Hunk #1 succeeded at 1788 (offset 1 line).
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/devel/py-mercurial/patches/patch-mercurial_exchange.py
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/devel/py-mercurial/patches/patch-mercurial_exchange.py
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-mercurial_exchange.py,v 1.1 2024/06/20 23:56:45 joerg Exp $
|
|Upstream f28c52a9f7b4
|https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/863
|
|--- mercurial/exchange.py.orig	2024-03-29 20:37:05.000000000 +0000
|+++ mercurial/exchange.py
--------------------------
Patching file mercurial/exchange.py using Plan A...
Hunk #1 succeeded at 703 (offset 35 lines).
Hunk #2 succeeded at 2568 (offset 26 lines).
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/devel/py-mercurial/patches/patch-mercurial_obsolete.py
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/devel/py-mercurial/patches/patch-mercurial_obsolete.py
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-mercurial_obsolete.py,v 1.2 2024/08/08 08:11:11 wiz Exp $
|
|Upstream f28c52a9f7b4
|
|--- mercurial/obsolete.py.orig	2024-08-01 14:34:33.000000000 +0000
|+++ mercurial/obsolete.py
--------------------------
Patching file mercurial/obsolete.py using Plan A...
Hunk #1 succeeded at 771.
Hunk #2 succeeded at 783.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/devel/py-mercurial/patches/patch-mercurial_obsutil.py
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/devel/py-mercurial/patches/patch-mercurial_obsutil.py
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-mercurial_obsutil.py,v 1.1 2024/06/20 23:56:45 joerg Exp $
|
|Upstream f28c52a9f7b4
|
|--- mercurial/obsutil.py.orig	2024-03-29 20:37:05.000000000 +0000
|+++ mercurial/obsutil.py
--------------------------
Patching file mercurial/obsutil.py using Plan A...
Hunk #1 succeeded at 108.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/devel/py-mercurial/patches/patch-setup.py
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/devel/py-mercurial/patches/patch-setup.py
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-setup.py,v 1.2 2023/10/02 20:37:22 triaxx Exp $
|
|Skip existence check for Python.h so this can be cross-compiled.
|
|The pkgsrc toolchain wrapper will interpose a sysroot to resolve the
|.h file reference.
|
|--- setup.py.orig	2023-05-04 12:17:18.000000000 +0000
|+++ setup.py
--------------------------
Patching file setup.py using Plan A...
Hunk #1 succeeded at 675 (offset 17 lines).
done
===> Creating toolchain wrappers for py310-mercurial-6.8.1
===> Configuring for py310-mercurial-6.8.1