=> "/opt/local/bin/bmake" ["-C", "/data/jenkins/workspace/pkgsrc-trunk-x86_64/www/py-django-celery-beat", "all", "PYTHON_VERSION_REQD=311", "BATCH=1", "DEPENDS_TARGET=/nonexistent"] ===> Building for py311-django-celery-beat-2.8.0 * Building wheel... /opt/local/lib/python3.11/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 :: BSD License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running bdist_wheel running build running build_py creating build/lib/django_celery_beat copying django_celery_beat/__init__.py -> build/lib/django_celery_beat copying django_celery_beat/admin.py -> build/lib/django_celery_beat copying django_celery_beat/apps.py -> build/lib/django_celery_beat copying django_celery_beat/clockedschedule.py -> build/lib/django_celery_beat copying django_celery_beat/models.py -> build/lib/django_celery_beat copying django_celery_beat/querysets.py -> build/lib/django_celery_beat copying django_celery_beat/schedulers.py -> build/lib/django_celery_beat copying django_celery_beat/signals.py -> build/lib/django_celery_beat copying django_celery_beat/tzcrontab.py -> build/lib/django_celery_beat copying django_celery_beat/utils.py -> build/lib/django_celery_beat copying django_celery_beat/validators.py -> build/lib/django_celery_beat creating build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0001_initial.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0002_auto_20161118_0346.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0003_auto_20161209_0049.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0004_auto_20170221_0000.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0005_add_solarschedule_events_choices.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0006_auto_20180210_1226.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0006_auto_20180322_0932.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0006_periodictask_priority.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0007_auto_20180521_0826.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0008_auto_20180914_1922.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0009_periodictask_headers.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0010_auto_20190429_0326.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0011_auto_20190508_0153.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0012_periodictask_expire_seconds.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0013_auto_20200609_0727.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0014_remove_clockedschedule_enabled.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0015_edit_solarschedule_events_choices.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0016_alter_crontabschedule_timezone.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0017_alter_crontabschedule_month_of_year.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0018_improve_crontab_helptext.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/0019_alter_periodictasks_options.py -> build/lib/django_celery_beat/migrations copying django_celery_beat/migrations/__init__.py -> build/lib/django_celery_beat/migrations running egg_info writing django_celery_beat.egg-info/PKG-INFO writing dependency_links to django_celery_beat.egg-info/dependency_links.txt writing entry points to django_celery_beat.egg-info/entry_points.txt writing requirements to django_celery_beat.egg-info/requires.txt writing top-level names to django_celery_beat.egg-info/top_level.txt reading manifest file 'django_celery_beat.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: manifest_maker: MANIFEST.in, line 9: 'recursive-include' expects ... warning: no files found matching '*' under directory 'examples' warning: no files found matching '*.rst' under directory 'requirements' warning: no previously-included files matching '__pycache__' found under directory '*' warning: no previously-included files matching '*.py[co]' found under directory '*' warning: no previously-included files matching '.*.sw[a-z]' found under directory '*' adding license file 'LICENSE' adding license file 'AUTHORS' writing manifest file 'django_celery_beat.egg-info/SOURCES.txt' /opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_celery_beat.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_celery_beat.locale.de.LC_MESSAGES' 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 'django_celery_beat.locale.de.LC_MESSAGES' 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 'django_celery_beat.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_celery_beat.locale.de.LC_MESSAGES' 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 'django_celery_beat.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_celery_beat.locale.es.LC_MESSAGES' 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 'django_celery_beat.locale.es.LC_MESSAGES' 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 'django_celery_beat.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_celery_beat.locale.es.LC_MESSAGES' 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 'django_celery_beat.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_celery_beat.locale.fa.LC_MESSAGES' 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 'django_celery_beat.locale.fa.LC_MESSAGES' 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 'django_celery_beat.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_celery_beat.locale.fa.LC_MESSAGES' 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 'django_celery_beat.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_celery_beat.locale.fr.LC_MESSAGES' 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 'django_celery_beat.locale.fr.LC_MESSAGES' 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 'django_celery_beat.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_celery_beat.locale.fr.LC_MESSAGES' 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 'django_celery_beat.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_celery_beat.locale.ko.LC_MESSAGES' 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 'django_celery_beat.locale.ko.LC_MESSAGES' 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 'django_celery_beat.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_celery_beat.locale.ko.LC_MESSAGES' 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 'django_celery_beat.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_celery_beat.locale.ru.LC_MESSAGES' 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 'django_celery_beat.locale.ru.LC_MESSAGES' 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 'django_celery_beat.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_celery_beat.locale.ru.LC_MESSAGES' 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 'django_celery_beat.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_celery_beat.locale.zh_Hans.LC_MESSAGES' 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 'django_celery_beat.locale.zh_Hans.LC_MESSAGES' 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 'django_celery_beat.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_celery_beat.locale.zh_Hans.LC_MESSAGES' 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 'django_celery_beat.templates.admin.djcelery' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_celery_beat.templates.admin.djcelery' 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 'django_celery_beat.templates.admin.djcelery' 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 'django_celery_beat.templates.admin.djcelery' to be distributed and are already explicitly excluding 'django_celery_beat.templates.admin.djcelery' 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/django_celery_beat/locale/de/LC_MESSAGES copying django_celery_beat/locale/de/LC_MESSAGES/django.mo -> build/lib/django_celery_beat/locale/de/LC_MESSAGES copying django_celery_beat/locale/de/LC_MESSAGES/django.po -> build/lib/django_celery_beat/locale/de/LC_MESSAGES creating build/lib/django_celery_beat/locale/es/LC_MESSAGES copying django_celery_beat/locale/es/LC_MESSAGES/django.mo -> build/lib/django_celery_beat/locale/es/LC_MESSAGES copying django_celery_beat/locale/es/LC_MESSAGES/django.po -> build/lib/django_celery_beat/locale/es/LC_MESSAGES creating build/lib/django_celery_beat/locale/fa/LC_MESSAGES copying django_celery_beat/locale/fa/LC_MESSAGES/django.mo -> build/lib/django_celery_beat/locale/fa/LC_MESSAGES copying django_celery_beat/locale/fa/LC_MESSAGES/django.po -> build/lib/django_celery_beat/locale/fa/LC_MESSAGES creating build/lib/django_celery_beat/locale/fr/LC_MESSAGES copying django_celery_beat/locale/fr/LC_MESSAGES/django.mo -> build/lib/django_celery_beat/locale/fr/LC_MESSAGES copying django_celery_beat/locale/fr/LC_MESSAGES/django.po -> build/lib/django_celery_beat/locale/fr/LC_MESSAGES creating build/lib/django_celery_beat/locale/ko/LC_MESSAGES copying django_celery_beat/locale/ko/LC_MESSAGES/django.mo -> build/lib/django_celery_beat/locale/ko/LC_MESSAGES copying django_celery_beat/locale/ko/LC_MESSAGES/django.po -> build/lib/django_celery_beat/locale/ko/LC_MESSAGES creating build/lib/django_celery_beat/locale/ru/LC_MESSAGES copying django_celery_beat/locale/ru/LC_MESSAGES/django.mo -> build/lib/django_celery_beat/locale/ru/LC_MESSAGES copying django_celery_beat/locale/ru/LC_MESSAGES/django.po -> build/lib/django_celery_beat/locale/ru/LC_MESSAGES creating build/lib/django_celery_beat/locale/zh_Hans/LC_MESSAGES copying django_celery_beat/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django_celery_beat/locale/zh_Hans/LC_MESSAGES copying django_celery_beat/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django_celery_beat/locale/zh_Hans/LC_MESSAGES creating build/lib/django_celery_beat/templates/admin/djcelery copying django_celery_beat/templates/admin/djcelery/change_list.html -> build/lib/django_celery_beat/templates/admin/djcelery copying django_celery_beat/templates/admin/djcelery/change_periodictask_form.html -> build/lib/django_celery_beat/templates/admin/djcelery installing to build/bdist.solaris-2.11-i86pc.64bit/wheel running install running install_lib creating build/bdist.solaris-2.11-i86pc.64bit/wheel creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat copying build/lib/django_celery_beat/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat copying build/lib/django_celery_beat/admin.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat copying build/lib/django_celery_beat/apps.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat copying build/lib/django_celery_beat/clockedschedule.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat copying build/lib/django_celery_beat/models.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat copying build/lib/django_celery_beat/querysets.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat copying build/lib/django_celery_beat/schedulers.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat copying build/lib/django_celery_beat/signals.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat copying build/lib/django_celery_beat/tzcrontab.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat copying build/lib/django_celery_beat/utils.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat copying build/lib/django_celery_beat/validators.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0001_initial.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0002_auto_20161118_0346.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0003_auto_20161209_0049.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0004_auto_20170221_0000.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0005_add_solarschedule_events_choices.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0006_auto_20180210_1226.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0006_auto_20180322_0932.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0006_periodictask_priority.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0007_auto_20180521_0826.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0008_auto_20180914_1922.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0009_periodictask_headers.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0010_auto_20190429_0326.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0011_auto_20190508_0153.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0012_periodictask_expire_seconds.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0013_auto_20200609_0727.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0014_remove_clockedschedule_enabled.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0015_edit_solarschedule_events_choices.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0016_alter_crontabschedule_timezone.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0017_alter_crontabschedule_month_of_year.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0018_improve_crontab_helptext.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/0019_alter_periodictasks_options.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations copying build/lib/django_celery_beat/migrations/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/migrations creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/locale creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/locale/de creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/locale/de/LC_MESSAGES copying build/lib/django_celery_beat/locale/de/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/locale/de/LC_MESSAGES copying build/lib/django_celery_beat/locale/de/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/locale/de/LC_MESSAGES creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/locale/es creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/locale/es/LC_MESSAGES copying build/lib/django_celery_beat/locale/es/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/locale/es/LC_MESSAGES copying build/lib/django_celery_beat/locale/es/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/locale/es/LC_MESSAGES creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/locale/fa creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/locale/fa/LC_MESSAGES copying build/lib/django_celery_beat/locale/fa/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/locale/fa/LC_MESSAGES copying build/lib/django_celery_beat/locale/fa/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/locale/fa/LC_MESSAGES creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/locale/fr creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/locale/fr/LC_MESSAGES copying build/lib/django_celery_beat/locale/fr/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/locale/fr/LC_MESSAGES copying build/lib/django_celery_beat/locale/fr/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/locale/fr/LC_MESSAGES creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/locale/ko creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/locale/ko/LC_MESSAGES copying build/lib/django_celery_beat/locale/ko/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/locale/ko/LC_MESSAGES copying build/lib/django_celery_beat/locale/ko/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/locale/ko/LC_MESSAGES creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/locale/ru creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/locale/ru/LC_MESSAGES copying build/lib/django_celery_beat/locale/ru/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/locale/ru/LC_MESSAGES copying build/lib/django_celery_beat/locale/ru/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/locale/ru/LC_MESSAGES creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/locale/zh_Hans creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/locale/zh_Hans/LC_MESSAGES copying build/lib/django_celery_beat/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/locale/zh_Hans/LC_MESSAGES copying build/lib/django_celery_beat/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/locale/zh_Hans/LC_MESSAGES creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/templates creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/templates/admin creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat/templates/admin/djcelery copying build/lib/django_celery_beat/templates/admin/djcelery/change_list.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/templates/admin/djcelery copying build/lib/django_celery_beat/templates/admin/djcelery/change_periodictask_form.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat/templates/admin/djcelery running install_egg_info Copying django_celery_beat.egg-info to build/bdist.solaris-2.11-i86pc.64bit/wheel/./django_celery_beat-2.8.0-py3.11.egg-info running install_scripts creating build/bdist.solaris-2.11-i86pc.64bit/wheel/django_celery_beat-2.8.0.dist-info/WHEEL creating '/tmp/work/www/py-django-celery-beat/work/django_celery_beat-2.8.0/dist/.tmp-4bmdc0yo/django_celery_beat-2.8.0-py3-none-any.whl' and adding 'build/bdist.solaris-2.11-i86pc.64bit/wheel' to it adding 'django_celery_beat/__init__.py' adding 'django_celery_beat/admin.py' adding 'django_celery_beat/apps.py' adding 'django_celery_beat/clockedschedule.py' adding 'django_celery_beat/models.py' adding 'django_celery_beat/querysets.py' adding 'django_celery_beat/schedulers.py' adding 'django_celery_beat/signals.py' adding 'django_celery_beat/tzcrontab.py' adding 'django_celery_beat/utils.py' adding 'django_celery_beat/validators.py' adding 'django_celery_beat/locale/de/LC_MESSAGES/django.mo' adding 'django_celery_beat/locale/de/LC_MESSAGES/django.po' adding 'django_celery_beat/locale/es/LC_MESSAGES/django.mo' adding 'django_celery_beat/locale/es/LC_MESSAGES/django.po' adding 'django_celery_beat/locale/fa/LC_MESSAGES/django.mo' adding 'django_celery_beat/locale/fa/LC_MESSAGES/django.po' adding 'django_celery_beat/locale/fr/LC_MESSAGES/django.mo' adding 'django_celery_beat/locale/fr/LC_MESSAGES/django.po' adding 'django_celery_beat/locale/ko/LC_MESSAGES/django.mo' adding 'django_celery_beat/locale/ko/LC_MESSAGES/django.po' adding 'django_celery_beat/locale/ru/LC_MESSAGES/django.mo' adding 'django_celery_beat/locale/ru/LC_MESSAGES/django.po' adding 'django_celery_beat/locale/zh_Hans/LC_MESSAGES/django.mo' adding 'django_celery_beat/locale/zh_Hans/LC_MESSAGES/django.po' adding 'django_celery_beat/migrations/0001_initial.py' adding 'django_celery_beat/migrations/0002_auto_20161118_0346.py' adding 'django_celery_beat/migrations/0003_auto_20161209_0049.py' adding 'django_celery_beat/migrations/0004_auto_20170221_0000.py' adding 'django_celery_beat/migrations/0005_add_solarschedule_events_choices.py' adding 'django_celery_beat/migrations/0006_auto_20180210_1226.py' adding 'django_celery_beat/migrations/0006_auto_20180322_0932.py' adding 'django_celery_beat/migrations/0006_periodictask_priority.py' adding 'django_celery_beat/migrations/0007_auto_20180521_0826.py' adding 'django_celery_beat/migrations/0008_auto_20180914_1922.py' adding 'django_celery_beat/migrations/0009_periodictask_headers.py' adding 'django_celery_beat/migrations/0010_auto_20190429_0326.py' adding 'django_celery_beat/migrations/0011_auto_20190508_0153.py' adding 'django_celery_beat/migrations/0012_periodictask_expire_seconds.py' adding 'django_celery_beat/migrations/0013_auto_20200609_0727.py' adding 'django_celery_beat/migrations/0014_remove_clockedschedule_enabled.py' adding 'django_celery_beat/migrations/0015_edit_solarschedule_events_choices.py' adding 'django_celery_beat/migrations/0016_alter_crontabschedule_timezone.py' adding 'django_celery_beat/migrations/0017_alter_crontabschedule_month_of_year.py' adding 'django_celery_beat/migrations/0018_improve_crontab_helptext.py' adding 'django_celery_beat/migrations/0019_alter_periodictasks_options.py' adding 'django_celery_beat/migrations/__init__.py' adding 'django_celery_beat/templates/admin/djcelery/change_list.html' adding 'django_celery_beat/templates/admin/djcelery/change_periodictask_form.html' adding 'django_celery_beat-2.8.0.dist-info/licenses/AUTHORS' adding 'django_celery_beat-2.8.0.dist-info/licenses/LICENSE' adding 'django_celery_beat-2.8.0.dist-info/METADATA' adding 'django_celery_beat-2.8.0.dist-info/WHEEL' adding 'django_celery_beat-2.8.0.dist-info/entry_points.txt' adding 'django_celery_beat-2.8.0.dist-info/top_level.txt' adding 'django_celery_beat-2.8.0.dist-info/RECORD' removing build/bdist.solaris-2.11-i86pc.64bit/wheel Successfully built django_celery_beat-2.8.0-py3-none-any.whl