=> Bootstrap dependency digest>=20211023: found digest-20220214 ===> 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'. ===> Building for py312-sbws-0.8.0nb1 (cd /tmp/net/py-sbws/work/sbws-0.8.0/ && /usr/bin/env USETOOLS=no PTHREAD_CFLAGS=\ -pthread\ PTHREAD_LDFLAGS=\ -pthread PTHREAD_LIBS= PTHREADBASE=/usr DL_CFLAGS=\ -pthread\ DL_LDFLAGS=\ -pthread DL_LIBS= PYTHON=/usr/pkg/bin/python3.12 CC=gcc CFLAGS=-O2\ -I/usr/include\ -I/usr/pkg/include/python3.12 CPPFLAGS=-I/usr/include\ -I/usr/pkg/include/python3.12 CXX=c++ CXXFLAGS=-O2\ -I/usr/include\ -I/usr/pkg/include/python3.12 COMPILER_RPATH_FLAG=-Wl,-R F77=gfortran FC=gfortran FFLAGS=-O LANG=C LC_ALL=C LC_COLLATE=C LC_CTYPE=C LC_MESSAGES=C LC_MONETARY=C LC_NUMERIC=C LC_TIME=C LDFLAGS=-Wl,-zrelro\ -L/usr/lib\ -Wl,-R/usr/lib\ -Wl,-R/usr/pkg/lib LINKER_RPATH_FLAG=-R PATH=/tmp/net/py-sbws/work/.cwrapper/bin:/tmp/net/py-sbws/work/.buildlink/bin:/tmp/net/py-sbws/work/.tools/bin:/usr/pkg/bin:/usr/bin:/bin:/usr/pkg/bin:/usr/local/bin:/usr/pkg/bin:/usr/X11R7/bin PREFIX=/usr/pkg MAKELEVEL=0 CONFIG_SITE= PKG_SYSCONFDIR=/usr/pkg/etc CPP=cpp CXXCPP=cpp HOME=/tmp/net/py-sbws/work/.home CWRAPPERS_CONFIG_DIR=/tmp/net/py-sbws/work/.cwrapper/config CPP=cpp LOCALBASE=/usr/pkg X11BASE=/usr/X11R7 PKGMANDIR=man PKGINFODIR=info PKGGNUDIR=gnu/ MAKECONF=/dev/null OBJECT_FMT=ELF USETOOLS=no BSD_INSTALL_PROGRAM=/usr/bin/install\ -c\ -s\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_SCRIPT=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_LIB=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_DATA=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 644 BSD_INSTALL_MAN=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 644 BSD_INSTALL=/usr/bin/install BSD_INSTALL_PROGRAM_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_SCRIPT_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_LIB_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_DATA_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_MAN_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_GAME=/usr/bin/install\ -c\ -s\ -o\ pbulk\ -g\ wheel\ -m\ 2555 BSD_INSTALL_GAME_DATA=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 664 BSD_INSTALL_GAME_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 775 INSTALL_INFO= MAKEINFO=/tmp/net/py-sbws/work/.tools/bin/makeinfo FLEX= BISON= ITSTOOL=/tmp/net/py-sbws/work/.tools/bin/itstool GDBUS_CODEGEN=/tmp/net/py-sbws/work/.tools/bin/gdbus-codegen PKG_CONFIG=/tmp/net/py-sbws/work/.tools/bin/pkg-config PKG_CONFIG_LIBDIR=/tmp/net/py-sbws/work/.buildlink/lib/pkgconfig:/tmp/net/py-sbws/work/.buildlink/share/pkgconfig PKG_CONFIG_LOG=/tmp/net/py-sbws/work/.pkg-config.log PKG_CONFIG_PATH= CWRAPPERS_CONFIG_DIR=/tmp/net/py-sbws/work/.cwrapper/config /usr/pkg/bin/python3.12 setup.py build -j4) running build running build_py creating build creating build/lib creating build/lib/sbws copying sbws/__init__.py -> build/lib/sbws copying sbws/globals.py -> build/lib/sbws copying sbws/sbws.py -> build/lib/sbws creating build/lib/tests copying tests/__init__.py -> build/lib/tests copying tests/conftest.py -> build/lib/tests creating build/lib/sbws/core copying sbws/core/__init__.py -> build/lib/sbws/core copying sbws/core/cleanup.py -> build/lib/sbws/core copying sbws/core/generate.py -> build/lib/sbws/core copying sbws/core/scanner.py -> build/lib/sbws/core copying sbws/core/stats.py -> build/lib/sbws/core creating build/lib/sbws/lib copying sbws/lib/__init__.py -> build/lib/sbws/lib copying sbws/lib/circuitbuilder.py -> build/lib/sbws/lib copying sbws/lib/destination.py -> build/lib/sbws/lib copying sbws/lib/relaylist.py -> build/lib/sbws/lib copying sbws/lib/relayprioritizer.py -> build/lib/sbws/lib copying sbws/lib/resultdump.py -> build/lib/sbws/lib copying sbws/lib/v3bwfile.py -> build/lib/sbws/lib creating build/lib/sbws/util copying sbws/util/__init__.py -> build/lib/sbws/util copying sbws/util/config.py -> build/lib/sbws/util copying sbws/util/filelock.py -> build/lib/sbws/util copying sbws/util/fs.py -> build/lib/sbws/util copying sbws/util/parser.py -> build/lib/sbws/util copying sbws/util/requests.py -> build/lib/sbws/util copying sbws/util/state.py -> build/lib/sbws/util copying sbws/util/stem.py -> build/lib/sbws/util copying sbws/util/timestamp.py -> build/lib/sbws/util copying sbws/util/userquery.py -> build/lib/sbws/util creating build/lib/tests/integration copying tests/integration/__init__.py -> build/lib/tests/integration copying tests/integration/conftest.py -> build/lib/tests/integration creating build/lib/tests/unit copying tests/unit/__init__.py -> build/lib/tests/unit copying tests/unit/conftest.py -> build/lib/tests/unit copying tests/unit/globals.py -> build/lib/tests/unit creating build/lib/tests/integration/util copying tests/integration/util/__init__.py -> build/lib/tests/integration/util copying tests/integration/util/test_stem.py -> build/lib/tests/integration/util running egg_info creating sbws.egg-info writing sbws.egg-info/PKG-INFO writing dependency_links to sbws.egg-info/dependency_links.txt writing entry points to sbws.egg-info/entry_points.txt writing requirements to sbws.egg-info/requires.txt writing top-level names to sbws.egg-info/top_level.txt writing manifest file 'sbws.egg-info/SOURCES.txt' reading manifest file 'sbws.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'examples' no previously-included directories found matching 'docs/build' no previously-included directories found matching 'tests/testnets/*/auth?' no previously-included directories found matching 'tests/testnets/*/relay?' no previously-included directories found matching 'tests/testnets/*/datadir' no previously-included directories found matching 'tests/testnets/*/exit?' warning: no previously-included files matching 'config*.ini' found under directory 'tests/testnets/*' warning: no previously-included files matching '*.log' found under directory 'tests/testnets/*' no previously-included directories found matching '**/__pycache__' adding license file 'LICENSE.md' adding license file 'AUTHORS.md' writing manifest file 'sbws.egg-info/SOURCES.txt' /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.integration.core' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'tests.integration.core' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'tests.integration.core' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'tests.integration.core' to be distributed and are already explicitly excluding 'tests.integration.core' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.integration.lib' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'tests.integration.lib' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'tests.integration.lib' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'tests.integration.lib' to be distributed and are already explicitly excluding 'tests.integration.lib' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.testnets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'tests.testnets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'tests.testnets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'tests.testnets' to be distributed and are already explicitly excluding 'tests.testnets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.unit.core' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'tests.unit.core' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'tests.unit.core' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'tests.unit.core' to be distributed and are already explicitly excluding 'tests.unit.core' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.unit.lib' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'tests.unit.lib' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'tests.unit.lib' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'tests.unit.lib' to be distributed and are already explicitly excluding 'tests.unit.lib' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.unit.lib.data' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'tests.unit.lib.data' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'tests.unit.lib.data' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'tests.unit.lib.data' to be distributed and are already explicitly excluding 'tests.unit.lib.data' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.unit.util' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'tests.unit.util' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'tests.unit.util' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'tests.unit.util' to be distributed and are already explicitly excluding 'tests.unit.util' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) copying sbws/config.default.ini -> build/lib/sbws copying sbws/config.log.default.ini -> build/lib/sbws creating build/lib/tests/testnets copying tests/testnets/.gitignore -> build/lib/tests/testnets copying tests/testnets/run-network.sh -> build/lib/tests/testnets creating build/lib/tests/testnets/simple-ipv4 copying tests/testnets/simple-ipv4/.net -> build/lib/tests/testnets/simple-ipv4 copying tests/testnets/simple-ipv4/00-common.sh -> build/lib/tests/testnets/simple-ipv4 copying tests/testnets/simple-ipv4/01-gen-configs.sh -> build/lib/tests/testnets/simple-ipv4 copying tests/testnets/simple-ipv4/02-start-network.sh -> build/lib/tests/testnets/simple-ipv4 copying tests/testnets/simple-ipv4/03-network-in-ready-state.py -> build/lib/tests/testnets/simple-ipv4 copying tests/testnets/simple-ipv4/04-stop-network.sh -> build/lib/tests/testnets/simple-ipv4 creating build/lib/tests/testnets/simple-ipv4/html copying tests/testnets/simple-ipv4/html/alphabet.txt -> build/lib/tests/testnets/simple-ipv4/html creating build/lib/tests/testnets/simple-ipv6 copying tests/testnets/simple-ipv6/.net -> build/lib/tests/testnets/simple-ipv6 copying tests/testnets/simple-ipv6/00-common.sh -> build/lib/tests/testnets/simple-ipv6 copying tests/testnets/simple-ipv6/01-gen-configs.sh -> build/lib/tests/testnets/simple-ipv6 copying tests/testnets/simple-ipv6/02-start-network.sh -> build/lib/tests/testnets/simple-ipv6 copying tests/testnets/simple-ipv6/03-network-in-ready-state.py -> build/lib/tests/testnets/simple-ipv6 copying tests/testnets/simple-ipv6/04-stop-network.sh -> build/lib/tests/testnets/simple-ipv6 creating build/lib/tests/testnets/simple.common copying tests/testnets/simple.common/01-gen-configs.sh -> build/lib/tests/testnets/simple.common copying tests/testnets/simple.common/02-start-network.sh -> build/lib/tests/testnets/simple.common copying tests/testnets/simple.common/03-network-in-ready-state.py -> build/lib/tests/testnets/simple.common copying tests/testnets/simple.common/04-stop-network.sh -> build/lib/tests/testnets/simple.common copying tests/integration/net.tar -> build/lib/tests/integration creating build/lib/tests/integration/core copying tests/integration/core/test_scanner.py -> build/lib/tests/integration/core creating build/lib/tests/integration/lib copying tests/integration/lib/test_relaylist.py -> build/lib/tests/integration/lib copying tests/integration/lib/test_relayprioritizer.py -> build/lib/tests/integration/lib creating build/lib/tests/unit/core copying tests/unit/core/test_stats.py -> build/lib/tests/unit/core creating build/lib/tests/unit/lib copying tests/unit/lib/test_resultdump.py -> build/lib/tests/unit/lib copying tests/unit/lib/test_results.py -> build/lib/tests/unit/lib copying tests/unit/lib/test_v3bwfile.py -> build/lib/tests/unit/lib creating build/lib/tests/unit/lib/data copying tests/unit/lib/data/results.txt -> build/lib/tests/unit/lib/data creating build/lib/tests/unit/util copying tests/unit/util/test_config.py -> build/lib/tests/unit/util copying tests/unit/util/test_state.py -> build/lib/tests/unit/util copying tests/unit/util/test_timestamp.py -> build/lib/tests/unit/util copying tests/unit/util/test_userquery.py -> build/lib/tests/unit/util