=> "/opt/local/bin/bmake" ["-C", "/data/jenkins/workspace/pkgsrc-trunk-x86_64/graphics/py-nwdiag", "all", "PYTHON_VERSION_REQD=313", "BATCH=1", "DEPENDS_TARGET=/nonexistent"] WARNING: lang/python/egg.mk is deprecated; use lang/python/wheel.mk instead. ===> Building for py313-nwdiag-2.0.0nb2 (cd /tmp/work/graphics/py-nwdiag/work/nwdiag-2.0.0/ && /usr/bin/env USETOOLS=no PTHREAD_CFLAGS=\ -pthread\ PTHREAD_LDFLAGS=\ -pthread PTHREAD_LIBS=-lpthread\ -lrt PTHREADBASE=/usr DL_CFLAGS= DL_LDFLAGS= DL_LIBS= PYTHON=/opt/local/bin/python3.13 CC=gcc CFLAGS=-pipe\ -O2\ -msave-args\ -fno-aggressive-loop-optimizations\ -I/usr/include\ -I/opt/local/include/python3.13\ -I/opt/local/include CPPFLAGS=-I/usr/include\ -I/opt/local/include/python3.13\ -I/opt/local/include CXX=g++ CXXFLAGS=-pipe\ -O2\ -msave-args\ -fno-aggressive-loop-optimizations\ -I/usr/include\ -I/opt/local/include/python3.13\ -I/opt/local/include COMPILER_RPATH_FLAG=-Wl,-R F77=f77 FC=f77 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=-L/usr/lib/amd64\ -Wl,-R/usr/lib/amd64\ -Wl,-R/opt/local/lib\ -lintl\ -liconv\ -L/opt/local/lib LINKER_RPATH_FLAG=-R PATH=/tmp/work/graphics/py-nwdiag/work/.cwrapper/bin:/tmp/work/graphics/py-nwdiag/work/.buildlink/bin:/tmp/work/graphics/py-nwdiag/work/.tools/bin:/opt/local/bin:/sbin:/usr/bin:/usr/sbin:/opt/tools/bin:/opt/local/bin:/opt/local/bin PREFIX=/opt/local MAKELEVEL=0 CONFIG_SITE= ftp_proxy=downloads-forbidden-except-during-fetch http_proxy=downloads-forbidden-except-during-fetch https_proxy=downloads-forbidden-except-during-fetch no_proxy= PKG_SYSCONFDIR=/opt/local/etc CPP=cpp CXXCPP=cpp HOME=/tmp/work/graphics/py-nwdiag/work/.home CWRAPPERS_CONFIG_DIR=/tmp/work/graphics/py-nwdiag/work/.cwrapper/config CPP=cpp LOCALBASE=/opt/local X11BASE=/opt/local PKGMANDIR=man PKGINFODIR=info PKGGNUDIR= MAKECONF=/dev/null OBJECT_FMT=ELF USETOOLS=no BSD_INSTALL_PROGRAM=/opt/local/bin/bsdinstall\ -c\ \ -o\ pbuild\ -g\ pbuild\ -m\ 755 BSD_INSTALL_SCRIPT=/opt/local/bin/bsdinstall\ -c\ -o\ pbuild\ -g\ pbuild\ -m\ 755 BSD_INSTALL_LIB=/opt/local/bin/bsdinstall\ -c\ -o\ pbuild\ -g\ pbuild\ -m\ 755 BSD_INSTALL_DATA=/opt/local/bin/bsdinstall\ -c\ -o\ pbuild\ -g\ pbuild\ -m\ 644 BSD_INSTALL_MAN=/opt/local/bin/bsdinstall\ -c\ -o\ pbuild\ -g\ pbuild\ -m\ 644 BSD_INSTALL=/opt/local/bin/bsdinstall BSD_INSTALL_PROGRAM_DIR=/opt/local/bin/bsdinstall\ -d\ -o\ pbuild\ -g\ pbuild\ -m\ 755 BSD_INSTALL_SCRIPT_DIR=/opt/local/bin/bsdinstall\ -d\ -o\ pbuild\ -g\ pbuild\ -m\ 755 BSD_INSTALL_LIB_DIR=/opt/local/bin/bsdinstall\ -d\ -o\ pbuild\ -g\ pbuild\ -m\ 755 BSD_INSTALL_DATA_DIR=/opt/local/bin/bsdinstall\ -d\ -o\ pbuild\ -g\ pbuild\ -m\ 755 BSD_INSTALL_MAN_DIR=/opt/local/bin/bsdinstall\ -d\ -o\ pbuild\ -g\ pbuild\ -m\ 755 BSD_INSTALL_GAME=/opt/local/bin/bsdinstall\ -c\ \ -o\ pbuild\ -g\ pbuild\ -m\ 2555 BSD_INSTALL_GAME_DATA=/opt/local/bin/bsdinstall\ -c\ -o\ pbuild\ -g\ pbuild\ -m\ 664 BSD_INSTALL_GAME_DIR=/opt/local/bin/bsdinstall\ -d\ -o\ pbuild\ -g\ pbuild\ -m\ 775 INSTALL_INFO= MAKEINFO=/tmp/work/graphics/py-nwdiag/work/.tools/bin/makeinfo FLEX= BISON= ITSTOOL=/tmp/work/graphics/py-nwdiag/work/.tools/bin/itstool GDBUS_CODEGEN=/tmp/work/graphics/py-nwdiag/work/.tools/bin/gdbus-codegen PKG_CONFIG=/tmp/work/graphics/py-nwdiag/work/.tools/bin/pkg-config PKG_CONFIG_LIBDIR=/tmp/work/graphics/py-nwdiag/work/.buildlink/lib/amd64/pkgconfig:/tmp/work/graphics/py-nwdiag/work/.buildlink/lib/pkgconfig:/tmp/work/graphics/py-nwdiag/work/.buildlink/share/pkgconfig PKG_CONFIG_LOG=/tmp/work/graphics/py-nwdiag/work/.pkg-config.log PKG_CONFIG_PATH= CWRAPPERS_CONFIG_DIR=/tmp/work/graphics/py-nwdiag/work/.cwrapper/config /opt/local/bin/python3.13 setup.py build -j2) /opt/local/lib/python3.13/site-packages/setuptools/dist.py:599: SetuptoolsDeprecationWarning: Invalid dash-separated key 'build-base' in 'build' (setup.cfg), please use the underscore name 'build_base' instead. !! ******************************************************************************** Usage of dash-separated 'build-base' will not be supported in future versions. Please use the underscore name 'build_base' instead. Available configuration options are listed in: https://setuptools.pypa.io/en/latest/userguide/declarative_config.html This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://github.com/pypa/setuptools/discussions/5011 for details. ******************************************************************************** !! opt = self._enforce_underscore(opt, section) /opt/local/lib/python3.13/site-packages/setuptools/_distutils/dist.py:318: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /opt/local/lib/python3.13/site-packages/setuptools/dist.py:599: SetuptoolsDeprecationWarning: Invalid dash-separated key 'build-base' in 'build' (setup.cfg), please use the underscore name 'build_base' instead. !! ******************************************************************************** Usage of dash-separated 'build-base' will not be supported in future versions. Please use the underscore name 'build_base' instead. (Affected: nwdiag). Available configuration options are listed in: https://setuptools.pypa.io/en/latest/userguide/declarative_config.html This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://github.com/pypa/setuptools/discussions/5011 for details. ******************************************************************************** !! opt = self._enforce_underscore(opt, section) /opt/local/lib/python3.13/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: Apache Software License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running build running build_py creating _build/lib copying src/nwdiag_sphinxhelper.py -> _build/lib copying src/rackdiag_sphinxhelper.py -> _build/lib copying src/packetdiag_sphinxhelper.py -> _build/lib creating _build/lib/nwdiag copying src/nwdiag/__init__.py -> _build/lib/nwdiag copying src/nwdiag/builder.py -> _build/lib/nwdiag copying src/nwdiag/command.py -> _build/lib/nwdiag copying src/nwdiag/drawer.py -> _build/lib/nwdiag copying src/nwdiag/elements.py -> _build/lib/nwdiag copying src/nwdiag/metrics.py -> _build/lib/nwdiag copying src/nwdiag/parser.py -> _build/lib/nwdiag creating _build/lib/packetdiag copying src/packetdiag/__init__.py -> _build/lib/packetdiag copying src/packetdiag/builder.py -> _build/lib/packetdiag copying src/packetdiag/command.py -> _build/lib/packetdiag copying src/packetdiag/drawer.py -> _build/lib/packetdiag copying src/packetdiag/elements.py -> _build/lib/packetdiag copying src/packetdiag/metrics.py -> _build/lib/packetdiag copying src/packetdiag/noderenderers.py -> _build/lib/packetdiag copying src/packetdiag/parser.py -> _build/lib/packetdiag creating _build/lib/rackdiag copying src/rackdiag/__init__.py -> _build/lib/rackdiag copying src/rackdiag/builder.py -> _build/lib/rackdiag copying src/rackdiag/command.py -> _build/lib/rackdiag copying src/rackdiag/drawer.py -> _build/lib/rackdiag copying src/rackdiag/elements.py -> _build/lib/rackdiag copying src/rackdiag/metrics.py -> _build/lib/rackdiag copying src/rackdiag/parser.py -> _build/lib/rackdiag creating _build/lib/nwdiag/tests copying src/nwdiag/tests/__init__.py -> _build/lib/nwdiag/tests copying src/nwdiag/tests/test_builder.py -> _build/lib/nwdiag/tests copying src/nwdiag/tests/test_generate_diagram.py -> _build/lib/nwdiag/tests copying src/nwdiag/tests/test_rst_directives.py -> _build/lib/nwdiag/tests copying src/nwdiag/tests/utils.py -> _build/lib/nwdiag/tests creating _build/lib/nwdiag/utils copying src/nwdiag/utils/__init__.py -> _build/lib/nwdiag/utils creating _build/lib/nwdiag/utils/rst copying src/nwdiag/utils/rst/__init__.py -> _build/lib/nwdiag/utils/rst copying src/nwdiag/utils/rst/directives.py -> _build/lib/nwdiag/utils/rst copying src/nwdiag/utils/rst/nodes.py -> _build/lib/nwdiag/utils/rst creating _build/lib/packetdiag/utils copying src/packetdiag/utils/__init__.py -> _build/lib/packetdiag/utils creating _build/lib/packetdiag/utils/rst copying src/packetdiag/utils/rst/__init__.py -> _build/lib/packetdiag/utils/rst copying src/packetdiag/utils/rst/directives.py -> _build/lib/packetdiag/utils/rst copying src/packetdiag/utils/rst/nodes.py -> _build/lib/packetdiag/utils/rst creating _build/lib/rackdiag/utils copying src/rackdiag/utils/__init__.py -> _build/lib/rackdiag/utils copying src/rackdiag/utils/math.py -> _build/lib/rackdiag/utils creating _build/lib/rackdiag/utils/rst copying src/rackdiag/utils/rst/__init__.py -> _build/lib/rackdiag/utils/rst copying src/rackdiag/utils/rst/directives.py -> _build/lib/rackdiag/utils/rst copying src/rackdiag/utils/rst/nodes.py -> _build/lib/rackdiag/utils/rst running egg_info writing src/nwdiag.egg-info/PKG-INFO writing dependency_links to src/nwdiag.egg-info/dependency_links.txt writing entry points to src/nwdiag.egg-info/entry_points.txt writing requirements to src/nwdiag.egg-info/requires.txt writing top-level names to src/nwdiag.egg-info/top_level.txt reading manifest file 'src/nwdiag.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching '*.gif' under directory 'src' warning: no previously-included files found matching '.drone.io.sh' warning: no previously-included files found matching 'examples/update.sh' adding license file 'LICENSE' writing manifest file 'src/nwdiag.egg-info/SOURCES.txt' /opt/local/lib/python3.13/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'nwdiag.tests.VLGothic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'nwdiag.tests.VLGothic' 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 'nwdiag.tests.VLGothic' 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 'nwdiag.tests.VLGothic' to be distributed and are already explicitly excluding 'nwdiag.tests.VLGothic' 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) /opt/local/lib/python3.13/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'nwdiag.tests.diagrams' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'nwdiag.tests.diagrams' 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 'nwdiag.tests.diagrams' 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 'nwdiag.tests.diagrams' to be distributed and are already explicitly excluding 'nwdiag.tests.diagrams' 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) /opt/local/lib/python3.13/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'nwdiag.tests.diagrams.errors' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'nwdiag.tests.diagrams.errors' 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 'nwdiag.tests.diagrams.errors' 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 'nwdiag.tests.diagrams.errors' to be distributed and are already explicitly excluding 'nwdiag.tests.diagrams.errors' 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) /opt/local/lib/python3.13/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'packetdiag.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'packetdiag.tests' 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 'packetdiag.tests' 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 'packetdiag.tests' to be distributed and are already explicitly excluding 'packetdiag.tests' 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) /opt/local/lib/python3.13/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'packetdiag.tests.VLGothic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'packetdiag.tests.VLGothic' 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 'packetdiag.tests.VLGothic' 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 'packetdiag.tests.VLGothic' to be distributed and are already explicitly excluding 'packetdiag.tests.VLGothic' 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) /opt/local/lib/python3.13/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'packetdiag.tests.diagrams' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'packetdiag.tests.diagrams' 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 'packetdiag.tests.diagrams' 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 'packetdiag.tests.diagrams' to be distributed and are already explicitly excluding 'packetdiag.tests.diagrams' 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) /opt/local/lib/python3.13/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'rackdiag.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'rackdiag.tests' 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 'rackdiag.tests' 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 'rackdiag.tests' to be distributed and are already explicitly excluding 'rackdiag.tests' 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) /opt/local/lib/python3.13/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'rackdiag.tests.VLGothic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'rackdiag.tests.VLGothic' 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 'rackdiag.tests.VLGothic' 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 'rackdiag.tests.VLGothic' to be distributed and are already explicitly excluding 'rackdiag.tests.VLGothic' 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) /opt/local/lib/python3.13/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'rackdiag.tests.diagrams' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'rackdiag.tests.diagrams' 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 'rackdiag.tests.diagrams' 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 'rackdiag.tests.diagrams' to be distributed and are already explicitly excluding 'rackdiag.tests.diagrams' 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) creating _build/lib/packetdiag/tests copying src/packetdiag/tests/test_generate_diagram.py -> _build/lib/packetdiag/tests copying src/packetdiag/tests/test_rst_directives.py -> _build/lib/packetdiag/tests creating _build/lib/packetdiag/tests/VLGothic copying src/packetdiag/tests/VLGothic/VL-Gothic-Regular.ttf -> _build/lib/packetdiag/tests/VLGothic creating _build/lib/packetdiag/tests/diagrams copying src/packetdiag/tests/diagrams/oneliner.diag -> _build/lib/packetdiag/tests/diagrams copying src/packetdiag/tests/diagrams/oneliner_with_quoted.diag -> _build/lib/packetdiag/tests/diagrams copying src/packetdiag/tests/diagrams/oneliner_without_last_semicolon.diag -> _build/lib/packetdiag/tests/diagrams copying src/packetdiag/tests/diagrams/scale_direction.diag -> _build/lib/packetdiag/tests/diagrams copying src/packetdiag/tests/diagrams/scale_interval.diag -> _build/lib/packetdiag/tests/diagrams copying src/packetdiag/tests/diagrams/tcp.diag -> _build/lib/packetdiag/tests/diagrams copying src/packetdiag/tests/diagrams/tcp_2.diag -> _build/lib/packetdiag/tests/diagrams creating _build/lib/rackdiag/tests copying src/rackdiag/tests/test_builder.py -> _build/lib/rackdiag/tests copying src/rackdiag/tests/test_generate_diagram.py -> _build/lib/rackdiag/tests copying src/rackdiag/tests/test_rst_directives.py -> _build/lib/rackdiag/tests creating _build/lib/rackdiag/tests/VLGothic copying src/rackdiag/tests/VLGothic/VL-Gothic-Regular.ttf -> _build/lib/rackdiag/tests/VLGothic creating _build/lib/rackdiag/tests/diagrams copying src/rackdiag/tests/diagrams/autonumber.diag -> _build/lib/rackdiag/tests/diagrams copying src/rackdiag/tests/diagrams/multi_rackitem.diag -> _build/lib/rackdiag/tests/diagrams copying src/rackdiag/tests/diagrams/multi_racks.diag -> _build/lib/rackdiag/tests/diagrams copying src/rackdiag/tests/diagrams/oneliner.diag -> _build/lib/rackdiag/tests/diagrams copying src/rackdiag/tests/diagrams/oneliner_with_quoted.diag -> _build/lib/rackdiag/tests/diagrams copying src/rackdiag/tests/diagrams/oneliner_without_last_semicolon.diag -> _build/lib/rackdiag/tests/diagrams copying src/rackdiag/tests/diagrams/rack_height.diag -> _build/lib/rackdiag/tests/diagrams copying src/rackdiag/tests/diagrams/rack_height_for_multi_racks.diag -> _build/lib/rackdiag/tests/diagrams copying src/rackdiag/tests/diagrams/simple.diag -> _build/lib/rackdiag/tests/diagrams creating _build/lib/nwdiag/tests/VLGothic copying src/nwdiag/tests/VLGothic/LICENSE -> _build/lib/nwdiag/tests/VLGothic copying src/nwdiag/tests/VLGothic/LICENSE.en -> _build/lib/nwdiag/tests/VLGothic copying src/nwdiag/tests/VLGothic/LICENSE_E.mplus -> _build/lib/nwdiag/tests/VLGothic copying src/nwdiag/tests/VLGothic/LICENSE_J.mplus -> _build/lib/nwdiag/tests/VLGothic copying src/nwdiag/tests/VLGothic/VL-Gothic-Regular.ttf -> _build/lib/nwdiag/tests/VLGothic creating _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/autoexpand_node_width.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/connected_networks.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/connected_networks2.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/connected_networks3.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/diagram_attributes.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/group_across_network.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/group_and_peer_network.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/group_inner_network.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/group_network.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/group_outer_network.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/node_address_attribute.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/node_attributes.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/node_belongs_to_multiple_networks.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/node_including_hyphen.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/peer_network.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/peer_network2.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/peer_network3.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/peer_network4.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/peer_network5.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/peer_network_branched.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/same_peer_network.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/single_network.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/split_group.diag -> _build/lib/nwdiag/tests/diagrams copying src/nwdiag/tests/diagrams/two_networks.diag -> _build/lib/nwdiag/tests/diagrams creating _build/lib/nwdiag/tests/diagrams/errors copying src/nwdiag/tests/diagrams/errors/peer_network_in_same_node.diag -> _build/lib/nwdiag/tests/diagrams/errors