=> "/opt/local/bin/bmake" ["-C", "/data/jenkins/workspace/pkgsrc-trunk-x86_64/www/py-django-cogwheels", "all", "PYTHON_VERSION_REQD=311", "BATCH=1", "DEPENDS_TARGET=/nonexistent"] WARNING: lang/python/egg.mk is deprecated; use lang/python/wheel.mk instead. ===> Building for py311-django-cogwheels-0.3nb2 (cd /tmp/work/www/py-django-cogwheels/work/django-cogwheels-0.3/ && /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.11 CC=gcc CFLAGS=-pipe\ -O2\ -msave-args\ -fno-aggressive-loop-optimizations\ -I/usr/include\ -I/opt/local/include/python3.11\ -I/opt/local/include CPPFLAGS=-I/usr/include\ -I/opt/local/include/python3.11\ -I/opt/local/include CXX=g++ CXXFLAGS=-pipe\ -O2\ -msave-args\ -fno-aggressive-loop-optimizations\ -I/usr/include\ -I/opt/local/include/python3.11\ -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/www/py-django-cogwheels/work/.cwrapper/bin:/tmp/work/www/py-django-cogwheels/work/.buildlink/bin:/tmp/work/www/py-django-cogwheels/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/www/py-django-cogwheels/work/.home CWRAPPERS_CONFIG_DIR=/tmp/work/www/py-django-cogwheels/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/www/py-django-cogwheels/work/.tools/bin/makeinfo FLEX= BISON= ITSTOOL=/tmp/work/www/py-django-cogwheels/work/.tools/bin/itstool GDBUS_CODEGEN=/tmp/work/www/py-django-cogwheels/work/.tools/bin/gdbus-codegen PKG_CONFIG=/tmp/work/www/py-django-cogwheels/work/.tools/bin/pkg-config PKG_CONFIG_LIBDIR=/tmp/work/www/py-django-cogwheels/work/.buildlink/lib/amd64/pkgconfig:/tmp/work/www/py-django-cogwheels/work/.buildlink/lib/pkgconfig:/tmp/work/www/py-django-cogwheels/work/.buildlink/share/pkgconfig PKG_CONFIG_LOG=/tmp/work/www/py-django-cogwheels/work/.pkg-config.log PKG_CONFIG_PATH= CWRAPPERS_CONFIG_DIR=/tmp/work/www/py-django-cogwheels/work/.cwrapper/config /opt/local/bin/python3.11 setup.py build -j2) running build running build_py creating build/lib/cogwheels copying cogwheels/__init__.py -> build/lib/cogwheels copying cogwheels/__version__.py -> build/lib/cogwheels running egg_info creating django_cogwheels.egg-info writing django_cogwheels.egg-info/PKG-INFO writing dependency_links to django_cogwheels.egg-info/dependency_links.txt writing requirements to django_cogwheels.egg-info/requires.txt writing top-level names to django_cogwheels.egg-info/top_level.txt writing manifest file 'django_cogwheels.egg-info/SOURCES.txt' reading manifest file 'django_cogwheels.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' no previously-included directories found matching 'cogwheels/development' adding license file 'LICENSE' writing manifest file 'django_cogwheels.egg-info/SOURCES.txt' /opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cogwheels.exceptions' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cogwheels.exceptions' 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 'cogwheels.exceptions' 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 'cogwheels.exceptions' to be distributed and are already explicitly excluding 'cogwheels.exceptions' 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.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cogwheels.helpers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cogwheels.helpers' 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 'cogwheels.helpers' 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 'cogwheels.helpers' to be distributed and are already explicitly excluding 'cogwheels.helpers' 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.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cogwheels.helpers.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cogwheels.helpers.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 'cogwheels.helpers.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 'cogwheels.helpers.tests' to be distributed and are already explicitly excluding 'cogwheels.helpers.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.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cogwheels.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cogwheels.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 'cogwheels.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 'cogwheels.tests' to be distributed and are already explicitly excluding 'cogwheels.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.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cogwheels.tests.conf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cogwheels.tests.conf' 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 'cogwheels.tests.conf' 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 'cogwheels.tests.conf' to be distributed and are already explicitly excluding 'cogwheels.tests.conf' 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.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cogwheels.tests.migrations' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cogwheels.tests.migrations' 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 'cogwheels.tests.migrations' 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 'cogwheels.tests.migrations' to be distributed and are already explicitly excluding 'cogwheels.tests.migrations' 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.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cogwheels.tests.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cogwheels.tests.modules' 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 'cogwheels.tests.modules' 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 'cogwheels.tests.modules' to be distributed and are already explicitly excluding 'cogwheels.tests.modules' 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.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cogwheels.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cogwheels.utils' 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 'cogwheels.utils' 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 'cogwheels.utils' to be distributed and are already explicitly excluding 'cogwheels.utils' 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/cogwheels/exceptions copying cogwheels/exceptions/__init__.py -> build/lib/cogwheels/exceptions copying cogwheels/exceptions/deprecations.py -> build/lib/cogwheels/exceptions copying cogwheels/exceptions/settings.py -> build/lib/cogwheels/exceptions creating build/lib/cogwheels/helpers copying cogwheels/helpers/__init__.py -> build/lib/cogwheels/helpers copying cogwheels/helpers/deprecation.py -> build/lib/cogwheels/helpers copying cogwheels/helpers/settings.py -> build/lib/cogwheels/helpers copying cogwheels/helpers/utils.py -> build/lib/cogwheels/helpers creating build/lib/cogwheels/helpers/tests copying cogwheels/helpers/tests/__init__.py -> build/lib/cogwheels/helpers/tests copying cogwheels/helpers/tests/test_deprecation_warning_stacklevel.py -> build/lib/cogwheels/helpers/tests copying cogwheels/helpers/tests/test_get.py -> build/lib/cogwheels/helpers/tests copying cogwheels/helpers/tests/test_get_model.py -> build/lib/cogwheels/helpers/tests copying cogwheels/helpers/tests/test_get_module.py -> build/lib/cogwheels/helpers/tests copying cogwheels/helpers/tests/test_get_object.py -> build/lib/cogwheels/helpers/tests copying cogwheels/helpers/tests/test_helper_attribute_shortcuts.py -> build/lib/cogwheels/helpers/tests copying cogwheels/helpers/tests/test_helper_init.py -> build/lib/cogwheels/helpers/tests copying cogwheels/helpers/tests/test_invalid_deprecations.py -> build/lib/cogwheels/helpers/tests copying cogwheels/helpers/tests/test_is_value_from_deprecated_setting.py -> build/lib/cogwheels/helpers/tests creating build/lib/cogwheels/tests copying cogwheels/tests/__init__.py -> build/lib/cogwheels/tests copying cogwheels/tests/base.py -> build/lib/cogwheels/tests copying cogwheels/tests/classes.py -> build/lib/cogwheels/tests copying cogwheels/tests/models.py -> build/lib/cogwheels/tests copying cogwheels/tests/settings.py -> build/lib/cogwheels/tests copying cogwheels/tests/urls.py -> build/lib/cogwheels/tests creating build/lib/cogwheels/tests/conf copying cogwheels/tests/conf/__init__.py -> build/lib/cogwheels/tests/conf copying cogwheels/tests/conf/defaults.py -> build/lib/cogwheels/tests/conf copying cogwheels/tests/conf/settings.py -> build/lib/cogwheels/tests/conf creating build/lib/cogwheels/tests/migrations copying cogwheels/tests/migrations/0001_initial.py -> build/lib/cogwheels/tests/migrations copying cogwheels/tests/migrations/__init__.py -> build/lib/cogwheels/tests/migrations creating build/lib/cogwheels/tests/modules copying cogwheels/tests/modules/__init__.py -> build/lib/cogwheels/tests/modules copying cogwheels/tests/modules/default_module.py -> build/lib/cogwheels/tests/modules copying cogwheels/tests/modules/replacement_module.py -> build/lib/cogwheels/tests/modules creating build/lib/cogwheels/utils copying cogwheels/utils/deprecation.py -> build/lib/cogwheels/utils copying cogwheels/utils/inspection.py -> build/lib/cogwheels/utils