=> "/opt/local/bin/bmake" ["-C", "/data/jenkins/workspace/pkgsrc-trunk-x86_64/sysutils/dirvish", "configure", "BATCH=1", "DEPENDS_TARGET=/nonexistent"] WARNING: [license.mk] Every package should define a LICENSE. => Checksum BLAKE2s OK for dirvish-20120107/dirvish-1.2.1.tgz => Checksum SHA512 OK for dirvish-20120107/dirvish-1.2.1.tgz ===> Installing dependencies for dirvish-1.2.1nb10 => Tool dependency cwrappers>=20150314: found cwrappers-20220403 => Tool dependency checkperms>=1.1: found checkperms-1.12 => Build dependency gcc13>=13.4.0: found gcc13-13.4.0 => Full dependency rsync>=2.6.0: found rsync-3.5.0 => Full dependency p5-Time-modules>=2003.0: found p5-Time-modules-2013.0912nb12 => Full dependency p5-Time-Period>=1.0: found p5-Time-Period-1.20nb20 => Full dependency gcc13-libs>=13.4.0: found gcc13-libs-13.4.0 ===> Overriding tools for dirvish-1.2.1nb10 ===> Extracting for dirvish-1.2.1nb10 ===> Patching for dirvish-1.2.1nb10 => Applying pkgsrc patches for dirvish-1.2.1nb10 => Verifying /data/jenkins/workspace/pkgsrc-trunk-x86_64/sysutils/dirvish/patches/patch-dirvish-expire.pl => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-trunk-x86_64/sysutils/dirvish/patches/patch-dirvish-expire.pl Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-dirvish-expire.pl,v 1.1 2024/06/27 17:40:34 abs Exp $ | |Taken from debian - Paul Slootman |Subject: Fix for future reserved word warning | |--- dirvish-expire.pl.orig 2024-06-20 09:09:32.049428903 +0000 |+++ dirvish-expire.pl -------------------------- Patching file dirvish-expire.pl using Plan A... Hunk #1 succeeded at 140. done => Verifying /data/jenkins/workspace/pkgsrc-trunk-x86_64/sysutils/dirvish/patches/patch-dirvish.conf.5 => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-trunk-x86_64/sysutils/dirvish/patches/patch-dirvish.conf.5 Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-dirvish.conf.5,v 1.1 2024/06/27 17:40:34 abs Exp $ | |Taken from debian - From: Ondřej Surý |Subject: Fix typo in docs about rsync-options which was deprecated | |Taken from debian - From: Paul Slootman |Subject: fix manpage nroff typo | |--- dirvish.conf.5.orig 2024-06-20 09:31:51.449735823 +0000 |+++ dirvish.conf.5 -------------------------- Patching file dirvish.conf.5 using Plan A... Hunk #1 succeeded at 101. Hunk #2 succeeded at 537. done => Verifying /data/jenkins/workspace/pkgsrc-trunk-x86_64/sysutils/dirvish/patches/patch-dirvish.pl => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-trunk-x86_64/sysutils/dirvish/patches/patch-dirvish.pl Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-dirvish.pl,v 1.1 2024/06/27 17:40:34 abs Exp $ | |Taken from debian - add per vault lockfile to stop overlapping runs | |Taken from debian - From: Paul Slootman |# If you do "dirvish --init" and forget the --vault bit, the error message |# is "vault undefined", which could make you think that a config file is |# incorrect. Change the message to "vault not specified", which is a bit |# clearer. | |Taken from debian - From: Paul Slootman |# If client is listed as the same as `hostname`, dirvish will not use |# ssh to connect but do a local transfer. Do the same if client is |# specified as 'localhost'. | |--- dirvish.pl.orig 2024-06-20 09:31:29.558321590 +0000 |+++ dirvish.pl -------------------------- Patching file dirvish.pl using Plan A... Hunk #1 succeeded at 273. Hunk #2 succeeded at 458. Hunk #3 succeeded at 531. Hunk #4 succeeded at 606. Hunk #5 succeeded at 741. Hunk #6 succeeded at 775. done ===> Creating toolchain wrappers for dirvish-1.2.1nb10 /usr/bin/sed -e '/^#/d' -e 's,@LINK_ARCH_DEFAULT@,link_arch64,g' -e 's,@LINK_LIBGCC_DEFAULT@,link_libgcc_arch64,g' -e 's,@LIBGCC_PREFIX@,/opt/local/gcc13/x86_64-sun-solaris2.11,g' < ../../extra/gcc13-libs/files/specs.pkgsrc > /tmp/work/sysutils/dirvish/work/.cwrapper/specs.pkgsrc ===> Configuring for dirvish-1.2.1nb10