=> 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'. ===> Installing for py311-django-kronos-1.0nb2 => Generating pre-install file lists => Creating installation directories (cd /tmp/www/py-django-kronos/work/django-kronos-1.0/ && /usr/bin/env DESTDIR=/tmp/www/py-django-kronos/work/.destdir 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.11 CC=gcc CFLAGS=-O2\ -I/usr/include\ -I/usr/pkg/include/python3.11 CPPFLAGS=-I/usr/include\ -I/usr/pkg/include/python3.11 CXX=c++ CXXFLAGS=-O2\ -I/usr/include\ -I/usr/pkg/include/python3.11 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/www/py-django-kronos/work/.cwrapper/bin:/tmp/www/py-django-kronos/work/.buildlink/bin:/tmp/www/py-django-kronos/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/www/py-django-kronos/work/.home CWRAPPERS_CONFIG_DIR=/tmp/www/py-django-kronos/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/www/py-django-kronos/work/.tools/bin/makeinfo FLEX= BISON= ITSTOOL=/tmp/www/py-django-kronos/work/.tools/bin/itstool GDBUS_CODEGEN=/tmp/www/py-django-kronos/work/.tools/bin/gdbus-codegen PKG_CONFIG=/tmp/www/py-django-kronos/work/.tools/bin/pkg-config PKG_CONFIG_LIBDIR=/tmp/www/py-django-kronos/work/.buildlink/lib/pkgconfig:/tmp/www/py-django-kronos/work/.buildlink/share/pkgconfig PKG_CONFIG_LOG=/tmp/www/py-django-kronos/work/.pkg-config.log PKG_CONFIG_PATH= CWRAPPERS_CONFIG_DIR=/tmp/www/py-django-kronos/work/.cwrapper/config /usr/pkg/bin/python3.11 setup.py "install" -c -O1 --root=/tmp/www/py-django-kronos/work/.destdir) running install /usr/pkg/lib/python3.11/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() running build running build_py running egg_info writing django_kronos.egg-info/PKG-INFO writing dependency_links to django_kronos.egg-info/dependency_links.txt writing requirements to django_kronos.egg-info/requires.txt writing top-level names to django_kronos.egg-info/top_level.txt reading manifest file 'django_kronos.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'management' under directory 'kronos' warning: no files found matching 'management' under directory 'kronos' warning: no files found matching 'commands' under directory 'kronos' adding license file 'LICENSE' writing manifest file 'django_kronos.egg-info/SOURCES.txt' /usr/pkg/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'kronos.management' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'kronos.management' 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 'kronos.management' 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 'kronos.management' to be distributed and are already explicitly excluding 'kronos.management' 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.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'kronos.management.commands' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'kronos.management.commands' 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 'kronos.management.commands' 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 'kronos.management.commands' to be distributed and are already explicitly excluding 'kronos.management.commands' 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.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'kronos.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'kronos.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 'kronos.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 'kronos.tests' to be distributed and are already explicitly excluding 'kronos.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) /usr/pkg/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'kronos.tests.project' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'kronos.tests.project' 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 'kronos.tests.project' 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 'kronos.tests.project' to be distributed and are already explicitly excluding 'kronos.tests.project' 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.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'kronos.tests.project.app' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'kronos.tests.project.app' 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 'kronos.tests.project.app' 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 'kronos.tests.project.app' to be distributed and are already explicitly excluding 'kronos.tests.project.app' 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.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'kronos.tests.project.app.management' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'kronos.tests.project.app.management' 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 'kronos.tests.project.app.management' 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 'kronos.tests.project.app.management' to be distributed and are already explicitly excluding 'kronos.tests.project.app.management' 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.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'kronos.tests.project.app.management.commands' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'kronos.tests.project.app.management.commands' 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 'kronos.tests.project.app.management.commands' 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 'kronos.tests.project.app.management.commands' to be distributed and are already explicitly excluding 'kronos.tests.project.app.management.commands' 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) running install_lib creating /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos copying build/lib/kronos/__init__.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos copying build/lib/kronos/settings.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos copying build/lib/kronos/settings_test.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos copying build/lib/kronos/version.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos creating /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/management copying build/lib/kronos/management/__init__.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/management creating /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/management/commands copying build/lib/kronos/management/commands/__init__.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/management/commands copying build/lib/kronos/management/commands/installtasks.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/management/commands copying build/lib/kronos/management/commands/runtask.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/management/commands copying build/lib/kronos/management/commands/showtasks.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/management/commands copying build/lib/kronos/management/commands/uninstalltasks.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/management/commands creating /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests copying build/lib/kronos/tests/__init__.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests copying build/lib/kronos/tests/tests.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests creating /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project copying build/lib/kronos/tests/project/__init__.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project copying build/lib/kronos/tests/project/cron.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project creating /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/app copying build/lib/kronos/tests/project/app/__init__.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/app copying build/lib/kronos/tests/project/app/cron.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/app creating /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/app/management copying build/lib/kronos/tests/project/app/management/__init__.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/app/management creating /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/app/management/commands copying build/lib/kronos/tests/project/app/management/commands/__init__.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/app/management/commands copying build/lib/kronos/tests/project/app/management/commands/task.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/app/management/commands copying build/lib/kronos/tests/project/app/management/commands/task_with_args.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/app/management/commands copying build/lib/kronos/tests/project/app/management/commands/task_with_empty_args.py -> /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/app/management/commands byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/__init__.py to __init__.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/settings.py to settings.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/settings_test.py to settings_test.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/version.py to version.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/management/__init__.py to __init__.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/management/commands/__init__.py to __init__.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/management/commands/installtasks.py to installtasks.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/management/commands/runtask.py to runtask.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/management/commands/showtasks.py to showtasks.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/management/commands/uninstalltasks.py to uninstalltasks.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/__init__.py to __init__.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/tests.py to tests.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/__init__.py to __init__.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/cron.py to cron.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/app/__init__.py to __init__.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/app/cron.py to cron.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/app/management/__init__.py to __init__.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/app/management/commands/__init__.py to __init__.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/app/management/commands/task.py to task.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/app/management/commands/task_with_args.py to task_with_args.cpython-311.pyc byte-compiling /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/kronos/tests/project/app/management/commands/task_with_empty_args.py to task_with_empty_args.cpython-311.pyc writing byte-compilation script '/tmp/tmpw3of4jpe.py' /usr/pkg/bin/python3.11 /tmp/tmpw3of4jpe.py removing /tmp/tmpw3of4jpe.py running install_egg_info Copying django_kronos.egg-info to /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/django_kronos-1.0-py3.11.egg-info running install_scripts => Automatic manual page handling => Generating post-install file lists if test -d "/tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/django_kronos-1.0-py3.11.egg-info"; then /usr/bin/find /tmp/www/py-django-kronos/work/.destdir/usr/pkg/lib/python3.11/site-packages/django_kronos-1.0-py3.11.egg-info -type f -exec /bin/chmod 644 '{}' ';' ; fi => Checking file-check results for py311-django-kronos-1.0nb2 => Checking for non-existent script interpreters in py311-django-kronos-1.0nb2 => Checking file permissions in py311-django-kronos-1.0nb2 warning: /tmp: group permissions (rwx) are higher than owner permissions (--x). warning: /tmp: group-writable directory. error: /tmp: world-writable directory. 1 errors and 2 warnings. *** Error code 1 Stop. make[1]: stopped in /amd/pkgsrc/CHROOT/P/pkgsrc/www/py-django-kronos *** Error code 1 Stop. make: stopped in /amd/pkgsrc/CHROOT/P/pkgsrc/www/py-django-kronos