+ 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/uim-mozc-2.29.5268.102nb5/work.log
+ su pbulk -c '"$@"' make /usr/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent PYTHON_VERSION_REQD=312 WRKLOG=/tmp/bulklog/uim-mozc-2.29.5268.102nb5/work.log
=> Checksum BLAKE2s OK for abseil-abseil-cpp-c2435f8342c2d0ed8101cb43adfd605fdc52dca2.tar.gz
=> Checksum SHA512 OK for abseil-abseil-cpp-c2435f8342c2d0ed8101cb43adfd605fdc52dca2.tar.gz
=> Checksum BLAKE2s OK for chromium-gyp-9ecf45e37677743503342ee4c6a76eaee80e4a7f.tar.gz
=> Checksum SHA512 OK for chromium-gyp-9ecf45e37677743503342ee4c6a76eaee80e4a7f.tar.gz
=> Checksum BLAKE2s OK for e-kato-macuim-7beac7ba000e0459a4dc933f3873b521664d2665.tar.gz
=> Checksum SHA512 OK for e-kato-macuim-7beac7ba000e0459a4dc933f3873b521664d2665.tar.gz
=> Checksum BLAKE2s OK for google-breakpad-216cea7bca53fa441a3ee0d0f5fd339a3a894224.tar.gz
=> Checksum SHA512 OK for google-breakpad-216cea7bca53fa441a3ee0d0f5fd339a3a894224.tar.gz
=> Checksum BLAKE2s OK for google-googletest-58d77fa8070e8cec2dc1ed015d66b454c8d78850.tar.gz
=> Checksum SHA512 OK for google-googletest-58d77fa8070e8cec2dc1ed015d66b454c8d78850.tar.gz
=> Checksum BLAKE2s OK for hiroyuki-komatsu-japanese-usage-dictionary-e5b3425575734c323e1d947009dd74709437b684.tar.gz
=> Checksum SHA512 OK for hiroyuki-komatsu-japanese-usage-dictionary-e5b3425575734c323e1d947009dd74709437b684.tar.gz
=> Checksum BLAKE2s OK for microsoft-wil-fc5dbf55989fe20351c71d038a8d12de4b397a6d.tar.gz
=> Checksum SHA512 OK for microsoft-wil-fc5dbf55989fe20351c71d038a8d12de4b397a6d.tar.gz
=> Checksum BLAKE2s OK for mozc-2.29.5268.102.tar.gz
=> Checksum SHA512 OK for mozc-2.29.5268.102.tar.gz
=> Checksum BLAKE2s OK for protocolbuffers-protobuf-54a2e5caa9d1a0a714fb2aa99753a1444414292a.tar.gz
=> Checksum SHA512 OK for protocolbuffers-protobuf-54a2e5caa9d1a0a714fb2aa99753a1444414292a.tar.gz
=> Checksum BLAKE2s OK for uim-mozc_BUILD.bazel-2.29.5268.102
=> Checksum SHA512 OK for uim-mozc_BUILD.bazel-2.29.5268.102
=> Checksum BLAKE2s OK for uim-mozc_bazel.patch-2.29.5268.102
=> Checksum SHA512 OK for uim-mozc_bazel.patch-2.29.5268.102
=> Checksum BLAKE2s OK for uim-mozc_mozc.patch-2.29.5268.102
=> Checksum SHA512 OK for uim-mozc_mozc.patch-2.29.5268.102
===> Installing dependencies for uim-mozc-2.29.5268.102nb5
==========================================================================
The following variables will affect the build process of this package,
uim-mozc-2.29.5268.102nb5.  Their current value is shown below:

        * JPEG_DEFAULT = jpeg
        * PYTHON_VERSION_DEFAULT = 312
        * SSLBASE = /usr
        * SSLCERTBUNDLE (not defined)
        * SSLCERTS = /etc/openssl/certs
        * SSLDIR = /etc/openssl
        * SSLKEYS = /etc/openssl/private
        * TERMINFO_DEFAULT = terminfo

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

        * JPEGBASE (defined, but empty)
        * JPEG_TYPE = jpeg
        * PYPACKAGE = python312
        * TERMINFO_TYPE = terminfo

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 bazel-[0-9]*: found bazel-6.4.0
=> Tool dependency glib2-tools-[0-9]*: found glib2-tools-2.82.2
=> Tool dependency python312>=3.12: found python312-3.12.8nb1
=> Tool dependency pkgconf-[0-9]*: found pkgconf-2.3.0
=> Tool dependency cwrappers>=20150314: found cwrappers-20220403
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Build dependency clang>=18.1.8nb3: found clang-18.1.8nb3
=> Full dependency qt6-qtbase>=6.8.0nb3: found qt6-qtbase-6.8.0nb4
=> Full dependency uim>=1.8.0: found uim-1.8.9nb16
=> Build dependency libxml2>=2.6.2: found libxml2-2.12.9nb3
=> Build dependency llvm>=18.0.0: found llvm-18.1.8nb3
=> Build dependency x11-links>=1.36: found x11-links-1.36
=> Build dependency zstd>=1.3.6: found zstd-1.5.6
=> Full dependency brotli>=1.0.1: found brotli-1.1.0
=> Full dependency dbus>=0.91: found dbus-1.14.10
=> Full dependency fontconfig>=2.11.91: found fontconfig-2.15.0
=> Full dependency freetype2>=2.13.0: found freetype2-2.13.3
=> Full dependency glib2>=2.4.0: found glib2-2.82.2
=> Full dependency graphite2>=1.2: found graphite2-1.3.14nb3
=> Full dependency harfbuzz>=2.1.1: found harfbuzz-10.1.0
=> Full dependency icu>=3.4: found icu-76.1nb1
=> Full dependency jpeg>=8nb1: found jpeg-9f
=> Full dependency libXft>=2.1.10: found libXft-2.3.8nb1
=> Full dependency libffi>=1.20: found libffi-3.4.6
=> Full dependency libgcroots>=0.2.1: found libgcroots-0.2.3
=> Full dependency libproxy>=0.2.3: found libproxy-0.5.9nb3
=> Full dependency libxkbcommon>=0.4.0: found libxkbcommon-1.7.0nb5
=> Full dependency pcre2>=10.21: found pcre2-10.44
=> Full dependency png>=1.2.4: found png-1.6.44
=> Full dependency sqlite3>=3.0.8: found sqlite3-3.47.2
=> Full dependency xcb-util>=0.3.9: found xcb-util-0.4.1
=> Full dependency xcb-util-image>=0.3.9: found xcb-util-image-0.4.1
=> Full dependency xcb-util-keysyms>=0.3.9: found xcb-util-keysyms-0.4.1
=> Full dependency xcb-util-renderutil>=0.3.8nb1: found xcb-util-renderutil-0.3.10
=> Full dependency xcb-util-wm>=0.3.9: found xcb-util-wm-0.4.2nb1
===> Overriding tools for uim-mozc-2.29.5268.102nb5
===> Extracting for uim-mozc-2.29.5268.102nb5
===> Patching for uim-mozc-2.29.5268.102nb5
=> Applying pkgsrc patches for uim-mozc-2.29.5268.102nb5
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-WORKSPACE.bazel
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-WORKSPACE.bazel
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-WORKSPACE.bazel,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- WORKSPACE.bazel.orig	2023-10-26 12:00:50.000000000 +0000
|+++ WORKSPACE.bazel
--------------------------
Patching file WORKSPACE.bazel using Plan A...
Hunk #1 succeeded at 128.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-base_cpu__stats.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-base_cpu__stats.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-base_cpu__stats.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- base/cpu_stats.cc.orig	2023-10-26 12:00:50.000000000 +0000
|+++ base/cpu_stats.cc
--------------------------
Patching file base/cpu_stats.cc using Plan A...
Hunk #1 succeeded at 116.
Hunk #2 succeeded at 169.
Hunk #3 succeeded at 200.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-base_file_recursive.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-base_file_recursive.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-base_file_recursive.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- base/file/recursive.cc.orig	2023-10-26 12:00:50.000000000 +0000
|+++ base/file/recursive.cc
--------------------------
Patching file base/file/recursive.cc using Plan A...
Hunk #1 succeeded at 105.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-base_logging.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-base_logging.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-base_logging.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- base/logging.cc.orig	2023-10-26 12:00:50.000000000 +0000
|+++ base/logging.cc
--------------------------
Patching file base/logging.cc using Plan A...
Hunk #1 succeeded at 114.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-base_password__manager.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-base_password__manager.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-base_password__manager.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- base/password_manager.cc.orig	2023-10-26 12:00:50.000000000 +0000
|+++ base/password_manager.cc
--------------------------
Patching file base/password_manager.cc using Plan A...
Hunk #1 succeeded at 265.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-base_port.h
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-base_port.h
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-base_port.h,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- base/port.h.orig	2023-10-26 12:00:50.000000000 +0000
|+++ base/port.h
--------------------------
Patching file base/port.h using Plan A...
Hunk #1 succeeded at 45.
Hunk #2 succeeded at 69.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-base_process.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-base_process.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-base_process.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- base/process.cc.orig	2023-12-13 09:15:36.129469332 +0000
|+++ base/process.cc
--------------------------
Patching file base/process.cc using Plan A...
Hunk #1 succeeded at 98.
Hunk #2 succeeded at 387.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-base_system__util.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-base_system__util.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-base_system__util.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- base/system_util.cc.orig	2023-10-26 12:00:50.000000000 +0000
|+++ base/system_util.cc
--------------------------
Patching file base/system_util.cc using Plan A...
Hunk #1 succeeded at 278.
Hunk #2 succeeded at 429.
Hunk #3 succeeded at 471.
Hunk #4 succeeded at 661.
Hunk #5 succeeded at 834.
Hunk #6 succeeded at 876.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-base_system__util__test.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-base_system__util__test.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-base_system__util__test.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- base/system_util_test.cc.orig	2023-12-13 09:25:13.483600855 +0000
|+++ base/system_util_test.cc
--------------------------
Patching file base/system_util_test.cc using Plan A...
Hunk #1 succeeded at 59.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-bazel_pkg__config__repository.bzl
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-bazel_pkg__config__repository.bzl
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-bazel_pkg__config__repository.bzl,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- bazel/pkg_config_repository.bzl.orig	2023-12-14 08:51:15.941327119 +0000
|+++ bazel/pkg_config_repository.bzl
--------------------------
Patching file bazel/pkg_config_repository.bzl using Plan A...
Hunk #1 succeeded at 103.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-client_client.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-client_client.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-client_client.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- client/client.cc.orig	2023-12-13 09:23:05.795914176 +0000
|+++ client/client.cc
--------------------------
Patching file client/client.cc using Plan A...
Hunk #1 succeeded at 897.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-config.bzl
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-config.bzl
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-config.bzl,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- config.bzl.orig	2023-12-14 11:23:07.849816899 +0000
|+++ config.bzl
--------------------------
Patching file config.bzl using Plan A...
Hunk #1 succeeded at 35.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-config_stats__config__util__test.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-config_stats__config__util__test.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-config_stats__config__util__test.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- config/stats_config_util_test.cc.orig	2023-12-13 09:31:24.408148702 +0000
|+++ config/stats_config_util_test.cc
--------------------------
Patching file config/stats_config_util_test.cc using Plan A...
Hunk #1 succeeded at 688.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-gui_config__dialog_config__dialog.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-gui_config__dialog_config__dialog.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-gui_config__dialog_config__dialog.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- gui/config_dialog/config_dialog.cc.orig	2023-12-13 09:33:40.403986822 +0000
|+++ gui/config_dialog/config_dialog.cc
--------------------------
Patching file gui/config_dialog/config_dialog.cc using Plan A...
Hunk #1 succeeded at 105.
Hunk #2 succeeded at 115.
Hunk #3 succeeded at 281.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-gui_config__dialog_keybinding__editor.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-gui_config__dialog_keybinding__editor.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-gui_config__dialog_keybinding__editor.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- gui/config_dialog/keybinding_editor.cc.orig	2023-12-13 09:41:52.856716895 +0000
|+++ gui/config_dialog/keybinding_editor.cc
--------------------------
Patching file gui/config_dialog/keybinding_editor.cc using Plan A...
Hunk #1 succeeded at 111.
Hunk #2 succeeded at 361.
Hunk #3 succeeded at 460.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-gui_config__dialog_keymap__editor.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-gui_config__dialog_keymap__editor.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-gui_config__dialog_keymap__editor.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- gui/config_dialog/keymap_editor.cc.orig	2023-12-13 09:38:10.376387232 +0000
|+++ gui/config_dialog/keymap_editor.cc
--------------------------
Patching file gui/config_dialog/keymap_editor.cc using Plan A...
Hunk #1 succeeded at 441.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-gui_dictionary__tool_dictionary__tool.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-gui_dictionary__tool_dictionary__tool.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-gui_dictionary__tool_dictionary__tool.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- gui/dictionary_tool/dictionary_tool.cc.orig	2023-12-13 09:38:40.198993431 +0000
|+++ gui/dictionary_tool/dictionary_tool.cc
--------------------------
Patching file gui/dictionary_tool/dictionary_tool.cc using Plan A...
Hunk #1 succeeded at 369.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-gui_word__register__dialog_word__register__dialog.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-gui_word__register__dialog_word__register__dialog.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-gui_word__register__dialog_word__register__dialog.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- gui/word_register_dialog/word_register_dialog.cc.orig	2023-12-13 09:33:09.127301725 +0000
|+++ gui/word_register_dialog/word_register_dialog.cc
--------------------------
Patching file gui/word_register_dialog/word_register_dialog.cc using Plan A...
Hunk #1 succeeded at 100.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-ipc_ipc__path__manager.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-ipc_ipc__path__manager.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ipc_ipc__path__manager.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- ipc/ipc_path_manager.cc.orig	2023-12-13 09:35:34.871003763 +0000
|+++ ipc/ipc_path_manager.cc
--------------------------
Patching file ipc/ipc_path_manager.cc using Plan A...
Hunk #1 succeeded at 389.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-ipc_unix__ipc.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-ipc_unix__ipc.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ipc_unix__ipc.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- ipc/unix_ipc.cc.orig	2023-10-26 12:00:50.000000000 +0000
|+++ ipc/unix_ipc.cc
--------------------------
Patching file ipc/unix_ipc.cc using Plan A...
Hunk #1 succeeded at 28.
Hunk #2 succeeded at 119.
Hunk #3 succeeded at 134.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-session_session.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-session_session.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-session_session.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- session/session.cc.orig	2023-12-13 09:32:05.846503615 +0000
|+++ session/session.cc
--------------------------
Patching file session/session.cc using Plan A...
Hunk #1 succeeded at 241.
Hunk #2 succeeded at 973.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-session_session__handler__scenario__test.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-session_session__handler__scenario__test.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-session_session__handler__scenario__test.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- session/session_handler_scenario_test.cc.orig	2023-12-13 09:39:32.677437804 +0000
|+++ session/session_handler_scenario_test.cc
--------------------------
Patching file session/session_handler_scenario_test.cc using Plan A...
Hunk #1 succeeded at 172.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-session_session__test.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-session_session__test.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-session_session__test.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- session/session_test.cc.orig	2023-12-13 09:36:18.413874507 +0000
|+++ session/session_test.cc
--------------------------
Patching file session/session_test.cc using Plan A...
Hunk #1 succeeded at 2011.
Hunk #2 succeeded at 2200.
Hunk #3 succeeded at 2228.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-third__party_abseil-cpp_absl_base_internal_raw__logging.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-third__party_abseil-cpp_absl_base_internal_raw__logging.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-third__party_abseil-cpp_absl_base_internal_raw__logging.cc,v 1.1 2024/02/10 02:20:18 ryoon Exp $
|
|--- third_party/abseil-cpp/absl/base/internal/raw_logging.cc.orig	2023-12-13 09:40:20.988739236 +0000
|+++ third_party/abseil-cpp/absl/base/internal/raw_logging.cc
--------------------------
Patching file third_party/abseil-cpp/absl/base/internal/raw_logging.cc using Plan A...
Hunk #1 succeeded at 39.
done
=> Verifying /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-third__party_protobuf_toolchain_cc__toolchain__config.bzl
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-netbsd-trunk-x86_64/inputmethod/uim-mozc/patches/patch-third__party_protobuf_toolchain_cc__toolchain__config.bzl
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-third__party_protobuf_toolchain_cc__toolchain__config.bzl,v 1.1 2024/02/10 02:20:19 ryoon Exp $
|
|--- third_party/protobuf/toolchain/cc_toolchain_config.bzl.orig	2023-12-13 11:45:04.226274104 +0000
|+++ third_party/protobuf/toolchain/cc_toolchain_config.bzl
--------------------------
Patching file third_party/protobuf/toolchain/cc_toolchain_config.bzl using Plan A...
Hunk #1 succeeded at 206.
done
/bin/cp -rf /home/pbulk/build/inputmethod/uim-mozc/work/mozc-2.29.5268.102/src/uim/Mozc/uim /home/pbulk/build/inputmethod/uim-mozc/work/mozc-2.29.5268.102/src/unix/uim
===> Creating toolchain wrappers for uim-mozc-2.29.5268.102nb5
===> Configuring for uim-mozc-2.29.5268.102nb5
=> Setting PREFIX
/bin/mkdir -p /home/pbulk/build/inputmethod/uim-mozc/work/mozc-2.29.5268.102/src/dist
/bin/ln -sf /data/distfiles/uim-mozc_BUILD.bazel-2.29.5268.102 /home/pbulk/build/inputmethod/uim-mozc/work/mozc-2.29.5268.102/src/dist/uim-mozc_BUILD.bazel-2.29.5268.102
/bin/ln -sf /data/distfiles/uim-mozc_mozc.patch-2.29.5268.102 /home/pbulk/build/inputmethod/uim-mozc/work/mozc-2.29.5268.102/src/dist/uim-mozc_mozc.patch-2.29.5268.102
/bin/ln -sf /data/distfiles/uim-mozc_bazel.patch-2.29.5268.102 /home/pbulk/build/inputmethod/uim-mozc/work/mozc-2.29.5268.102/src/dist/uim-mozc_bazel.patch-2.29.5268.102
/bin/rm -rf /home/pbulk/build/inputmethod/uim-mozc/work/.cwrapper
cd /home/pbulk/build/inputmethod/uim-mozc/work/mozc-2.29.5268.102/src &&  /bin/ln -sf /data/distfiles/uim-mozc_BUILD.bazel-2.29.5268.102 uim-mozc_BUILD.bazel-2.29.5268.102
cd /home/pbulk/build/inputmethod/uim-mozc/work/mozc-2.29.5268.102/src &&  /bin/ln -sf /data/distfiles/uim-mozc_mozc.patch-2.29.5268.102 uim-mozc_mozc.patch-2.29.5268.102
cd /home/pbulk/build/inputmethod/uim-mozc/work/mozc-2.29.5268.102/src &&  /bin/ln -sf /data/distfiles/uim-mozc_bazel.patch-2.29.5268.102 uim-mozc_bazel.patch-2.29.5268.102
/bin/ln -sf /data/distfiles/uim-mozc_BUILD.bazel-2.29.5268.102  /home/pbulk/build/inputmethod/uim-mozc/work/mozc-2.29.5268.102/src/unix/uim/BUILD.bazel
cd /home/pbulk/build/inputmethod/uim-mozc/work/mozc-2.29.5268.102/src/.. &&  /usr/bin/patch < /home/pbulk/build/inputmethod/uim-mozc/work/mozc-2.29.5268.102/src/uim-mozc_mozc.patch-2.29.5268.102 &&  /usr/bin/patch -p1 < /home/pbulk/build/inputmethod/uim-mozc/work/mozc-2.29.5268.102/src/uim-mozc_bazel.patch-2.29.5268.102
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- src.orig/unix/uim/key_translator.h
|+++ src/unix/uim/key_translator.h
--------------------------
Patching file src/unix/uim/key_translator.h using Plan A...
Hunk #1 succeeded at 40.
Hunk #2 succeeded at 51.
Hunk #3 succeeded at 103.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- src.orig/unix/uim/key_translator.cc
|+++ src/unix/uim/key_translator.cc
--------------------------
Patching file src/unix/uim/key_translator.cc using Plan A...
Hunk #1 succeeded at 367.
done
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff --git a/src/WORKSPACE.bazel b/src/WORKSPACE.bazel
|index 1a422b31..6b64f117 100644
|--- a/src/WORKSPACE.bazel
|+++ b/src/WORKSPACE.bazel
--------------------------
Patching file src/WORKSPACE.bazel using Plan A...
Hunk #1 succeeded at 108 (offset 38 lines).
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff --git a/src/unix/BUILD.bazel b/src/unix/BUILD.bazel
|index b69ce0bb..c986e891 100644
|--- a/src/unix/BUILD.bazel
|+++ b/src/unix/BUILD.bazel
--------------------------
Patching file src/unix/BUILD.bazel using Plan A...
Hunk #1 succeeded at 115 (offset 2 lines).
done
=> Generating pkg-config file for builtin expat package.
=> Generating pkg-config files for builtin xz package.