+ case "${usergroup_phase}" in + local run_cmd + run_cmd=run_su + shift + run_su /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent PYTHON_VERSION_REQD=311 WRKLOG=/tmp/bulklog/py-vmailmgr-0.97.0.20150901/work.log + su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent PYTHON_VERSION_REQD=311 WRKLOG=/tmp/bulklog/py-vmailmgr-0.97.0.20150901/work.log => Bootstrap dependency digest>=20211023: found digest-20220214 => Checksum BLAKE2s OK for vmailmgr-526d53c1d0e604ec29ada61b79485ceeb8b978cd-526d53c1d0e604ec29ada61b79485ceeb8b978cd.tar.gz => Checksum SHA512 OK for vmailmgr-526d53c1d0e604ec29ada61b79485ceeb8b978cd-526d53c1d0e604ec29ada61b79485ceeb8b978cd.tar.gz ===> Installing dependencies for py-vmailmgr-0.97.0.20150901 ========================================================================== The following variables will affect the build process of this package, py-vmailmgr-0.97.0.20150901. Their current value is shown below: * PKG_SYSCONFBASE = /etc/opt/pkg * PYTHON_VERSION_DEFAULT = 311 * QMAILDIR = /var/opt/pkg/qmail * VARBASE = /var/opt/pkg Based on these variables, the following variables have been set: * PYPACKAGE = python311 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 `/opt/pkg/bin/bmake clean' after the changes. ========================================================================== => Tool dependency mktools-[0-9]*: found mktools-20220614 => Tool dependency automake>=1.9: found automake-1.16.5nb3 => Tool dependency autoconf>=2.58: found autoconf-2.72 => Tool dependency gmake>=3.81: found gmake-4.4.1 => Tool dependency perl>=5.0: found perl-5.38.2 => Tool dependency cwrappers>=20150314: found cwrappers-20220403 => Tool dependency checkperms>=1.1: found checkperms-1.12 => Full dependency python311>=3.11.0: found python311-3.11.9 ===> Overriding tools for py-vmailmgr-0.97.0.20150901 ===> Extracting for py-vmailmgr-0.97.0.20150901 cd /home/pbulk/build/mail/py-vmailmgr/work/vmailmgr-526d53c1d0e604ec29ada61b79485ceeb8b978cd; /usr/bin/mkdir -p python-tempname; /usr/bin/mv python python-tempname/vmailmgr; /usr/bin/mv python-tempname python cd /home/pbulk/build/mail/py-vmailmgr/work/vmailmgr-526d53c1d0e604ec29ada61b79485ceeb8b978cd/lib/config && /usr/bin/bash build-config.sh _autoresponse_dir.cc was changed, REPLACING. _autoresponse_file.cc was changed, REPLACING. _bulletin_dir.cc was changed, REPLACING. _default_expiry.cc was changed, REPLACING. _default_maildir.cc was changed, REPLACING. _default_msgcount.cc was changed, REPLACING. _default_msgsize.cc was changed, REPLACING. _default_hardquota.cc was changed, REPLACING. _default_softquota.cc was changed, REPLACING. _default_username.cc was changed, REPLACING. _error_maildir.cc was changed, REPLACING. _global_bulletin_dir.cc was changed, REPLACING. _maildir_arg_str.cc was changed, REPLACING. _password_file.cc was changed, REPLACING. _postmaster_aliases.cc was changed, REPLACING. _postmaster_email.cc was changed, REPLACING. _qmail_root.cc was changed, REPLACING. _separators.cc was changed, REPLACING. _socket_file.cc was changed, REPLACING. _user_dir.cc was changed, REPLACING. _user_dir_bits.cc was changed, REPLACING. _user_dir_slices.cc was changed, REPLACING. showvconfig.cc was changed, REPLACING. configrc.h was changed, REPLACING. Makefile.am is unchanged. ===> Patching for py-vmailmgr-0.97.0.20150901 => Applying pkgsrc patches for py-vmailmgr-0.97.0.20150901 => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-Makefile.am => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-Makefile.am Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-Makefile.am,v 1.2 2024/02/27 19:13:43 schmonz Exp $ | |Build cgi, php, and python as their own packages. | |--- Makefile.am.orig 2015-09-01 16:03:21.000000000 +0000 |+++ Makefile.am -------------------------- Patching file Makefile.am using Plan A... Hunk #1 succeeded at 1. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-acinclude.m4 => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-acinclude.m4 Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-acinclude.m4,v 1.1 2024/02/25 12:09:21 schmonz Exp $ | |Fix autoreconf warnings. | |--- acinclude.m4.orig 2024-02-21 15:45:31.387684310 +0000 |+++ acinclude.m4 -------------------------- Patching file acinclude.m4 using Plan A... Hunk #1 succeeded at 1. Hunk #2 succeeded at 10. Hunk #3 succeeded at 19. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-authenticate_Makefile.am => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-authenticate_Makefile.am Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-authenticate_Makefile.am,v 1.1 2024/02/25 12:09:21 schmonz Exp $ | |Build Courier IMAP authenticator as a separate package. | |Avoid "warning: ignoring prerequisites on suffix rule definition" | |--- authenticate/Makefile.am.orig 2015-09-01 16:03:21.000000000 +0000 |+++ authenticate/Makefile.am -------------------------- Patching file authenticate/Makefile.am using Plan A... Hunk #1 succeeded at 1. Hunk #2 succeeded at 19. Hunk #3 succeeded at 29. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-commands_Makefile.am => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-commands_Makefile.am Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-commands_Makefile.am,v 1.1 2024/02/25 12:09:21 schmonz Exp $ | |Fix typo in list of .pod files, spotted on Ubuntu via "install: will not |overwrite just-created vadduser.1" | |Avoid "warning: ignoring prerequisites on suffix rule definition" | |--- commands/Makefile.am.orig 2015-09-01 16:03:21.000000000 +0000 |+++ commands/Makefile.am -------------------------- Patching file commands/Makefile.am using Plan A... Hunk #1 succeeded at 4. Hunk #2 succeeded at 23. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-commands_vadduser.cc => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-commands_vadduser.cc Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-commands_vadduser.cc,v 1.1 2024/02/25 12:09:22 schmonz Exp $ | |Avoid dangling else. | |--- commands/vadduser.cc.orig 2024-02-22 18:36:02.894040336 +0000 |+++ commands/vadduser.cc -------------------------- Patching file commands/vadduser.cc using Plan A... Hunk #1 succeeded at 190. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-commands_vdeliver.cc => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-commands_vdeliver.cc Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-commands_vdeliver.cc,v 1.2 2024/02/25 12:44:44 schmonz Exp $ | |Patches from FreeBSD ports and GitHub PR #1. | |--- commands/vdeliver.cc.orig 2015-09-01 16:03:21.000000000 +0000 |+++ commands/vdeliver.cc -------------------------- Patching file commands/vdeliver.cc using Plan A... Hunk #1 succeeded at 176. Hunk #2 succeeded at 262. Hunk #3 succeeded at 335. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-configure.ac => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-configure.ac Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-configure.ac,v 1.2 2024/02/27 19:13:43 schmonz Exp $ | |Don't build courier-imap, cgi, php, or python by default. |Remove unused text-browser checks. | |--- configure.ac.orig 2015-09-01 16:03:21.000000000 +0000 |+++ configure.ac -------------------------- Patching file configure.ac using Plan A... Hunk #1 succeeded at 1. Hunk #2 succeeded at 55. Hunk #3 succeeded at 127. Hunk #4 succeeded at 148. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-daemon_Makefile.am => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-daemon_Makefile.am Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-daemon_Makefile.am,v 1.1 2024/02/25 12:09:22 schmonz Exp $ | |Avoid "warning: ignoring prerequisites on suffix rule definition" | |--- daemon/Makefile.am.orig 2015-09-01 16:03:21.000000000 +0000 |+++ daemon/Makefile.am -------------------------- Patching file daemon/Makefile.am using Plan A... Hunk #1 succeeded at 15. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-daemon_main.cc => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-daemon_main.cc Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-daemon_main.cc,v 1.1 2024/02/25 12:09:22 schmonz Exp $ | |Remove unused function. | |--- daemon/main.cc.orig 2024-02-22 18:32:57.270441623 +0000 |+++ daemon/main.cc -------------------------- Patching file daemon/main.cc using Plan A... Hunk #1 succeeded at 61. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-doc_HOWTO.texi => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-doc_HOWTO.texi Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-doc_HOWTO.texi,v 1.1 2024/02/25 12:09:22 schmonz Exp $ | |Avoid encoding error for umlaut-laden character. | |--- doc/HOWTO.texi.orig 2024-02-21 20:15:30.534197736 +0000 |+++ doc/HOWTO.texi -------------------------- Patching file doc/HOWTO.texi using Plan A... Hunk #1 succeeded at 1. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-doc_Makefile.am => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-doc_Makefile.am Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-doc_Makefile.am,v 1.2 2024/02/28 15:42:05 schmonz Exp $ | |Avoid "warning: ignoring prerequisites on suffix rule definition" | |Avoid building PDFs that aren't installed anyway. | |--- doc/Makefile.am.orig 2015-09-01 16:03:21.000000000 +0000 |+++ doc/Makefile.am -------------------------- Patching file doc/Makefile.am using Plan A... Hunk #1 succeeded at 7. Hunk #2 succeeded at 30. Hunk #3 succeeded at 44. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_cli++_main.cc => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_cli++_main.cc Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-lib_cli++_main.cc,v 1.1 2024/02/25 12:09:22 schmonz Exp $ | |Remove unused function. | |--- lib/cli++/main.cc.orig 2024-02-22 18:32:27.213171111 +0000 |+++ lib/cli++/main.cc -------------------------- Patching file lib/cli++/main.cc using Plan A... Hunk #1 succeeded at 49. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_fdbuf_fdbuf.h => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_fdbuf_fdbuf.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-lib_fdbuf_fdbuf.h,v 1.1 2024/02/25 12:09:22 schmonz Exp $ | |Fix warnings. | |--- lib/fdbuf/fdbuf.h.orig 2024-02-20 03:19:48.448432259 +0000 |+++ lib/fdbuf/fdbuf.h -------------------------- Patching file lib/fdbuf/fdbuf.h using Plan A... Hunk #1 succeeded at 20 (offset -1 lines). done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_mergelib.sh => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_mergelib.sh Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-lib_mergelib.sh,v 1.1 2024/02/25 12:09:22 schmonz Exp $ | |Fix macOS "ld: multiple SYMDEF member files found in an archive". | |--- lib/mergelib.sh.orig 2015-09-01 16:03:21.000000000 +0000 |+++ lib/mergelib.sh -------------------------- Patching file lib/mergelib.sh using Plan A... Hunk #1 succeeded at 10. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_misc_crc32.cc => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_misc_crc32.cc Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-lib_misc_crc32.cc,v 1.1 2024/02/25 12:09:22 schmonz Exp $ | |Remove unsupported keyword. | |--- lib/misc/crc32.cc.orig 2024-02-22 18:31:14.384171118 +0000 |+++ lib/misc/crc32.cc -------------------------- Patching file lib/misc/crc32.cc using Plan A... Hunk #1 succeeded at 132. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_misc_md5-crypt.c => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_misc_md5-crypt.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-lib_misc_md5-crypt.c,v 1.1 2024/02/25 12:09:22 schmonz Exp $ | |Provide modern prototypes. | |--- lib/misc/md5-crypt.c.orig 2024-02-22 18:33:20.895490263 +0000 |+++ lib/misc/md5-crypt.c -------------------------- Patching file lib/misc/md5-crypt.c using Plan A... Hunk #1 succeeded at 53. Hunk #2 succeeded at 209. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_misc_md5.c => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_misc_md5.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-lib_misc_md5.c,v 1.1 2024/02/25 12:09:22 schmonz Exp $ | |Provide modern prototypes. | |--- lib/misc/md5.c.orig 2015-09-01 16:03:21.000000000 +0000 |+++ lib/misc/md5.c -------------------------- Patching file lib/misc/md5.c using Plan A... Hunk #1 succeeded at 69. Hunk #2 succeeded at 86. Hunk #3 succeeded at 102. Hunk #4 succeeded at 131. Hunk #5 succeeded at 186. Hunk #6 succeeded at 202. Hunk #7 succeeded at 257. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_misc_response.h => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_misc_response.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-lib_misc_response.h,v 1.1 2024/02/25 12:09:22 schmonz Exp $ | |Avoid operator precedence warning. | |--- lib/misc/response.h.orig 2024-02-22 18:26:09.457292318 +0000 |+++ lib/misc/response.h -------------------------- Patching file lib/misc/response.h using Plan A... Hunk #1 succeeded at 19. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_vpwtable_cdb__write.cc => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_vpwtable_cdb__write.cc Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-lib_vpwtable_cdb__write.cc,v 1.1 2024/02/25 12:09:22 schmonz Exp $ | |Fix warnings. | |--- lib/vpwtable/cdb_write.cc.orig 2024-02-20 03:14:13.278367363 +0000 |+++ lib/vpwtable/cdb_write.cc -------------------------- Patching file lib/vpwtable/cdb_write.cc using Plan A... Hunk #1 succeeded at 23. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_vpwtable_gdbm__del.cc => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_vpwtable_gdbm__del.cc Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-lib_vpwtable_gdbm__del.cc,v 1.1 2024/02/25 12:09:22 schmonz Exp $ | |Patch from FreeBSD ports. | |--- lib/vpwtable/gdbm_del.cc.orig 2024-02-20 03:20:54.978827529 +0000 |+++ lib/vpwtable/gdbm_del.cc -------------------------- Patching file lib/vpwtable/gdbm_del.cc using Plan A... Hunk #1 succeeded at 23. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_vpwtable_gdbm__exists.cc => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_vpwtable_gdbm__exists.cc Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-lib_vpwtable_gdbm__exists.cc,v 1.1 2024/02/25 12:09:22 schmonz Exp $ | |Patch from FreeBSD ports. | |--- lib/vpwtable/gdbm_exists.cc.orig 2024-02-20 03:21:16.821104286 +0000 |+++ lib/vpwtable/gdbm_exists.cc -------------------------- Patching file lib/vpwtable/gdbm_exists.cc using Plan A... Hunk #1 succeeded at 23. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_vpwtable_gdbm__getbyname.cc => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_vpwtable_gdbm__getbyname.cc Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-lib_vpwtable_gdbm__getbyname.cc,v 1.1 2024/02/25 12:09:22 schmonz Exp $ | |Patch from FreeBSD ports. | |--- lib/vpwtable/gdbm_getbyname.cc.orig 2024-02-20 03:21:36.626537464 +0000 |+++ lib/vpwtable/gdbm_getbyname.cc -------------------------- Patching file lib/vpwtable/gdbm_getbyname.cc using Plan A... Hunk #1 succeeded at 24. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_vpwtable_gdbm__put.cc => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_vpwtable_gdbm__put.cc Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-lib_vpwtable_gdbm__put.cc,v 1.1 2024/02/25 12:09:22 schmonz Exp $ | |Patch from FreeBSD ports. | |--- lib/vpwtable/gdbm_put.cc.orig 2024-02-20 03:21:52.065572565 +0000 |+++ lib/vpwtable/gdbm_put.cc -------------------------- Patching file lib/vpwtable/gdbm_put.cc using Plan A... Hunk #1 succeeded at 25. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_vpwtable_gdbm__write.cc => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-lib_vpwtable_gdbm__write.cc Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-lib_vpwtable_gdbm__write.cc,v 1.1 2024/02/25 12:09:22 schmonz Exp $ | |Patch from FreeBSD ports. | |--- lib/vpwtable/gdbm_write.cc.orig 2015-09-01 16:03:21.000000000 +0000 |+++ lib/vpwtable/gdbm_write.cc -------------------------- Patching file lib/vpwtable/gdbm_write.cc using Plan A... Hunk #1 succeeded at 16. Hunk #2 succeeded at 60. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-python_vmailmgr_Makefile.am => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-python_vmailmgr_Makefile.am Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-python_vmailmgr_Makefile.am,v 1.1 2024/02/27 19:13:43 schmonz Exp $ | |Use pkgsrc-selected python. | |--- python/vmailmgr/Makefile.am.orig 2015-09-01 16:03:21.000000000 +0000 |+++ python/vmailmgr/Makefile.am -------------------------- Patching file python/vmailmgr/Makefile.am using Plan A... Hunk #1 succeeded at 26. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-python_vmailmgr_____init____.py => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-python_vmailmgr_____init____.py Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-python_vmailmgr_____init____.py,v 1.1 2024/02/27 19:13:43 schmonz Exp $ | |Port to Python 3, maintaining 2.7 compatibility. | |--- python/vmailmgr/__init__.py.orig 2015-09-01 16:03:21.000000000 +0000 |+++ python/vmailmgr/__init__.py -------------------------- Patching file python/vmailmgr/__init__.py using Plan A... Hunk #1 succeeded at 1. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-python_vmailmgr_commands.py => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-python_vmailmgr_commands.py Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-python_vmailmgr_commands.py,v 1.1 2024/02/27 19:13:44 schmonz Exp $ | |Port to Python 3, maintaining 2.7 compatibility. | |--- python/vmailmgr/commands.py.orig 2015-09-01 16:03:21.000000000 +0000 |+++ python/vmailmgr/commands.py -------------------------- Patching file python/vmailmgr/commands.py using Plan A... Hunk #1 succeeded at 14. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-python_vmailmgr_config.py => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-python_vmailmgr_config.py Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-python_vmailmgr_config.py,v 1.1 2024/02/27 19:13:44 schmonz Exp $ | |Port to Python 3, maintaining 2.7 compatibility. | |--- python/vmailmgr/config.py.orig 2015-09-01 16:03:21.000000000 +0000 |+++ python/vmailmgr/config.py -------------------------- Patching file python/vmailmgr/config.py using Plan A... Hunk #1 succeeded at 15. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-python_vmailmgr_daemon.py => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-python_vmailmgr_daemon.py Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-python_vmailmgr_daemon.py,v 1.1 2024/02/27 19:13:44 schmonz Exp $ | |Port to Python 3, maintaining 2.7 compatibility. | |--- python/vmailmgr/daemon.py.orig 2015-09-01 16:03:21.000000000 +0000 |+++ python/vmailmgr/daemon.py -------------------------- Patching file python/vmailmgr/daemon.py using Plan A... Hunk #1 succeeded at 14. Hunk #2 succeeded at 47. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-python_vmailmgr_types.py => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr/../../mail/vmailmgr-base/patches/patch-python_vmailmgr_types.py Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-python_vmailmgr_types.py,v 1.1 2024/02/27 19:13:44 schmonz Exp $ | |Port to Python 3, maintaining 2.7 compatibility. | |--- python/vmailmgr/types.py.orig 2015-09-01 16:03:21.000000000 +0000 |+++ python/vmailmgr/types.py -------------------------- Patching file python/vmailmgr/types.py using Plan A... Hunk #1 succeeded at 14. Hunk #2 succeeded at 83. Hunk #3 succeeded at 123. done ===> Creating toolchain wrappers for py-vmailmgr-0.97.0.20150901 ERROR: gettext-lib>=0.22 is not installed; can't buildlink files. *** Error code 1 Stop. bmake[1]: stopped in /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr *** Error code 1 Stop. bmake: stopped in /data/jenkins/workspace/pkgsrc-upstream-trunk/mail/py-vmailmgr