=> Bootstrap dependency digest>=20211023: found digest-20220214
=> Checksum BLAKE2s OK for uvloop-0.20.0.tar.gz
=> Checksum SHA512 OK for uvloop-0.20.0.tar.gz
===> Installing dependencies for py313-uvloop-0.20.0
==========================================================================
The following variables will affect the build process of this package,
py313-uvloop-0.20.0.  Their current value is shown below:

        * PYTHON_VERSION_DEFAULT = 312

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

        * PYPACKAGE = python313

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/bin/make clean' after the changes.
==========================================================================
=> Tool dependency py313-cython>=0.29.36: found py313-cython-3.0.11
=> Tool dependency py313-setuptools>=60: found py313-setuptools-75.1.0
=> Tool dependency py313-wheel-[0-9]*: found py313-wheel-0.44.0
=> Tool dependency py313-build>=0: found py313-build-1.2.2.post1
=> Tool dependency py313-installer>=0.7.0nb1: found py313-installer-0.7.0nb1
=> Tool dependency mktools-[0-9]*: found mktools-20220614
=> Tool dependency cwrappers>=20150314: found cwrappers-20220403
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Full dependency libuv>=1.48.0: found libuv-1.49.1
=> Full dependency python313>=3.13: found python313-3.13.0
===> Skipping vulnerability checks.
WARNING: No /usr/pkg/pkgdb/pkg-vulnerabilities file found.
WARNING: To fix run: `/usr/sbin/pkg_admin -K /usr/pkg/pkgdb fetch-pkg-vulnerabilities'.
===> Overriding tools for py313-uvloop-0.20.0
===> Extracting for py313-uvloop-0.20.0
===> Patching for py313-uvloop-0.20.0
=> Applying pkgsrc patches for py313-uvloop-0.20.0
=> Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/devel/py-uvloop/patches/patch-setup.py
=> Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/devel/py-uvloop/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.7 2023/10/18 08:57:11 adam Exp $
|
|Use system libuv (--use-system-libuv option does not work for 'install').
|
|--- setup.py.orig	2023-10-13 15:49:42.000000000 +0000
|+++ setup.py
--------------------------
Patching file setup.py using Plan A...
Hunk #1 succeeded at 83.
done
=> Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/devel/py-uvloop/patches/patch-uvloop_loop.c
=> Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/devel/py-uvloop/patches/patch-uvloop_loop.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-uvloop_loop.c,v 1.1 2022/04/25 21:46:50 tnn Exp $
|
|If SO_REUSEPORT is not defined, then use SO_REUSEADDR.
|This is ugly, but should be safe: the code won't be reached because
|has_REUSEPORT is false at run-time.
|Patching this way is 100% a hack and not upstreamable,
|but it avoids re-cythonizing the package.
|
|--- uvloop/loop.c.orig	2021-08-10 19:05:48.000000000 +0000
|+++ uvloop/loop.c
--------------------------
Patching file uvloop/loop.c using Plan A...
Hunk #1 succeeded at 15.
done
===> Creating toolchain wrappers for py313-uvloop-0.20.0
===> Configuring for py313-uvloop-0.20.0
=> Checking for portability problems in extracted files