+ 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=312 WRKLOG=/tmp/bulklog/breezy-3.3.8/work.log + su pbulk -c '"$@"' make /usr/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent PYTHON_VERSION_REQD=312 WRKLOG=/tmp/bulklog/breezy-3.3.8/work.log => Bootstrap dependency digest>=20211023: found digest-20220214 => Checksum BLAKE2s OK for breezy-3.3.8.tar.gz => Checksum SHA512 OK for breezy-3.3.8.tar.gz ===> Installing dependencies for breezy-3.3.8 ========================================================================== The following variables will affect the build process of this package, breezy-3.3.8. Their current value is shown below: * PYTHON_VERSION_DEFAULT = 312 Based on these variables, the following variables have been set: * PYPACKAGE = python312 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 py312-setuptools>=0: found py312-setuptools-75.1.0 => Tool dependency py312-wheel>=0: found py312-wheel-0.44.0 => Tool dependency py312-cython>=0.29: found py312-cython-3.0.11 => Tool dependency py312-build>=0: found py312-build-1.2.2.post1 => Tool dependency py312-installer>=0.7.0nb1: found py312-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 py312-configobj>0: found py312-configobj-5.0.9 => Full dependency py312-dulwich>=0.20.23: found py312-dulwich-0.22.1 => Full dependency py312-fastbencode>=0.0.9: found py312-fastbencode-0.3.1 => Full dependency py312-fastimport>0: found py312-fastimport-0.9.14nb2 => Full dependency py312-merge3>=0.0.14: found py312-merge3-0.0.15 => Full dependency py312-patiencediff>=0.2.2: found py312-patiencediff-0.2.15 => Full dependency py312-yaml>=0: found py312-yaml-6.0.2 => Full dependency zlib>=1.2.3: found zlib-1.3.1 => Full dependency python312>=3.12: found python312-3.12.7 ===> Overriding tools for breezy-3.3.8 ===> Extracting for breezy-3.3.8 => Fix python path for test case. echo 'fn main() { println!("cargo:rustc-link-arg-bins=-Wl,-R,/usr/pkg/lib"); } ' > /home/pbulk/build/devel/breezy/work/breezy-3.3.8/build.rs ===> Patching for breezy-3.3.8 => Applying pkgsrc patches for breezy-3.3.8 => Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/devel/breezy/patches/patch-breezy_bzr_rio.py => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/devel/breezy/patches/patch-breezy_bzr_rio.py Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-breezy_bzr_rio.py,v 1.1 2024/10/05 13:34:19 rhialto Exp $ | |Do NOT try to use Rust if a perfectly good Python implementation is available. | |--- breezy/bzr/rio.py.orig 2024-10-03 15:34:05.073511063 +0000 |+++ breezy/bzr/rio.py -------------------------- Patching file breezy/bzr/rio.py using Plan A... Hunk #1 succeeded at 341. done => Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/devel/breezy/patches/patch-breezy_tests_test__server.py => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/devel/breezy/patches/patch-breezy_tests_test__server.py Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-breezy_tests_test__server.py,v 1.1 2019/10/27 13:05:46 rhialto Exp $ | |Stub out call to shutdown() since it mysteriously fails with |an OSError exception with EINVAL. |See https://bugs.launchpad.net/brz/+bug/1849971 | |--- breezy/tests/test_server.py.orig 2019-06-16 22:18:58.000000000 +0000 |+++ breezy/tests/test_server.py -------------------------- Patching file breezy/tests/test_server.py using Plan A... Hunk #1 succeeded at 376 (offset -5 lines). done => Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/devel/breezy/patches/patch-setup.py => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/devel/breezy/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 2024/10/05 13:34:19 rhialto Exp $ | |- Surely this should work in some other way, but without this, | "setup.py build" errors out with "error: invalid command 'build_mo'". | | It turns out that the created .po files aren't even installed, so | why bother building them... but if you want to, the code is there, | commented out. | |- Do NOT build any extensions in Rust, especially not if their functionality | is totally trivial and there is an implementation in Python anyway. | Also we have set CIBUILDWHEEL=1 in the environment. | | At some point we likely will no longer be able to avoid Rust. In the mean | time, commented-out fragments in the Makefile remain for the case where | one wants to try using Rust. | |--- setup.py.orig 2024-06-27 14:42:24.000000000 +0000 |+++ setup.py -------------------------- Patching file setup.py using Plan A... Hunk #1 succeeded at 79. Hunk #2 succeeded at 226. done ===> Creating toolchain wrappers for breezy-3.3.8 ===> Configuring for breezy-3.3.8 => Replacing python interpreter in breezy/git/bzr-receive-pack breezy/git/bzr-upload-pack breezy/git/git-remote-bzr breezy/git/git_remote_helper.py breezy/plugins/bash_completion/bashcomp.py breezy/tests/ssl_certs/create_ssls.py breezy/version_info_formats/format_python.py brz contrib/brz_access. INFO: [replace-interpreter] Nothing changed in breezy/git/git_remote_helper.py. INFO: [replace-interpreter] Nothing changed in breezy/plugins/bash_completion/bashcomp.py. INFO: [replace-interpreter] Nothing changed in breezy/version_info_formats/format_python.py. WARNING: [replace-interpreter] Skipping non-existent file "brz".