>>> py3-django: Building community/py3-django 4.2.20-r0 (using abuild 3.15.0_rc3-r1) started Tue, 22 Apr 2025 17:58:49 +0000
>>> py3-django: Validating /home/buildozer/aports/community/py3-django/APKBUILD...
>>> py3-django: Analyzing dependencies...
>>> py3-django: Installing for build: build-base python3 py3-asgiref py3-sqlparse tzdata py3-gpep517 py3-setuptools py3-wheel
(1/29) Installing libbz2 (1.0.8-r6)
(2/29) Installing libffi (3.4.8-r0)
(3/29) Installing gdbm (1.24-r0)
(4/29) Installing xz-libs (5.8.1-r0)
(5/29) Installing mpdecimal (4.0.0-r0)
(6/29) Installing libpanelw (6.5_p20250412-r0)
(7/29) Installing sqlite-libs (3.49.1-r0)
(8/29) Installing python3 (3.12.10-r0)
(9/29) Installing python3-pycache-pyc0 (3.12.10-r0)
(10/29) Installing pyc (3.12.10-r0)
(11/29) Installing python3-pyc (3.12.10-r0)
(12/29) Installing py3-asgiref (3.8.1-r1)
(13/29) Installing py3-asgiref-pyc (3.8.1-r1)
(14/29) Installing py3-sqlparse (0.5.1-r0)
(15/29) Installing py3-sqlparse-pyc (0.5.1-r0)
(16/29) Installing tzdata (2025b-r0)
(17/29) Installing py3-installer (0.7.0-r2)
(18/29) Installing py3-installer-pyc (0.7.0-r2)
(19/29) Installing py3-gpep517 (16-r0)
(20/29) Installing py3-gpep517-pyc (16-r0)
(21/29) Installing py3-parsing (3.2.0-r0)
(22/29) Installing py3-parsing-pyc (3.2.0-r0)
(23/29) Installing py3-packaging (24.2-r0)
(24/29) Installing py3-packaging-pyc (24.2-r0)
(25/29) Installing py3-setuptools (77.0.3-r0)
(26/29) Installing py3-setuptools-pyc (77.0.3-r0)
(27/29) Installing py3-wheel (0.43.0-r0)
(28/29) Installing py3-wheel-pyc (0.43.0-r0)
(29/29) Installing .makedepends-py3-django (20250422.175850)
Executing busybox-1.37.0-r16.trigger
OK: 319 MiB in 133 packages
>>> py3-django: Cleaning up srcdir
>>> py3-django: Cleaning up pkgdir
>>> py3-django: Cleaning up tmpdir
>>> py3-django: Fetching https://distfiles.alpinelinux.org/distfiles/edge/Django-4.2.20.tar.gz
>>> py3-django: Fetching https://distfiles.alpinelinux.org/distfiles/edge/Django-4.2.20.tar.gz
>>> py3-django: Checking sha512sums...
Django-4.2.20.tar.gz: OK
>>> py3-django: Unpacking /var/cache/distfiles/edge/Django-4.2.20.tar.gz...
2025-04-22 17:58:52,843 gpep517 INFO Building wheel via backend setuptools.build_meta
/usr/lib/python3.12/site-packages/setuptools/dist.py:760: 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()
2025-04-22 17:58:52,912 root INFO running bdist_wheel
2025-04-22 17:58:52,928 root INFO running build
2025-04-22 17:58:52,928 root INFO running build_py
2025-04-22 17:58:52,932 root INFO creating build/lib/django
2025-04-22 17:58:52,932 root INFO copying django/__init__.py -> build/lib/django
2025-04-22 17:58:52,933 root INFO copying django/__main__.py -> build/lib/django
2025-04-22 17:58:52,933 root INFO copying django/shortcuts.py -> build/lib/django
2025-04-22 17:58:52,933 root INFO creating build/lib/django/db
2025-04-22 17:58:52,934 root INFO copying django/db/__init__.py -> build/lib/django/db
2025-04-22 17:58:52,934 root INFO copying django/db/utils.py -> build/lib/django/db
2025-04-22 17:58:52,934 root INFO copying django/db/transaction.py -> build/lib/django/db
2025-04-22 17:58:52,935 root INFO creating build/lib/django/views
2025-04-22 17:58:52,935 root INFO copying django/views/__init__.py -> build/lib/django/views
2025-04-22 17:58:52,935 root INFO copying django/views/i18n.py -> build/lib/django/views
2025-04-22 17:58:52,935 root INFO copying django/views/defaults.py -> build/lib/django/views
2025-04-22 17:58:52,936 root INFO copying django/views/csrf.py -> build/lib/django/views
2025-04-22 17:58:52,936 root INFO copying django/views/static.py -> build/lib/django/views
2025-04-22 17:58:52,936 root INFO copying django/views/debug.py -> build/lib/django/views
2025-04-22 17:58:52,937 root INFO creating build/lib/django/middleware
2025-04-22 17:58:52,937 root INFO copying django/middleware/__init__.py -> build/lib/django/middleware
2025-04-22 17:58:52,937 root INFO copying django/middleware/locale.py -> build/lib/django/middleware
2025-04-22 17:58:52,937 root INFO copying django/middleware/cache.py -> build/lib/django/middleware
2025-04-22 17:58:52,938 root INFO copying django/middleware/http.py -> build/lib/django/middleware
2025-04-22 17:58:52,938 root INFO copying django/middleware/security.py -> build/lib/django/middleware
2025-04-22 17:58:52,938 root INFO copying django/middleware/gzip.py -> build/lib/django/middleware
2025-04-22 17:58:52,939 root INFO copying django/middleware/csrf.py -> build/lib/django/middleware
2025-04-22 17:58:52,939 root INFO copying django/middleware/clickjacking.py -> build/lib/django/middleware
2025-04-22 17:58:52,939 root INFO copying django/middleware/common.py -> build/lib/django/middleware
2025-04-22 17:58:52,939 root INFO creating build/lib/django/http
2025-04-22 17:58:52,940 root INFO copying django/http/__init__.py -> build/lib/django/http
2025-04-22 17:58:52,940 root INFO copying django/http/response.py -> build/lib/django/http
2025-04-22 17:58:52,940 root INFO copying django/http/multipartparser.py -> build/lib/django/http
2025-04-22 17:58:52,941 root INFO copying django/http/cookie.py -> build/lib/django/http
2025-04-22 17:58:52,941 root INFO copying django/http/request.py -> build/lib/django/http
2025-04-22 17:58:52,941 root INFO creating build/lib/django/dispatch
2025-04-22 17:58:52,941 root INFO copying django/dispatch/__init__.py -> build/lib/django/dispatch
2025-04-22 17:58:52,942 root INFO copying django/dispatch/dispatcher.py -> build/lib/django/dispatch
2025-04-22 17:58:52,942 root INFO creating build/lib/django/urls
2025-04-22 17:58:52,942 root INFO copying django/urls/__init__.py -> build/lib/django/urls
2025-04-22 17:58:52,943 root INFO copying django/urls/converters.py -> build/lib/django/urls
2025-04-22 17:58:52,943 root INFO copying django/urls/exceptions.py -> build/lib/django/urls
2025-04-22 17:58:52,943 root INFO copying django/urls/conf.py -> build/lib/django/urls
2025-04-22 17:58:52,943 root INFO copying django/urls/utils.py -> build/lib/django/urls
2025-04-22 17:58:52,944 root INFO copying django/urls/resolvers.py -> build/lib/django/urls
2025-04-22 17:58:52,944 root INFO copying django/urls/base.py -> build/lib/django/urls
2025-04-22 17:58:52,945 root INFO creating build/lib/django/template
2025-04-22 17:58:52,945 root INFO copying django/template/__init__.py -> build/lib/django/template
2025-04-22 17:58:52,945 root INFO copying django/template/library.py -> build/lib/django/template
2025-04-22 17:58:52,945 root INFO copying django/template/engine.py -> build/lib/django/template
2025-04-22 17:58:52,946 root INFO copying django/template/response.py -> build/lib/django/template
2025-04-22 17:58:52,946 root INFO copying django/template/loader_tags.py -> build/lib/django/template
2025-04-22 17:58:52,946 root INFO copying django/template/loader.py -> build/lib/django/template
2025-04-22 17:58:52,946 root INFO copying django/template/autoreload.py -> build/lib/django/template
2025-04-22 17:58:52,947 root INFO copying django/template/exceptions.py -> build/lib/django/template
2025-04-22 17:58:52,947 root INFO copying django/template/smartif.py -> build/lib/django/template
2025-04-22 17:58:52,947 root INFO copying django/template/defaulttags.py -> build/lib/django/template
2025-04-22 17:58:52,948 root INFO copying django/template/context.py -> build/lib/django/template
2025-04-22 17:58:52,948 root INFO copying django/template/utils.py -> build/lib/django/template
2025-04-22 17:58:52,948 root INFO copying django/template/defaultfilters.py -> build/lib/django/template
2025-04-22 17:58:52,948 root INFO copying django/template/context_processors.py -> build/lib/django/template
2025-04-22 17:58:52,949 root INFO copying django/template/base.py -> build/lib/django/template
2025-04-22 17:58:52,949 root INFO creating build/lib/django/conf
2025-04-22 17:58:52,949 root INFO copying django/conf/__init__.py -> build/lib/django/conf
2025-04-22 17:58:52,950 root INFO copying django/conf/global_settings.py -> build/lib/django/conf
2025-04-22 17:58:52,950 root INFO creating build/lib/django/utils
2025-04-22 17:58:52,951 root INFO copying django/utils/datetime_safe.py -> build/lib/django/utils
2025-04-22 17:58:52,951 root INFO copying django/utils/__init__.py -> build/lib/django/utils
2025-04-22 17:58:52,951 root INFO copying django/utils/itercompat.py -> build/lib/django/utils
2025-04-22 17:58:52,951 root INFO copying django/utils/functional.py -> build/lib/django/utils
2025-04-22 17:58:52,952 root INFO copying django/utils/hashable.py -> build/lib/django/utils
2025-04-22 17:58:52,952 root INFO copying django/utils/log.py -> build/lib/django/utils
2025-04-22 17:58:52,952 root INFO copying django/utils/_os.py -> build/lib/django/utils
2025-04-22 17:58:52,952 root INFO copying django/utils/dateparse.py -> build/lib/django/utils
2025-04-22 17:58:52,953 root INFO copying django/utils/decorators.py -> build/lib/django/utils
2025-04-22 17:58:52,953 root INFO copying django/utils/topological_sort.py -> build/lib/django/utils
2025-04-22 17:58:52,953 root INFO copying django/utils/deprecation.py -> build/lib/django/utils
2025-04-22 17:58:52,953 root INFO copying django/utils/formats.py -> build/lib/django/utils
2025-04-22 17:58:52,954 root INFO copying django/utils/autoreload.py -> build/lib/django/utils
2025-04-22 17:58:52,954 root INFO copying django/utils/timezone.py -> build/lib/django/utils
2025-04-22 17:58:52,954 root INFO copying django/utils/timesince.py -> build/lib/django/utils
2025-04-22 17:58:52,954 root INFO copying django/utils/cache.py -> build/lib/django/utils
2025-04-22 17:58:52,955 root INFO copying django/utils/version.py -> build/lib/django/utils
2025-04-22 17:58:52,955 root INFO copying django/utils/datastructures.py -> build/lib/django/utils
2025-04-22 17:58:52,955 root INFO copying django/utils/dateformat.py -> build/lib/django/utils
2025-04-22 17:58:52,955 root INFO copying django/utils/html.py -> build/lib/django/utils
2025-04-22 17:58:52,956 root INFO copying django/utils/termcolors.py -> build/lib/django/utils
2025-04-22 17:58:52,956 root INFO copying django/utils/tree.py -> build/lib/django/utils
2025-04-22 17:58:52,956 root INFO copying django/utils/http.py -> build/lib/django/utils
2025-04-22 17:58:52,956 root INFO copying django/utils/ipv6.py -> build/lib/django/utils
2025-04-22 17:58:52,957 root INFO copying django/utils/asyncio.py -> build/lib/django/utils
2025-04-22 17:58:52,957 root INFO copying django/utils/connection.py -> build/lib/django/utils
2025-04-22 17:58:52,957 root INFO copying django/utils/lorem_ipsum.py -> build/lib/django/utils
2025-04-22 17:58:52,957 root INFO copying django/utils/baseconv.py -> build/lib/django/utils
2025-04-22 17:58:52,958 root INFO copying django/utils/numberformat.py -> build/lib/django/utils
2025-04-22 17:58:52,958 root INFO copying django/utils/inspect.py -> build/lib/django/utils
2025-04-22 17:58:52,958 root INFO copying django/utils/feedgenerator.py -> build/lib/django/utils
2025-04-22 17:58:52,958 root INFO copying django/utils/duration.py -> build/lib/django/utils
2025-04-22 17:58:52,959 root INFO copying django/utils/deconstruct.py -> build/lib/django/utils
2025-04-22 17:58:52,959 root INFO copying django/utils/safestring.py -> build/lib/django/utils
2025-04-22 17:58:52,959 root INFO copying django/utils/module_loading.py -> build/lib/django/utils
2025-04-22 17:58:52,959 root INFO copying django/utils/archive.py -> build/lib/django/utils
2025-04-22 17:58:52,960 root INFO copying django/utils/crypto.py -> build/lib/django/utils
2025-04-22 17:58:52,960 root INFO copying django/utils/regex_helper.py -> build/lib/django/utils
2025-04-22 17:58:52,960 root INFO copying django/utils/dates.py -> build/lib/django/utils
2025-04-22 17:58:52,960 root INFO copying django/utils/xmlutils.py -> build/lib/django/utils
2025-04-22 17:58:52,961 root INFO copying django/utils/encoding.py -> build/lib/django/utils
2025-04-22 17:58:52,961 root INFO copying django/utils/jslex.py -> build/lib/django/utils
2025-04-22 17:58:52,961 root INFO copying django/utils/text.py -> build/lib/django/utils
2025-04-22 17:58:52,961 root INFO creating build/lib/django/templatetags
2025-04-22 17:58:52,962 root INFO copying django/templatetags/__init__.py -> build/lib/django/templatetags
2025-04-22 17:58:52,962 root INFO copying django/templatetags/tz.py -> build/lib/django/templatetags
2025-04-22 17:58:52,962 root INFO copying django/templatetags/i18n.py -> build/lib/django/templatetags
2025-04-22 17:58:52,962 root INFO copying django/templatetags/cache.py -> build/lib/django/templatetags
2025-04-22 17:58:52,963 root INFO copying django/templatetags/static.py -> build/lib/django/templatetags
2025-04-22 17:58:52,963 root INFO copying django/templatetags/l10n.py -> build/lib/django/templatetags
2025-04-22 17:58:52,963 root INFO creating build/lib/django/test
2025-04-22 17:58:52,963 root INFO copying django/test/__init__.py -> build/lib/django/test
2025-04-22 17:58:52,964 root INFO copying django/test/signals.py -> build/lib/django/test
2025-04-22 17:58:52,964 root INFO copying django/test/selenium.py -> build/lib/django/test
2025-04-22 17:58:52,964 root INFO copying django/test/testcases.py -> build/lib/django/test
2025-04-22 17:58:52,965 root INFO copying django/test/html.py -> build/lib/django/test
2025-04-22 17:58:52,965 root INFO copying django/test/utils.py -> build/lib/django/test
2025-04-22 17:58:52,965 root INFO copying django/test/runner.py -> build/lib/django/test
2025-04-22 17:58:52,965 root INFO copying django/test/client.py -> build/lib/django/test
2025-04-22 17:58:52,966 root INFO creating build/lib/django/core
2025-04-22 17:58:52,966 root INFO copying django/core/__init__.py -> build/lib/django/core
2025-04-22 17:58:52,966 root INFO copying django/core/signals.py -> build/lib/django/core
2025-04-22 17:58:52,967 root INFO copying django/core/asgi.py -> build/lib/django/core
2025-04-22 17:58:52,967 root INFO copying django/core/validators.py -> build/lib/django/core
2025-04-22 17:58:52,967 root INFO copying django/core/exceptions.py -> build/lib/django/core
2025-04-22 17:58:52,967 root INFO copying django/core/paginator.py -> build/lib/django/core
2025-04-22 17:58:52,968 root INFO copying django/core/wsgi.py -> build/lib/django/core
2025-04-22 17:58:52,968 root INFO copying django/core/signing.py -> build/lib/django/core
2025-04-22 17:58:52,968 root INFO creating build/lib/django/contrib
2025-04-22 17:58:52,968 root INFO copying django/contrib/__init__.py -> build/lib/django/contrib
2025-04-22 17:58:52,969 root INFO creating build/lib/django/forms
2025-04-22 17:58:52,969 root INFO copying django/forms/__init__.py -> build/lib/django/forms
2025-04-22 17:58:52,969 root INFO copying django/forms/widgets.py -> build/lib/django/forms
2025-04-22 17:58:52,970 root INFO copying django/forms/forms.py -> build/lib/django/forms
2025-04-22 17:58:52,970 root INFO copying django/forms/models.py -> build/lib/django/forms
2025-04-22 17:58:52,970 root INFO copying django/forms/utils.py -> build/lib/django/forms
2025-04-22 17:58:52,970 root INFO copying django/forms/renderers.py -> build/lib/django/forms
2025-04-22 17:58:52,971 root INFO copying django/forms/fields.py -> build/lib/django/forms
2025-04-22 17:58:52,971 root INFO copying django/forms/boundfield.py -> build/lib/django/forms
2025-04-22 17:58:52,971 root INFO copying django/forms/formsets.py -> build/lib/django/forms
2025-04-22 17:58:52,972 root INFO creating build/lib/django/apps
2025-04-22 17:58:52,972 root INFO copying django/apps/__init__.py -> build/lib/django/apps
2025-04-22 17:58:52,972 root INFO copying django/apps/registry.py -> build/lib/django/apps
2025-04-22 17:58:52,972 root INFO copying django/apps/config.py -> build/lib/django/apps
2025-04-22 17:58:52,973 root INFO creating build/lib/django/db/models
2025-04-22 17:58:52,973 root INFO copying django/db/models/__init__.py -> build/lib/django/db/models
2025-04-22 17:58:52,973 root INFO copying django/db/models/options.py -> build/lib/django/db/models
2025-04-22 17:58:52,974 root INFO copying django/db/models/enums.py -> build/lib/django/db/models
2025-04-22 17:58:52,974 root INFO copying django/db/models/signals.py -> build/lib/django/db/models
2025-04-22 17:58:52,974 root INFO copying django/db/models/query.py -> build/lib/django/db/models
2025-04-22 17:58:52,975 root INFO copying django/db/models/lookups.py -> build/lib/django/db/models
2025-04-22 17:58:52,975 root INFO copying django/db/models/manager.py -> build/lib/django/db/models
2025-04-22 17:58:52,975 root INFO copying django/db/models/indexes.py -> build/lib/django/db/models
2025-04-22 17:58:52,975 root INFO copying django/db/models/utils.py -> build/lib/django/db/models
2025-04-22 17:58:52,976 root INFO copying django/db/models/deletion.py -> build/lib/django/db/models
2025-04-22 17:58:52,976 root INFO copying django/db/models/expressions.py -> build/lib/django/db/models
2025-04-22 17:58:52,976 root INFO copying django/db/models/constraints.py -> build/lib/django/db/models
2025-04-22 17:58:52,977 root INFO copying django/db/models/query_utils.py -> build/lib/django/db/models
2025-04-22 17:58:52,977 root INFO copying django/db/models/constants.py -> build/lib/django/db/models
2025-04-22 17:58:52,977 root INFO copying django/db/models/base.py -> build/lib/django/db/models
2025-04-22 17:58:52,977 root INFO copying django/db/models/aggregates.py -> build/lib/django/db/models
2025-04-22 17:58:52,978 root INFO creating build/lib/django/db/migrations
2025-04-22 17:58:52,978 root INFO copying django/db/migrations/__init__.py -> build/lib/django/db/migrations
2025-04-22 17:58:52,978 root INFO copying django/db/migrations/state.py -> build/lib/django/db/migrations
2025-04-22 17:58:52,979 root INFO copying django/db/migrations/graph.py -> build/lib/django/db/migrations
2025-04-22 17:58:52,979 root INFO copying django/db/migrations/writer.py -> build/lib/django/db/migrations
2025-04-22 17:58:52,979 root INFO copying django/db/migrations/serializer.py -> build/lib/django/db/migrations
2025-04-22 17:58:52,979 root INFO copying django/db/migrations/loader.py -> build/lib/django/db/migrations
2025-04-22 17:58:52,980 root INFO copying django/db/migrations/executor.py -> build/lib/django/db/migrations
2025-04-22 17:58:52,980 root INFO copying django/db/migrations/exceptions.py -> build/lib/django/db/migrations
2025-04-22 17:58:52,980 root INFO copying django/db/migrations/optimizer.py -> build/lib/django/db/migrations
2025-04-22 17:58:52,980 root INFO copying django/db/migrations/utils.py -> build/lib/django/db/migrations
2025-04-22 17:58:52,981 root INFO copying django/db/migrations/recorder.py -> build/lib/django/db/migrations
2025-04-22 17:58:52,981 root INFO copying django/db/migrations/migration.py -> build/lib/django/db/migrations
2025-04-22 17:58:52,981 root INFO copying django/db/migrations/autodetector.py -> build/lib/django/db/migrations
2025-04-22 17:58:52,982 root INFO copying django/db/migrations/questioner.py -> build/lib/django/db/migrations
2025-04-22 17:58:52,982 root INFO creating build/lib/django/db/backends
2025-04-22 17:58:52,982 root INFO copying django/db/backends/__init__.py -> build/lib/django/db/backends
2025-04-22 17:58:52,982 root INFO copying django/db/backends/signals.py -> build/lib/django/db/backends
2025-04-22 17:58:52,983 root INFO copying django/db/backends/ddl_references.py -> build/lib/django/db/backends
2025-04-22 17:58:52,983 root INFO copying django/db/backends/utils.py -> build/lib/django/db/backends
2025-04-22 17:58:52,984 root INFO creating build/lib/django/db/models/functions
2025-04-22 17:58:52,984 root INFO copying django/db/models/functions/__init__.py -> build/lib/django/db/models/functions
2025-04-22 17:58:52,984 root INFO copying django/db/models/functions/datetime.py -> build/lib/django/db/models/functions
2025-04-22 17:58:52,984 root INFO copying django/db/models/functions/window.py -> build/lib/django/db/models/functions
2025-04-22 17:58:52,985 root INFO copying django/db/models/functions/comparison.py -> build/lib/django/db/models/functions
2025-04-22 17:58:52,985 root INFO copying django/db/models/functions/math.py -> build/lib/django/db/models/functions
2025-04-22 17:58:52,985 root INFO copying django/db/models/functions/text.py -> build/lib/django/db/models/functions
2025-04-22 17:58:52,985 root INFO copying django/db/models/functions/mixins.py -> build/lib/django/db/models/functions
2025-04-22 17:58:52,986 root INFO creating build/lib/django/db/models/sql
2025-04-22 17:58:52,986 root INFO copying django/db/models/sql/__init__.py -> build/lib/django/db/models/sql
2025-04-22 17:58:52,987 root INFO copying django/db/models/sql/query.py -> build/lib/django/db/models/sql
2025-04-22 17:58:52,987 root INFO copying django/db/models/sql/compiler.py -> build/lib/django/db/models/sql
2025-04-22 17:58:52,987 root INFO copying django/db/models/sql/subqueries.py -> build/lib/django/db/models/sql
2025-04-22 17:58:52,988 root INFO copying django/db/models/sql/datastructures.py -> build/lib/django/db/models/sql
2025-04-22 17:58:52,988 root INFO copying django/db/models/sql/where.py -> build/lib/django/db/models/sql
2025-04-22 17:58:52,988 root INFO copying django/db/models/sql/constants.py -> build/lib/django/db/models/sql
2025-04-22 17:58:52,989 root INFO creating build/lib/django/db/models/fields
2025-04-22 17:58:52,989 root INFO copying django/db/models/fields/__init__.py -> build/lib/django/db/models/fields
2025-04-22 17:58:52,990 root INFO copying django/db/models/fields/related_descriptors.py -> build/lib/django/db/models/fields
2025-04-22 17:58:52,990 root INFO copying django/db/models/fields/json.py -> build/lib/django/db/models/fields
2025-04-22 17:58:52,990 root INFO copying django/db/models/fields/related_lookups.py -> build/lib/django/db/models/fields
2025-04-22 17:58:52,991 root INFO copying django/db/models/fields/proxy.py -> build/lib/django/db/models/fields
2025-04-22 17:58:52,991 root INFO copying django/db/models/fields/reverse_related.py -> build/lib/django/db/models/fields
2025-04-22 17:58:52,991 root INFO copying django/db/models/fields/files.py -> build/lib/django/db/models/fields
2025-04-22 17:58:52,991 root INFO copying django/db/models/fields/related.py -> build/lib/django/db/models/fields
2025-04-22 17:58:52,992 root INFO copying django/db/models/fields/mixins.py -> build/lib/django/db/models/fields
2025-04-22 17:58:52,992 root INFO creating build/lib/django/db/migrations/operations
2025-04-22 17:58:52,993 root INFO copying django/db/migrations/operations/__init__.py -> build/lib/django/db/migrations/operations
2025-04-22 17:58:52,993 root INFO copying django/db/migrations/operations/models.py -> build/lib/django/db/migrations/operations
2025-04-22 17:58:52,993 root INFO copying django/db/migrations/operations/fields.py -> build/lib/django/db/migrations/operations
2025-04-22 17:58:52,993 root INFO copying django/db/migrations/operations/special.py -> build/lib/django/db/migrations/operations
2025-04-22 17:58:52,994 root INFO copying django/db/migrations/operations/base.py -> build/lib/django/db/migrations/operations
2025-04-22 17:58:52,994 root INFO creating build/lib/django/db/backends/base
2025-04-22 17:58:52,994 root INFO copying django/db/backends/base/__init__.py -> build/lib/django/db/backends/base
2025-04-22 17:58:52,995 root INFO copying django/db/backends/base/schema.py -> build/lib/django/db/backends/base
2025-04-22 17:58:52,995 root INFO copying django/db/backends/base/features.py -> build/lib/django/db/backends/base
2025-04-22 17:58:52,995 root INFO copying django/db/backends/base/operations.py -> build/lib/django/db/backends/base
2025-04-22 17:58:52,995 root INFO copying django/db/backends/base/validation.py -> build/lib/django/db/backends/base
2025-04-22 17:58:52,996 root INFO copying django/db/backends/base/creation.py -> build/lib/django/db/backends/base
2025-04-22 17:58:52,996 root INFO copying django/db/backends/base/introspection.py -> build/lib/django/db/backends/base
2025-04-22 17:58:52,996 root INFO copying django/db/backends/base/base.py -> build/lib/django/db/backends/base
2025-04-22 17:58:52,997 root INFO copying django/db/backends/base/client.py -> build/lib/django/db/backends/base
2025-04-22 17:58:52,997 root INFO creating build/lib/django/db/backends/postgresql
2025-04-22 17:58:52,997 root INFO copying django/db/backends/postgresql/__init__.py -> build/lib/django/db/backends/postgresql
2025-04-22 17:58:52,997 root INFO copying django/db/backends/postgresql/schema.py -> build/lib/django/db/backends/postgresql
2025-04-22 17:58:52,998 root INFO copying django/db/backends/postgresql/features.py -> build/lib/django/db/backends/postgresql
2025-04-22 17:58:52,998 root INFO copying django/db/backends/postgresql/operations.py -> build/lib/django/db/backends/postgresql
2025-04-22 17:58:52,998 root INFO copying django/db/backends/postgresql/psycopg_any.py -> build/lib/django/db/backends/postgresql
2025-04-22 17:58:52,998 root INFO copying django/db/backends/postgresql/creation.py -> build/lib/django/db/backends/postgresql
2025-04-22 17:58:52,999 root INFO copying django/db/backends/postgresql/introspection.py -> build/lib/django/db/backends/postgresql
2025-04-22 17:58:52,999 root INFO copying django/db/backends/postgresql/base.py -> build/lib/django/db/backends/postgresql
2025-04-22 17:58:52,999 root INFO copying django/db/backends/postgresql/client.py -> build/lib/django/db/backends/postgresql
2025-04-22 17:58:53,000 root INFO creating build/lib/django/db/backends/dummy
2025-04-22 17:58:53,000 root INFO copying django/db/backends/dummy/__init__.py -> build/lib/django/db/backends/dummy
2025-04-22 17:58:53,000 root INFO copying django/db/backends/dummy/features.py -> build/lib/django/db/backends/dummy
2025-04-22 17:58:53,000 root INFO copying django/db/backends/dummy/base.py -> build/lib/django/db/backends/dummy
2025-04-22 17:58:53,001 root INFO creating build/lib/django/db/backends/sqlite3
2025-04-22 17:58:53,001 root INFO copying django/db/backends/sqlite3/__init__.py -> build/lib/django/db/backends/sqlite3
2025-04-22 17:58:53,001 root INFO copying django/db/backends/sqlite3/schema.py -> build/lib/django/db/backends/sqlite3
2025-04-22 17:58:53,001 root INFO copying django/db/backends/sqlite3/features.py -> build/lib/django/db/backends/sqlite3
2025-04-22 17:58:53,002 root INFO copying django/db/backends/sqlite3/operations.py -> build/lib/django/db/backends/sqlite3
2025-04-22 17:58:53,002 root INFO copying django/db/backends/sqlite3/creation.py -> build/lib/django/db/backends/sqlite3
2025-04-22 17:58:53,002 root INFO copying django/db/backends/sqlite3/introspection.py -> build/lib/django/db/backends/sqlite3
2025-04-22 17:58:53,003 root INFO copying django/db/backends/sqlite3/_functions.py -> build/lib/django/db/backends/sqlite3
2025-04-22 17:58:53,003 root INFO copying django/db/backends/sqlite3/base.py -> build/lib/django/db/backends/sqlite3
2025-04-22 17:58:53,003 root INFO copying django/db/backends/sqlite3/client.py -> build/lib/django/db/backends/sqlite3
2025-04-22 17:58:53,004 root INFO creating build/lib/django/db/backends/oracle
2025-04-22 17:58:53,004 root INFO copying django/db/backends/oracle/__init__.py -> build/lib/django/db/backends/oracle
2025-04-22 17:58:53,004 root INFO copying django/db/backends/oracle/functions.py -> build/lib/django/db/backends/oracle
2025-04-22 17:58:53,004 root INFO copying django/db/backends/oracle/schema.py -> build/lib/django/db/backends/oracle
2025-04-22 17:58:53,004 root INFO copying django/db/backends/oracle/features.py -> build/lib/django/db/backends/oracle
2025-04-22 17:58:53,005 root INFO copying django/db/backends/oracle/operations.py -> build/lib/django/db/backends/oracle
2025-04-22 17:58:53,005 root INFO copying django/db/backends/oracle/utils.py -> build/lib/django/db/backends/oracle
2025-04-22 17:58:53,005 root INFO copying django/db/backends/oracle/validation.py -> build/lib/django/db/backends/oracle
2025-04-22 17:58:53,006 root INFO copying django/db/backends/oracle/creation.py -> build/lib/django/db/backends/oracle
2025-04-22 17:58:53,006 root INFO copying django/db/backends/oracle/introspection.py -> build/lib/django/db/backends/oracle
2025-04-22 17:58:53,006 root INFO copying django/db/backends/oracle/base.py -> build/lib/django/db/backends/oracle
2025-04-22 17:58:53,006 root INFO copying django/db/backends/oracle/client.py -> build/lib/django/db/backends/oracle
2025-04-22 17:58:53,007 root INFO creating build/lib/django/db/backends/mysql
2025-04-22 17:58:53,007 root INFO copying django/db/backends/mysql/__init__.py -> build/lib/django/db/backends/mysql
2025-04-22 17:58:53,007 root INFO copying django/db/backends/mysql/compiler.py -> build/lib/django/db/backends/mysql
2025-04-22 17:58:53,007 root INFO copying django/db/backends/mysql/schema.py -> build/lib/django/db/backends/mysql
2025-04-22 17:58:53,008 root INFO copying django/db/backends/mysql/features.py -> build/lib/django/db/backends/mysql
2025-04-22 17:58:53,008 root INFO copying django/db/backends/mysql/operations.py -> build/lib/django/db/backends/mysql
2025-04-22 17:58:53,008 root INFO copying django/db/backends/mysql/validation.py -> build/lib/django/db/backends/mysql
2025-04-22 17:58:53,009 root INFO copying django/db/backends/mysql/creation.py -> build/lib/django/db/backends/mysql
2025-04-22 17:58:53,009 root INFO copying django/db/backends/mysql/introspection.py -> build/lib/django/db/backends/mysql
2025-04-22 17:58:53,009 root INFO copying django/db/backends/mysql/base.py -> build/lib/django/db/backends/mysql
2025-04-22 17:58:53,009 root INFO copying django/db/backends/mysql/client.py -> build/lib/django/db/backends/mysql
2025-04-22 17:58:53,010 root INFO creating build/lib/django/views/generic
2025-04-22 17:58:53,010 root INFO copying django/views/generic/__init__.py -> build/lib/django/views/generic
2025-04-22 17:58:53,010 root INFO copying django/views/generic/list.py -> build/lib/django/views/generic
2025-04-22 17:58:53,010 root INFO copying django/views/generic/detail.py -> build/lib/django/views/generic
2025-04-22 17:58:53,011 root INFO copying django/views/generic/base.py -> build/lib/django/views/generic
2025-04-22 17:58:53,011 root INFO copying django/views/generic/dates.py -> build/lib/django/views/generic
2025-04-22 17:58:53,011 root INFO copying django/views/generic/edit.py -> build/lib/django/views/generic
2025-04-22 17:58:53,012 root INFO creating build/lib/django/views/decorators
2025-04-22 17:58:53,012 root INFO copying django/views/decorators/__init__.py -> build/lib/django/views/decorators
2025-04-22 17:58:53,012 root INFO copying django/views/decorators/cache.py -> build/lib/django/views/decorators
2025-04-22 17:58:53,012 root INFO copying django/views/decorators/http.py -> build/lib/django/views/decorators
2025-04-22 17:58:53,013 root INFO copying django/views/decorators/vary.py -> build/lib/django/views/decorators
2025-04-22 17:58:53,013 root INFO copying django/views/decorators/gzip.py -> build/lib/django/views/decorators
2025-04-22 17:58:53,013 root INFO copying django/views/decorators/csrf.py -> build/lib/django/views/decorators
2025-04-22 17:58:53,013 root INFO copying django/views/decorators/clickjacking.py -> build/lib/django/views/decorators
2025-04-22 17:58:53,013 root INFO copying django/views/decorators/debug.py -> build/lib/django/views/decorators
2025-04-22 17:58:53,014 root INFO copying django/views/decorators/common.py -> build/lib/django/views/decorators
2025-04-22 17:58:53,014 root INFO creating build/lib/django/template/loaders
2025-04-22 17:58:53,014 root INFO copying django/template/loaders/__init__.py -> build/lib/django/template/loaders
2025-04-22 17:58:53,015 root INFO copying django/template/loaders/locmem.py -> build/lib/django/template/loaders
2025-04-22 17:58:53,015 root INFO copying django/template/loaders/cached.py -> build/lib/django/template/loaders
2025-04-22 17:58:53,015 root INFO copying django/template/loaders/app_directories.py -> build/lib/django/template/loaders
2025-04-22 17:58:53,015 root INFO copying django/template/loaders/filesystem.py -> build/lib/django/template/loaders
2025-04-22 17:58:53,016 root INFO copying django/template/loaders/base.py -> build/lib/django/template/loaders
2025-04-22 17:58:53,016 root INFO creating build/lib/django/template/backends
2025-04-22 17:58:53,016 root INFO copying django/template/backends/__init__.py -> build/lib/django/template/backends
2025-04-22 17:58:53,016 root INFO copying django/template/backends/jinja2.py -> build/lib/django/template/backends
2025-04-22 17:58:53,017 root INFO copying django/template/backends/utils.py -> build/lib/django/template/backends
2025-04-22 17:58:53,017 root INFO copying django/template/backends/django.py -> build/lib/django/template/backends
2025-04-22 17:58:53,017 root INFO copying django/template/backends/base.py -> build/lib/django/template/backends
2025-04-22 17:58:53,017 root INFO copying django/template/backends/dummy.py -> build/lib/django/template/backends
2025-04-22 17:58:53,018 root INFO creating build/lib/django/conf/urls
2025-04-22 17:58:53,018 root INFO copying django/conf/urls/__init__.py -> build/lib/django/conf/urls
2025-04-22 17:58:53,018 root INFO copying django/conf/urls/i18n.py -> build/lib/django/conf/urls
2025-04-22 17:58:53,018 root INFO copying django/conf/urls/static.py -> build/lib/django/conf/urls
2025-04-22 17:58:53,019 root INFO creating build/lib/django/conf/locale
2025-04-22 17:58:53,019 root INFO copying django/conf/locale/__init__.py -> build/lib/django/conf/locale
2025-04-22 17:58:53,020 root INFO creating build/lib/django/conf/locale/lv
2025-04-22 17:58:53,020 root INFO copying django/conf/locale/lv/__init__.py -> build/lib/django/conf/locale/lv
2025-04-22 17:58:53,020 root INFO copying django/conf/locale/lv/formats.py -> build/lib/django/conf/locale/lv
2025-04-22 17:58:53,020 root INFO creating build/lib/django/conf/locale/es_PR
2025-04-22 17:58:53,020 root INFO copying django/conf/locale/es_PR/__init__.py -> build/lib/django/conf/locale/es_PR
2025-04-22 17:58:53,021 root INFO copying django/conf/locale/es_PR/formats.py -> build/lib/django/conf/locale/es_PR
2025-04-22 17:58:53,021 root INFO creating build/lib/django/conf/locale/en_AU
2025-04-22 17:58:53,021 root INFO copying django/conf/locale/en_AU/__init__.py -> build/lib/django/conf/locale/en_AU
2025-04-22 17:58:53,021 root INFO copying django/conf/locale/en_AU/formats.py -> build/lib/django/conf/locale/en_AU
2025-04-22 17:58:53,022 root INFO creating build/lib/django/conf/locale/de_CH
2025-04-22 17:58:53,022 root INFO copying django/conf/locale/de_CH/__init__.py -> build/lib/django/conf/locale/de_CH
2025-04-22 17:58:53,022 root INFO copying django/conf/locale/de_CH/formats.py -> build/lib/django/conf/locale/de_CH
2025-04-22 17:58:53,022 root INFO creating build/lib/django/conf/locale/ca
2025-04-22 17:58:53,023 root INFO copying django/conf/locale/ca/__init__.py -> build/lib/django/conf/locale/ca
2025-04-22 17:58:53,023 root INFO copying django/conf/locale/ca/formats.py -> build/lib/django/conf/locale/ca
2025-04-22 17:58:53,023 root INFO creating build/lib/django/conf/locale/en_GB
2025-04-22 17:58:53,023 root INFO copying django/conf/locale/en_GB/__init__.py -> build/lib/django/conf/locale/en_GB
2025-04-22 17:58:53,024 root INFO copying django/conf/locale/en_GB/formats.py -> build/lib/django/conf/locale/en_GB
2025-04-22 17:58:53,024 root INFO creating build/lib/django/conf/locale/el
2025-04-22 17:58:53,024 root INFO copying django/conf/locale/el/__init__.py -> build/lib/django/conf/locale/el
2025-04-22 17:58:53,024 root INFO copying django/conf/locale/el/formats.py -> build/lib/django/conf/locale/el
2025-04-22 17:58:53,025 root INFO creating build/lib/django/conf/locale/en
2025-04-22 17:58:53,025 root INFO copying django/conf/locale/en/__init__.py -> build/lib/django/conf/locale/en
2025-04-22 17:58:53,025 root INFO copying django/conf/locale/en/formats.py -> build/lib/django/conf/locale/en
2025-04-22 17:58:53,025 root INFO creating build/lib/django/conf/locale/et
2025-04-22 17:58:53,026 root INFO copying django/conf/locale/et/__init__.py -> build/lib/django/conf/locale/et
2025-04-22 17:58:53,026 root INFO copying django/conf/locale/et/formats.py -> build/lib/django/conf/locale/et
2025-04-22 17:58:53,026 root INFO creating build/lib/django/conf/locale/nn
2025-04-22 17:58:53,026 root INFO copying django/conf/locale/nn/__init__.py -> build/lib/django/conf/locale/nn
2025-04-22 17:58:53,027 root INFO copying django/conf/locale/nn/formats.py -> build/lib/django/conf/locale/nn
2025-04-22 17:58:53,027 root INFO creating build/lib/django/conf/locale/cy
2025-04-22 17:58:53,027 root INFO copying django/conf/locale/cy/__init__.py -> build/lib/django/conf/locale/cy
2025-04-22 17:58:53,027 root INFO copying django/conf/locale/cy/formats.py -> build/lib/django/conf/locale/cy
2025-04-22 17:58:53,028 root INFO creating build/lib/django/conf/locale/ko
2025-04-22 17:58:53,028 root INFO copying django/conf/locale/ko/__init__.py -> build/lib/django/conf/locale/ko
2025-04-22 17:58:53,028 root INFO copying django/conf/locale/ko/formats.py -> build/lib/django/conf/locale/ko
2025-04-22 17:58:53,028 root INFO creating build/lib/django/conf/locale/is
2025-04-22 17:58:53,028 root INFO copying django/conf/locale/is/__init__.py -> build/lib/django/conf/locale/is
2025-04-22 17:58:53,029 root INFO copying django/conf/locale/is/formats.py -> build/lib/django/conf/locale/is
2025-04-22 17:58:53,029 root INFO creating build/lib/django/conf/locale/sr_Latn
2025-04-22 17:58:53,029 root INFO copying django/conf/locale/sr_Latn/__init__.py -> build/lib/django/conf/locale/sr_Latn
2025-04-22 17:58:53,029 root INFO copying django/conf/locale/sr_Latn/formats.py -> build/lib/django/conf/locale/sr_Latn
2025-04-22 17:58:53,030 root INFO creating build/lib/django/conf/locale/fy
2025-04-22 17:58:53,030 root INFO copying django/conf/locale/fy/__init__.py -> build/lib/django/conf/locale/fy
2025-04-22 17:58:53,030 root INFO copying django/conf/locale/fy/formats.py -> build/lib/django/conf/locale/fy
2025-04-22 17:58:53,031 root INFO creating build/lib/django/conf/locale/bg
2025-04-22 17:58:53,031 root INFO copying django/conf/locale/bg/__init__.py -> build/lib/django/conf/locale/bg
2025-04-22 17:58:53,031 root INFO copying django/conf/locale/bg/formats.py -> build/lib/django/conf/locale/bg
2025-04-22 17:58:53,031 root INFO creating build/lib/django/conf/locale/ga
2025-04-22 17:58:53,031 root INFO copying django/conf/locale/ga/__init__.py -> build/lib/django/conf/locale/ga
2025-04-22 17:58:53,032 root INFO copying django/conf/locale/ga/formats.py -> build/lib/django/conf/locale/ga
2025-04-22 17:58:53,032 root INFO creating build/lib/django/conf/locale/gl
2025-04-22 17:58:53,032 root INFO copying django/conf/locale/gl/__init__.py -> build/lib/django/conf/locale/gl
2025-04-22 17:58:53,032 root INFO copying django/conf/locale/gl/formats.py -> build/lib/django/conf/locale/gl
2025-04-22 17:58:53,033 root INFO creating build/lib/django/conf/locale/ig
2025-04-22 17:58:53,033 root INFO copying django/conf/locale/ig/__init__.py -> build/lib/django/conf/locale/ig
2025-04-22 17:58:53,033 root INFO copying django/conf/locale/ig/formats.py -> build/lib/django/conf/locale/ig
2025-04-22 17:58:53,033 root INFO creating build/lib/django/conf/locale/uk
2025-04-22 17:58:53,033 root INFO copying django/conf/locale/uk/__init__.py -> build/lib/django/conf/locale/uk
2025-04-22 17:58:53,034 root INFO copying django/conf/locale/uk/formats.py -> build/lib/django/conf/locale/uk
2025-04-22 17:58:53,034 root INFO creating build/lib/django/conf/locale/uz
2025-04-22 17:58:53,034 root INFO copying django/conf/locale/uz/__init__.py -> build/lib/django/conf/locale/uz
2025-04-22 17:58:53,034 root INFO copying django/conf/locale/uz/formats.py -> build/lib/django/conf/locale/uz
2025-04-22 17:58:53,035 root INFO creating build/lib/django/conf/locale/kn
2025-04-22 17:58:53,035 root INFO copying django/conf/locale/kn/__init__.py -> build/lib/django/conf/locale/kn
2025-04-22 17:58:53,035 root INFO copying django/conf/locale/kn/formats.py -> build/lib/django/conf/locale/kn
2025-04-22 17:58:53,035 root INFO creating build/lib/django/conf/locale/ja
2025-04-22 17:58:53,036 root INFO copying django/conf/locale/ja/__init__.py -> build/lib/django/conf/locale/ja
2025-04-22 17:58:53,036 root INFO copying django/conf/locale/ja/formats.py -> build/lib/django/conf/locale/ja
2025-04-22 17:58:53,036 root INFO creating build/lib/django/conf/locale/cs
2025-04-22 17:58:53,037 root INFO copying django/conf/locale/cs/__init__.py -> build/lib/django/conf/locale/cs
2025-04-22 17:58:53,037 root INFO copying django/conf/locale/cs/formats.py -> build/lib/django/conf/locale/cs
2025-04-22 17:58:53,037 root INFO creating build/lib/django/conf/locale/tr
2025-04-22 17:58:53,037 root INFO copying django/conf/locale/tr/__init__.py -> build/lib/django/conf/locale/tr
2025-04-22 17:58:53,038 root INFO copying django/conf/locale/tr/formats.py -> build/lib/django/conf/locale/tr
2025-04-22 17:58:53,038 root INFO creating build/lib/django/conf/locale/sl
2025-04-22 17:58:53,038 root INFO copying django/conf/locale/sl/__init__.py -> build/lib/django/conf/locale/sl
2025-04-22 17:58:53,038 root INFO copying django/conf/locale/sl/formats.py -> build/lib/django/conf/locale/sl
2025-04-22 17:58:53,039 root INFO creating build/lib/django/conf/locale/sq
2025-04-22 17:58:53,039 root INFO copying django/conf/locale/sq/__init__.py -> build/lib/django/conf/locale/sq
2025-04-22 17:58:53,039 root INFO copying django/conf/locale/sq/formats.py -> build/lib/django/conf/locale/sq
2025-04-22 17:58:53,039 root INFO creating build/lib/django/conf/locale/az
2025-04-22 17:58:53,039 root INFO copying django/conf/locale/az/__init__.py -> build/lib/django/conf/locale/az
2025-04-22 17:58:53,040 root INFO copying django/conf/locale/az/formats.py -> build/lib/django/conf/locale/az
2025-04-22 17:58:53,040 root INFO creating build/lib/django/conf/locale/eo
2025-04-22 17:58:53,040 root INFO copying django/conf/locale/eo/__init__.py -> build/lib/django/conf/locale/eo
2025-04-22 17:58:53,040 root INFO copying django/conf/locale/eo/formats.py -> build/lib/django/conf/locale/eo
2025-04-22 17:58:53,041 root INFO creating build/lib/django/conf/locale/pt_BR
2025-04-22 17:58:53,041 root INFO copying django/conf/locale/pt_BR/__init__.py -> build/lib/django/conf/locale/pt_BR
2025-04-22 17:58:53,041 root INFO copying django/conf/locale/pt_BR/formats.py -> build/lib/django/conf/locale/pt_BR
2025-04-22 17:58:53,041 root INFO creating build/lib/django/conf/locale/pl
2025-04-22 17:58:53,042 root INFO copying django/conf/locale/pl/__init__.py -> build/lib/django/conf/locale/pl
2025-04-22 17:58:53,042 root INFO copying django/conf/locale/pl/formats.py -> build/lib/django/conf/locale/pl
2025-04-22 17:58:53,042 root INFO creating build/lib/django/conf/locale/gd
2025-04-22 17:58:53,042 root INFO copying django/conf/locale/gd/__init__.py -> build/lib/django/conf/locale/gd
2025-04-22 17:58:53,042 root INFO copying django/conf/locale/gd/formats.py -> build/lib/django/conf/locale/gd
2025-04-22 17:58:53,043 root INFO creating build/lib/django/conf/locale/hr
2025-04-22 17:58:53,043 root INFO copying django/conf/locale/hr/__init__.py -> build/lib/django/conf/locale/hr
2025-04-22 17:58:53,043 root INFO copying django/conf/locale/hr/formats.py -> build/lib/django/conf/locale/hr
2025-04-22 17:58:53,044 root INFO creating build/lib/django/conf/locale/ru
2025-04-22 17:58:53,044 root INFO copying django/conf/locale/ru/__init__.py -> build/lib/django/conf/locale/ru
2025-04-22 17:58:53,044 root INFO copying django/conf/locale/ru/formats.py -> build/lib/django/conf/locale/ru
2025-04-22 17:58:53,044 root INFO creating build/lib/django/conf/locale/es
2025-04-22 17:58:53,044 root INFO copying django/conf/locale/es/__init__.py -> build/lib/django/conf/locale/es
2025-04-22 17:58:53,045 root INFO copying django/conf/locale/es/formats.py -> build/lib/django/conf/locale/es
2025-04-22 17:58:53,045 root INFO creating build/lib/django/conf/locale/id
2025-04-22 17:58:53,045 root INFO copying django/conf/locale/id/__init__.py -> build/lib/django/conf/locale/id
2025-04-22 17:58:53,045 root INFO copying django/conf/locale/id/formats.py -> build/lib/django/conf/locale/id
2025-04-22 17:58:53,046 root INFO creating build/lib/django/conf/locale/fi
2025-04-22 17:58:53,046 root INFO copying django/conf/locale/fi/__init__.py -> build/lib/django/conf/locale/fi
2025-04-22 17:58:53,046 root INFO copying django/conf/locale/fi/formats.py -> build/lib/django/conf/locale/fi
2025-04-22 17:58:53,046 root INFO creating build/lib/django/conf/locale/mk
2025-04-22 17:58:53,047 root INFO copying django/conf/locale/mk/__init__.py -> build/lib/django/conf/locale/mk
2025-04-22 17:58:53,047 root INFO copying django/conf/locale/mk/formats.py -> build/lib/django/conf/locale/mk
2025-04-22 17:58:53,047 root INFO creating build/lib/django/conf/locale/hi
2025-04-22 17:58:53,047 root INFO copying django/conf/locale/hi/__init__.py -> build/lib/django/conf/locale/hi
2025-04-22 17:58:53,048 root INFO copying django/conf/locale/hi/formats.py -> build/lib/django/conf/locale/hi
2025-04-22 17:58:53,048 root INFO creating build/lib/django/conf/locale/sk
2025-04-22 17:58:53,048 root INFO copying django/conf/locale/sk/__init__.py -> build/lib/django/conf/locale/sk
2025-04-22 17:58:53,048 root INFO copying django/conf/locale/sk/formats.py -> build/lib/django/conf/locale/sk
2025-04-22 17:58:53,049 root INFO creating build/lib/django/conf/locale/lt
2025-04-22 17:58:53,049 root INFO copying django/conf/locale/lt/__init__.py -> build/lib/django/conf/locale/lt
2025-04-22 17:58:53,049 root INFO copying django/conf/locale/lt/formats.py -> build/lib/django/conf/locale/lt
2025-04-22 17:58:53,049 root INFO creating build/lib/django/conf/locale/de
2025-04-22 17:58:53,050 root INFO copying django/conf/locale/de/__init__.py -> build/lib/django/conf/locale/de
2025-04-22 17:58:53,050 root INFO copying django/conf/locale/de/formats.py -> build/lib/django/conf/locale/de
2025-04-22 17:58:53,050 root INFO creating build/lib/django/conf/locale/it
2025-04-22 17:58:53,050 root INFO copying django/conf/locale/it/__init__.py -> build/lib/django/conf/locale/it
2025-04-22 17:58:53,051 root INFO copying django/conf/locale/it/formats.py -> build/lib/django/conf/locale/it
2025-04-22 17:58:53,051 root INFO creating build/lib/django/conf/locale/sr
2025-04-22 17:58:53,051 root INFO copying django/conf/locale/sr/__init__.py -> build/lib/django/conf/locale/sr
2025-04-22 17:58:53,051 root INFO copying django/conf/locale/sr/formats.py -> build/lib/django/conf/locale/sr
2025-04-22 17:58:53,052 root INFO creating build/lib/django/conf/locale/bs
2025-04-22 17:58:53,052 root INFO copying django/conf/locale/bs/__init__.py -> build/lib/django/conf/locale/bs
2025-04-22 17:58:53,052 root INFO copying django/conf/locale/bs/formats.py -> build/lib/django/conf/locale/bs
2025-04-22 17:58:53,052 root INFO creating build/lib/django/conf/locale/es_NI
2025-04-22 17:58:53,053 root INFO copying django/conf/locale/es_NI/__init__.py -> build/lib/django/conf/locale/es_NI
2025-04-22 17:58:53,053 root INFO copying django/conf/locale/es_NI/formats.py -> build/lib/django/conf/locale/es_NI
2025-04-22 17:58:53,053 root INFO creating build/lib/django/conf/locale/ro
2025-04-22 17:58:53,053 root INFO copying django/conf/locale/ro/__init__.py -> build/lib/django/conf/locale/ro
2025-04-22 17:58:53,054 root INFO copying django/conf/locale/ro/formats.py -> build/lib/django/conf/locale/ro
2025-04-22 17:58:53,054 root INFO creating build/lib/django/conf/locale/ky
2025-04-22 17:58:53,054 root INFO copying django/conf/locale/ky/__init__.py -> build/lib/django/conf/locale/ky
2025-04-22 17:58:53,054 root INFO copying django/conf/locale/ky/formats.py -> build/lib/django/conf/locale/ky
2025-04-22 17:58:53,055 root INFO creating build/lib/django/conf/locale/fr
2025-04-22 17:58:53,055 root INFO copying django/conf/locale/fr/__init__.py -> build/lib/django/conf/locale/fr
2025-04-22 17:58:53,055 root INFO copying django/conf/locale/fr/formats.py -> build/lib/django/conf/locale/fr
2025-04-22 17:58:53,056 root INFO creating build/lib/django/conf/locale/ar
2025-04-22 17:58:53,056 root INFO copying django/conf/locale/ar/__init__.py -> build/lib/django/conf/locale/ar
2025-04-22 17:58:53,056 root INFO copying django/conf/locale/ar/formats.py -> build/lib/django/conf/locale/ar
2025-04-22 17:58:53,056 root INFO creating build/lib/django/conf/locale/es_AR
2025-04-22 17:58:53,057 root INFO copying django/conf/locale/es_AR/__init__.py -> build/lib/django/conf/locale/es_AR
2025-04-22 17:58:53,057 root INFO copying django/conf/locale/es_AR/formats.py -> build/lib/django/conf/locale/es_AR
2025-04-22 17:58:53,057 root INFO creating build/lib/django/conf/locale/vi
2025-04-22 17:58:53,057 root INFO copying django/conf/locale/vi/__init__.py -> build/lib/django/conf/locale/vi
2025-04-22 17:58:53,058 root INFO copying django/conf/locale/vi/formats.py -> build/lib/django/conf/locale/vi
2025-04-22 17:58:53,058 root INFO creating build/lib/django/conf/locale/ckb
2025-04-22 17:58:53,058 root INFO copying django/conf/locale/ckb/__init__.py -> build/lib/django/conf/locale/ckb
2025-04-22 17:58:53,058 root INFO copying django/conf/locale/ckb/formats.py -> build/lib/django/conf/locale/ckb
2025-04-22 17:58:53,059 root INFO creating build/lib/django/conf/locale/sv
2025-04-22 17:58:53,059 root INFO copying django/conf/locale/sv/__init__.py -> build/lib/django/conf/locale/sv
2025-04-22 17:58:53,059 root INFO copying django/conf/locale/sv/formats.py -> build/lib/django/conf/locale/sv
2025-04-22 17:58:53,060 root INFO creating build/lib/django/conf/locale/zh_Hant
2025-04-22 17:58:53,060 root INFO copying django/conf/locale/zh_Hant/__init__.py -> build/lib/django/conf/locale/zh_Hant
2025-04-22 17:58:53,060 root INFO copying django/conf/locale/zh_Hant/formats.py -> build/lib/django/conf/locale/zh_Hant
2025-04-22 17:58:53,060 root INFO creating build/lib/django/conf/locale/es_CO
2025-04-22 17:58:53,061 root INFO copying django/conf/locale/es_CO/__init__.py -> build/lib/django/conf/locale/es_CO
2025-04-22 17:58:53,061 root INFO copying django/conf/locale/es_CO/formats.py -> build/lib/django/conf/locale/es_CO
2025-04-22 17:58:53,061 root INFO creating build/lib/django/conf/locale/ml
2025-04-22 17:58:53,061 root INFO copying django/conf/locale/ml/__init__.py -> build/lib/django/conf/locale/ml
2025-04-22 17:58:53,062 root INFO copying django/conf/locale/ml/formats.py -> build/lib/django/conf/locale/ml
2025-04-22 17:58:53,062 root INFO creating build/lib/django/conf/locale/ar_DZ
2025-04-22 17:58:53,062 root INFO copying django/conf/locale/ar_DZ/__init__.py -> build/lib/django/conf/locale/ar_DZ
2025-04-22 17:58:53,062 root INFO copying django/conf/locale/ar_DZ/formats.py -> build/lib/django/conf/locale/ar_DZ
2025-04-22 17:58:53,063 root INFO creating build/lib/django/conf/locale/ms
2025-04-22 17:58:53,063 root INFO copying django/conf/locale/ms/__init__.py -> build/lib/django/conf/locale/ms
2025-04-22 17:58:53,063 root INFO copying django/conf/locale/ms/formats.py -> build/lib/django/conf/locale/ms
2025-04-22 17:58:53,063 root INFO creating build/lib/django/conf/locale/zh_Hans
2025-04-22 17:58:53,064 root INFO copying django/conf/locale/zh_Hans/__init__.py -> build/lib/django/conf/locale/zh_Hans
2025-04-22 17:58:53,064 root INFO copying django/conf/locale/zh_Hans/formats.py -> build/lib/django/conf/locale/zh_Hans
2025-04-22 17:58:53,064 root INFO creating build/lib/django/conf/locale/hu
2025-04-22 17:58:53,064 root INFO copying django/conf/locale/hu/__init__.py -> build/lib/django/conf/locale/hu
2025-04-22 17:58:53,065 root INFO copying django/conf/locale/hu/formats.py -> build/lib/django/conf/locale/hu
2025-04-22 17:58:53,065 root INFO creating build/lib/django/conf/locale/ta
2025-04-22 17:58:53,065 root INFO copying django/conf/locale/ta/__init__.py -> build/lib/django/conf/locale/ta
2025-04-22 17:58:53,065 root INFO copying django/conf/locale/ta/formats.py -> build/lib/django/conf/locale/ta
2025-04-22 17:58:53,066 root INFO creating build/lib/django/conf/locale/eu
2025-04-22 17:58:53,066 root INFO copying django/conf/locale/eu/__init__.py -> build/lib/django/conf/locale/eu
2025-04-22 17:58:53,066 root INFO copying django/conf/locale/eu/formats.py -> build/lib/django/conf/locale/eu
2025-04-22 17:58:53,067 root INFO creating build/lib/django/conf/locale/es_MX
2025-04-22 17:58:53,067 root INFO copying django/conf/locale/es_MX/__init__.py -> build/lib/django/conf/locale/es_MX
2025-04-22 17:58:53,067 root INFO copying django/conf/locale/es_MX/formats.py -> build/lib/django/conf/locale/es_MX
2025-04-22 17:58:53,067 root INFO creating build/lib/django/conf/locale/tk
2025-04-22 17:58:53,068 root INFO copying django/conf/locale/tk/__init__.py -> build/lib/django/conf/locale/tk
2025-04-22 17:58:53,068 root INFO copying django/conf/locale/tk/formats.py -> build/lib/django/conf/locale/tk
2025-04-22 17:58:53,068 root INFO creating build/lib/django/conf/locale/th
2025-04-22 17:58:53,068 root INFO copying django/conf/locale/th/__init__.py -> build/lib/django/conf/locale/th
2025-04-22 17:58:53,069 root INFO copying django/conf/locale/th/formats.py -> build/lib/django/conf/locale/th
2025-04-22 17:58:53,069 root INFO creating build/lib/django/conf/locale/nb
2025-04-22 17:58:53,069 root INFO copying django/conf/locale/nb/__init__.py -> build/lib/django/conf/locale/nb
2025-04-22 17:58:53,069 root INFO copying django/conf/locale/nb/formats.py -> build/lib/django/conf/locale/nb
2025-04-22 17:58:53,070 root INFO creating build/lib/django/conf/locale/mn
2025-04-22 17:58:53,070 root INFO copying django/conf/locale/mn/__init__.py -> build/lib/django/conf/locale/mn
2025-04-22 17:58:53,070 root INFO copying django/conf/locale/mn/formats.py -> build/lib/django/conf/locale/mn
2025-04-22 17:58:53,071 root INFO creating build/lib/django/conf/locale/ka
2025-04-22 17:58:53,071 root INFO copying django/conf/locale/ka/__init__.py -> build/lib/django/conf/locale/ka
2025-04-22 17:58:53,071 root INFO copying django/conf/locale/ka/formats.py -> build/lib/django/conf/locale/ka
2025-04-22 17:58:53,071 root INFO creating build/lib/django/conf/locale/nl
2025-04-22 17:58:53,072 root INFO copying django/conf/locale/nl/__init__.py -> build/lib/django/conf/locale/nl
2025-04-22 17:58:53,072 root INFO copying django/conf/locale/nl/formats.py -> build/lib/django/conf/locale/nl
2025-04-22 17:58:53,072 root INFO creating build/lib/django/conf/locale/te
2025-04-22 17:58:53,072 root INFO copying django/conf/locale/te/__init__.py -> build/lib/django/conf/locale/te
2025-04-22 17:58:53,073 root INFO copying django/conf/locale/te/formats.py -> build/lib/django/conf/locale/te
2025-04-22 17:58:53,073 root INFO creating build/lib/django/conf/locale/pt
2025-04-22 17:58:53,073 root INFO copying django/conf/locale/pt/__init__.py -> build/lib/django/conf/locale/pt
2025-04-22 17:58:53,073 root INFO copying django/conf/locale/pt/formats.py -> build/lib/django/conf/locale/pt
2025-04-22 17:58:53,074 root INFO creating build/lib/django/conf/locale/bn
2025-04-22 17:58:53,074 root INFO copying django/conf/locale/bn/__init__.py -> build/lib/django/conf/locale/bn
2025-04-22 17:58:53,074 root INFO copying django/conf/locale/bn/formats.py -> build/lib/django/conf/locale/bn
2025-04-22 17:58:53,075 root INFO creating build/lib/django/conf/locale/he
2025-04-22 17:58:53,075 root INFO copying django/conf/locale/he/__init__.py -> build/lib/django/conf/locale/he
2025-04-22 17:58:53,075 root INFO copying django/conf/locale/he/formats.py -> build/lib/django/conf/locale/he
2025-04-22 17:58:53,075 root INFO creating build/lib/django/conf/locale/fa
2025-04-22 17:58:53,075 root INFO copying django/conf/locale/fa/__init__.py -> build/lib/django/conf/locale/fa
2025-04-22 17:58:53,076 root INFO copying django/conf/locale/fa/formats.py -> build/lib/django/conf/locale/fa
2025-04-22 17:58:53,076 root INFO creating build/lib/django/conf/locale/tg
2025-04-22 17:58:53,076 root INFO copying django/conf/locale/tg/__init__.py -> build/lib/django/conf/locale/tg
2025-04-22 17:58:53,077 root INFO copying django/conf/locale/tg/formats.py -> build/lib/django/conf/locale/tg
2025-04-22 17:58:53,077 root INFO creating build/lib/django/conf/locale/km
2025-04-22 17:58:53,077 root INFO copying django/conf/locale/km/__init__.py -> build/lib/django/conf/locale/km
2025-04-22 17:58:53,077 root INFO copying django/conf/locale/km/formats.py -> build/lib/django/conf/locale/km
2025-04-22 17:58:53,077 root INFO creating build/lib/django/conf/locale/da
2025-04-22 17:58:53,078 root INFO copying django/conf/locale/da/__init__.py -> build/lib/django/conf/locale/da
2025-04-22 17:58:53,078 root INFO copying django/conf/locale/da/formats.py -> build/lib/django/conf/locale/da
2025-04-22 17:58:53,078 root INFO creating build/lib/django/utils/translation
2025-04-22 17:58:53,078 root INFO copying django/utils/translation/__init__.py -> build/lib/django/utils/translation
2025-04-22 17:58:53,079 root INFO copying django/utils/translation/template.py -> build/lib/django/utils/translation
2025-04-22 17:58:53,079 root INFO copying django/utils/translation/reloader.py -> build/lib/django/utils/translation
2025-04-22 17:58:53,079 root INFO copying django/utils/translation/trans_null.py -> build/lib/django/utils/translation
2025-04-22 17:58:53,079 root INFO copying django/utils/translation/trans_real.py -> build/lib/django/utils/translation
2025-04-22 17:58:53,080 root INFO creating build/lib/django/core/files
2025-04-22 17:58:53,080 root INFO copying django/core/files/__init__.py -> build/lib/django/core/files
2025-04-22 17:58:53,080 root INFO copying django/core/files/uploadhandler.py -> build/lib/django/core/files
2025-04-22 17:58:53,080 root INFO copying django/core/files/uploadedfile.py -> build/lib/django/core/files
2025-04-22 17:58:53,081 root INFO copying django/core/files/utils.py -> build/lib/django/core/files
2025-04-22 17:58:53,081 root INFO copying django/core/files/temp.py -> build/lib/django/core/files
2025-04-22 17:58:53,081 root INFO copying django/core/files/move.py -> build/lib/django/core/files
2025-04-22 17:58:53,081 root INFO copying django/core/files/locks.py -> build/lib/django/core/files
2025-04-22 17:58:53,081 root INFO copying django/core/files/base.py -> build/lib/django/core/files
2025-04-22 17:58:53,081 root INFO copying django/core/files/images.py -> build/lib/django/core/files
2025-04-22 17:58:53,082 root INFO creating build/lib/django/core/handlers
2025-04-22 17:58:53,082 root INFO copying django/core/handlers/__init__.py -> build/lib/django/core/handlers
2025-04-22 17:58:53,082 root INFO copying django/core/handlers/asgi.py -> build/lib/django/core/handlers
2025-04-22 17:58:53,082 root INFO copying django/core/handlers/exception.py -> build/lib/django/core/handlers
2025-04-22 17:58:53,083 root INFO copying django/core/handlers/wsgi.py -> build/lib/django/core/handlers
2025-04-22 17:58:53,083 root INFO copying django/core/handlers/base.py -> build/lib/django/core/handlers
2025-04-22 17:58:53,083 root INFO creating build/lib/django/core/servers
2025-04-22 17:58:53,083 root INFO copying django/core/servers/__init__.py -> build/lib/django/core/servers
2025-04-22 17:58:53,084 root INFO copying django/core/servers/basehttp.py -> build/lib/django/core/servers
2025-04-22 17:58:53,084 root INFO creating build/lib/django/core/mail
2025-04-22 17:58:53,084 root INFO copying django/core/mail/__init__.py -> build/lib/django/core/mail
2025-04-22 17:58:53,084 root INFO copying django/core/mail/utils.py -> build/lib/django/core/mail
2025-04-22 17:58:53,084 root INFO copying django/core/mail/message.py -> build/lib/django/core/mail
2025-04-22 17:58:53,085 root INFO creating build/lib/django/core/cache
2025-04-22 17:58:53,085 root INFO copying django/core/cache/__init__.py -> build/lib/django/core/cache
2025-04-22 17:58:53,085 root INFO copying django/core/cache/utils.py -> build/lib/django/core/cache
2025-04-22 17:58:53,085 root INFO creating build/lib/django/core/management
2025-04-22 17:58:53,086 root INFO copying django/core/management/__init__.py -> build/lib/django/core/management
2025-04-22 17:58:53,086 root INFO copying django/core/management/color.py -> build/lib/django/core/management
2025-04-22 17:58:53,086 root INFO copying django/core/management/utils.py -> build/lib/django/core/management
2025-04-22 17:58:53,086 root INFO copying django/core/management/sql.py -> build/lib/django/core/management
2025-04-22 17:58:53,087 root INFO copying django/core/management/templates.py -> build/lib/django/core/management
2025-04-22 17:58:53,087 root INFO copying django/core/management/base.py -> build/lib/django/core/management
2025-04-22 17:58:53,087 root INFO creating build/lib/django/core/serializers
2025-04-22 17:58:53,087 root INFO copying django/core/serializers/python.py -> build/lib/django/core/serializers
2025-04-22 17:58:53,087 root INFO copying django/core/serializers/__init__.py -> build/lib/django/core/serializers
2025-04-22 17:58:53,088 root INFO copying django/core/serializers/xml_serializer.py -> build/lib/django/core/serializers
2025-04-22 17:58:53,088 root INFO copying django/core/serializers/jsonl.py -> build/lib/django/core/serializers
2025-04-22 17:58:53,088 root INFO copying django/core/serializers/json.py -> build/lib/django/core/serializers
2025-04-22 17:58:53,088 root INFO copying django/core/serializers/pyyaml.py -> build/lib/django/core/serializers
2025-04-22 17:58:53,089 root INFO copying django/core/serializers/base.py -> build/lib/django/core/serializers
2025-04-22 17:58:53,089 root INFO creating build/lib/django/core/checks
2025-04-22 17:58:53,089 root INFO copying django/core/checks/__init__.py -> build/lib/django/core/checks
2025-04-22 17:58:53,089 root INFO copying django/core/checks/registry.py -> build/lib/django/core/checks
2025-04-22 17:58:53,090 root INFO copying django/core/checks/database.py -> build/lib/django/core/checks
2025-04-22 17:58:53,090 root INFO copying django/core/checks/messages.py -> build/lib/django/core/checks
2025-04-22 17:58:53,090 root INFO copying django/core/checks/urls.py -> build/lib/django/core/checks
2025-04-22 17:58:53,090 root INFO copying django/core/checks/model_checks.py -> build/lib/django/core/checks
2025-04-22 17:58:53,090 root INFO copying django/core/checks/caches.py -> build/lib/django/core/checks
2025-04-22 17:58:53,091 root INFO copying django/core/checks/translation.py -> build/lib/django/core/checks
2025-04-22 17:58:53,091 root INFO copying django/core/checks/templates.py -> build/lib/django/core/checks
2025-04-22 17:58:53,091 root INFO copying django/core/checks/async_checks.py -> build/lib/django/core/checks
2025-04-22 17:58:53,091 root INFO copying django/core/checks/files.py -> build/lib/django/core/checks
2025-04-22 17:58:53,092 root INFO creating build/lib/django/core/files/storage
2025-04-22 17:58:53,092 root INFO copying django/core/files/storage/__init__.py -> build/lib/django/core/files/storage
2025-04-22 17:58:53,092 root INFO copying django/core/files/storage/handler.py -> build/lib/django/core/files/storage
2025-04-22 17:58:53,092 root INFO copying django/core/files/storage/memory.py -> build/lib/django/core/files/storage
2025-04-22 17:58:53,092 root INFO copying django/core/files/storage/filesystem.py -> build/lib/django/core/files/storage
2025-04-22 17:58:53,093 root INFO copying django/core/files/storage/base.py -> build/lib/django/core/files/storage
2025-04-22 17:58:53,093 root INFO copying django/core/files/storage/mixins.py -> build/lib/django/core/files/storage
2025-04-22 17:58:53,093 root INFO creating build/lib/django/core/mail/backends
2025-04-22 17:58:53,093 root INFO copying django/core/mail/backends/__init__.py -> build/lib/django/core/mail/backends
2025-04-22 17:58:53,094 root INFO copying django/core/mail/backends/locmem.py -> build/lib/django/core/mail/backends
2025-04-22 17:58:53,094 root INFO copying django/core/mail/backends/base.py -> build/lib/django/core/mail/backends
2025-04-22 17:58:53,094 root INFO copying django/core/mail/backends/console.py -> build/lib/django/core/mail/backends
2025-04-22 17:58:53,094 root INFO copying django/core/mail/backends/dummy.py -> build/lib/django/core/mail/backends
2025-04-22 17:58:53,094 root INFO copying django/core/mail/backends/smtp.py -> build/lib/django/core/mail/backends
2025-04-22 17:58:53,095 root INFO copying django/core/mail/backends/filebased.py -> build/lib/django/core/mail/backends
2025-04-22 17:58:53,095 root INFO creating build/lib/django/core/cache/backends
2025-04-22 17:58:53,095 root INFO copying django/core/cache/backends/__init__.py -> build/lib/django/core/cache/backends
2025-04-22 17:58:53,095 root INFO copying django/core/cache/backends/locmem.py -> build/lib/django/core/cache/backends
2025-04-22 17:58:53,096 root INFO copying django/core/cache/backends/db.py -> build/lib/django/core/cache/backends
2025-04-22 17:58:53,096 root INFO copying django/core/cache/backends/memcached.py -> build/lib/django/core/cache/backends
2025-04-22 17:58:53,096 root INFO copying django/core/cache/backends/redis.py -> build/lib/django/core/cache/backends
2025-04-22 17:58:53,096 root INFO copying django/core/cache/backends/base.py -> build/lib/django/core/cache/backends
2025-04-22 17:58:53,097 root INFO copying django/core/cache/backends/dummy.py -> build/lib/django/core/cache/backends
2025-04-22 17:58:53,097 root INFO copying django/core/cache/backends/filebased.py -> build/lib/django/core/cache/backends
2025-04-22 17:58:53,097 root INFO creating build/lib/django/core/management/commands
2025-04-22 17:58:53,098 root INFO copying django/core/management/commands/__init__.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,098 root INFO copying django/core/management/commands/sqlmigrate.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,098 root INFO copying django/core/management/commands/startapp.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,098 root INFO copying django/core/management/commands/showmigrations.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,098 root INFO copying django/core/management/commands/optimizemigration.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,099 root INFO copying django/core/management/commands/dumpdata.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,099 root INFO copying django/core/management/commands/migrate.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,099 root INFO copying django/core/management/commands/shell.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,099 root INFO copying django/core/management/commands/loaddata.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,100 root INFO copying django/core/management/commands/createcachetable.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,100 root INFO copying django/core/management/commands/dbshell.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,100 root INFO copying django/core/management/commands/inspectdb.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,100 root INFO copying django/core/management/commands/compilemessages.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,101 root INFO copying django/core/management/commands/startproject.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,101 root INFO copying django/core/management/commands/testserver.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,101 root INFO copying django/core/management/commands/flush.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,101 root INFO copying django/core/management/commands/diffsettings.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,101 root INFO copying django/core/management/commands/sqlflush.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,102 root INFO copying django/core/management/commands/makemigrations.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,102 root INFO copying django/core/management/commands/sqlsequencereset.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,102 root INFO copying django/core/management/commands/makemessages.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,102 root INFO copying django/core/management/commands/runserver.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,102 root INFO copying django/core/management/commands/check.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,103 root INFO copying django/core/management/commands/sendtestemail.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,103 root INFO copying django/core/management/commands/squashmigrations.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,103 root INFO copying django/core/management/commands/test.py -> build/lib/django/core/management/commands
2025-04-22 17:58:53,104 root INFO creating build/lib/django/core/checks/compatibility
2025-04-22 17:58:53,104 root INFO copying django/core/checks/compatibility/__init__.py -> build/lib/django/core/checks/compatibility
2025-04-22 17:58:53,104 root INFO copying django/core/checks/compatibility/django_4_0.py -> build/lib/django/core/checks/compatibility
2025-04-22 17:58:53,104 root INFO creating build/lib/django/core/checks/security
2025-04-22 17:58:53,104 root INFO copying django/core/checks/security/__init__.py -> build/lib/django/core/checks/security
2025-04-22 17:58:53,105 root INFO copying django/core/checks/security/sessions.py -> build/lib/django/core/checks/security
2025-04-22 17:58:53,105 root INFO copying django/core/checks/security/csrf.py -> build/lib/django/core/checks/security
2025-04-22 17:58:53,105 root INFO copying django/core/checks/security/base.py -> build/lib/django/core/checks/security
2025-04-22 17:58:53,105 root INFO creating build/lib/django/contrib/auth
2025-04-22 17:58:53,106 root INFO copying django/contrib/auth/__init__.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,106 root INFO copying django/contrib/auth/hashers.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,106 root INFO copying django/contrib/auth/signals.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,106 root INFO copying django/contrib/auth/middleware.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,107 root INFO copying django/contrib/auth/views.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,107 root INFO copying django/contrib/auth/forms.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,107 root INFO copying django/contrib/auth/validators.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,107 root INFO copying django/contrib/auth/decorators.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,108 root INFO copying django/contrib/auth/models.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,108 root INFO copying django/contrib/auth/backends.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,108 root INFO copying django/contrib/auth/apps.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,108 root INFO copying django/contrib/auth/urls.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,108 root INFO copying django/contrib/auth/admin.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,109 root INFO copying django/contrib/auth/checks.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,109 root INFO copying django/contrib/auth/context_processors.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,109 root INFO copying django/contrib/auth/tokens.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,109 root INFO copying django/contrib/auth/base_user.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,110 root INFO copying django/contrib/auth/password_validation.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,110 root INFO copying django/contrib/auth/mixins.py -> build/lib/django/contrib/auth
2025-04-22 17:58:53,110 root INFO creating build/lib/django/contrib/contenttypes
2025-04-22 17:58:53,110 root INFO copying django/contrib/contenttypes/__init__.py -> build/lib/django/contrib/contenttypes
2025-04-22 17:58:53,111 root INFO copying django/contrib/contenttypes/views.py -> build/lib/django/contrib/contenttypes
2025-04-22 17:58:53,111 root INFO copying django/contrib/contenttypes/forms.py -> build/lib/django/contrib/contenttypes
2025-04-22 17:58:53,111 root INFO copying django/contrib/contenttypes/models.py -> build/lib/django/contrib/contenttypes
2025-04-22 17:58:53,111 root INFO copying django/contrib/contenttypes/apps.py -> build/lib/django/contrib/contenttypes
2025-04-22 17:58:53,111 root INFO copying django/contrib/contenttypes/admin.py -> build/lib/django/contrib/contenttypes
2025-04-22 17:58:53,112 root INFO copying django/contrib/contenttypes/checks.py -> build/lib/django/contrib/contenttypes
2025-04-22 17:58:53,112 root INFO copying django/contrib/contenttypes/fields.py -> build/lib/django/contrib/contenttypes
2025-04-22 17:58:53,112 root INFO creating build/lib/django/contrib/redirects
2025-04-22 17:58:53,112 root INFO copying django/contrib/redirects/__init__.py -> build/lib/django/contrib/redirects
2025-04-22 17:58:53,113 root INFO copying django/contrib/redirects/middleware.py -> build/lib/django/contrib/redirects
2025-04-22 17:58:53,113 root INFO copying django/contrib/redirects/models.py -> build/lib/django/contrib/redirects
2025-04-22 17:58:53,113 root INFO copying django/contrib/redirects/apps.py -> build/lib/django/contrib/redirects
2025-04-22 17:58:53,113 root INFO copying django/contrib/redirects/admin.py -> build/lib/django/contrib/redirects
2025-04-22 17:58:53,114 root INFO creating build/lib/django/contrib/messages
2025-04-22 17:58:53,114 root INFO copying django/contrib/messages/__init__.py -> build/lib/django/contrib/messages
2025-04-22 17:58:53,114 root INFO copying django/contrib/messages/middleware.py -> build/lib/django/contrib/messages
2025-04-22 17:58:53,114 root INFO copying django/contrib/messages/views.py -> build/lib/django/contrib/messages
2025-04-22 17:58:53,114 root INFO copying django/contrib/messages/apps.py -> build/lib/django/contrib/messages
2025-04-22 17:58:53,115 root INFO copying django/contrib/messages/utils.py -> build/lib/django/contrib/messages
2025-04-22 17:58:53,115 root INFO copying django/contrib/messages/api.py -> build/lib/django/contrib/messages
2025-04-22 17:58:53,115 root INFO copying django/contrib/messages/context_processors.py -> build/lib/django/contrib/messages
2025-04-22 17:58:53,115 root INFO copying django/contrib/messages/constants.py -> build/lib/django/contrib/messages
2025-04-22 17:58:53,115 root INFO creating build/lib/django/contrib/sites
2025-04-22 17:58:53,116 root INFO copying django/contrib/sites/__init__.py -> build/lib/django/contrib/sites
2025-04-22 17:58:53,116 root INFO copying django/contrib/sites/managers.py -> build/lib/django/contrib/sites
2025-04-22 17:58:53,116 root INFO copying django/contrib/sites/middleware.py -> build/lib/django/contrib/sites
2025-04-22 17:58:53,116 root INFO copying django/contrib/sites/models.py -> build/lib/django/contrib/sites
2025-04-22 17:58:53,117 root INFO copying django/contrib/sites/apps.py -> build/lib/django/contrib/sites
2025-04-22 17:58:53,117 root INFO copying django/contrib/sites/admin.py -> build/lib/django/contrib/sites
2025-04-22 17:58:53,117 root INFO copying django/contrib/sites/checks.py -> build/lib/django/contrib/sites
2025-04-22 17:58:53,117 root INFO copying django/contrib/sites/management.py -> build/lib/django/contrib/sites
2025-04-22 17:58:53,117 root INFO copying django/contrib/sites/requests.py -> build/lib/django/contrib/sites
2025-04-22 17:58:53,118 root INFO copying django/contrib/sites/shortcuts.py -> build/lib/django/contrib/sites
2025-04-22 17:58:53,118 root INFO creating build/lib/django/contrib/sitemaps
2025-04-22 17:58:53,118 root INFO copying django/contrib/sitemaps/__init__.py -> build/lib/django/contrib/sitemaps
2025-04-22 17:58:53,118 root INFO copying django/contrib/sitemaps/views.py -> build/lib/django/contrib/sitemaps
2025-04-22 17:58:53,119 root INFO copying django/contrib/sitemaps/apps.py -> build/lib/django/contrib/sitemaps
2025-04-22 17:58:53,119 root INFO creating build/lib/django/contrib/flatpages
2025-04-22 17:58:53,119 root INFO copying django/contrib/flatpages/__init__.py -> build/lib/django/contrib/flatpages
2025-04-22 17:58:53,119 root INFO copying django/contrib/flatpages/middleware.py -> build/lib/django/contrib/flatpages
2025-04-22 17:58:53,120 root INFO copying django/contrib/flatpages/views.py -> build/lib/django/contrib/flatpages
2025-04-22 17:58:53,120 root INFO copying django/contrib/flatpages/forms.py -> build/lib/django/contrib/flatpages
2025-04-22 17:58:53,120 root INFO copying django/contrib/flatpages/models.py -> build/lib/django/contrib/flatpages
2025-04-22 17:58:53,120 root INFO copying django/contrib/flatpages/apps.py -> build/lib/django/contrib/flatpages
2025-04-22 17:58:53,120 root INFO copying django/contrib/flatpages/urls.py -> build/lib/django/contrib/flatpages
2025-04-22 17:58:53,121 root INFO copying django/contrib/flatpages/admin.py -> build/lib/django/contrib/flatpages
2025-04-22 17:58:53,121 root INFO copying django/contrib/flatpages/sitemaps.py -> build/lib/django/contrib/flatpages
2025-04-22 17:58:53,121 root INFO creating build/lib/django/contrib/staticfiles
2025-04-22 17:58:53,121 root INFO copying django/contrib/staticfiles/__init__.py -> build/lib/django/contrib/staticfiles
2025-04-22 17:58:53,122 root INFO copying django/contrib/staticfiles/handlers.py -> build/lib/django/contrib/staticfiles
2025-04-22 17:58:53,122 root INFO copying django/contrib/staticfiles/views.py -> build/lib/django/contrib/staticfiles
2025-04-22 17:58:53,122 root INFO copying django/contrib/staticfiles/testing.py -> build/lib/django/contrib/staticfiles
2025-04-22 17:58:53,122 root INFO copying django/contrib/staticfiles/apps.py -> build/lib/django/contrib/staticfiles
2025-04-22 17:58:53,122 root INFO copying django/contrib/staticfiles/urls.py -> build/lib/django/contrib/staticfiles
2025-04-22 17:58:53,123 root INFO copying django/contrib/staticfiles/utils.py -> build/lib/django/contrib/staticfiles
2025-04-22 17:58:53,123 root INFO copying django/contrib/staticfiles/checks.py -> build/lib/django/contrib/staticfiles
2025-04-22 17:58:53,123 root INFO copying django/contrib/staticfiles/finders.py -> build/lib/django/contrib/staticfiles
2025-04-22 17:58:53,123 root INFO copying django/contrib/staticfiles/storage.py -> build/lib/django/contrib/staticfiles
2025-04-22 17:58:53,124 root INFO creating build/lib/django/contrib/sessions
2025-04-22 17:58:53,124 root INFO copying django/contrib/sessions/__init__.py -> build/lib/django/contrib/sessions
2025-04-22 17:58:53,124 root INFO copying django/contrib/sessions/middleware.py -> build/lib/django/contrib/sessions
2025-04-22 17:58:53,124 root INFO copying django/contrib/sessions/exceptions.py -> build/lib/django/contrib/sessions
2025-04-22 17:58:53,124 root INFO copying django/contrib/sessions/base_session.py -> build/lib/django/contrib/sessions
2025-04-22 17:58:53,125 root INFO copying django/contrib/sessions/models.py -> build/lib/django/contrib/sessions
2025-04-22 17:58:53,125 root INFO copying django/contrib/sessions/apps.py -> build/lib/django/contrib/sessions
2025-04-22 17:58:53,125 root INFO copying django/contrib/sessions/serializers.py -> build/lib/django/contrib/sessions
2025-04-22 17:58:53,125 root INFO creating build/lib/django/contrib/admindocs
2025-04-22 17:58:53,126 root INFO copying django/contrib/admindocs/__init__.py -> build/lib/django/contrib/admindocs
2025-04-22 17:58:53,126 root INFO copying django/contrib/admindocs/middleware.py -> build/lib/django/contrib/admindocs
2025-04-22 17:58:53,126 root INFO copying django/contrib/admindocs/views.py -> build/lib/django/contrib/admindocs
2025-04-22 17:58:53,126 root INFO copying django/contrib/admindocs/apps.py -> build/lib/django/contrib/admindocs
2025-04-22 17:58:53,126 root INFO copying django/contrib/admindocs/urls.py -> build/lib/django/contrib/admindocs
2025-04-22 17:58:53,127 root INFO copying django/contrib/admindocs/utils.py -> build/lib/django/contrib/admindocs
2025-04-22 17:58:53,127 root INFO creating build/lib/django/contrib/syndication
2025-04-22 17:58:53,127 root INFO copying django/contrib/syndication/__init__.py -> build/lib/django/contrib/syndication
2025-04-22 17:58:53,127 root INFO copying django/contrib/syndication/views.py -> build/lib/django/contrib/syndication
2025-04-22 17:58:53,128 root INFO copying django/contrib/syndication/apps.py -> build/lib/django/contrib/syndication
2025-04-22 17:58:53,128 root INFO creating build/lib/django/contrib/postgres
2025-04-22 17:58:53,128 root INFO copying django/contrib/postgres/__init__.py -> build/lib/django/contrib/postgres
2025-04-22 17:58:53,128 root INFO copying django/contrib/postgres/functions.py -> build/lib/django/contrib/postgres
2025-04-22 17:58:53,128 root INFO copying django/contrib/postgres/signals.py -> build/lib/django/contrib/postgres
2025-04-22 17:58:53,129 root INFO copying django/contrib/postgres/lookups.py -> build/lib/django/contrib/postgres
2025-04-22 17:58:53,129 root INFO copying django/contrib/postgres/validators.py -> build/lib/django/contrib/postgres
2025-04-22 17:58:53,129 root INFO copying django/contrib/postgres/operations.py -> build/lib/django/contrib/postgres
2025-04-22 17:58:53,129 root INFO copying django/contrib/postgres/apps.py -> build/lib/django/contrib/postgres
2025-04-22 17:58:53,130 root INFO copying django/contrib/postgres/indexes.py -> build/lib/django/contrib/postgres
2025-04-22 17:58:53,130 root INFO copying django/contrib/postgres/utils.py -> build/lib/django/contrib/postgres
2025-04-22 17:58:53,130 root INFO copying django/contrib/postgres/expressions.py -> build/lib/django/contrib/postgres
2025-04-22 17:58:53,130 root INFO copying django/contrib/postgres/search.py -> build/lib/django/contrib/postgres
2025-04-22 17:58:53,131 root INFO copying django/contrib/postgres/constraints.py -> build/lib/django/contrib/postgres
2025-04-22 17:58:53,131 root INFO copying django/contrib/postgres/serializers.py -> build/lib/django/contrib/postgres
2025-04-22 17:58:53,131 root INFO creating build/lib/django/contrib/gis
2025-04-22 17:58:53,131 root INFO copying django/contrib/gis/__init__.py -> build/lib/django/contrib/gis
2025-04-22 17:58:53,132 root INFO copying django/contrib/gis/views.py -> build/lib/django/contrib/gis
2025-04-22 17:58:53,132 root INFO copying django/contrib/gis/apps.py -> build/lib/django/contrib/gis
2025-04-22 17:58:53,132 root INFO copying django/contrib/gis/geometry.py -> build/lib/django/contrib/gis
2025-04-22 17:58:53,132 root INFO copying django/contrib/gis/feeds.py -> build/lib/django/contrib/gis
2025-04-22 17:58:53,132 root INFO copying django/contrib/gis/ptr.py -> build/lib/django/contrib/gis
2025-04-22 17:58:53,133 root INFO copying django/contrib/gis/shortcuts.py -> build/lib/django/contrib/gis
2025-04-22 17:58:53,133 root INFO copying django/contrib/gis/measure.py -> build/lib/django/contrib/gis
2025-04-22 17:58:53,133 root INFO creating build/lib/django/contrib/admin
2025-04-22 17:58:53,133 root INFO copying django/contrib/admin/__init__.py -> build/lib/django/contrib/admin
2025-04-22 17:58:53,134 root INFO copying django/contrib/admin/options.py -> build/lib/django/contrib/admin
2025-04-22 17:58:53,134 root INFO copying django/contrib/admin/widgets.py -> build/lib/django/contrib/admin
2025-04-22 17:58:53,134 root INFO copying django/contrib/admin/forms.py -> build/lib/django/contrib/admin
2025-04-22 17:58:53,135 root INFO copying django/contrib/admin/decorators.py -> build/lib/django/contrib/admin
2025-04-22 17:58:53,135 root INFO copying django/contrib/admin/filters.py -> build/lib/django/contrib/admin
2025-04-22 17:58:53,135 root INFO copying django/contrib/admin/exceptions.py -> build/lib/django/contrib/admin
2025-04-22 17:58:53,135 root INFO copying django/contrib/admin/models.py -> build/lib/django/contrib/admin
2025-04-22 17:58:53,135 root INFO copying django/contrib/admin/apps.py -> build/lib/django/contrib/admin
2025-04-22 17:58:53,136 root INFO copying django/contrib/admin/utils.py -> build/lib/django/contrib/admin
2025-04-22 17:58:53,136 root INFO copying django/contrib/admin/checks.py -> build/lib/django/contrib/admin
2025-04-22 17:58:53,136 root INFO copying django/contrib/admin/tests.py -> build/lib/django/contrib/admin
2025-04-22 17:58:53,136 root INFO copying django/contrib/admin/helpers.py -> build/lib/django/contrib/admin
2025-04-22 17:58:53,137 root INFO copying django/contrib/admin/sites.py -> build/lib/django/contrib/admin
2025-04-22 17:58:53,137 root INFO copying django/contrib/admin/actions.py -> build/lib/django/contrib/admin
2025-04-22 17:58:53,137 root INFO creating build/lib/django/contrib/humanize
2025-04-22 17:58:53,138 root INFO copying django/contrib/humanize/__init__.py -> build/lib/django/contrib/humanize
2025-04-22 17:58:53,138 root INFO copying django/contrib/humanize/apps.py -> build/lib/django/contrib/humanize
2025-04-22 17:58:53,138 root INFO creating build/lib/django/contrib/auth/handlers
2025-04-22 17:58:53,138 root INFO copying django/contrib/auth/handlers/__init__.py -> build/lib/django/contrib/auth/handlers
2025-04-22 17:58:53,138 root INFO copying django/contrib/auth/handlers/modwsgi.py -> build/lib/django/contrib/auth/handlers
2025-04-22 17:58:53,139 root INFO creating build/lib/django/contrib/auth/migrations
2025-04-22 17:58:53,139 root INFO copying django/contrib/auth/migrations/__init__.py -> build/lib/django/contrib/auth/migrations
2025-04-22 17:58:53,139 root INFO copying django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py -> build/lib/django/contrib/auth/migrations
2025-04-22 17:58:53,139 root INFO copying django/contrib/auth/migrations/0002_alter_permission_name_max_length.py -> build/lib/django/contrib/auth/migrations
2025-04-22 17:58:53,140 root INFO copying django/contrib/auth/migrations/0008_alter_user_username_max_length.py -> build/lib/django/contrib/auth/migrations
2025-04-22 17:58:53,140 root INFO copying django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py -> build/lib/django/contrib/auth/migrations
2025-04-22 17:58:53,140 root INFO copying django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py -> build/lib/django/contrib/auth/migrations
2025-04-22 17:58:53,140 root INFO copying django/contrib/auth/migrations/0006_require_contenttypes_0002.py -> build/lib/django/contrib/auth/migrations
2025-04-22 17:58:53,141 root INFO copying django/contrib/auth/migrations/0011_update_proxy_permissions.py -> build/lib/django/contrib/auth/migrations
2025-04-22 17:58:53,141 root INFO copying django/contrib/auth/migrations/0005_alter_user_last_login_null.py -> build/lib/django/contrib/auth/migrations
2025-04-22 17:58:53,141 root INFO copying django/contrib/auth/migrations/0001_initial.py -> build/lib/django/contrib/auth/migrations
2025-04-22 17:58:53,141 root INFO copying django/contrib/auth/migrations/0010_alter_group_name_max_length.py -> build/lib/django/contrib/auth/migrations
2025-04-22 17:58:53,141 root INFO copying django/contrib/auth/migrations/0003_alter_user_email_max_length.py -> build/lib/django/contrib/auth/migrations
2025-04-22 17:58:53,142 root INFO copying django/contrib/auth/migrations/0004_alter_user_username_opts.py -> build/lib/django/contrib/auth/migrations
2025-04-22 17:58:53,142 root INFO creating build/lib/django/contrib/auth/management
2025-04-22 17:58:53,142 root INFO copying django/contrib/auth/management/__init__.py -> build/lib/django/contrib/auth/management
2025-04-22 17:58:53,142 root INFO creating build/lib/django/contrib/auth/management/commands
2025-04-22 17:58:53,142 root INFO copying django/contrib/auth/management/commands/__init__.py -> build/lib/django/contrib/auth/management/commands
2025-04-22 17:58:53,143 root INFO copying django/contrib/auth/management/commands/createsuperuser.py -> build/lib/django/contrib/auth/management/commands
2025-04-22 17:58:53,143 root INFO copying django/contrib/auth/management/commands/changepassword.py -> build/lib/django/contrib/auth/management/commands
2025-04-22 17:58:53,143 root INFO creating build/lib/django/contrib/contenttypes/migrations
2025-04-22 17:58:53,143 root INFO copying django/contrib/contenttypes/migrations/__init__.py -> build/lib/django/contrib/contenttypes/migrations
2025-04-22 17:58:53,144 root INFO copying django/contrib/contenttypes/migrations/0001_initial.py -> build/lib/django/contrib/contenttypes/migrations
2025-04-22 17:58:53,144 root INFO copying django/contrib/contenttypes/migrations/0002_remove_content_type_name.py -> build/lib/django/contrib/contenttypes/migrations
2025-04-22 17:58:53,144 root INFO creating build/lib/django/contrib/contenttypes/management
2025-04-22 17:58:53,144 root INFO copying django/contrib/contenttypes/management/__init__.py -> build/lib/django/contrib/contenttypes/management
2025-04-22 17:58:53,145 root INFO creating build/lib/django/contrib/contenttypes/management/commands
2025-04-22 17:58:53,145 root INFO copying django/contrib/contenttypes/management/commands/__init__.py -> build/lib/django/contrib/contenttypes/management/commands
2025-04-22 17:58:53,145 root INFO copying django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py -> build/lib/django/contrib/contenttypes/management/commands
2025-04-22 17:58:53,145 root INFO creating build/lib/django/contrib/redirects/migrations
2025-04-22 17:58:53,145 root INFO copying django/contrib/redirects/migrations/__init__.py -> build/lib/django/contrib/redirects/migrations
2025-04-22 17:58:53,146 root INFO copying django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py -> build/lib/django/contrib/redirects/migrations
2025-04-22 17:58:53,146 root INFO copying django/contrib/redirects/migrations/0001_initial.py -> build/lib/django/contrib/redirects/migrations
2025-04-22 17:58:53,146 root INFO creating build/lib/django/contrib/messages/storage
2025-04-22 17:58:53,146 root INFO copying django/contrib/messages/storage/__init__.py -> build/lib/django/contrib/messages/storage
2025-04-22 17:58:53,147 root INFO copying django/contrib/messages/storage/session.py -> build/lib/django/contrib/messages/storage
2025-04-22 17:58:53,147 root INFO copying django/contrib/messages/storage/cookie.py -> build/lib/django/contrib/messages/storage
2025-04-22 17:58:53,147 root INFO copying django/contrib/messages/storage/fallback.py -> build/lib/django/contrib/messages/storage
2025-04-22 17:58:53,147 root INFO copying django/contrib/messages/storage/base.py -> build/lib/django/contrib/messages/storage
2025-04-22 17:58:53,148 root INFO creating build/lib/django/contrib/sites/migrations
2025-04-22 17:58:53,148 root INFO copying django/contrib/sites/migrations/__init__.py -> build/lib/django/contrib/sites/migrations
2025-04-22 17:58:53,148 root INFO copying django/contrib/sites/migrations/0001_initial.py -> build/lib/django/contrib/sites/migrations
2025-04-22 17:58:53,148 root INFO copying django/contrib/sites/migrations/0002_alter_domain_unique.py -> build/lib/django/contrib/sites/migrations
2025-04-22 17:58:53,148 root INFO creating build/lib/django/contrib/sitemaps/management
2025-04-22 17:58:53,149 root INFO copying django/contrib/sitemaps/management/__init__.py -> build/lib/django/contrib/sitemaps/management
2025-04-22 17:58:53,149 root INFO creating build/lib/django/contrib/sitemaps/management/commands
2025-04-22 17:58:53,149 root INFO copying django/contrib/sitemaps/management/commands/__init__.py -> build/lib/django/contrib/sitemaps/management/commands
2025-04-22 17:58:53,149 root INFO copying django/contrib/sitemaps/management/commands/ping_google.py -> build/lib/django/contrib/sitemaps/management/commands
2025-04-22 17:58:53,149 root INFO creating build/lib/django/contrib/flatpages/migrations
2025-04-22 17:58:53,150 root INFO copying django/contrib/flatpages/migrations/__init__.py -> build/lib/django/contrib/flatpages/migrations
2025-04-22 17:58:53,150 root INFO copying django/contrib/flatpages/migrations/0001_initial.py -> build/lib/django/contrib/flatpages/migrations
2025-04-22 17:58:53,150 root INFO creating build/lib/django/contrib/flatpages/templatetags
2025-04-22 17:58:53,150 root INFO copying django/contrib/flatpages/templatetags/__init__.py -> build/lib/django/contrib/flatpages/templatetags
2025-04-22 17:58:53,150 root INFO copying django/contrib/flatpages/templatetags/flatpages.py -> build/lib/django/contrib/flatpages/templatetags
2025-04-22 17:58:53,151 root INFO creating build/lib/django/contrib/staticfiles/management
2025-04-22 17:58:53,151 root INFO copying django/contrib/staticfiles/management/__init__.py -> build/lib/django/contrib/staticfiles/management
2025-04-22 17:58:53,151 root INFO creating build/lib/django/contrib/staticfiles/management/commands
2025-04-22 17:58:53,151 root INFO copying django/contrib/staticfiles/management/commands/__init__.py -> build/lib/django/contrib/staticfiles/management/commands
2025-04-22 17:58:53,151 root INFO copying django/contrib/staticfiles/management/commands/collectstatic.py -> build/lib/django/contrib/staticfiles/management/commands
2025-04-22 17:58:53,152 root INFO copying django/contrib/staticfiles/management/commands/findstatic.py -> build/lib/django/contrib/staticfiles/management/commands
2025-04-22 17:58:53,152 root INFO copying django/contrib/staticfiles/management/commands/runserver.py -> build/lib/django/contrib/staticfiles/management/commands
2025-04-22 17:58:53,152 root INFO creating build/lib/django/contrib/sessions/migrations
2025-04-22 17:58:53,152 root INFO copying django/contrib/sessions/migrations/__init__.py -> build/lib/django/contrib/sessions/migrations
2025-04-22 17:58:53,153 root INFO copying django/contrib/sessions/migrations/0001_initial.py -> build/lib/django/contrib/sessions/migrations
2025-04-22 17:58:53,153 root INFO creating build/lib/django/contrib/sessions/management
2025-04-22 17:58:53,153 root INFO copying django/contrib/sessions/management/__init__.py -> build/lib/django/contrib/sessions/management
2025-04-22 17:58:53,153 root INFO creating build/lib/django/contrib/sessions/backends
2025-04-22 17:58:53,154 root INFO copying django/contrib/sessions/backends/__init__.py -> build/lib/django/contrib/sessions/backends
2025-04-22 17:58:53,154 root INFO copying django/contrib/sessions/backends/cache.py -> build/lib/django/contrib/sessions/backends
2025-04-22 17:58:53,154 root INFO copying django/contrib/sessions/backends/db.py -> build/lib/django/contrib/sessions/backends
2025-04-22 17:58:53,154 root INFO copying django/contrib/sessions/backends/cached_db.py -> build/lib/django/contrib/sessions/backends
2025-04-22 17:58:53,154 root INFO copying django/contrib/sessions/backends/signed_cookies.py -> build/lib/django/contrib/sessions/backends
2025-04-22 17:58:53,155 root INFO copying django/contrib/sessions/backends/base.py -> build/lib/django/contrib/sessions/backends
2025-04-22 17:58:53,155 root INFO copying django/contrib/sessions/backends/file.py -> build/lib/django/contrib/sessions/backends
2025-04-22 17:58:53,155 root INFO creating build/lib/django/contrib/sessions/management/commands
2025-04-22 17:58:53,155 root INFO copying django/contrib/sessions/management/commands/__init__.py -> build/lib/django/contrib/sessions/management/commands
2025-04-22 17:58:53,156 root INFO copying django/contrib/sessions/management/commands/clearsessions.py -> build/lib/django/contrib/sessions/management/commands
2025-04-22 17:58:53,156 root INFO creating build/lib/django/contrib/postgres/aggregates
2025-04-22 17:58:53,156 root INFO copying django/contrib/postgres/aggregates/__init__.py -> build/lib/django/contrib/postgres/aggregates
2025-04-22 17:58:53,156 root INFO copying django/contrib/postgres/aggregates/statistics.py -> build/lib/django/contrib/postgres/aggregates
2025-04-22 17:58:53,156 root INFO copying django/contrib/postgres/aggregates/general.py -> build/lib/django/contrib/postgres/aggregates
2025-04-22 17:58:53,157 root INFO copying django/contrib/postgres/aggregates/mixins.py -> build/lib/django/contrib/postgres/aggregates
2025-04-22 17:58:53,157 root INFO creating build/lib/django/contrib/postgres/fields
2025-04-22 17:58:53,157 root INFO copying django/contrib/postgres/fields/__init__.py -> build/lib/django/contrib/postgres/fields
2025-04-22 17:58:53,157 root INFO copying django/contrib/postgres/fields/hstore.py -> build/lib/django/contrib/postgres/fields
2025-04-22 17:58:53,158 root INFO copying django/contrib/postgres/fields/citext.py -> build/lib/django/contrib/postgres/fields
2025-04-22 17:58:53,158 root INFO copying django/contrib/postgres/fields/jsonb.py -> build/lib/django/contrib/postgres/fields
2025-04-22 17:58:53,158 root INFO copying django/contrib/postgres/fields/utils.py -> build/lib/django/contrib/postgres/fields
2025-04-22 17:58:53,158 root INFO copying django/contrib/postgres/fields/ranges.py -> build/lib/django/contrib/postgres/fields
2025-04-22 17:58:53,158 root INFO copying django/contrib/postgres/fields/array.py -> build/lib/django/contrib/postgres/fields
2025-04-22 17:58:53,159 root INFO creating build/lib/django/contrib/postgres/forms
2025-04-22 17:58:53,159 root INFO copying django/contrib/postgres/forms/__init__.py -> build/lib/django/contrib/postgres/forms
2025-04-22 17:58:53,159 root INFO copying django/contrib/postgres/forms/hstore.py -> build/lib/django/contrib/postgres/forms
2025-04-22 17:58:53,159 root INFO copying django/contrib/postgres/forms/ranges.py -> build/lib/django/contrib/postgres/forms
2025-04-22 17:58:53,160 root INFO copying django/contrib/postgres/forms/array.py -> build/lib/django/contrib/postgres/forms
2025-04-22 17:58:53,160 root INFO creating build/lib/django/contrib/gis/db
2025-04-22 17:58:53,160 root INFO copying django/contrib/gis/db/__init__.py -> build/lib/django/contrib/gis/db
2025-04-22 17:58:53,160 root INFO creating build/lib/django/contrib/gis/sitemaps
2025-04-22 17:58:53,161 root INFO copying django/contrib/gis/sitemaps/__init__.py -> build/lib/django/contrib/gis/sitemaps
2025-04-22 17:58:53,161 root INFO copying django/contrib/gis/sitemaps/views.py -> build/lib/django/contrib/gis/sitemaps
2025-04-22 17:58:53,161 root INFO copying django/contrib/gis/sitemaps/kml.py -> build/lib/django/contrib/gis/sitemaps
2025-04-22 17:58:53,161 root INFO creating build/lib/django/contrib/gis/utils
2025-04-22 17:58:53,161 root INFO copying django/contrib/gis/utils/__init__.py -> build/lib/django/contrib/gis/utils
2025-04-22 17:58:53,162 root INFO copying django/contrib/gis/utils/layermapping.py -> build/lib/django/contrib/gis/utils
2025-04-22 17:58:53,162 root INFO copying django/contrib/gis/utils/srs.py -> build/lib/django/contrib/gis/utils
2025-04-22 17:58:53,162 root INFO copying django/contrib/gis/utils/ogrinfo.py -> build/lib/django/contrib/gis/utils
2025-04-22 17:58:53,162 root INFO copying django/contrib/gis/utils/ogrinspect.py -> build/lib/django/contrib/gis/utils
2025-04-22 17:58:53,163 root INFO creating build/lib/django/contrib/gis/geoip2
2025-04-22 17:58:53,163 root INFO copying django/contrib/gis/geoip2/__init__.py -> build/lib/django/contrib/gis/geoip2
2025-04-22 17:58:53,163 root INFO copying django/contrib/gis/geoip2/resources.py -> build/lib/django/contrib/gis/geoip2
2025-04-22 17:58:53,163 root INFO copying django/contrib/gis/geoip2/base.py -> build/lib/django/contrib/gis/geoip2
2025-04-22 17:58:53,164 root INFO creating build/lib/django/contrib/gis/management
2025-04-22 17:58:53,164 root INFO copying django/contrib/gis/management/__init__.py -> build/lib/django/contrib/gis/management
2025-04-22 17:58:53,164 root INFO creating build/lib/django/contrib/gis/serializers
2025-04-22 17:58:53,164 root INFO copying django/contrib/gis/serializers/__init__.py -> build/lib/django/contrib/gis/serializers
2025-04-22 17:58:53,165 root INFO copying django/contrib/gis/serializers/geojson.py -> build/lib/django/contrib/gis/serializers
2025-04-22 17:58:53,165 root INFO creating build/lib/django/contrib/gis/admin
2025-04-22 17:58:53,165 root INFO copying django/contrib/gis/admin/__init__.py -> build/lib/django/contrib/gis/admin
2025-04-22 17:58:53,165 root INFO copying django/contrib/gis/admin/options.py -> build/lib/django/contrib/gis/admin
2025-04-22 17:58:53,165 root INFO copying django/contrib/gis/admin/widgets.py -> build/lib/django/contrib/gis/admin
2025-04-22 17:58:53,166 root INFO creating build/lib/django/contrib/gis/geos
2025-04-22 17:58:53,166 root INFO copying django/contrib/gis/geos/__init__.py -> build/lib/django/contrib/gis/geos
2025-04-22 17:58:53,166 root INFO copying django/contrib/gis/geos/libgeos.py -> build/lib/django/contrib/gis/geos
2025-04-22 17:58:53,166 root INFO copying django/contrib/gis/geos/collections.py -> build/lib/django/contrib/gis/geos
2025-04-22 17:58:53,167 root INFO copying django/contrib/gis/geos/linestring.py -> build/lib/django/contrib/gis/geos
2025-04-22 17:58:53,167 root INFO copying django/contrib/gis/geos/prepared.py -> build/lib/django/contrib/gis/geos
2025-04-22 17:58:53,167 root INFO copying django/contrib/gis/geos/io.py -> build/lib/django/contrib/gis/geos
2025-04-22 17:58:53,167 root INFO copying django/contrib/gis/geos/mutable_list.py -> build/lib/django/contrib/gis/geos
2025-04-22 17:58:53,167 root INFO copying django/contrib/gis/geos/point.py -> build/lib/django/contrib/gis/geos
2025-04-22 17:58:53,168 root INFO copying django/contrib/gis/geos/geometry.py -> build/lib/django/contrib/gis/geos
2025-04-22 17:58:53,168 root INFO copying django/contrib/gis/geos/polygon.py -> build/lib/django/contrib/gis/geos
2025-04-22 17:58:53,168 root INFO copying django/contrib/gis/geos/error.py -> build/lib/django/contrib/gis/geos
2025-04-22 17:58:53,168 root INFO copying django/contrib/gis/geos/factory.py -> build/lib/django/contrib/gis/geos
2025-04-22 17:58:53,168 root INFO copying django/contrib/gis/geos/base.py -> build/lib/django/contrib/gis/geos
2025-04-22 17:58:53,169 root INFO copying django/contrib/gis/geos/coordseq.py -> build/lib/django/contrib/gis/geos
2025-04-22 17:58:53,169 root INFO creating build/lib/django/contrib/gis/gdal
2025-04-22 17:58:53,169 root INFO copying django/contrib/gis/gdal/__init__.py -> build/lib/django/contrib/gis/gdal
2025-04-22 17:58:53,170 root INFO copying django/contrib/gis/gdal/geomtype.py -> build/lib/django/contrib/gis/gdal
2025-04-22 17:58:53,170 root INFO copying django/contrib/gis/gdal/field.py -> build/lib/django/contrib/gis/gdal
2025-04-22 17:58:53,170 root INFO copying django/contrib/gis/gdal/geometries.py -> build/lib/django/contrib/gis/gdal
2025-04-22 17:58:53,170 root INFO copying django/contrib/gis/gdal/feature.py -> build/lib/django/contrib/gis/gdal
2025-04-22 17:58:53,170 root INFO copying django/contrib/gis/gdal/envelope.py -> build/lib/django/contrib/gis/gdal
2025-04-22 17:58:53,171 root INFO copying django/contrib/gis/gdal/libgdal.py -> build/lib/django/contrib/gis/gdal
2025-04-22 17:58:53,171 root INFO copying django/contrib/gis/gdal/srs.py -> build/lib/django/contrib/gis/gdal
2025-04-22 17:58:53,171 root INFO copying django/contrib/gis/gdal/error.py -> build/lib/django/contrib/gis/gdal
2025-04-22 17:58:53,171 root INFO copying django/contrib/gis/gdal/datasource.py -> build/lib/django/contrib/gis/gdal
2025-04-22 17:58:53,172 root INFO copying django/contrib/gis/gdal/driver.py -> build/lib/django/contrib/gis/gdal
2025-04-22 17:58:53,172 root INFO copying django/contrib/gis/gdal/layer.py -> build/lib/django/contrib/gis/gdal
2025-04-22 17:58:53,172 root INFO copying django/contrib/gis/gdal/base.py -> build/lib/django/contrib/gis/gdal
2025-04-22 17:58:53,172 root INFO creating build/lib/django/contrib/gis/forms
2025-04-22 17:58:53,172 root INFO copying django/contrib/gis/forms/__init__.py -> build/lib/django/contrib/gis/forms
2025-04-22 17:58:53,173 root INFO copying django/contrib/gis/forms/widgets.py -> build/lib/django/contrib/gis/forms
2025-04-22 17:58:53,173 root INFO copying django/contrib/gis/forms/fields.py -> build/lib/django/contrib/gis/forms
2025-04-22 17:58:53,173 root INFO creating build/lib/django/contrib/gis/db/models
2025-04-22 17:58:53,173 root INFO copying django/contrib/gis/db/models/__init__.py -> build/lib/django/contrib/gis/db/models
2025-04-22 17:58:53,174 root INFO copying django/contrib/gis/db/models/functions.py -> build/lib/django/contrib/gis/db/models
2025-04-22 17:58:53,174 root INFO copying django/contrib/gis/db/models/lookups.py -> build/lib/django/contrib/gis/db/models
2025-04-22 17:58:53,174 root INFO copying django/contrib/gis/db/models/fields.py -> build/lib/django/contrib/gis/db/models
2025-04-22 17:58:53,174 root INFO copying django/contrib/gis/db/models/aggregates.py -> build/lib/django/contrib/gis/db/models
2025-04-22 17:58:53,175 root INFO copying django/contrib/gis/db/models/proxy.py -> build/lib/django/contrib/gis/db/models
2025-04-22 17:58:53,175 root INFO creating build/lib/django/contrib/gis/db/backends
2025-04-22 17:58:53,175 root INFO copying django/contrib/gis/db/backends/__init__.py -> build/lib/django/contrib/gis/db/backends
2025-04-22 17:58:53,175 root INFO copying django/contrib/gis/db/backends/utils.py -> build/lib/django/contrib/gis/db/backends
2025-04-22 17:58:53,176 root INFO creating build/lib/django/contrib/gis/db/models/sql
2025-04-22 17:58:53,176 root INFO copying django/contrib/gis/db/models/sql/__init__.py -> build/lib/django/contrib/gis/db/models/sql
2025-04-22 17:58:53,176 root INFO copying django/contrib/gis/db/models/sql/conversion.py -> build/lib/django/contrib/gis/db/models/sql
2025-04-22 17:58:53,176 root INFO creating build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:53,177 root INFO copying django/contrib/gis/db/backends/spatialite/__init__.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:53,177 root INFO copying django/contrib/gis/db/backends/spatialite/schema.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:53,177 root INFO copying django/contrib/gis/db/backends/spatialite/features.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:53,177 root INFO copying django/contrib/gis/db/backends/spatialite/operations.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:53,177 root INFO copying django/contrib/gis/db/backends/spatialite/models.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:53,178 root INFO copying django/contrib/gis/db/backends/spatialite/introspection.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:53,178 root INFO copying django/contrib/gis/db/backends/spatialite/base.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:53,178 root INFO copying django/contrib/gis/db/backends/spatialite/client.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:53,178 root INFO copying django/contrib/gis/db/backends/spatialite/adapter.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:53,179 root INFO creating build/lib/django/contrib/gis/db/backends/base
2025-04-22 17:58:53,179 root INFO copying django/contrib/gis/db/backends/base/__init__.py -> build/lib/django/contrib/gis/db/backends/base
2025-04-22 17:58:53,179 root INFO copying django/contrib/gis/db/backends/base/features.py -> build/lib/django/contrib/gis/db/backends/base
2025-04-22 17:58:53,179 root INFO copying django/contrib/gis/db/backends/base/operations.py -> build/lib/django/contrib/gis/db/backends/base
2025-04-22 17:58:53,179 root INFO copying django/contrib/gis/db/backends/base/models.py -> build/lib/django/contrib/gis/db/backends/base
2025-04-22 17:58:53,180 root INFO copying django/contrib/gis/db/backends/base/adapter.py -> build/lib/django/contrib/gis/db/backends/base
2025-04-22 17:58:53,180 root INFO creating build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 17:58:53,180 root INFO copying django/contrib/gis/db/backends/postgis/__init__.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 17:58:53,180 root INFO copying django/contrib/gis/db/backends/postgis/schema.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 17:58:53,181 root INFO copying django/contrib/gis/db/backends/postgis/features.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 17:58:53,181 root INFO copying django/contrib/gis/db/backends/postgis/operations.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 17:58:53,181 root INFO copying django/contrib/gis/db/backends/postgis/models.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 17:58:53,181 root INFO copying django/contrib/gis/db/backends/postgis/introspection.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 17:58:53,181 root INFO copying django/contrib/gis/db/backends/postgis/base.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 17:58:53,182 root INFO copying django/contrib/gis/db/backends/postgis/const.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 17:58:53,182 root INFO copying django/contrib/gis/db/backends/postgis/pgraster.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 17:58:53,182 root INFO copying django/contrib/gis/db/backends/postgis/adapter.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 17:58:53,182 root INFO creating build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 17:58:53,183 root INFO copying django/contrib/gis/db/backends/oracle/__init__.py -> build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 17:58:53,183 root INFO copying django/contrib/gis/db/backends/oracle/schema.py -> build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 17:58:53,183 root INFO copying django/contrib/gis/db/backends/oracle/features.py -> build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 17:58:53,183 root INFO copying django/contrib/gis/db/backends/oracle/operations.py -> build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 17:58:53,184 root INFO copying django/contrib/gis/db/backends/oracle/models.py -> build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 17:58:53,184 root INFO copying django/contrib/gis/db/backends/oracle/introspection.py -> build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 17:58:53,184 root INFO copying django/contrib/gis/db/backends/oracle/base.py -> build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 17:58:53,184 root INFO copying django/contrib/gis/db/backends/oracle/adapter.py -> build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 17:58:53,185 root INFO creating build/lib/django/contrib/gis/db/backends/mysql
2025-04-22 17:58:53,185 root INFO copying django/contrib/gis/db/backends/mysql/__init__.py -> build/lib/django/contrib/gis/db/backends/mysql
2025-04-22 17:58:53,185 root INFO copying django/contrib/gis/db/backends/mysql/schema.py -> build/lib/django/contrib/gis/db/backends/mysql
2025-04-22 17:58:53,185 root INFO copying django/contrib/gis/db/backends/mysql/features.py -> build/lib/django/contrib/gis/db/backends/mysql
2025-04-22 17:58:53,185 root INFO copying django/contrib/gis/db/backends/mysql/operations.py -> build/lib/django/contrib/gis/db/backends/mysql
2025-04-22 17:58:53,186 root INFO copying django/contrib/gis/db/backends/mysql/introspection.py -> build/lib/django/contrib/gis/db/backends/mysql
2025-04-22 17:58:53,186 root INFO copying django/contrib/gis/db/backends/mysql/base.py -> build/lib/django/contrib/gis/db/backends/mysql
2025-04-22 17:58:53,186 root INFO creating build/lib/django/contrib/gis/management/commands
2025-04-22 17:58:53,186 root INFO copying django/contrib/gis/management/commands/__init__.py -> build/lib/django/contrib/gis/management/commands
2025-04-22 17:58:53,186 root INFO copying django/contrib/gis/management/commands/inspectdb.py -> build/lib/django/contrib/gis/management/commands
2025-04-22 17:58:53,187 root INFO copying django/contrib/gis/management/commands/ogrinspect.py -> build/lib/django/contrib/gis/management/commands
2025-04-22 17:58:53,187 root INFO creating build/lib/django/contrib/gis/geos/prototypes
2025-04-22 17:58:53,187 root INFO copying django/contrib/gis/geos/prototypes/__init__.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 17:58:53,187 root INFO copying django/contrib/gis/geos/prototypes/prepared.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 17:58:53,188 root INFO copying django/contrib/gis/geos/prototypes/io.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 17:58:53,188 root INFO copying django/contrib/gis/geos/prototypes/threadsafe.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 17:58:53,188 root INFO copying django/contrib/gis/geos/prototypes/errcheck.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 17:58:53,188 root INFO copying django/contrib/gis/geos/prototypes/misc.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 17:58:53,189 root INFO copying django/contrib/gis/geos/prototypes/predicates.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 17:58:53,189 root INFO copying django/contrib/gis/geos/prototypes/topology.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 17:58:53,189 root INFO copying django/contrib/gis/geos/prototypes/geom.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 17:58:53,189 root INFO copying django/contrib/gis/geos/prototypes/coordseq.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 17:58:53,190 root INFO creating build/lib/django/contrib/gis/gdal/raster
2025-04-22 17:58:53,190 root INFO copying django/contrib/gis/gdal/raster/__init__.py -> build/lib/django/contrib/gis/gdal/raster
2025-04-22 17:58:53,190 root INFO copying django/contrib/gis/gdal/raster/source.py -> build/lib/django/contrib/gis/gdal/raster
2025-04-22 17:58:53,190 root INFO copying django/contrib/gis/gdal/raster/band.py -> build/lib/django/contrib/gis/gdal/raster
2025-04-22 17:58:53,190 root INFO copying django/contrib/gis/gdal/raster/base.py -> build/lib/django/contrib/gis/gdal/raster
2025-04-22 17:58:53,191 root INFO copying django/contrib/gis/gdal/raster/const.py -> build/lib/django/contrib/gis/gdal/raster
2025-04-22 17:58:53,191 root INFO creating build/lib/django/contrib/gis/gdal/prototypes
2025-04-22 17:58:53,191 root INFO copying django/contrib/gis/gdal/prototypes/__init__.py -> build/lib/django/contrib/gis/gdal/prototypes
2025-04-22 17:58:53,191 root INFO copying django/contrib/gis/gdal/prototypes/generation.py -> build/lib/django/contrib/gis/gdal/prototypes
2025-04-22 17:58:53,192 root INFO copying django/contrib/gis/gdal/prototypes/ds.py -> build/lib/django/contrib/gis/gdal/prototypes
2025-04-22 17:58:53,192 root INFO copying django/contrib/gis/gdal/prototypes/raster.py -> build/lib/django/contrib/gis/gdal/prototypes
2025-04-22 17:58:53,192 root INFO copying django/contrib/gis/gdal/prototypes/srs.py -> build/lib/django/contrib/gis/gdal/prototypes
2025-04-22 17:58:53,192 root INFO copying django/contrib/gis/gdal/prototypes/errcheck.py -> build/lib/django/contrib/gis/gdal/prototypes
2025-04-22 17:58:53,192 root INFO copying django/contrib/gis/gdal/prototypes/geom.py -> build/lib/django/contrib/gis/gdal/prototypes
2025-04-22 17:58:53,193 root INFO creating build/lib/django/contrib/admin/views
2025-04-22 17:58:53,193 root INFO copying django/contrib/admin/views/__init__.py -> build/lib/django/contrib/admin/views
2025-04-22 17:58:53,193 root INFO copying django/contrib/admin/views/decorators.py -> build/lib/django/contrib/admin/views
2025-04-22 17:58:53,193 root INFO copying django/contrib/admin/views/autocomplete.py -> build/lib/django/contrib/admin/views
2025-04-22 17:58:53,194 root INFO copying django/contrib/admin/views/main.py -> build/lib/django/contrib/admin/views
2025-04-22 17:58:53,194 root INFO creating build/lib/django/contrib/admin/migrations
2025-04-22 17:58:53,194 root INFO copying django/contrib/admin/migrations/__init__.py -> build/lib/django/contrib/admin/migrations
2025-04-22 17:58:53,194 root INFO copying django/contrib/admin/migrations/0002_logentry_remove_auto_add.py -> build/lib/django/contrib/admin/migrations
2025-04-22 17:58:53,195 root INFO copying django/contrib/admin/migrations/0001_initial.py -> build/lib/django/contrib/admin/migrations
2025-04-22 17:58:53,195 root INFO copying django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py -> build/lib/django/contrib/admin/migrations
2025-04-22 17:58:53,195 root INFO creating build/lib/django/contrib/admin/templatetags
2025-04-22 17:58:53,195 root INFO copying django/contrib/admin/templatetags/__init__.py -> build/lib/django/contrib/admin/templatetags
2025-04-22 17:58:53,195 root INFO copying django/contrib/admin/templatetags/log.py -> build/lib/django/contrib/admin/templatetags
2025-04-22 17:58:53,196 root INFO copying django/contrib/admin/templatetags/admin_urls.py -> build/lib/django/contrib/admin/templatetags
2025-04-22 17:58:53,196 root INFO copying django/contrib/admin/templatetags/admin_modify.py -> build/lib/django/contrib/admin/templatetags
2025-04-22 17:58:53,196 root INFO copying django/contrib/admin/templatetags/admin_list.py -> build/lib/django/contrib/admin/templatetags
2025-04-22 17:58:53,196 root INFO copying django/contrib/admin/templatetags/base.py -> build/lib/django/contrib/admin/templatetags
2025-04-22 17:58:53,197 root INFO creating build/lib/django/contrib/humanize/templatetags
2025-04-22 17:58:53,197 root INFO copying django/contrib/humanize/templatetags/__init__.py -> build/lib/django/contrib/humanize/templatetags
2025-04-22 17:58:53,197 root INFO copying django/contrib/humanize/templatetags/humanize.py -> build/lib/django/contrib/humanize/templatetags
2025-04-22 17:58:53,198 root INFO running egg_info
2025-04-22 17:58:53,201 root INFO writing Django.egg-info/PKG-INFO
2025-04-22 17:58:53,202 root INFO writing dependency_links to Django.egg-info/dependency_links.txt
2025-04-22 17:58:53,203 root INFO writing entry points to Django.egg-info/entry_points.txt
2025-04-22 17:58:53,204 root INFO writing requirements to Django.egg-info/requires.txt
2025-04-22 17:58:53,204 root INFO writing top-level names to Django.egg-info/top_level.txt
2025-04-22 17:58:53,245 root INFO reading manifest file 'Django.egg-info/SOURCES.txt'
2025-04-22 17:58:53,369 root INFO reading manifest template 'MANIFEST.in'
2025-04-22 17:58:53,527 root WARNING warning: no previously-included files matching '__pycache__' found anywhere in distribution
2025-04-22 17:58:53,539 root INFO adding license file 'LICENSE'
2025-04-22 17:58:53,539 root INFO adding license file 'LICENSE.python'
2025-04-22 17:58:53,539 root INFO adding license file 'AUTHORS'
2025-04-22 17:58:53,693 root INFO writing manifest file 'Django.egg-info/SOURCES.txt'
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.app_template' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.app_template' 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.conf.app_template' 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.conf.app_template' to be distributed and are
        already explicitly excluding 'django.conf.app_template' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.app_template.migrations' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.app_template.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 'django.conf.app_template.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 'django.conf.app_template.migrations' to be distributed and are
        already explicitly excluding 'django.conf.app_template.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.af.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.conf.locale.af.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.conf.locale.af.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.af.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.ar.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.conf.locale.ar.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.conf.locale.ar.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.ar.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.ar_DZ.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.conf.locale.ar_DZ.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.conf.locale.ar_DZ.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.ar_DZ.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.ast.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.conf.locale.ast.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.conf.locale.ast.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.ast.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.az.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.conf.locale.az.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.conf.locale.az.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.az.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.be.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.conf.locale.be.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.conf.locale.be.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.be.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.bg.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.conf.locale.bg.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.conf.locale.bg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.bg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.bn.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.conf.locale.bn.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.conf.locale.bn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.bn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.br.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.conf.locale.br.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.conf.locale.br.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.br.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.bs.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.conf.locale.bs.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.conf.locale.bs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.bs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.ca.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.conf.locale.ca.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.conf.locale.ca.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.ca.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.ckb.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.conf.locale.ckb.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.conf.locale.ckb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.ckb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.cs.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.conf.locale.cs.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.conf.locale.cs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.cs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.cy.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.conf.locale.cy.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.conf.locale.cy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.cy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.da.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.conf.locale.da.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.conf.locale.da.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.da.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.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.conf.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.conf.locale.de.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.dsb.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.conf.locale.dsb.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.conf.locale.dsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.dsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.el.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.conf.locale.el.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.conf.locale.el.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.el.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.en.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.conf.locale.en.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.conf.locale.en.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.en.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.en_AU.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.conf.locale.en_AU.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.conf.locale.en_AU.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.en_AU.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.en_GB.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.conf.locale.en_GB.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.conf.locale.en_GB.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.en_GB.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.eo.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.conf.locale.eo.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.conf.locale.eo.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.eo.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.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.conf.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.conf.locale.es.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.es_AR.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.conf.locale.es_AR.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.conf.locale.es_AR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.es_AR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.es_CO.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.conf.locale.es_CO.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.conf.locale.es_CO.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.es_CO.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.es_MX.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.conf.locale.es_MX.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.conf.locale.es_MX.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.es_MX.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.es_VE.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.conf.locale.es_VE.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.conf.locale.es_VE.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.es_VE.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.et.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.conf.locale.et.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.conf.locale.et.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.et.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.eu.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.conf.locale.eu.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.conf.locale.eu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.eu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.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.conf.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.conf.locale.fa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.fi.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.conf.locale.fi.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.conf.locale.fi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.fi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.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.conf.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.conf.locale.fr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.fy.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.conf.locale.fy.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.conf.locale.fy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.fy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.ga.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.conf.locale.ga.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.conf.locale.ga.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.ga.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.gd.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.conf.locale.gd.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.conf.locale.gd.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.gd.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.gl.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.conf.locale.gl.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.conf.locale.gl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.gl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.he.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.conf.locale.he.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.conf.locale.he.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.he.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.hi.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.conf.locale.hi.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.conf.locale.hi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.hi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.hr.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.conf.locale.hr.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.conf.locale.hr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.hr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.hsb.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.conf.locale.hsb.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.conf.locale.hsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.hsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.hu.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.conf.locale.hu.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.conf.locale.hu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.hu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.hy.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.conf.locale.hy.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.conf.locale.hy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.hy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.ia.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.conf.locale.ia.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.conf.locale.ia.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.ia.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.id.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.conf.locale.id.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.conf.locale.id.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.id.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ig.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.ig.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.conf.locale.ig.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.conf.locale.ig.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.ig.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.io.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.conf.locale.io.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.conf.locale.io.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.io.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.is.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.conf.locale.is.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.conf.locale.is.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.is.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.it.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.conf.locale.it.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.conf.locale.it.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.it.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.ja.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.conf.locale.ja.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.conf.locale.ja.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.ja.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.ka.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.conf.locale.ka.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.conf.locale.ka.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.ka.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.kab.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.conf.locale.kab.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.conf.locale.kab.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.kab.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.kk.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.conf.locale.kk.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.conf.locale.kk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.kk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.km.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.conf.locale.km.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.conf.locale.km.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.km.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.kn.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.conf.locale.kn.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.conf.locale.kn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.kn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.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.conf.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.conf.locale.ko.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.ky.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.conf.locale.ky.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.conf.locale.ky.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.ky.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.lb.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.conf.locale.lb.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.conf.locale.lb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.lb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.lt.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.conf.locale.lt.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.conf.locale.lt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.lt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.lv.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.conf.locale.lv.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.conf.locale.lv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.lv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.mk.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.conf.locale.mk.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.conf.locale.mk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.mk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.ml.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.conf.locale.ml.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.conf.locale.ml.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.ml.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.mn.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.conf.locale.mn.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.conf.locale.mn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.mn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.mr.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.conf.locale.mr.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.conf.locale.mr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.mr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.ms.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.conf.locale.ms.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.conf.locale.ms.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.ms.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.my.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.conf.locale.my.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.conf.locale.my.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.my.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.nb.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.conf.locale.nb.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.conf.locale.nb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.nb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.ne.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.conf.locale.ne.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.conf.locale.ne.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.ne.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.nl.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.conf.locale.nl.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.conf.locale.nl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.nl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.nn.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.conf.locale.nn.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.conf.locale.nn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.nn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.os.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.conf.locale.os.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.conf.locale.os.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.os.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.pa.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.conf.locale.pa.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.conf.locale.pa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.pa.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.pl.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.conf.locale.pl.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.conf.locale.pl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.pl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.pt.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.conf.locale.pt.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.conf.locale.pt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.pt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.pt_BR.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.conf.locale.pt_BR.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.conf.locale.pt_BR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.pt_BR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.ro.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.conf.locale.ro.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.conf.locale.ro.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.ro.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.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.conf.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.conf.locale.ru.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.sk.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.conf.locale.sk.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.conf.locale.sk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.sk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.sl.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.conf.locale.sl.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.conf.locale.sl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.sl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.sq.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.conf.locale.sq.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.conf.locale.sq.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.sq.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.sr.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.conf.locale.sr.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.conf.locale.sr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.sr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.sr_Latn.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.conf.locale.sr_Latn.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.conf.locale.sr_Latn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.sr_Latn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.sv.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.conf.locale.sv.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.conf.locale.sv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.sv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.sw.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.conf.locale.sw.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.conf.locale.sw.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.sw.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.ta.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.conf.locale.ta.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.conf.locale.ta.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.ta.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.te.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.conf.locale.te.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.conf.locale.te.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.te.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.tg.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.conf.locale.tg.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.conf.locale.tg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.tg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.th.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.conf.locale.th.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.conf.locale.th.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.th.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.tk.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.conf.locale.tk.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.conf.locale.tk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.tk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.tr.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.conf.locale.tr.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.conf.locale.tr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.tr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.tt.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.conf.locale.tt.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.conf.locale.tt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.tt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.udm.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.conf.locale.udm.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.conf.locale.udm.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.udm.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.uk.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.conf.locale.uk.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.conf.locale.uk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.uk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.ur.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.conf.locale.ur.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.conf.locale.ur.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.ur.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.uz.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.conf.locale.uz.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.conf.locale.uz.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.uz.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.vi.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.conf.locale.vi.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.conf.locale.vi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.vi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.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.conf.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.conf.locale.zh_Hans.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.locale.zh_Hant.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.conf.locale.zh_Hant.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.conf.locale.zh_Hant.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.conf.locale.zh_Hant.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.project_template' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.project_template' 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.conf.project_template' 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.conf.project_template' to be distributed and are
        already explicitly excluding 'django.conf.project_template' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.project_template.project_name' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.conf.project_template.project_name' 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.conf.project_template.project_name' 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.conf.project_template.project_name' to be distributed and are
        already explicitly excluding 'django.conf.project_template.project_name' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.af.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.contrib.admin.locale.af.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.contrib.admin.locale.af.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.af.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.am.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.am.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.contrib.admin.locale.am.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.contrib.admin.locale.am.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.am.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.ar.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.contrib.admin.locale.ar.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.contrib.admin.locale.ar.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.ar.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.ar_DZ.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.contrib.admin.locale.ar_DZ.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.contrib.admin.locale.ar_DZ.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.ar_DZ.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.ast.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.contrib.admin.locale.ast.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.contrib.admin.locale.ast.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.ast.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.az.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.contrib.admin.locale.az.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.contrib.admin.locale.az.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.az.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.be.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.contrib.admin.locale.be.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.contrib.admin.locale.be.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.be.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.bg.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.contrib.admin.locale.bg.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.contrib.admin.locale.bg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.bg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.bn.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.contrib.admin.locale.bn.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.contrib.admin.locale.bn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.bn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.br.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.contrib.admin.locale.br.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.contrib.admin.locale.br.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.br.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.bs.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.contrib.admin.locale.bs.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.contrib.admin.locale.bs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.bs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.ca.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.contrib.admin.locale.ca.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.contrib.admin.locale.ca.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.ca.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.ckb.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.contrib.admin.locale.ckb.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.contrib.admin.locale.ckb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.ckb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.cs.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.contrib.admin.locale.cs.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.contrib.admin.locale.cs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.cs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.cy.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.contrib.admin.locale.cy.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.contrib.admin.locale.cy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.cy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.da.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.contrib.admin.locale.da.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.contrib.admin.locale.da.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.da.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.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.contrib.admin.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.contrib.admin.locale.de.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.dsb.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.contrib.admin.locale.dsb.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.contrib.admin.locale.dsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.dsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.el.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.contrib.admin.locale.el.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.contrib.admin.locale.el.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.el.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.en.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.contrib.admin.locale.en.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.contrib.admin.locale.en.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.en.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.en_AU.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.contrib.admin.locale.en_AU.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.contrib.admin.locale.en_AU.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.en_AU.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.en_GB.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.contrib.admin.locale.en_GB.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.contrib.admin.locale.en_GB.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.en_GB.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.eo.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.contrib.admin.locale.eo.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.contrib.admin.locale.eo.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.eo.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.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.contrib.admin.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.contrib.admin.locale.es.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.es_AR.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.contrib.admin.locale.es_AR.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.contrib.admin.locale.es_AR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.es_AR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.es_CO.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.contrib.admin.locale.es_CO.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.contrib.admin.locale.es_CO.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.es_CO.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.es_MX.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.contrib.admin.locale.es_MX.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.contrib.admin.locale.es_MX.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.es_MX.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.es_VE.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.contrib.admin.locale.es_VE.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.contrib.admin.locale.es_VE.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.es_VE.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.et.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.contrib.admin.locale.et.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.contrib.admin.locale.et.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.et.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.eu.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.contrib.admin.locale.eu.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.contrib.admin.locale.eu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.eu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.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.contrib.admin.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.contrib.admin.locale.fa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.fi.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.contrib.admin.locale.fi.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.contrib.admin.locale.fi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.fi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.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.contrib.admin.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.contrib.admin.locale.fr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.fy.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.contrib.admin.locale.fy.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.contrib.admin.locale.fy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.fy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.ga.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.contrib.admin.locale.ga.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.contrib.admin.locale.ga.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.ga.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.gd.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.contrib.admin.locale.gd.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.contrib.admin.locale.gd.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.gd.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.gl.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.contrib.admin.locale.gl.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.contrib.admin.locale.gl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.gl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.he.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.contrib.admin.locale.he.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.contrib.admin.locale.he.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.he.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.hi.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.contrib.admin.locale.hi.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.contrib.admin.locale.hi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.hi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.hr.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.contrib.admin.locale.hr.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.contrib.admin.locale.hr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.hr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.hsb.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.contrib.admin.locale.hsb.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.contrib.admin.locale.hsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.hsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.hu.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.contrib.admin.locale.hu.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.contrib.admin.locale.hu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.hu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.hy.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.contrib.admin.locale.hy.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.contrib.admin.locale.hy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.hy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.ia.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.contrib.admin.locale.ia.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.contrib.admin.locale.ia.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.ia.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.id.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.contrib.admin.locale.id.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.contrib.admin.locale.id.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.id.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.io.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.contrib.admin.locale.io.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.contrib.admin.locale.io.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.io.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.is.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.contrib.admin.locale.is.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.contrib.admin.locale.is.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.is.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.it.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.contrib.admin.locale.it.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.contrib.admin.locale.it.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.it.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.ja.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.contrib.admin.locale.ja.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.contrib.admin.locale.ja.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.ja.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.ka.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.contrib.admin.locale.ka.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.contrib.admin.locale.ka.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.ka.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.kab.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.contrib.admin.locale.kab.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.contrib.admin.locale.kab.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.kab.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.kk.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.contrib.admin.locale.kk.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.contrib.admin.locale.kk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.kk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.km.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.contrib.admin.locale.km.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.contrib.admin.locale.km.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.km.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.kn.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.contrib.admin.locale.kn.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.contrib.admin.locale.kn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.kn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.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.contrib.admin.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.contrib.admin.locale.ko.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.ky.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.contrib.admin.locale.ky.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.contrib.admin.locale.ky.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.ky.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.lb.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.contrib.admin.locale.lb.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.contrib.admin.locale.lb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.lb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.lt.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.contrib.admin.locale.lt.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.contrib.admin.locale.lt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.lt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.lv.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.contrib.admin.locale.lv.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.contrib.admin.locale.lv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.lv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.mk.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.contrib.admin.locale.mk.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.contrib.admin.locale.mk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.mk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.ml.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.contrib.admin.locale.ml.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.contrib.admin.locale.ml.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.ml.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.mn.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.contrib.admin.locale.mn.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.contrib.admin.locale.mn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.mn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.mr.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.contrib.admin.locale.mr.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.contrib.admin.locale.mr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.mr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.ms.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.contrib.admin.locale.ms.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.contrib.admin.locale.ms.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.ms.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.my.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.contrib.admin.locale.my.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.contrib.admin.locale.my.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.my.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.nb.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.contrib.admin.locale.nb.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.contrib.admin.locale.nb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.nb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.ne.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.contrib.admin.locale.ne.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.contrib.admin.locale.ne.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.ne.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.nl.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.contrib.admin.locale.nl.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.contrib.admin.locale.nl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.nl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.nn.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.contrib.admin.locale.nn.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.contrib.admin.locale.nn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.nn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.os.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.contrib.admin.locale.os.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.contrib.admin.locale.os.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.os.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.pa.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.contrib.admin.locale.pa.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.contrib.admin.locale.pa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.pa.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.pl.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.contrib.admin.locale.pl.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.contrib.admin.locale.pl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.pl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.pt.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.contrib.admin.locale.pt.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.contrib.admin.locale.pt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.pt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.pt_BR.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.contrib.admin.locale.pt_BR.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.contrib.admin.locale.pt_BR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.pt_BR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.ro.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.contrib.admin.locale.ro.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.contrib.admin.locale.ro.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.ro.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.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.contrib.admin.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.contrib.admin.locale.ru.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.sk.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.contrib.admin.locale.sk.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.contrib.admin.locale.sk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.sk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.sl.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.contrib.admin.locale.sl.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.contrib.admin.locale.sl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.sl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.sq.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.contrib.admin.locale.sq.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.contrib.admin.locale.sq.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.sq.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.sr.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.contrib.admin.locale.sr.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.contrib.admin.locale.sr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.sr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.sr_Latn.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.contrib.admin.locale.sr_Latn.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.contrib.admin.locale.sr_Latn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.sr_Latn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.sv.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.contrib.admin.locale.sv.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.contrib.admin.locale.sv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.sv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.sw.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.contrib.admin.locale.sw.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.contrib.admin.locale.sw.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.sw.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.ta.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.contrib.admin.locale.ta.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.contrib.admin.locale.ta.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.ta.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.te.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.contrib.admin.locale.te.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.contrib.admin.locale.te.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.te.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.tg.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.contrib.admin.locale.tg.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.contrib.admin.locale.tg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.tg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.th.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.contrib.admin.locale.th.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.contrib.admin.locale.th.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.th.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.tk.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.contrib.admin.locale.tk.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.contrib.admin.locale.tk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.tk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.tr.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.contrib.admin.locale.tr.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.contrib.admin.locale.tr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.tr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.tt.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.contrib.admin.locale.tt.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.contrib.admin.locale.tt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.tt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.udm.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.contrib.admin.locale.udm.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.contrib.admin.locale.udm.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.udm.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.uk.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.contrib.admin.locale.uk.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.contrib.admin.locale.uk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.uk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.ur.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.contrib.admin.locale.ur.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.contrib.admin.locale.ur.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.ur.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.uz.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.contrib.admin.locale.uz.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.contrib.admin.locale.uz.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.uz.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.vi.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.contrib.admin.locale.vi.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.contrib.admin.locale.vi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.vi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.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.contrib.admin.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.contrib.admin.locale.zh_Hans.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.locale.zh_Hant.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.contrib.admin.locale.zh_Hant.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.contrib.admin.locale.zh_Hant.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admin.locale.zh_Hant.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.css' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.static.admin.css' 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.contrib.admin.static.admin.css' 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.contrib.admin.static.admin.css' to be distributed and are
        already explicitly excluding 'django.contrib.admin.static.admin.css' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.css.vendor.select2' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.static.admin.css.vendor.select2' 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.contrib.admin.static.admin.css.vendor.select2' 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.contrib.admin.static.admin.css.vendor.select2' to be distributed and are
        already explicitly excluding 'django.contrib.admin.static.admin.css.vendor.select2' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.img' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.static.admin.img' 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.contrib.admin.static.admin.img' 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.contrib.admin.static.admin.img' to be distributed and are
        already explicitly excluding 'django.contrib.admin.static.admin.img' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.img.gis' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.static.admin.img.gis' 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.contrib.admin.static.admin.img.gis' 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.contrib.admin.static.admin.img.gis' to be distributed and are
        already explicitly excluding 'django.contrib.admin.static.admin.img.gis' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.js' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.static.admin.js' 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.contrib.admin.static.admin.js' 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.contrib.admin.static.admin.js' to be distributed and are
        already explicitly excluding 'django.contrib.admin.static.admin.js' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.js.admin' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.static.admin.js.admin' 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.contrib.admin.static.admin.js.admin' 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.contrib.admin.static.admin.js.admin' to be distributed and are
        already explicitly excluding 'django.contrib.admin.static.admin.js.admin' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.jquery' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.static.admin.js.vendor.jquery' 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.contrib.admin.static.admin.js.vendor.jquery' 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.contrib.admin.static.admin.js.vendor.jquery' to be distributed and are
        already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.jquery' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.select2' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.static.admin.js.vendor.select2' 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.contrib.admin.static.admin.js.vendor.select2' 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.contrib.admin.static.admin.js.vendor.select2' to be distributed and are
        already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.select2' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.select2.i18n' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.static.admin.js.vendor.select2.i18n' 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.contrib.admin.static.admin.js.vendor.select2.i18n' 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.contrib.admin.static.admin.js.vendor.select2.i18n' to be distributed and are
        already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.select2.i18n' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.xregexp' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.static.admin.js.vendor.xregexp' 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.contrib.admin.static.admin.js.vendor.xregexp' 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.contrib.admin.static.admin.js.vendor.xregexp' to be distributed and are
        already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.xregexp' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.templates.admin' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.templates.admin' 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.contrib.admin.templates.admin' 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.contrib.admin.templates.admin' to be distributed and are
        already explicitly excluding 'django.contrib.admin.templates.admin' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.templates.admin.auth.user' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.templates.admin.auth.user' 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.contrib.admin.templates.admin.auth.user' 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.contrib.admin.templates.admin.auth.user' to be distributed and are
        already explicitly excluding 'django.contrib.admin.templates.admin.auth.user' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.templates.admin.edit_inline' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.templates.admin.edit_inline' 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.contrib.admin.templates.admin.edit_inline' 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.contrib.admin.templates.admin.edit_inline' to be distributed and are
        already explicitly excluding 'django.contrib.admin.templates.admin.edit_inline' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.templates.admin.includes' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.templates.admin.includes' 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.contrib.admin.templates.admin.includes' 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.contrib.admin.templates.admin.includes' to be distributed and are
        already explicitly excluding 'django.contrib.admin.templates.admin.includes' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.templates.admin.widgets' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.templates.admin.widgets' 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.contrib.admin.templates.admin.widgets' 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.contrib.admin.templates.admin.widgets' to be distributed and are
        already explicitly excluding 'django.contrib.admin.templates.admin.widgets' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.templates.registration' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.templates.registration' 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.contrib.admin.templates.registration' 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.contrib.admin.templates.registration' to be distributed and are
        already explicitly excluding 'django.contrib.admin.templates.registration' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.af.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.contrib.admindocs.locale.af.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.contrib.admindocs.locale.af.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.af.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.ar.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.contrib.admindocs.locale.ar.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.contrib.admindocs.locale.ar.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.ar.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.ar_DZ.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.contrib.admindocs.locale.ar_DZ.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.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.ar_DZ.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.ast.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.contrib.admindocs.locale.ast.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.contrib.admindocs.locale.ast.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.ast.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.az.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.contrib.admindocs.locale.az.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.contrib.admindocs.locale.az.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.az.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.be.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.contrib.admindocs.locale.be.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.contrib.admindocs.locale.be.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.be.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.bg.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.contrib.admindocs.locale.bg.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.contrib.admindocs.locale.bg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.bg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.bn.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.contrib.admindocs.locale.bn.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.contrib.admindocs.locale.bn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.bn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.br.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.contrib.admindocs.locale.br.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.contrib.admindocs.locale.br.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.br.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.bs.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.contrib.admindocs.locale.bs.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.contrib.admindocs.locale.bs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.bs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.ca.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.contrib.admindocs.locale.ca.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.contrib.admindocs.locale.ca.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.ca.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.ckb.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.contrib.admindocs.locale.ckb.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.contrib.admindocs.locale.ckb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.ckb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.cs.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.contrib.admindocs.locale.cs.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.contrib.admindocs.locale.cs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.cs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.cy.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.contrib.admindocs.locale.cy.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.contrib.admindocs.locale.cy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.cy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.da.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.contrib.admindocs.locale.da.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.contrib.admindocs.locale.da.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.da.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.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.contrib.admindocs.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.contrib.admindocs.locale.de.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.dsb.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.contrib.admindocs.locale.dsb.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.contrib.admindocs.locale.dsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.dsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.el.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.contrib.admindocs.locale.el.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.contrib.admindocs.locale.el.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.el.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.en.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.contrib.admindocs.locale.en.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.contrib.admindocs.locale.en.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.en.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.en_AU.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.contrib.admindocs.locale.en_AU.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.contrib.admindocs.locale.en_AU.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.en_AU.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.en_GB.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.contrib.admindocs.locale.en_GB.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.contrib.admindocs.locale.en_GB.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.en_GB.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.eo.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.contrib.admindocs.locale.eo.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.contrib.admindocs.locale.eo.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.eo.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.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.contrib.admindocs.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.contrib.admindocs.locale.es.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.es_AR.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.contrib.admindocs.locale.es_AR.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.contrib.admindocs.locale.es_AR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.es_AR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.es_CO.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.contrib.admindocs.locale.es_CO.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.contrib.admindocs.locale.es_CO.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.es_CO.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.es_MX.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.contrib.admindocs.locale.es_MX.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.contrib.admindocs.locale.es_MX.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.es_MX.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.es_VE.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.contrib.admindocs.locale.es_VE.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.contrib.admindocs.locale.es_VE.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.es_VE.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.et.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.contrib.admindocs.locale.et.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.contrib.admindocs.locale.et.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.et.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.eu.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.contrib.admindocs.locale.eu.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.contrib.admindocs.locale.eu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.eu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.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.contrib.admindocs.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.contrib.admindocs.locale.fa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.fi.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.contrib.admindocs.locale.fi.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.contrib.admindocs.locale.fi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.fi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.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.contrib.admindocs.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.contrib.admindocs.locale.fr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.fy.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.contrib.admindocs.locale.fy.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.contrib.admindocs.locale.fy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.fy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.ga.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.contrib.admindocs.locale.ga.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.contrib.admindocs.locale.ga.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.ga.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.gd.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.contrib.admindocs.locale.gd.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.contrib.admindocs.locale.gd.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.gd.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.gl.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.contrib.admindocs.locale.gl.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.contrib.admindocs.locale.gl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.gl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.he.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.contrib.admindocs.locale.he.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.contrib.admindocs.locale.he.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.he.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.hi.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.contrib.admindocs.locale.hi.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.contrib.admindocs.locale.hi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.hi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.hr.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.contrib.admindocs.locale.hr.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.contrib.admindocs.locale.hr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.hr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.hsb.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.contrib.admindocs.locale.hsb.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.contrib.admindocs.locale.hsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.hsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.hu.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.contrib.admindocs.locale.hu.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.contrib.admindocs.locale.hu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.hu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.ia.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.contrib.admindocs.locale.ia.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.contrib.admindocs.locale.ia.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.ia.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.id.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.contrib.admindocs.locale.id.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.contrib.admindocs.locale.id.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.id.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.io.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.contrib.admindocs.locale.io.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.contrib.admindocs.locale.io.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.io.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.is.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.contrib.admindocs.locale.is.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.contrib.admindocs.locale.is.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.is.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.it.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.contrib.admindocs.locale.it.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.contrib.admindocs.locale.it.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.it.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.ja.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.contrib.admindocs.locale.ja.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.contrib.admindocs.locale.ja.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.ja.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.ka.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.contrib.admindocs.locale.ka.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.contrib.admindocs.locale.ka.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.ka.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.kab.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.contrib.admindocs.locale.kab.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.contrib.admindocs.locale.kab.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.kab.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.kk.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.contrib.admindocs.locale.kk.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.contrib.admindocs.locale.kk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.kk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.km.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.contrib.admindocs.locale.km.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.contrib.admindocs.locale.km.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.km.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.kn.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.contrib.admindocs.locale.kn.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.contrib.admindocs.locale.kn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.kn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.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.contrib.admindocs.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.contrib.admindocs.locale.ko.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.ky.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.contrib.admindocs.locale.ky.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.contrib.admindocs.locale.ky.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.ky.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.lb.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.contrib.admindocs.locale.lb.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.contrib.admindocs.locale.lb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.lb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.lt.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.contrib.admindocs.locale.lt.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.contrib.admindocs.locale.lt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.lt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.lv.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.contrib.admindocs.locale.lv.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.contrib.admindocs.locale.lv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.lv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.mk.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.contrib.admindocs.locale.mk.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.contrib.admindocs.locale.mk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.mk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.ml.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.contrib.admindocs.locale.ml.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.contrib.admindocs.locale.ml.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.ml.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.mn.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.contrib.admindocs.locale.mn.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.contrib.admindocs.locale.mn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.mn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.mr.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.contrib.admindocs.locale.mr.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.contrib.admindocs.locale.mr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.mr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.ms.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.contrib.admindocs.locale.ms.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.contrib.admindocs.locale.ms.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.ms.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.my.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.contrib.admindocs.locale.my.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.contrib.admindocs.locale.my.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.my.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.nb.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.contrib.admindocs.locale.nb.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.contrib.admindocs.locale.nb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.nb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.ne.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.contrib.admindocs.locale.ne.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.contrib.admindocs.locale.ne.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.ne.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.nl.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.contrib.admindocs.locale.nl.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.contrib.admindocs.locale.nl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.nl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.nn.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.contrib.admindocs.locale.nn.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.contrib.admindocs.locale.nn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.nn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.os.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.contrib.admindocs.locale.os.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.contrib.admindocs.locale.os.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.os.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.pa.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.contrib.admindocs.locale.pa.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.contrib.admindocs.locale.pa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.pa.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.pl.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.contrib.admindocs.locale.pl.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.contrib.admindocs.locale.pl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.pl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.pt.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.contrib.admindocs.locale.pt.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.contrib.admindocs.locale.pt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.pt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.pt_BR.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.contrib.admindocs.locale.pt_BR.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.contrib.admindocs.locale.pt_BR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.pt_BR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.ro.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.contrib.admindocs.locale.ro.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.contrib.admindocs.locale.ro.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.ro.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.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.contrib.admindocs.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.contrib.admindocs.locale.ru.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.sk.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.contrib.admindocs.locale.sk.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.contrib.admindocs.locale.sk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.sk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.sl.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.contrib.admindocs.locale.sl.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.contrib.admindocs.locale.sl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.sl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.sq.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.contrib.admindocs.locale.sq.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.contrib.admindocs.locale.sq.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.sq.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.sr.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.contrib.admindocs.locale.sr.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.contrib.admindocs.locale.sr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.sr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.sr_Latn.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.contrib.admindocs.locale.sr_Latn.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.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.sr_Latn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.sv.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.contrib.admindocs.locale.sv.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.contrib.admindocs.locale.sv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.sv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.sw.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.contrib.admindocs.locale.sw.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.contrib.admindocs.locale.sw.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.sw.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.ta.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.contrib.admindocs.locale.ta.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.contrib.admindocs.locale.ta.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.ta.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.te.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.contrib.admindocs.locale.te.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.contrib.admindocs.locale.te.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.te.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.tg.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.contrib.admindocs.locale.tg.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.contrib.admindocs.locale.tg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.tg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.th.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.contrib.admindocs.locale.th.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.contrib.admindocs.locale.th.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.th.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.tr.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.contrib.admindocs.locale.tr.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.contrib.admindocs.locale.tr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.tr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.tt.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.contrib.admindocs.locale.tt.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.contrib.admindocs.locale.tt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.tt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.udm.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.contrib.admindocs.locale.udm.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.contrib.admindocs.locale.udm.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.udm.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.uk.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.contrib.admindocs.locale.uk.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.contrib.admindocs.locale.uk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.uk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.ur.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.contrib.admindocs.locale.ur.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.contrib.admindocs.locale.ur.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.ur.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.vi.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.contrib.admindocs.locale.vi.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.contrib.admindocs.locale.vi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.vi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.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.contrib.admindocs.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.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.locale.zh_Hant.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.contrib.admindocs.locale.zh_Hant.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.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.locale.zh_Hant.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.templates.admin_doc' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admindocs.templates.admin_doc' 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.contrib.admindocs.templates.admin_doc' 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.contrib.admindocs.templates.admin_doc' to be distributed and are
        already explicitly excluding 'django.contrib.admindocs.templates.admin_doc' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.af.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.contrib.auth.locale.af.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.contrib.auth.locale.af.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.af.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.ar.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.contrib.auth.locale.ar.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.contrib.auth.locale.ar.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.ar.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.ar_DZ.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.contrib.auth.locale.ar_DZ.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.contrib.auth.locale.ar_DZ.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.ar_DZ.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.ast.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.contrib.auth.locale.ast.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.contrib.auth.locale.ast.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.ast.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.az.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.contrib.auth.locale.az.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.contrib.auth.locale.az.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.az.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.be.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.contrib.auth.locale.be.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.contrib.auth.locale.be.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.be.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.bg.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.contrib.auth.locale.bg.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.contrib.auth.locale.bg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.bg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.bn.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.contrib.auth.locale.bn.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.contrib.auth.locale.bn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.bn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.br.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.contrib.auth.locale.br.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.contrib.auth.locale.br.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.br.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.bs.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.contrib.auth.locale.bs.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.contrib.auth.locale.bs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.bs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.ca.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.contrib.auth.locale.ca.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.contrib.auth.locale.ca.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.ca.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.ckb.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.contrib.auth.locale.ckb.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.contrib.auth.locale.ckb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.ckb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.cs.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.contrib.auth.locale.cs.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.contrib.auth.locale.cs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.cs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.cy.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.contrib.auth.locale.cy.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.contrib.auth.locale.cy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.cy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.da.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.contrib.auth.locale.da.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.contrib.auth.locale.da.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.da.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.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.contrib.auth.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.contrib.auth.locale.de.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.dsb.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.contrib.auth.locale.dsb.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.contrib.auth.locale.dsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.dsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.el.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.contrib.auth.locale.el.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.contrib.auth.locale.el.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.el.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.en.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.contrib.auth.locale.en.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.contrib.auth.locale.en.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.en.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.en_AU.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.contrib.auth.locale.en_AU.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.contrib.auth.locale.en_AU.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.en_AU.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.en_GB.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.contrib.auth.locale.en_GB.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.contrib.auth.locale.en_GB.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.en_GB.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.eo.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.contrib.auth.locale.eo.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.contrib.auth.locale.eo.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.eo.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.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.contrib.auth.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.contrib.auth.locale.es.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.es_AR.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.contrib.auth.locale.es_AR.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.contrib.auth.locale.es_AR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.es_AR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.es_CO.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.contrib.auth.locale.es_CO.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.contrib.auth.locale.es_CO.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.es_CO.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.es_MX.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.contrib.auth.locale.es_MX.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.contrib.auth.locale.es_MX.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.es_MX.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.es_VE.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.contrib.auth.locale.es_VE.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.contrib.auth.locale.es_VE.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.es_VE.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.et.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.contrib.auth.locale.et.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.contrib.auth.locale.et.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.et.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.eu.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.contrib.auth.locale.eu.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.contrib.auth.locale.eu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.eu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.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.contrib.auth.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.contrib.auth.locale.fa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.fi.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.contrib.auth.locale.fi.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.contrib.auth.locale.fi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.fi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.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.contrib.auth.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.contrib.auth.locale.fr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.fy.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.contrib.auth.locale.fy.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.contrib.auth.locale.fy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.fy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.ga.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.contrib.auth.locale.ga.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.contrib.auth.locale.ga.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.ga.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.gd.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.contrib.auth.locale.gd.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.contrib.auth.locale.gd.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.gd.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.gl.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.contrib.auth.locale.gl.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.contrib.auth.locale.gl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.gl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.he.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.contrib.auth.locale.he.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.contrib.auth.locale.he.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.he.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.hi.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.contrib.auth.locale.hi.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.contrib.auth.locale.hi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.hi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.hr.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.contrib.auth.locale.hr.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.contrib.auth.locale.hr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.hr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.hsb.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.contrib.auth.locale.hsb.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.contrib.auth.locale.hsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.hsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.hu.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.contrib.auth.locale.hu.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.contrib.auth.locale.hu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.hu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.hy.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.contrib.auth.locale.hy.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.contrib.auth.locale.hy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.hy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.ia.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.contrib.auth.locale.ia.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.contrib.auth.locale.ia.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.ia.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.id.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.contrib.auth.locale.id.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.contrib.auth.locale.id.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.id.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.io.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.contrib.auth.locale.io.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.contrib.auth.locale.io.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.io.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.is.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.contrib.auth.locale.is.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.contrib.auth.locale.is.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.is.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.it.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.contrib.auth.locale.it.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.contrib.auth.locale.it.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.it.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.ja.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.contrib.auth.locale.ja.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.contrib.auth.locale.ja.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.ja.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.ka.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.contrib.auth.locale.ka.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.contrib.auth.locale.ka.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.ka.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.kab.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.contrib.auth.locale.kab.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.contrib.auth.locale.kab.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.kab.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.kk.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.contrib.auth.locale.kk.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.contrib.auth.locale.kk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.kk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.km.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.contrib.auth.locale.km.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.contrib.auth.locale.km.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.km.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.kn.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.contrib.auth.locale.kn.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.contrib.auth.locale.kn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.kn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.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.contrib.auth.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.contrib.auth.locale.ko.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.ky.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.contrib.auth.locale.ky.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.contrib.auth.locale.ky.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.ky.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.lb.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.contrib.auth.locale.lb.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.contrib.auth.locale.lb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.lb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.lt.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.contrib.auth.locale.lt.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.contrib.auth.locale.lt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.lt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.lv.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.contrib.auth.locale.lv.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.contrib.auth.locale.lv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.lv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.mk.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.contrib.auth.locale.mk.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.contrib.auth.locale.mk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.mk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.ml.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.contrib.auth.locale.ml.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.contrib.auth.locale.ml.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.ml.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.mn.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.contrib.auth.locale.mn.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.contrib.auth.locale.mn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.mn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.mr.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.contrib.auth.locale.mr.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.contrib.auth.locale.mr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.mr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.ms.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.contrib.auth.locale.ms.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.contrib.auth.locale.ms.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.ms.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.my.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.contrib.auth.locale.my.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.contrib.auth.locale.my.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.my.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.nb.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.contrib.auth.locale.nb.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.contrib.auth.locale.nb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.nb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.ne.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.contrib.auth.locale.ne.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.contrib.auth.locale.ne.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.ne.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.nl.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.contrib.auth.locale.nl.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.contrib.auth.locale.nl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.nl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.nn.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.contrib.auth.locale.nn.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.contrib.auth.locale.nn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.nn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.os.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.contrib.auth.locale.os.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.contrib.auth.locale.os.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.os.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.pa.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.contrib.auth.locale.pa.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.contrib.auth.locale.pa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.pa.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.pl.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.contrib.auth.locale.pl.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.contrib.auth.locale.pl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.pl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.pt.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.contrib.auth.locale.pt.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.contrib.auth.locale.pt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.pt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.pt_BR.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.contrib.auth.locale.pt_BR.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.contrib.auth.locale.pt_BR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.pt_BR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.ro.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.contrib.auth.locale.ro.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.contrib.auth.locale.ro.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.ro.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.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.contrib.auth.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.contrib.auth.locale.ru.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.sk.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.contrib.auth.locale.sk.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.contrib.auth.locale.sk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.sk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.sl.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.contrib.auth.locale.sl.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.contrib.auth.locale.sl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.sl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.sq.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.contrib.auth.locale.sq.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.contrib.auth.locale.sq.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.sq.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.sr.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.contrib.auth.locale.sr.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.contrib.auth.locale.sr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.sr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.sr_Latn.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.contrib.auth.locale.sr_Latn.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.contrib.auth.locale.sr_Latn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.sr_Latn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.sv.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.contrib.auth.locale.sv.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.contrib.auth.locale.sv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.sv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.sw.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.contrib.auth.locale.sw.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.contrib.auth.locale.sw.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.sw.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.ta.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.contrib.auth.locale.ta.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.contrib.auth.locale.ta.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.ta.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.te.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.contrib.auth.locale.te.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.contrib.auth.locale.te.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.te.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.tg.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.contrib.auth.locale.tg.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.contrib.auth.locale.tg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.tg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.th.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.contrib.auth.locale.th.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.contrib.auth.locale.th.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.th.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.tk.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.contrib.auth.locale.tk.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.contrib.auth.locale.tk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.tk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.tr.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.contrib.auth.locale.tr.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.contrib.auth.locale.tr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.tr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.tt.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.contrib.auth.locale.tt.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.contrib.auth.locale.tt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.tt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.udm.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.contrib.auth.locale.udm.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.contrib.auth.locale.udm.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.udm.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.uk.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.contrib.auth.locale.uk.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.contrib.auth.locale.uk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.uk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.ur.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.contrib.auth.locale.ur.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.contrib.auth.locale.ur.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.ur.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.uz.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.contrib.auth.locale.uz.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.contrib.auth.locale.uz.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.uz.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.vi.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.contrib.auth.locale.vi.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.contrib.auth.locale.vi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.vi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.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.contrib.auth.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.contrib.auth.locale.zh_Hans.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.locale.zh_Hant.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.contrib.auth.locale.zh_Hant.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.contrib.auth.locale.zh_Hant.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.auth.locale.zh_Hant.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.templates.auth.widgets' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.templates.auth.widgets' 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.contrib.auth.templates.auth.widgets' 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.contrib.auth.templates.auth.widgets' to be distributed and are
        already explicitly excluding 'django.contrib.auth.templates.auth.widgets' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.templates.registration' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.auth.templates.registration' 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.contrib.auth.templates.registration' 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.contrib.auth.templates.registration' to be distributed and are
        already explicitly excluding 'django.contrib.auth.templates.registration' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.af.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.contrib.contenttypes.locale.af.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.contrib.contenttypes.locale.af.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.af.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.ar.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.contrib.contenttypes.locale.ar.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.contrib.contenttypes.locale.ar.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.ar.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.ar_DZ.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.contrib.contenttypes.locale.ar_DZ.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.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.ar_DZ.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.ast.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.contrib.contenttypes.locale.ast.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.contrib.contenttypes.locale.ast.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.ast.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.az.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.contrib.contenttypes.locale.az.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.contrib.contenttypes.locale.az.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.az.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.be.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.contrib.contenttypes.locale.be.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.contrib.contenttypes.locale.be.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.be.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.bg.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.contrib.contenttypes.locale.bg.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.contrib.contenttypes.locale.bg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.bg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.bn.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.contrib.contenttypes.locale.bn.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.contrib.contenttypes.locale.bn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.bn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.br.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.contrib.contenttypes.locale.br.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.contrib.contenttypes.locale.br.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.br.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.bs.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.contrib.contenttypes.locale.bs.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.contrib.contenttypes.locale.bs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.bs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.ca.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.contrib.contenttypes.locale.ca.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.contrib.contenttypes.locale.ca.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.ca.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.ckb.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.contrib.contenttypes.locale.ckb.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.contrib.contenttypes.locale.ckb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.ckb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.cs.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.contrib.contenttypes.locale.cs.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.contrib.contenttypes.locale.cs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.cs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.cy.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.contrib.contenttypes.locale.cy.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.contrib.contenttypes.locale.cy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.cy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.da.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.contrib.contenttypes.locale.da.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.contrib.contenttypes.locale.da.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.da.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.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.contrib.contenttypes.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.contrib.contenttypes.locale.de.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.dsb.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.contrib.contenttypes.locale.dsb.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.contrib.contenttypes.locale.dsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.dsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.el.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.contrib.contenttypes.locale.el.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.contrib.contenttypes.locale.el.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.el.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.en.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.contrib.contenttypes.locale.en.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.contrib.contenttypes.locale.en.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.en.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.en_AU.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.contrib.contenttypes.locale.en_AU.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.contrib.contenttypes.locale.en_AU.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.en_AU.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.en_GB.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.contrib.contenttypes.locale.en_GB.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.contrib.contenttypes.locale.en_GB.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.en_GB.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.eo.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.contrib.contenttypes.locale.eo.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.contrib.contenttypes.locale.eo.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.eo.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.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.contrib.contenttypes.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.contrib.contenttypes.locale.es.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.es_AR.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.contrib.contenttypes.locale.es_AR.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.contrib.contenttypes.locale.es_AR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.es_AR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.es_CO.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.contrib.contenttypes.locale.es_CO.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.contrib.contenttypes.locale.es_CO.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.es_CO.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.es_MX.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.contrib.contenttypes.locale.es_MX.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.contrib.contenttypes.locale.es_MX.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.es_MX.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.es_VE.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.contrib.contenttypes.locale.es_VE.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.contrib.contenttypes.locale.es_VE.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.es_VE.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.et.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.contrib.contenttypes.locale.et.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.contrib.contenttypes.locale.et.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.et.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.eu.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.contrib.contenttypes.locale.eu.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.contrib.contenttypes.locale.eu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.eu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.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.contrib.contenttypes.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.contrib.contenttypes.locale.fa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.fi.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.contrib.contenttypes.locale.fi.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.contrib.contenttypes.locale.fi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.fi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.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.contrib.contenttypes.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.contrib.contenttypes.locale.fr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.fy.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.contrib.contenttypes.locale.fy.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.contrib.contenttypes.locale.fy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.fy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.ga.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.contrib.contenttypes.locale.ga.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.contrib.contenttypes.locale.ga.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.ga.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.gd.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.contrib.contenttypes.locale.gd.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.contrib.contenttypes.locale.gd.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.gd.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.gl.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.contrib.contenttypes.locale.gl.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.contrib.contenttypes.locale.gl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.gl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.he.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.contrib.contenttypes.locale.he.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.contrib.contenttypes.locale.he.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.he.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.hi.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.contrib.contenttypes.locale.hi.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.contrib.contenttypes.locale.hi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.hi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.hr.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.contrib.contenttypes.locale.hr.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.contrib.contenttypes.locale.hr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.hr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.hsb.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.contrib.contenttypes.locale.hsb.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.contrib.contenttypes.locale.hsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.hsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.hu.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.contrib.contenttypes.locale.hu.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.contrib.contenttypes.locale.hu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.hu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.hy.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.contrib.contenttypes.locale.hy.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.contrib.contenttypes.locale.hy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.hy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.ia.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.contrib.contenttypes.locale.ia.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.contrib.contenttypes.locale.ia.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.ia.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.id.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.contrib.contenttypes.locale.id.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.contrib.contenttypes.locale.id.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.id.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.io.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.contrib.contenttypes.locale.io.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.contrib.contenttypes.locale.io.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.io.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.is.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.contrib.contenttypes.locale.is.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.contrib.contenttypes.locale.is.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.is.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.it.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.contrib.contenttypes.locale.it.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.contrib.contenttypes.locale.it.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.it.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.ja.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.contrib.contenttypes.locale.ja.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.contrib.contenttypes.locale.ja.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.ja.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.ka.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.contrib.contenttypes.locale.ka.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.contrib.contenttypes.locale.ka.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.ka.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.kk.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.contrib.contenttypes.locale.kk.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.contrib.contenttypes.locale.kk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.kk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.km.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.contrib.contenttypes.locale.km.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.contrib.contenttypes.locale.km.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.km.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.kn.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.contrib.contenttypes.locale.kn.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.contrib.contenttypes.locale.kn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.kn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.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.contrib.contenttypes.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.contrib.contenttypes.locale.ko.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.ky.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.contrib.contenttypes.locale.ky.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.contrib.contenttypes.locale.ky.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.ky.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.lb.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.contrib.contenttypes.locale.lb.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.contrib.contenttypes.locale.lb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.lb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.lt.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.contrib.contenttypes.locale.lt.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.contrib.contenttypes.locale.lt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.lt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.lv.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.contrib.contenttypes.locale.lv.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.contrib.contenttypes.locale.lv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.lv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.mk.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.contrib.contenttypes.locale.mk.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.contrib.contenttypes.locale.mk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.mk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.ml.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.contrib.contenttypes.locale.ml.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.contrib.contenttypes.locale.ml.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.ml.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.mn.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.contrib.contenttypes.locale.mn.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.contrib.contenttypes.locale.mn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.mn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.mr.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.contrib.contenttypes.locale.mr.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.contrib.contenttypes.locale.mr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.mr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.ms.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.contrib.contenttypes.locale.ms.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.contrib.contenttypes.locale.ms.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.ms.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.my.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.contrib.contenttypes.locale.my.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.contrib.contenttypes.locale.my.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.my.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.nb.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.contrib.contenttypes.locale.nb.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.contrib.contenttypes.locale.nb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.nb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.ne.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.contrib.contenttypes.locale.ne.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.contrib.contenttypes.locale.ne.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.ne.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.nl.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.contrib.contenttypes.locale.nl.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.contrib.contenttypes.locale.nl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.nl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.nn.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.contrib.contenttypes.locale.nn.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.contrib.contenttypes.locale.nn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.nn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.os.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.contrib.contenttypes.locale.os.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.contrib.contenttypes.locale.os.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.os.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.pa.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.contrib.contenttypes.locale.pa.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.contrib.contenttypes.locale.pa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.pa.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.pl.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.contrib.contenttypes.locale.pl.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.contrib.contenttypes.locale.pl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.pl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.pt.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.contrib.contenttypes.locale.pt.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.contrib.contenttypes.locale.pt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.pt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.pt_BR.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.contrib.contenttypes.locale.pt_BR.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.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.pt_BR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.ro.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.contrib.contenttypes.locale.ro.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.contrib.contenttypes.locale.ro.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.ro.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.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.contrib.contenttypes.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.contrib.contenttypes.locale.ru.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.sk.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.contrib.contenttypes.locale.sk.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.contrib.contenttypes.locale.sk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.sk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.sl.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.contrib.contenttypes.locale.sl.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.contrib.contenttypes.locale.sl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.sl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.sq.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.contrib.contenttypes.locale.sq.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.contrib.contenttypes.locale.sq.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.sq.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.sr.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.contrib.contenttypes.locale.sr.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.contrib.contenttypes.locale.sr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.sr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.sr_Latn.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.contrib.contenttypes.locale.sr_Latn.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.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.sr_Latn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.sv.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.contrib.contenttypes.locale.sv.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.contrib.contenttypes.locale.sv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.sv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.sw.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.contrib.contenttypes.locale.sw.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.contrib.contenttypes.locale.sw.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.sw.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.ta.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.contrib.contenttypes.locale.ta.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.contrib.contenttypes.locale.ta.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.ta.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.te.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.contrib.contenttypes.locale.te.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.contrib.contenttypes.locale.te.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.te.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.tg.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.contrib.contenttypes.locale.tg.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.contrib.contenttypes.locale.tg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.tg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.th.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.contrib.contenttypes.locale.th.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.contrib.contenttypes.locale.th.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.th.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.tk.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.contrib.contenttypes.locale.tk.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.contrib.contenttypes.locale.tk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.tk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.tr.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.contrib.contenttypes.locale.tr.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.contrib.contenttypes.locale.tr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.tr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.tt.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.contrib.contenttypes.locale.tt.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.contrib.contenttypes.locale.tt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.tt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.udm.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.contrib.contenttypes.locale.udm.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.contrib.contenttypes.locale.udm.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.udm.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.uk.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.contrib.contenttypes.locale.uk.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.contrib.contenttypes.locale.uk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.uk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.ur.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.contrib.contenttypes.locale.ur.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.contrib.contenttypes.locale.ur.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.ur.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.vi.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.contrib.contenttypes.locale.vi.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.contrib.contenttypes.locale.vi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.vi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.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.contrib.contenttypes.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.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.contenttypes.locale.zh_Hant.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.contrib.contenttypes.locale.zh_Hant.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.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.contenttypes.locale.zh_Hant.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.af.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.contrib.flatpages.locale.af.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.contrib.flatpages.locale.af.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.af.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.ar.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.contrib.flatpages.locale.ar.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.contrib.flatpages.locale.ar.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.ar.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.ar_DZ.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.contrib.flatpages.locale.ar_DZ.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.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.ar_DZ.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.ast.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.contrib.flatpages.locale.ast.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.contrib.flatpages.locale.ast.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.ast.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.az.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.contrib.flatpages.locale.az.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.contrib.flatpages.locale.az.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.az.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.be.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.contrib.flatpages.locale.be.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.contrib.flatpages.locale.be.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.be.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.bg.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.contrib.flatpages.locale.bg.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.contrib.flatpages.locale.bg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.bg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.bn.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.contrib.flatpages.locale.bn.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.contrib.flatpages.locale.bn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.bn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.br.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.contrib.flatpages.locale.br.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.contrib.flatpages.locale.br.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.br.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.bs.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.contrib.flatpages.locale.bs.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.contrib.flatpages.locale.bs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.bs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.ca.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.contrib.flatpages.locale.ca.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.contrib.flatpages.locale.ca.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.ca.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.ckb.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.contrib.flatpages.locale.ckb.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.contrib.flatpages.locale.ckb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.ckb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.cs.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.contrib.flatpages.locale.cs.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.contrib.flatpages.locale.cs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.cs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.cy.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.contrib.flatpages.locale.cy.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.contrib.flatpages.locale.cy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.cy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.da.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.contrib.flatpages.locale.da.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.contrib.flatpages.locale.da.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.da.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.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.contrib.flatpages.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.contrib.flatpages.locale.de.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.dsb.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.contrib.flatpages.locale.dsb.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.contrib.flatpages.locale.dsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.dsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.el.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.contrib.flatpages.locale.el.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.contrib.flatpages.locale.el.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.el.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.en.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.contrib.flatpages.locale.en.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.contrib.flatpages.locale.en.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.en.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.en_AU.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.contrib.flatpages.locale.en_AU.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.contrib.flatpages.locale.en_AU.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.en_AU.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.en_GB.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.contrib.flatpages.locale.en_GB.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.contrib.flatpages.locale.en_GB.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.en_GB.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.eo.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.contrib.flatpages.locale.eo.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.contrib.flatpages.locale.eo.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.eo.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.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.contrib.flatpages.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.contrib.flatpages.locale.es.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.es_AR.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.contrib.flatpages.locale.es_AR.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.contrib.flatpages.locale.es_AR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.es_AR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.es_CO.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.contrib.flatpages.locale.es_CO.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.contrib.flatpages.locale.es_CO.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.es_CO.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.es_MX.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.contrib.flatpages.locale.es_MX.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.contrib.flatpages.locale.es_MX.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.es_MX.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.es_VE.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.contrib.flatpages.locale.es_VE.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.contrib.flatpages.locale.es_VE.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.es_VE.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.et.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.contrib.flatpages.locale.et.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.contrib.flatpages.locale.et.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.et.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.eu.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.contrib.flatpages.locale.eu.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.contrib.flatpages.locale.eu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.eu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.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.contrib.flatpages.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.contrib.flatpages.locale.fa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.fi.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.contrib.flatpages.locale.fi.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.contrib.flatpages.locale.fi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.fi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.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.contrib.flatpages.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.contrib.flatpages.locale.fr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.fy.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.contrib.flatpages.locale.fy.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.contrib.flatpages.locale.fy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.fy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.ga.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.contrib.flatpages.locale.ga.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.contrib.flatpages.locale.ga.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.ga.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.gd.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.contrib.flatpages.locale.gd.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.contrib.flatpages.locale.gd.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.gd.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.gl.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.contrib.flatpages.locale.gl.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.contrib.flatpages.locale.gl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.gl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.he.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.contrib.flatpages.locale.he.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.contrib.flatpages.locale.he.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.he.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.hi.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.contrib.flatpages.locale.hi.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.contrib.flatpages.locale.hi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.hi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.hr.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.contrib.flatpages.locale.hr.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.contrib.flatpages.locale.hr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.hr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.hsb.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.contrib.flatpages.locale.hsb.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.contrib.flatpages.locale.hsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.hsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.hu.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.contrib.flatpages.locale.hu.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.contrib.flatpages.locale.hu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.hu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.hy.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.contrib.flatpages.locale.hy.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.contrib.flatpages.locale.hy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.hy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.ia.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.contrib.flatpages.locale.ia.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.contrib.flatpages.locale.ia.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.ia.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.id.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.contrib.flatpages.locale.id.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.contrib.flatpages.locale.id.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.id.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.io.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.contrib.flatpages.locale.io.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.contrib.flatpages.locale.io.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.io.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.is.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.contrib.flatpages.locale.is.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.contrib.flatpages.locale.is.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.is.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.it.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.contrib.flatpages.locale.it.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.contrib.flatpages.locale.it.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.it.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.ja.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.contrib.flatpages.locale.ja.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.contrib.flatpages.locale.ja.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.ja.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.ka.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.contrib.flatpages.locale.ka.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.contrib.flatpages.locale.ka.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.ka.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.kk.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.contrib.flatpages.locale.kk.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.contrib.flatpages.locale.kk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.kk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.km.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.contrib.flatpages.locale.km.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.contrib.flatpages.locale.km.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.km.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.kn.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.contrib.flatpages.locale.kn.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.contrib.flatpages.locale.kn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.kn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.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.contrib.flatpages.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.contrib.flatpages.locale.ko.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.ky.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.contrib.flatpages.locale.ky.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.contrib.flatpages.locale.ky.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.ky.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.lb.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.contrib.flatpages.locale.lb.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.contrib.flatpages.locale.lb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.lb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.lt.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.contrib.flatpages.locale.lt.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.contrib.flatpages.locale.lt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.lt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.lv.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.contrib.flatpages.locale.lv.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.contrib.flatpages.locale.lv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.lv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.mk.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.contrib.flatpages.locale.mk.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.contrib.flatpages.locale.mk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.mk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.ml.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.contrib.flatpages.locale.ml.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.contrib.flatpages.locale.ml.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.ml.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.mn.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.contrib.flatpages.locale.mn.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.contrib.flatpages.locale.mn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.mn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.mr.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.contrib.flatpages.locale.mr.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.contrib.flatpages.locale.mr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.mr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.ms.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.contrib.flatpages.locale.ms.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.contrib.flatpages.locale.ms.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.ms.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.my.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.contrib.flatpages.locale.my.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.contrib.flatpages.locale.my.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.my.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.nb.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.contrib.flatpages.locale.nb.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.contrib.flatpages.locale.nb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.nb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.ne.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.contrib.flatpages.locale.ne.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.contrib.flatpages.locale.ne.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.ne.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.nl.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.contrib.flatpages.locale.nl.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.contrib.flatpages.locale.nl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.nl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.nn.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.contrib.flatpages.locale.nn.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.contrib.flatpages.locale.nn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.nn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.os.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.contrib.flatpages.locale.os.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.contrib.flatpages.locale.os.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.os.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.pa.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.contrib.flatpages.locale.pa.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.contrib.flatpages.locale.pa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.pa.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.pl.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.contrib.flatpages.locale.pl.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.contrib.flatpages.locale.pl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.pl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.pt.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.contrib.flatpages.locale.pt.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.contrib.flatpages.locale.pt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.pt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.pt_BR.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.contrib.flatpages.locale.pt_BR.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.contrib.flatpages.locale.pt_BR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.pt_BR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.ro.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.contrib.flatpages.locale.ro.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.contrib.flatpages.locale.ro.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.ro.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.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.contrib.flatpages.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.contrib.flatpages.locale.ru.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.sk.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.contrib.flatpages.locale.sk.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.contrib.flatpages.locale.sk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.sk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.sl.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.contrib.flatpages.locale.sl.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.contrib.flatpages.locale.sl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.sl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.sq.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.contrib.flatpages.locale.sq.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.contrib.flatpages.locale.sq.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.sq.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.sr.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.contrib.flatpages.locale.sr.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.contrib.flatpages.locale.sr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.sr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.sr_Latn.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.contrib.flatpages.locale.sr_Latn.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.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.sr_Latn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.sv.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.contrib.flatpages.locale.sv.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.contrib.flatpages.locale.sv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.sv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.sw.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.contrib.flatpages.locale.sw.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.contrib.flatpages.locale.sw.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.sw.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.ta.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.contrib.flatpages.locale.ta.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.contrib.flatpages.locale.ta.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.ta.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.te.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.contrib.flatpages.locale.te.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.contrib.flatpages.locale.te.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.te.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.tg.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.contrib.flatpages.locale.tg.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.contrib.flatpages.locale.tg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.tg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.th.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.contrib.flatpages.locale.th.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.contrib.flatpages.locale.th.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.th.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.tk.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.contrib.flatpages.locale.tk.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.contrib.flatpages.locale.tk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.tk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.tr.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.contrib.flatpages.locale.tr.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.contrib.flatpages.locale.tr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.tr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.tt.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.contrib.flatpages.locale.tt.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.contrib.flatpages.locale.tt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.tt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.udm.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.contrib.flatpages.locale.udm.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.contrib.flatpages.locale.udm.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.udm.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.uk.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.contrib.flatpages.locale.uk.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.contrib.flatpages.locale.uk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.uk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.ur.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.contrib.flatpages.locale.ur.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.contrib.flatpages.locale.ur.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.ur.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.vi.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.contrib.flatpages.locale.vi.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.contrib.flatpages.locale.vi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.vi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.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.contrib.flatpages.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.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.flatpages.locale.zh_Hant.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.contrib.flatpages.locale.zh_Hant.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.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.flatpages.locale.zh_Hant.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.af.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.contrib.gis.locale.af.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.contrib.gis.locale.af.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.af.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.ar.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.contrib.gis.locale.ar.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.contrib.gis.locale.ar.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.ar.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.ar_DZ.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.contrib.gis.locale.ar_DZ.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.contrib.gis.locale.ar_DZ.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.ar_DZ.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.ast.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.contrib.gis.locale.ast.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.contrib.gis.locale.ast.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.ast.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.az.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.contrib.gis.locale.az.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.contrib.gis.locale.az.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.az.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.be.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.contrib.gis.locale.be.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.contrib.gis.locale.be.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.be.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.bg.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.contrib.gis.locale.bg.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.contrib.gis.locale.bg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.bg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.bn.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.contrib.gis.locale.bn.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.contrib.gis.locale.bn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.bn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.br.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.contrib.gis.locale.br.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.contrib.gis.locale.br.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.br.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.bs.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.contrib.gis.locale.bs.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.contrib.gis.locale.bs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.bs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.ca.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.contrib.gis.locale.ca.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.contrib.gis.locale.ca.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.ca.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.ckb.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.contrib.gis.locale.ckb.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.contrib.gis.locale.ckb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.ckb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.cs.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.contrib.gis.locale.cs.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.contrib.gis.locale.cs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.cs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.cy.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.contrib.gis.locale.cy.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.contrib.gis.locale.cy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.cy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.da.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.contrib.gis.locale.da.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.contrib.gis.locale.da.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.da.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.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.contrib.gis.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.contrib.gis.locale.de.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.dsb.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.contrib.gis.locale.dsb.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.contrib.gis.locale.dsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.dsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.el.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.contrib.gis.locale.el.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.contrib.gis.locale.el.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.el.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.en.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.contrib.gis.locale.en.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.contrib.gis.locale.en.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.en.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.en_AU.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.contrib.gis.locale.en_AU.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.contrib.gis.locale.en_AU.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.en_AU.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.en_GB.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.contrib.gis.locale.en_GB.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.contrib.gis.locale.en_GB.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.en_GB.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.eo.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.contrib.gis.locale.eo.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.contrib.gis.locale.eo.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.eo.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.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.contrib.gis.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.contrib.gis.locale.es.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.es_AR.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.contrib.gis.locale.es_AR.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.contrib.gis.locale.es_AR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.es_AR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.es_CO.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.contrib.gis.locale.es_CO.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.contrib.gis.locale.es_CO.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.es_CO.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.es_MX.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.contrib.gis.locale.es_MX.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.contrib.gis.locale.es_MX.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.es_MX.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.es_VE.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.contrib.gis.locale.es_VE.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.contrib.gis.locale.es_VE.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.es_VE.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.et.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.contrib.gis.locale.et.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.contrib.gis.locale.et.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.et.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.eu.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.contrib.gis.locale.eu.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.contrib.gis.locale.eu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.eu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.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.contrib.gis.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.contrib.gis.locale.fa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.fi.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.contrib.gis.locale.fi.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.contrib.gis.locale.fi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.fi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.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.contrib.gis.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.contrib.gis.locale.fr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.fy.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.contrib.gis.locale.fy.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.contrib.gis.locale.fy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.fy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.ga.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.contrib.gis.locale.ga.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.contrib.gis.locale.ga.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.ga.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.gd.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.contrib.gis.locale.gd.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.contrib.gis.locale.gd.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.gd.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.gl.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.contrib.gis.locale.gl.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.contrib.gis.locale.gl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.gl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.he.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.contrib.gis.locale.he.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.contrib.gis.locale.he.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.he.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.hi.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.contrib.gis.locale.hi.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.contrib.gis.locale.hi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.hi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.hr.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.contrib.gis.locale.hr.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.contrib.gis.locale.hr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.hr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.hsb.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.contrib.gis.locale.hsb.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.contrib.gis.locale.hsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.hsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.hu.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.contrib.gis.locale.hu.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.contrib.gis.locale.hu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.hu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.hy.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.contrib.gis.locale.hy.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.contrib.gis.locale.hy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.hy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.ia.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.contrib.gis.locale.ia.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.contrib.gis.locale.ia.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.ia.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.id.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.contrib.gis.locale.id.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.contrib.gis.locale.id.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.id.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.io.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.contrib.gis.locale.io.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.contrib.gis.locale.io.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.io.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.is.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.contrib.gis.locale.is.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.contrib.gis.locale.is.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.is.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.it.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.contrib.gis.locale.it.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.contrib.gis.locale.it.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.it.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.ja.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.contrib.gis.locale.ja.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.contrib.gis.locale.ja.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.ja.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.ka.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.contrib.gis.locale.ka.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.contrib.gis.locale.ka.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.ka.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.kk.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.contrib.gis.locale.kk.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.contrib.gis.locale.kk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.kk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.km.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.contrib.gis.locale.km.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.contrib.gis.locale.km.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.km.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.kn.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.contrib.gis.locale.kn.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.contrib.gis.locale.kn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.kn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.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.contrib.gis.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.contrib.gis.locale.ko.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.ky.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.contrib.gis.locale.ky.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.contrib.gis.locale.ky.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.ky.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.lb.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.contrib.gis.locale.lb.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.contrib.gis.locale.lb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.lb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.lt.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.contrib.gis.locale.lt.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.contrib.gis.locale.lt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.lt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.lv.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.contrib.gis.locale.lv.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.contrib.gis.locale.lv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.lv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.mk.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.contrib.gis.locale.mk.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.contrib.gis.locale.mk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.mk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.ml.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.contrib.gis.locale.ml.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.contrib.gis.locale.ml.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.ml.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.mn.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.contrib.gis.locale.mn.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.contrib.gis.locale.mn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.mn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.mr.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.contrib.gis.locale.mr.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.contrib.gis.locale.mr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.mr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.ms.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.contrib.gis.locale.ms.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.contrib.gis.locale.ms.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.ms.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.my.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.contrib.gis.locale.my.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.contrib.gis.locale.my.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.my.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.nb.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.contrib.gis.locale.nb.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.contrib.gis.locale.nb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.nb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.ne.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.contrib.gis.locale.ne.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.contrib.gis.locale.ne.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.ne.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.nl.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.contrib.gis.locale.nl.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.contrib.gis.locale.nl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.nl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.nn.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.contrib.gis.locale.nn.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.contrib.gis.locale.nn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.nn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.os.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.contrib.gis.locale.os.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.contrib.gis.locale.os.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.os.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.pa.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.contrib.gis.locale.pa.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.contrib.gis.locale.pa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.pa.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.pl.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.contrib.gis.locale.pl.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.contrib.gis.locale.pl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.pl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.pt.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.contrib.gis.locale.pt.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.contrib.gis.locale.pt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.pt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.pt_BR.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.contrib.gis.locale.pt_BR.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.contrib.gis.locale.pt_BR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.pt_BR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.ro.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.contrib.gis.locale.ro.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.contrib.gis.locale.ro.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.ro.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.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.contrib.gis.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.contrib.gis.locale.ru.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.sk.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.contrib.gis.locale.sk.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.contrib.gis.locale.sk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.sk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.sl.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.contrib.gis.locale.sl.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.contrib.gis.locale.sl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.sl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.sq.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.contrib.gis.locale.sq.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.contrib.gis.locale.sq.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.sq.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.sr.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.contrib.gis.locale.sr.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.contrib.gis.locale.sr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.sr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.sr_Latn.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.contrib.gis.locale.sr_Latn.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.contrib.gis.locale.sr_Latn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.sr_Latn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.sv.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.contrib.gis.locale.sv.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.contrib.gis.locale.sv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.sv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.sw.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.contrib.gis.locale.sw.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.contrib.gis.locale.sw.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.sw.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.ta.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.contrib.gis.locale.ta.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.contrib.gis.locale.ta.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.ta.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.te.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.contrib.gis.locale.te.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.contrib.gis.locale.te.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.te.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.tg.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.contrib.gis.locale.tg.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.contrib.gis.locale.tg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.tg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.th.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.contrib.gis.locale.th.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.contrib.gis.locale.th.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.th.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.tr.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.contrib.gis.locale.tr.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.contrib.gis.locale.tr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.tr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.tt.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.contrib.gis.locale.tt.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.contrib.gis.locale.tt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.tt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.udm.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.contrib.gis.locale.udm.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.contrib.gis.locale.udm.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.udm.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.uk.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.contrib.gis.locale.uk.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.contrib.gis.locale.uk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.uk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.ur.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.contrib.gis.locale.ur.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.contrib.gis.locale.ur.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.ur.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.vi.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.contrib.gis.locale.vi.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.contrib.gis.locale.vi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.vi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.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.contrib.gis.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.contrib.gis.locale.zh_Hans.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.locale.zh_Hant.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.contrib.gis.locale.zh_Hant.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.contrib.gis.locale.zh_Hant.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.gis.locale.zh_Hant.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.static.gis.css' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.static.gis.css' 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.contrib.gis.static.gis.css' 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.contrib.gis.static.gis.css' to be distributed and are
        already explicitly excluding 'django.contrib.gis.static.gis.css' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.static.gis.img' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.static.gis.img' 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.contrib.gis.static.gis.img' 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.contrib.gis.static.gis.img' to be distributed and are
        already explicitly excluding 'django.contrib.gis.static.gis.img' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.static.gis.js' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.static.gis.js' 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.contrib.gis.static.gis.js' 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.contrib.gis.static.gis.js' to be distributed and are
        already explicitly excluding 'django.contrib.gis.static.gis.js' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.templates.gis' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.templates.gis' 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.contrib.gis.templates.gis' 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.contrib.gis.templates.gis' to be distributed and are
        already explicitly excluding 'django.contrib.gis.templates.gis' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.templates.gis.admin' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.templates.gis.admin' 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.contrib.gis.templates.gis.admin' 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.contrib.gis.templates.gis.admin' to be distributed and are
        already explicitly excluding 'django.contrib.gis.templates.gis.admin' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.templates.gis.kml' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.gis.templates.gis.kml' 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.contrib.gis.templates.gis.kml' 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.contrib.gis.templates.gis.kml' to be distributed and are
        already explicitly excluding 'django.contrib.gis.templates.gis.kml' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.af.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.contrib.humanize.locale.af.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.contrib.humanize.locale.af.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.af.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.ar.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.contrib.humanize.locale.ar.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.contrib.humanize.locale.ar.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.ar.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.ar_DZ.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.contrib.humanize.locale.ar_DZ.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.contrib.humanize.locale.ar_DZ.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.ar_DZ.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.ast.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.contrib.humanize.locale.ast.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.contrib.humanize.locale.ast.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.ast.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.az.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.contrib.humanize.locale.az.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.contrib.humanize.locale.az.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.az.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.be.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.contrib.humanize.locale.be.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.contrib.humanize.locale.be.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.be.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.bg.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.contrib.humanize.locale.bg.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.contrib.humanize.locale.bg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.bg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.bn.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.contrib.humanize.locale.bn.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.contrib.humanize.locale.bn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.bn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.br.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.contrib.humanize.locale.br.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.contrib.humanize.locale.br.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.br.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.bs.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.contrib.humanize.locale.bs.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.contrib.humanize.locale.bs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.bs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.ca.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.contrib.humanize.locale.ca.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.contrib.humanize.locale.ca.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.ca.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.ckb.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.contrib.humanize.locale.ckb.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.contrib.humanize.locale.ckb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.ckb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.cs.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.contrib.humanize.locale.cs.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.contrib.humanize.locale.cs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.cs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.cy.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.contrib.humanize.locale.cy.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.contrib.humanize.locale.cy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.cy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.da.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.contrib.humanize.locale.da.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.contrib.humanize.locale.da.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.da.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.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.contrib.humanize.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.contrib.humanize.locale.de.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.dsb.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.contrib.humanize.locale.dsb.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.contrib.humanize.locale.dsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.dsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.el.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.contrib.humanize.locale.el.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.contrib.humanize.locale.el.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.el.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.en.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.contrib.humanize.locale.en.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.contrib.humanize.locale.en.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.en.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.en_AU.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.contrib.humanize.locale.en_AU.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.contrib.humanize.locale.en_AU.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.en_AU.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.en_GB.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.contrib.humanize.locale.en_GB.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.contrib.humanize.locale.en_GB.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.en_GB.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.eo.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.contrib.humanize.locale.eo.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.contrib.humanize.locale.eo.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.eo.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.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.contrib.humanize.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.contrib.humanize.locale.es.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.es_AR.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.contrib.humanize.locale.es_AR.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.contrib.humanize.locale.es_AR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.es_AR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.es_CO.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.contrib.humanize.locale.es_CO.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.contrib.humanize.locale.es_CO.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.es_CO.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.es_MX.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.contrib.humanize.locale.es_MX.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.contrib.humanize.locale.es_MX.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.es_MX.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.es_VE.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.contrib.humanize.locale.es_VE.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.contrib.humanize.locale.es_VE.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.es_VE.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.et.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.contrib.humanize.locale.et.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.contrib.humanize.locale.et.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.et.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.eu.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.contrib.humanize.locale.eu.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.contrib.humanize.locale.eu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.eu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.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.contrib.humanize.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.contrib.humanize.locale.fa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.fi.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.contrib.humanize.locale.fi.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.contrib.humanize.locale.fi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.fi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.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.contrib.humanize.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.contrib.humanize.locale.fr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.fy.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.contrib.humanize.locale.fy.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.contrib.humanize.locale.fy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.fy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.ga.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.contrib.humanize.locale.ga.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.contrib.humanize.locale.ga.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.ga.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.gd.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.contrib.humanize.locale.gd.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.contrib.humanize.locale.gd.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.gd.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.gl.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.contrib.humanize.locale.gl.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.contrib.humanize.locale.gl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.gl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.he.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.contrib.humanize.locale.he.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.contrib.humanize.locale.he.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.he.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.hi.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.contrib.humanize.locale.hi.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.contrib.humanize.locale.hi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.hi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.hr.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.contrib.humanize.locale.hr.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.contrib.humanize.locale.hr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.hr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.hsb.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.contrib.humanize.locale.hsb.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.contrib.humanize.locale.hsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.hsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.hu.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.contrib.humanize.locale.hu.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.contrib.humanize.locale.hu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.hu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.hy.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.contrib.humanize.locale.hy.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.contrib.humanize.locale.hy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.hy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.ia.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.contrib.humanize.locale.ia.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.contrib.humanize.locale.ia.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.ia.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.id.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.contrib.humanize.locale.id.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.contrib.humanize.locale.id.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.id.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.io.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.contrib.humanize.locale.io.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.contrib.humanize.locale.io.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.io.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.is.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.contrib.humanize.locale.is.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.contrib.humanize.locale.is.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.is.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.it.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.contrib.humanize.locale.it.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.contrib.humanize.locale.it.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.it.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.ja.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.contrib.humanize.locale.ja.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.contrib.humanize.locale.ja.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.ja.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.ka.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.contrib.humanize.locale.ka.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.contrib.humanize.locale.ka.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.ka.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.kk.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.contrib.humanize.locale.kk.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.contrib.humanize.locale.kk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.kk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.km.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.contrib.humanize.locale.km.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.contrib.humanize.locale.km.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.km.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.kn.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.contrib.humanize.locale.kn.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.contrib.humanize.locale.kn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.kn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.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.contrib.humanize.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.contrib.humanize.locale.ko.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.ky.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.contrib.humanize.locale.ky.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.contrib.humanize.locale.ky.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.ky.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.lb.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.contrib.humanize.locale.lb.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.contrib.humanize.locale.lb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.lb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.lt.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.contrib.humanize.locale.lt.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.contrib.humanize.locale.lt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.lt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.lv.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.contrib.humanize.locale.lv.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.contrib.humanize.locale.lv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.lv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.mk.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.contrib.humanize.locale.mk.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.contrib.humanize.locale.mk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.mk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.ml.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.contrib.humanize.locale.ml.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.contrib.humanize.locale.ml.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.ml.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.mn.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.contrib.humanize.locale.mn.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.contrib.humanize.locale.mn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.mn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.mr.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.contrib.humanize.locale.mr.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.contrib.humanize.locale.mr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.mr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.ms.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.contrib.humanize.locale.ms.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.contrib.humanize.locale.ms.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.ms.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.my.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.contrib.humanize.locale.my.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.contrib.humanize.locale.my.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.my.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.nb.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.contrib.humanize.locale.nb.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.contrib.humanize.locale.nb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.nb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.ne.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.contrib.humanize.locale.ne.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.contrib.humanize.locale.ne.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.ne.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.nl.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.contrib.humanize.locale.nl.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.contrib.humanize.locale.nl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.nl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.nn.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.contrib.humanize.locale.nn.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.contrib.humanize.locale.nn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.nn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.os.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.contrib.humanize.locale.os.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.contrib.humanize.locale.os.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.os.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.pa.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.contrib.humanize.locale.pa.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.contrib.humanize.locale.pa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.pa.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.pl.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.contrib.humanize.locale.pl.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.contrib.humanize.locale.pl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.pl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.pt.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.contrib.humanize.locale.pt.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.contrib.humanize.locale.pt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.pt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.pt_BR.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.contrib.humanize.locale.pt_BR.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.contrib.humanize.locale.pt_BR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.pt_BR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.ro.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.contrib.humanize.locale.ro.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.contrib.humanize.locale.ro.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.ro.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.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.contrib.humanize.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.contrib.humanize.locale.ru.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.sk.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.contrib.humanize.locale.sk.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.contrib.humanize.locale.sk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.sk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.sl.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.contrib.humanize.locale.sl.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.contrib.humanize.locale.sl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.sl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.sq.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.contrib.humanize.locale.sq.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.contrib.humanize.locale.sq.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.sq.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.sr.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.contrib.humanize.locale.sr.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.contrib.humanize.locale.sr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.sr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.sr_Latn.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.contrib.humanize.locale.sr_Latn.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.contrib.humanize.locale.sr_Latn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.sr_Latn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.sv.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.contrib.humanize.locale.sv.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.contrib.humanize.locale.sv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.sv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.sw.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.contrib.humanize.locale.sw.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.contrib.humanize.locale.sw.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.sw.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.ta.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.contrib.humanize.locale.ta.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.contrib.humanize.locale.ta.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.ta.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.te.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.contrib.humanize.locale.te.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.contrib.humanize.locale.te.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.te.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.tg.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.contrib.humanize.locale.tg.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.contrib.humanize.locale.tg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.tg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.th.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.contrib.humanize.locale.th.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.contrib.humanize.locale.th.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.th.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.tk.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.contrib.humanize.locale.tk.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.contrib.humanize.locale.tk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.tk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.tr.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.contrib.humanize.locale.tr.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.contrib.humanize.locale.tr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.tr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.tt.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.contrib.humanize.locale.tt.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.contrib.humanize.locale.tt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.tt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.udm.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.contrib.humanize.locale.udm.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.contrib.humanize.locale.udm.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.udm.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.uk.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.contrib.humanize.locale.uk.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.contrib.humanize.locale.uk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.uk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.ur.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.contrib.humanize.locale.ur.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.contrib.humanize.locale.ur.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.ur.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.uz.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.contrib.humanize.locale.uz.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.contrib.humanize.locale.uz.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.uz.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.vi.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.contrib.humanize.locale.vi.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.contrib.humanize.locale.vi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.vi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.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.contrib.humanize.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.contrib.humanize.locale.zh_Hans.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.humanize.locale.zh_Hant.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.contrib.humanize.locale.zh_Hant.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.contrib.humanize.locale.zh_Hant.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.humanize.locale.zh_Hant.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.jinja2.postgres.widgets' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.jinja2.postgres.widgets' 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.contrib.postgres.jinja2.postgres.widgets' 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.contrib.postgres.jinja2.postgres.widgets' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.jinja2.postgres.widgets' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.af.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.contrib.postgres.locale.af.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.contrib.postgres.locale.af.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.af.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.ar.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.contrib.postgres.locale.ar.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.contrib.postgres.locale.ar.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.ar.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.ar_DZ.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.contrib.postgres.locale.ar_DZ.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.contrib.postgres.locale.ar_DZ.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.ar_DZ.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.az.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.contrib.postgres.locale.az.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.contrib.postgres.locale.az.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.az.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.be.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.contrib.postgres.locale.be.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.contrib.postgres.locale.be.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.be.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.bg.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.contrib.postgres.locale.bg.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.contrib.postgres.locale.bg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.bg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.ca.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.contrib.postgres.locale.ca.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.contrib.postgres.locale.ca.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.ca.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.ckb.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.contrib.postgres.locale.ckb.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.contrib.postgres.locale.ckb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.ckb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.cs.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.contrib.postgres.locale.cs.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.contrib.postgres.locale.cs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.cs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.da.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.contrib.postgres.locale.da.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.contrib.postgres.locale.da.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.da.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.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.contrib.postgres.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.contrib.postgres.locale.de.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.dsb.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.contrib.postgres.locale.dsb.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.contrib.postgres.locale.dsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.dsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.el.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.contrib.postgres.locale.el.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.contrib.postgres.locale.el.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.el.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.en.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.contrib.postgres.locale.en.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.contrib.postgres.locale.en.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.en.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.en_AU.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.contrib.postgres.locale.en_AU.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.contrib.postgres.locale.en_AU.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.en_AU.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.eo.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.contrib.postgres.locale.eo.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.contrib.postgres.locale.eo.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.eo.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.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.contrib.postgres.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.contrib.postgres.locale.es.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.es_AR.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.contrib.postgres.locale.es_AR.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.contrib.postgres.locale.es_AR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.es_AR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.es_CO.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.contrib.postgres.locale.es_CO.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.contrib.postgres.locale.es_CO.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.es_CO.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.es_MX.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.contrib.postgres.locale.es_MX.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.contrib.postgres.locale.es_MX.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.es_MX.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.et.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.contrib.postgres.locale.et.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.contrib.postgres.locale.et.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.et.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.eu.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.contrib.postgres.locale.eu.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.contrib.postgres.locale.eu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.eu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.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.contrib.postgres.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.contrib.postgres.locale.fa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.fi.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.contrib.postgres.locale.fi.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.contrib.postgres.locale.fi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.fi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.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.contrib.postgres.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.contrib.postgres.locale.fr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.gd.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.contrib.postgres.locale.gd.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.contrib.postgres.locale.gd.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.gd.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.gl.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.contrib.postgres.locale.gl.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.contrib.postgres.locale.gl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.gl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.he.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.contrib.postgres.locale.he.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.contrib.postgres.locale.he.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.he.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.hr.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.contrib.postgres.locale.hr.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.contrib.postgres.locale.hr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.hr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.hsb.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.contrib.postgres.locale.hsb.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.contrib.postgres.locale.hsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.hsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.hu.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.contrib.postgres.locale.hu.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.contrib.postgres.locale.hu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.hu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.hy.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.contrib.postgres.locale.hy.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.contrib.postgres.locale.hy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.hy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.ia.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.contrib.postgres.locale.ia.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.contrib.postgres.locale.ia.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.ia.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.id.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.contrib.postgres.locale.id.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.contrib.postgres.locale.id.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.id.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.is.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.contrib.postgres.locale.is.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.contrib.postgres.locale.is.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.is.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.it.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.contrib.postgres.locale.it.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.contrib.postgres.locale.it.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.it.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.ja.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.contrib.postgres.locale.ja.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.contrib.postgres.locale.ja.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.ja.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.ka.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.contrib.postgres.locale.ka.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.contrib.postgres.locale.ka.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.ka.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.kk.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.contrib.postgres.locale.kk.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.contrib.postgres.locale.kk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.kk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.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.contrib.postgres.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.contrib.postgres.locale.ko.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.ky.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.contrib.postgres.locale.ky.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.contrib.postgres.locale.ky.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.ky.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.lt.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.contrib.postgres.locale.lt.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.contrib.postgres.locale.lt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.lt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.lv.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.contrib.postgres.locale.lv.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.contrib.postgres.locale.lv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.lv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.mk.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.contrib.postgres.locale.mk.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.contrib.postgres.locale.mk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.mk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.ml.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.contrib.postgres.locale.ml.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.contrib.postgres.locale.ml.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.ml.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.mn.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.contrib.postgres.locale.mn.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.contrib.postgres.locale.mn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.mn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.ms.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.contrib.postgres.locale.ms.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.contrib.postgres.locale.ms.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.ms.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.nb.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.contrib.postgres.locale.nb.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.contrib.postgres.locale.nb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.nb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.ne.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.contrib.postgres.locale.ne.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.contrib.postgres.locale.ne.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.ne.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.nl.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.contrib.postgres.locale.nl.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.contrib.postgres.locale.nl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.nl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.nn.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.contrib.postgres.locale.nn.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.contrib.postgres.locale.nn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.nn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.pl.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.contrib.postgres.locale.pl.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.contrib.postgres.locale.pl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.pl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.pt.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.contrib.postgres.locale.pt.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.contrib.postgres.locale.pt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.pt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.pt_BR.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.contrib.postgres.locale.pt_BR.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.contrib.postgres.locale.pt_BR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.pt_BR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.ro.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.contrib.postgres.locale.ro.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.contrib.postgres.locale.ro.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.ro.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.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.contrib.postgres.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.contrib.postgres.locale.ru.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.sk.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.contrib.postgres.locale.sk.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.contrib.postgres.locale.sk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.sk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.sl.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.contrib.postgres.locale.sl.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.contrib.postgres.locale.sl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.sl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.sq.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.contrib.postgres.locale.sq.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.contrib.postgres.locale.sq.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.sq.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.sr.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.contrib.postgres.locale.sr.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.contrib.postgres.locale.sr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.sr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.sr_Latn.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.contrib.postgres.locale.sr_Latn.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.contrib.postgres.locale.sr_Latn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.sr_Latn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.sv.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.contrib.postgres.locale.sv.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.contrib.postgres.locale.sv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.sv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.tg.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.contrib.postgres.locale.tg.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.contrib.postgres.locale.tg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.tg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.tk.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.contrib.postgres.locale.tk.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.contrib.postgres.locale.tk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.tk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.tr.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.contrib.postgres.locale.tr.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.contrib.postgres.locale.tr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.tr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.uk.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.contrib.postgres.locale.uk.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.contrib.postgres.locale.uk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.uk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.uz.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.contrib.postgres.locale.uz.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.contrib.postgres.locale.uz.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.uz.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.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.contrib.postgres.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.contrib.postgres.locale.zh_Hans.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.locale.zh_Hant.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.contrib.postgres.locale.zh_Hant.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.contrib.postgres.locale.zh_Hant.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.locale.zh_Hant.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.templates.postgres.widgets' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.postgres.templates.postgres.widgets' 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.contrib.postgres.templates.postgres.widgets' 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.contrib.postgres.templates.postgres.widgets' to be distributed and are
        already explicitly excluding 'django.contrib.postgres.templates.postgres.widgets' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.af.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.contrib.redirects.locale.af.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.contrib.redirects.locale.af.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.af.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.ar.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.contrib.redirects.locale.ar.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.contrib.redirects.locale.ar.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.ar.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.ar_DZ.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.contrib.redirects.locale.ar_DZ.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.contrib.redirects.locale.ar_DZ.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.ar_DZ.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.ast.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.contrib.redirects.locale.ast.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.contrib.redirects.locale.ast.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.ast.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.az.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.contrib.redirects.locale.az.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.contrib.redirects.locale.az.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.az.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.be.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.contrib.redirects.locale.be.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.contrib.redirects.locale.be.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.be.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.bg.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.contrib.redirects.locale.bg.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.contrib.redirects.locale.bg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.bg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.bn.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.contrib.redirects.locale.bn.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.contrib.redirects.locale.bn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.bn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.br.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.contrib.redirects.locale.br.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.contrib.redirects.locale.br.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.br.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.bs.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.contrib.redirects.locale.bs.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.contrib.redirects.locale.bs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.bs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.ca.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.contrib.redirects.locale.ca.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.contrib.redirects.locale.ca.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.ca.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.ckb.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.contrib.redirects.locale.ckb.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.contrib.redirects.locale.ckb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.ckb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.cs.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.contrib.redirects.locale.cs.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.contrib.redirects.locale.cs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.cs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.cy.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.contrib.redirects.locale.cy.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.contrib.redirects.locale.cy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.cy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.da.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.contrib.redirects.locale.da.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.contrib.redirects.locale.da.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.da.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.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.contrib.redirects.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.contrib.redirects.locale.de.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.dsb.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.contrib.redirects.locale.dsb.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.contrib.redirects.locale.dsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.dsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.el.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.contrib.redirects.locale.el.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.contrib.redirects.locale.el.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.el.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.en.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.contrib.redirects.locale.en.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.contrib.redirects.locale.en.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.en.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.en_AU.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.contrib.redirects.locale.en_AU.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.contrib.redirects.locale.en_AU.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.en_AU.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.en_GB.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.contrib.redirects.locale.en_GB.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.contrib.redirects.locale.en_GB.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.en_GB.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.eo.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.contrib.redirects.locale.eo.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.contrib.redirects.locale.eo.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.eo.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.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.contrib.redirects.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.contrib.redirects.locale.es.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.es_AR.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.contrib.redirects.locale.es_AR.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.contrib.redirects.locale.es_AR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.es_AR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.es_CO.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.contrib.redirects.locale.es_CO.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.contrib.redirects.locale.es_CO.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.es_CO.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.es_MX.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.contrib.redirects.locale.es_MX.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.contrib.redirects.locale.es_MX.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.es_MX.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.es_VE.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.contrib.redirects.locale.es_VE.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.contrib.redirects.locale.es_VE.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.es_VE.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.et.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.contrib.redirects.locale.et.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.contrib.redirects.locale.et.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.et.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.eu.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.contrib.redirects.locale.eu.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.contrib.redirects.locale.eu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.eu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.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.contrib.redirects.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.contrib.redirects.locale.fa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.fi.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.contrib.redirects.locale.fi.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.contrib.redirects.locale.fi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.fi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.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.contrib.redirects.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.contrib.redirects.locale.fr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.fy.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.contrib.redirects.locale.fy.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.contrib.redirects.locale.fy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.fy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.ga.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.contrib.redirects.locale.ga.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.contrib.redirects.locale.ga.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.ga.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.gd.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.contrib.redirects.locale.gd.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.contrib.redirects.locale.gd.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.gd.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.gl.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.contrib.redirects.locale.gl.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.contrib.redirects.locale.gl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.gl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.he.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.contrib.redirects.locale.he.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.contrib.redirects.locale.he.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.he.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.hi.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.contrib.redirects.locale.hi.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.contrib.redirects.locale.hi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.hi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.hr.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.contrib.redirects.locale.hr.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.contrib.redirects.locale.hr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.hr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.hsb.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.contrib.redirects.locale.hsb.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.contrib.redirects.locale.hsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.hsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.hu.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.contrib.redirects.locale.hu.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.contrib.redirects.locale.hu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.hu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.hy.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.contrib.redirects.locale.hy.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.contrib.redirects.locale.hy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.hy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.ia.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.contrib.redirects.locale.ia.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.contrib.redirects.locale.ia.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.ia.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.id.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.contrib.redirects.locale.id.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.contrib.redirects.locale.id.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.id.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.io.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.contrib.redirects.locale.io.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.contrib.redirects.locale.io.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.io.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.is.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.contrib.redirects.locale.is.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.contrib.redirects.locale.is.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.is.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.it.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.contrib.redirects.locale.it.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.contrib.redirects.locale.it.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.it.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.ja.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.contrib.redirects.locale.ja.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.contrib.redirects.locale.ja.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.ja.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.ka.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.contrib.redirects.locale.ka.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.contrib.redirects.locale.ka.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.ka.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.kab.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.contrib.redirects.locale.kab.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.contrib.redirects.locale.kab.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.kab.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.kk.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.contrib.redirects.locale.kk.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.contrib.redirects.locale.kk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.kk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.km.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.contrib.redirects.locale.km.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.contrib.redirects.locale.km.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.km.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.kn.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.contrib.redirects.locale.kn.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.contrib.redirects.locale.kn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.kn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.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.contrib.redirects.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.contrib.redirects.locale.ko.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.ky.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.contrib.redirects.locale.ky.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.contrib.redirects.locale.ky.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.ky.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.lb.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.contrib.redirects.locale.lb.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.contrib.redirects.locale.lb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.lb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.lt.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.contrib.redirects.locale.lt.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.contrib.redirects.locale.lt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.lt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.lv.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.contrib.redirects.locale.lv.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.contrib.redirects.locale.lv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.lv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.mk.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.contrib.redirects.locale.mk.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.contrib.redirects.locale.mk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.mk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.ml.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.contrib.redirects.locale.ml.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.contrib.redirects.locale.ml.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.ml.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.mn.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.contrib.redirects.locale.mn.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.contrib.redirects.locale.mn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.mn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.mr.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.contrib.redirects.locale.mr.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.contrib.redirects.locale.mr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.mr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.ms.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.contrib.redirects.locale.ms.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.contrib.redirects.locale.ms.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.ms.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.my.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.contrib.redirects.locale.my.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.contrib.redirects.locale.my.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.my.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.nb.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.contrib.redirects.locale.nb.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.contrib.redirects.locale.nb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.nb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.ne.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.contrib.redirects.locale.ne.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.contrib.redirects.locale.ne.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.ne.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.nl.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.contrib.redirects.locale.nl.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.contrib.redirects.locale.nl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.nl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.nn.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.contrib.redirects.locale.nn.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.contrib.redirects.locale.nn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.nn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.os.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.contrib.redirects.locale.os.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.contrib.redirects.locale.os.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.os.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.pa.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.contrib.redirects.locale.pa.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.contrib.redirects.locale.pa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.pa.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.pl.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.contrib.redirects.locale.pl.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.contrib.redirects.locale.pl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.pl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.pt.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.contrib.redirects.locale.pt.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.contrib.redirects.locale.pt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.pt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.pt_BR.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.contrib.redirects.locale.pt_BR.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.contrib.redirects.locale.pt_BR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.pt_BR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.ro.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.contrib.redirects.locale.ro.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.contrib.redirects.locale.ro.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.ro.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.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.contrib.redirects.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.contrib.redirects.locale.ru.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.sk.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.contrib.redirects.locale.sk.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.contrib.redirects.locale.sk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.sk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.sl.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.contrib.redirects.locale.sl.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.contrib.redirects.locale.sl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.sl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.sq.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.contrib.redirects.locale.sq.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.contrib.redirects.locale.sq.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.sq.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.sr.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.contrib.redirects.locale.sr.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.contrib.redirects.locale.sr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.sr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.sr_Latn.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.contrib.redirects.locale.sr_Latn.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.contrib.redirects.locale.sr_Latn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.sr_Latn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.sv.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.contrib.redirects.locale.sv.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.contrib.redirects.locale.sv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.sv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.sw.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.contrib.redirects.locale.sw.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.contrib.redirects.locale.sw.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.sw.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.ta.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.contrib.redirects.locale.ta.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.contrib.redirects.locale.ta.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.ta.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.te.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.contrib.redirects.locale.te.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.contrib.redirects.locale.te.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.te.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.tg.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.contrib.redirects.locale.tg.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.contrib.redirects.locale.tg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.tg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.th.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.contrib.redirects.locale.th.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.contrib.redirects.locale.th.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.th.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.tk.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.contrib.redirects.locale.tk.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.contrib.redirects.locale.tk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.tk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.tr.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.contrib.redirects.locale.tr.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.contrib.redirects.locale.tr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.tr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.tt.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.contrib.redirects.locale.tt.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.contrib.redirects.locale.tt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.tt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.udm.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.contrib.redirects.locale.udm.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.contrib.redirects.locale.udm.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.udm.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.uk.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.contrib.redirects.locale.uk.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.contrib.redirects.locale.uk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.uk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.ur.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.contrib.redirects.locale.ur.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.contrib.redirects.locale.ur.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.ur.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.uz.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.contrib.redirects.locale.uz.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.contrib.redirects.locale.uz.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.uz.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.vi.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.contrib.redirects.locale.vi.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.contrib.redirects.locale.vi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.vi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.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.contrib.redirects.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.contrib.redirects.locale.zh_Hans.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.redirects.locale.zh_Hant.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.contrib.redirects.locale.zh_Hant.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.contrib.redirects.locale.zh_Hant.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.redirects.locale.zh_Hant.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.af.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.contrib.sessions.locale.af.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.contrib.sessions.locale.af.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.af.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.ar.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.contrib.sessions.locale.ar.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.contrib.sessions.locale.ar.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.ar.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.ar_DZ.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.contrib.sessions.locale.ar_DZ.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.contrib.sessions.locale.ar_DZ.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.ar_DZ.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.ast.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.contrib.sessions.locale.ast.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.contrib.sessions.locale.ast.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.ast.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.az.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.contrib.sessions.locale.az.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.contrib.sessions.locale.az.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.az.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.be.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.contrib.sessions.locale.be.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.contrib.sessions.locale.be.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.be.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.bg.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.contrib.sessions.locale.bg.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.contrib.sessions.locale.bg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.bg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.bn.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.contrib.sessions.locale.bn.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.contrib.sessions.locale.bn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.bn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.br.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.contrib.sessions.locale.br.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.contrib.sessions.locale.br.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.br.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.bs.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.contrib.sessions.locale.bs.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.contrib.sessions.locale.bs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.bs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.ca.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.contrib.sessions.locale.ca.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.contrib.sessions.locale.ca.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.ca.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.ckb.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.contrib.sessions.locale.ckb.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.contrib.sessions.locale.ckb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.ckb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.cs.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.contrib.sessions.locale.cs.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.contrib.sessions.locale.cs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.cs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.cy.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.contrib.sessions.locale.cy.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.contrib.sessions.locale.cy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.cy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.da.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.contrib.sessions.locale.da.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.contrib.sessions.locale.da.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.da.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.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.contrib.sessions.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.contrib.sessions.locale.de.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.dsb.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.contrib.sessions.locale.dsb.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.contrib.sessions.locale.dsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.dsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.el.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.contrib.sessions.locale.el.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.contrib.sessions.locale.el.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.el.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.en.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.contrib.sessions.locale.en.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.contrib.sessions.locale.en.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.en.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.en_AU.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.contrib.sessions.locale.en_AU.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.contrib.sessions.locale.en_AU.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.en_AU.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.en_GB.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.contrib.sessions.locale.en_GB.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.contrib.sessions.locale.en_GB.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.en_GB.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.eo.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.contrib.sessions.locale.eo.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.contrib.sessions.locale.eo.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.eo.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.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.contrib.sessions.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.contrib.sessions.locale.es.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.es_AR.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.contrib.sessions.locale.es_AR.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.contrib.sessions.locale.es_AR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.es_AR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.es_CO.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.contrib.sessions.locale.es_CO.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.contrib.sessions.locale.es_CO.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.es_CO.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.es_MX.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.contrib.sessions.locale.es_MX.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.contrib.sessions.locale.es_MX.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.es_MX.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.es_VE.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.contrib.sessions.locale.es_VE.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.contrib.sessions.locale.es_VE.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.es_VE.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.et.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.contrib.sessions.locale.et.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.contrib.sessions.locale.et.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.et.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.eu.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.contrib.sessions.locale.eu.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.contrib.sessions.locale.eu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.eu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.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.contrib.sessions.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.contrib.sessions.locale.fa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.fi.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.contrib.sessions.locale.fi.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.contrib.sessions.locale.fi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.fi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.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.contrib.sessions.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.contrib.sessions.locale.fr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.fy.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.contrib.sessions.locale.fy.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.contrib.sessions.locale.fy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.fy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.ga.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.contrib.sessions.locale.ga.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.contrib.sessions.locale.ga.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.ga.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.gd.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.contrib.sessions.locale.gd.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.contrib.sessions.locale.gd.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.gd.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.gl.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.contrib.sessions.locale.gl.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.contrib.sessions.locale.gl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.gl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.he.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.contrib.sessions.locale.he.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.contrib.sessions.locale.he.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.he.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.hi.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.contrib.sessions.locale.hi.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.contrib.sessions.locale.hi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.hi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.hr.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.contrib.sessions.locale.hr.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.contrib.sessions.locale.hr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.hr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.hsb.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.contrib.sessions.locale.hsb.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.contrib.sessions.locale.hsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.hsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.hu.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.contrib.sessions.locale.hu.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.contrib.sessions.locale.hu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.hu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.hy.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.contrib.sessions.locale.hy.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.contrib.sessions.locale.hy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.hy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.ia.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.contrib.sessions.locale.ia.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.contrib.sessions.locale.ia.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.ia.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.id.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.contrib.sessions.locale.id.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.contrib.sessions.locale.id.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.id.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.io.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.contrib.sessions.locale.io.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.contrib.sessions.locale.io.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.io.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.is.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.contrib.sessions.locale.is.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.contrib.sessions.locale.is.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.is.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.it.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.contrib.sessions.locale.it.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.contrib.sessions.locale.it.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.it.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.ja.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.contrib.sessions.locale.ja.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.contrib.sessions.locale.ja.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.ja.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.ka.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.contrib.sessions.locale.ka.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.contrib.sessions.locale.ka.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.ka.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.kab.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.contrib.sessions.locale.kab.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.contrib.sessions.locale.kab.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.kab.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.kk.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.contrib.sessions.locale.kk.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.contrib.sessions.locale.kk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.kk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.km.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.contrib.sessions.locale.km.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.contrib.sessions.locale.km.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.km.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.kn.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.contrib.sessions.locale.kn.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.contrib.sessions.locale.kn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.kn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.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.contrib.sessions.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.contrib.sessions.locale.ko.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.ky.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.contrib.sessions.locale.ky.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.contrib.sessions.locale.ky.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.ky.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.lb.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.contrib.sessions.locale.lb.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.contrib.sessions.locale.lb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.lb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.lt.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.contrib.sessions.locale.lt.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.contrib.sessions.locale.lt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.lt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.lv.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.contrib.sessions.locale.lv.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.contrib.sessions.locale.lv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.lv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.mk.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.contrib.sessions.locale.mk.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.contrib.sessions.locale.mk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.mk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.ml.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.contrib.sessions.locale.ml.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.contrib.sessions.locale.ml.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.ml.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.mn.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.contrib.sessions.locale.mn.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.contrib.sessions.locale.mn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.mn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.mr.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.contrib.sessions.locale.mr.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.contrib.sessions.locale.mr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.mr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.ms.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.contrib.sessions.locale.ms.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.contrib.sessions.locale.ms.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.ms.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.my.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.contrib.sessions.locale.my.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.contrib.sessions.locale.my.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.my.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.nb.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.contrib.sessions.locale.nb.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.contrib.sessions.locale.nb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.nb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.ne.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.contrib.sessions.locale.ne.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.contrib.sessions.locale.ne.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.ne.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.nl.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.contrib.sessions.locale.nl.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.contrib.sessions.locale.nl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.nl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.nn.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.contrib.sessions.locale.nn.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.contrib.sessions.locale.nn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.nn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.os.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.contrib.sessions.locale.os.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.contrib.sessions.locale.os.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.os.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.pa.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.contrib.sessions.locale.pa.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.contrib.sessions.locale.pa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.pa.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.pl.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.contrib.sessions.locale.pl.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.contrib.sessions.locale.pl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.pl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.pt.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.contrib.sessions.locale.pt.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.contrib.sessions.locale.pt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.pt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.pt_BR.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.contrib.sessions.locale.pt_BR.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.contrib.sessions.locale.pt_BR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.pt_BR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.ro.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.contrib.sessions.locale.ro.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.contrib.sessions.locale.ro.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.ro.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.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.contrib.sessions.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.contrib.sessions.locale.ru.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.sk.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.contrib.sessions.locale.sk.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.contrib.sessions.locale.sk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.sk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.sl.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.contrib.sessions.locale.sl.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.contrib.sessions.locale.sl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.sl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.sq.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.contrib.sessions.locale.sq.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.contrib.sessions.locale.sq.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.sq.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.sr.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.contrib.sessions.locale.sr.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.contrib.sessions.locale.sr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.sr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.sr_Latn.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.contrib.sessions.locale.sr_Latn.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.contrib.sessions.locale.sr_Latn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.sr_Latn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.sv.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.contrib.sessions.locale.sv.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.contrib.sessions.locale.sv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.sv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.sw.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.contrib.sessions.locale.sw.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.contrib.sessions.locale.sw.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.sw.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.ta.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.contrib.sessions.locale.ta.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.contrib.sessions.locale.ta.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.ta.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.te.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.contrib.sessions.locale.te.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.contrib.sessions.locale.te.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.te.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.tg.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.contrib.sessions.locale.tg.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.contrib.sessions.locale.tg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.tg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.th.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.contrib.sessions.locale.th.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.contrib.sessions.locale.th.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.th.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.tk.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.contrib.sessions.locale.tk.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.contrib.sessions.locale.tk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.tk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.tr.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.contrib.sessions.locale.tr.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.contrib.sessions.locale.tr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.tr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.tt.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.contrib.sessions.locale.tt.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.contrib.sessions.locale.tt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.tt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.udm.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.contrib.sessions.locale.udm.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.contrib.sessions.locale.udm.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.udm.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.uk.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.contrib.sessions.locale.uk.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.contrib.sessions.locale.uk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.uk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.ur.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.contrib.sessions.locale.ur.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.contrib.sessions.locale.ur.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.ur.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.uz.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.contrib.sessions.locale.uz.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.contrib.sessions.locale.uz.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.uz.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.vi.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.contrib.sessions.locale.vi.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.contrib.sessions.locale.vi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.vi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.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.contrib.sessions.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.contrib.sessions.locale.zh_Hans.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sessions.locale.zh_Hant.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.contrib.sessions.locale.zh_Hant.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.contrib.sessions.locale.zh_Hant.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sessions.locale.zh_Hant.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sitemaps.templates' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sitemaps.templates' 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.contrib.sitemaps.templates' 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.contrib.sitemaps.templates' to be distributed and are
        already explicitly excluding 'django.contrib.sitemaps.templates' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.af.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.contrib.sites.locale.af.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.contrib.sites.locale.af.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.af.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.ar.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.contrib.sites.locale.ar.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.contrib.sites.locale.ar.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.ar.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.ar_DZ.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.contrib.sites.locale.ar_DZ.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.contrib.sites.locale.ar_DZ.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.ar_DZ.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.ast.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.contrib.sites.locale.ast.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.contrib.sites.locale.ast.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.ast.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.az.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.contrib.sites.locale.az.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.contrib.sites.locale.az.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.az.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.be.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.contrib.sites.locale.be.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.contrib.sites.locale.be.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.be.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.bg.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.contrib.sites.locale.bg.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.contrib.sites.locale.bg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.bg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.bn.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.contrib.sites.locale.bn.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.contrib.sites.locale.bn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.bn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.br.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.contrib.sites.locale.br.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.contrib.sites.locale.br.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.br.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.bs.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.contrib.sites.locale.bs.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.contrib.sites.locale.bs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.bs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.ca.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.contrib.sites.locale.ca.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.contrib.sites.locale.ca.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.ca.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.ckb.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.contrib.sites.locale.ckb.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.contrib.sites.locale.ckb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.ckb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.cs.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.contrib.sites.locale.cs.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.contrib.sites.locale.cs.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.cs.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.cy.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.contrib.sites.locale.cy.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.contrib.sites.locale.cy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.cy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.da.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.contrib.sites.locale.da.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.contrib.sites.locale.da.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.da.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.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.contrib.sites.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.contrib.sites.locale.de.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.dsb.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.contrib.sites.locale.dsb.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.contrib.sites.locale.dsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.dsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.el.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.contrib.sites.locale.el.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.contrib.sites.locale.el.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.el.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.en.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.contrib.sites.locale.en.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.contrib.sites.locale.en.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.en.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.en_AU.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.contrib.sites.locale.en_AU.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.contrib.sites.locale.en_AU.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.en_AU.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.en_GB.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.contrib.sites.locale.en_GB.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.contrib.sites.locale.en_GB.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.en_GB.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.eo.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.contrib.sites.locale.eo.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.contrib.sites.locale.eo.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.eo.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.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.contrib.sites.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.contrib.sites.locale.es.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.es_AR.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.contrib.sites.locale.es_AR.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.contrib.sites.locale.es_AR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.es_AR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.es_CO.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.contrib.sites.locale.es_CO.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.contrib.sites.locale.es_CO.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.es_CO.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.es_MX.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.contrib.sites.locale.es_MX.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.contrib.sites.locale.es_MX.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.es_MX.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.es_VE.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.contrib.sites.locale.es_VE.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.contrib.sites.locale.es_VE.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.es_VE.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.et.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.contrib.sites.locale.et.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.contrib.sites.locale.et.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.et.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.eu.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.contrib.sites.locale.eu.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.contrib.sites.locale.eu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.eu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.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.contrib.sites.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.contrib.sites.locale.fa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.fi.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.contrib.sites.locale.fi.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.contrib.sites.locale.fi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.fi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.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.contrib.sites.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.contrib.sites.locale.fr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.fy.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.contrib.sites.locale.fy.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.contrib.sites.locale.fy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.fy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.ga.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.contrib.sites.locale.ga.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.contrib.sites.locale.ga.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.ga.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.gd.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.contrib.sites.locale.gd.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.contrib.sites.locale.gd.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.gd.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.gl.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.contrib.sites.locale.gl.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.contrib.sites.locale.gl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.gl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.he.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.contrib.sites.locale.he.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.contrib.sites.locale.he.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.he.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.hi.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.contrib.sites.locale.hi.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.contrib.sites.locale.hi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.hi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.hr.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.contrib.sites.locale.hr.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.contrib.sites.locale.hr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.hr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.hsb.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.contrib.sites.locale.hsb.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.contrib.sites.locale.hsb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.hsb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.hu.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.contrib.sites.locale.hu.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.contrib.sites.locale.hu.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.hu.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.hy.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.contrib.sites.locale.hy.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.contrib.sites.locale.hy.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.hy.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.ia.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.contrib.sites.locale.ia.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.contrib.sites.locale.ia.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.ia.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.id.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.contrib.sites.locale.id.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.contrib.sites.locale.id.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.id.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.io.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.contrib.sites.locale.io.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.contrib.sites.locale.io.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.io.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.is.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.contrib.sites.locale.is.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.contrib.sites.locale.is.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.is.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.it.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.contrib.sites.locale.it.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.contrib.sites.locale.it.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.it.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.ja.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.contrib.sites.locale.ja.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.contrib.sites.locale.ja.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.ja.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.ka.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.contrib.sites.locale.ka.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.contrib.sites.locale.ka.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.ka.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.kab.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.contrib.sites.locale.kab.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.contrib.sites.locale.kab.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.kab.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.kk.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.contrib.sites.locale.kk.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.contrib.sites.locale.kk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.kk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.km.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.contrib.sites.locale.km.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.contrib.sites.locale.km.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.km.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.kn.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.contrib.sites.locale.kn.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.contrib.sites.locale.kn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.kn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.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.contrib.sites.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.contrib.sites.locale.ko.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.ky.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.contrib.sites.locale.ky.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.contrib.sites.locale.ky.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.ky.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.lb.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.contrib.sites.locale.lb.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.contrib.sites.locale.lb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.lb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.lt.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.contrib.sites.locale.lt.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.contrib.sites.locale.lt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.lt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.lv.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.contrib.sites.locale.lv.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.contrib.sites.locale.lv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.lv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.mk.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.contrib.sites.locale.mk.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.contrib.sites.locale.mk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.mk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.ml.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.contrib.sites.locale.ml.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.contrib.sites.locale.ml.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.ml.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.mn.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.contrib.sites.locale.mn.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.contrib.sites.locale.mn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.mn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.mr.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.contrib.sites.locale.mr.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.contrib.sites.locale.mr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.mr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.ms.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.contrib.sites.locale.ms.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.contrib.sites.locale.ms.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.ms.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.my.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.contrib.sites.locale.my.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.contrib.sites.locale.my.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.my.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.nb.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.contrib.sites.locale.nb.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.contrib.sites.locale.nb.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.nb.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.ne.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.contrib.sites.locale.ne.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.contrib.sites.locale.ne.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.ne.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.nl.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.contrib.sites.locale.nl.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.contrib.sites.locale.nl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.nl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.nn.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.contrib.sites.locale.nn.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.contrib.sites.locale.nn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.nn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.os.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.contrib.sites.locale.os.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.contrib.sites.locale.os.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.os.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.pa.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.contrib.sites.locale.pa.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.contrib.sites.locale.pa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.pa.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.pl.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.contrib.sites.locale.pl.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.contrib.sites.locale.pl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.pl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.pt.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.contrib.sites.locale.pt.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.contrib.sites.locale.pt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.pt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.pt_BR.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.contrib.sites.locale.pt_BR.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.contrib.sites.locale.pt_BR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.pt_BR.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.ro.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.contrib.sites.locale.ro.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.contrib.sites.locale.ro.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.ro.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.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.contrib.sites.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.contrib.sites.locale.ru.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.sk.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.contrib.sites.locale.sk.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.contrib.sites.locale.sk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.sk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.sl.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.contrib.sites.locale.sl.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.contrib.sites.locale.sl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.sl.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.sq.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.contrib.sites.locale.sq.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.contrib.sites.locale.sq.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.sq.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.sr.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.contrib.sites.locale.sr.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.contrib.sites.locale.sr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.sr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.sr_Latn.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.contrib.sites.locale.sr_Latn.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.contrib.sites.locale.sr_Latn.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.sr_Latn.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.sv.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.contrib.sites.locale.sv.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.contrib.sites.locale.sv.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.sv.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.sw.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.contrib.sites.locale.sw.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.contrib.sites.locale.sw.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.sw.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.ta.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.contrib.sites.locale.ta.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.contrib.sites.locale.ta.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.ta.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.te.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.contrib.sites.locale.te.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.contrib.sites.locale.te.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.te.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.tg.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.contrib.sites.locale.tg.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.contrib.sites.locale.tg.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.tg.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.th.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.contrib.sites.locale.th.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.contrib.sites.locale.th.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.th.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.tk.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.contrib.sites.locale.tk.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.contrib.sites.locale.tk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.tk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.tr.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.contrib.sites.locale.tr.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.contrib.sites.locale.tr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.tr.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.tt.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.contrib.sites.locale.tt.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.contrib.sites.locale.tt.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.tt.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.udm.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.contrib.sites.locale.udm.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.contrib.sites.locale.udm.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.udm.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.uk.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.contrib.sites.locale.uk.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.contrib.sites.locale.uk.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.uk.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.ur.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.contrib.sites.locale.ur.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.contrib.sites.locale.ur.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.ur.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.uz.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.contrib.sites.locale.uz.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.contrib.sites.locale.uz.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.uz.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.vi.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.contrib.sites.locale.vi.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.contrib.sites.locale.vi.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.vi.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.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.contrib.sites.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.contrib.sites.locale.zh_Hans.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.sites.locale.zh_Hant.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.contrib.sites.locale.zh_Hant.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.contrib.sites.locale.zh_Hant.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django.contrib.sites.locale.zh_Hant.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)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.jinja2.django.forms' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.forms.jinja2.django.forms' 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.forms.jinja2.django.forms' 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.forms.jinja2.django.forms' to be distributed and are
        already explicitly excluding 'django.forms.jinja2.django.forms' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.jinja2.django.forms.errors.dict' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.forms.jinja2.django.forms.errors.dict' 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.forms.jinja2.django.forms.errors.dict' 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.forms.jinja2.django.forms.errors.dict' to be distributed and are
        already explicitly excluding 'django.forms.jinja2.django.forms.errors.dict' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.jinja2.django.forms.errors.list' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.forms.jinja2.django.forms.errors.list' 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.forms.jinja2.django.forms.errors.list' 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.forms.jinja2.django.forms.errors.list' to be distributed and are
        already explicitly excluding 'django.forms.jinja2.django.forms.errors.list' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.jinja2.django.forms.formsets' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.forms.jinja2.django.forms.formsets' 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.forms.jinja2.django.forms.formsets' 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.forms.jinja2.django.forms.formsets' to be distributed and are
        already explicitly excluding 'django.forms.jinja2.django.forms.formsets' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.jinja2.django.forms.widgets' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.forms.jinja2.django.forms.widgets' 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.forms.jinja2.django.forms.widgets' 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.forms.jinja2.django.forms.widgets' to be distributed and are
        already explicitly excluding 'django.forms.jinja2.django.forms.widgets' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.templates.django.forms' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.forms.templates.django.forms' 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.forms.templates.django.forms' 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.forms.templates.django.forms' to be distributed and are
        already explicitly excluding 'django.forms.templates.django.forms' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.templates.django.forms.errors.dict' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.forms.templates.django.forms.errors.dict' 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.forms.templates.django.forms.errors.dict' 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.forms.templates.django.forms.errors.dict' to be distributed and are
        already explicitly excluding 'django.forms.templates.django.forms.errors.dict' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.templates.django.forms.errors.list' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.forms.templates.django.forms.errors.list' 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.forms.templates.django.forms.errors.list' 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.forms.templates.django.forms.errors.list' to be distributed and are
        already explicitly excluding 'django.forms.templates.django.forms.errors.list' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.templates.django.forms.formsets' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.forms.templates.django.forms.formsets' 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.forms.templates.django.forms.formsets' 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.forms.templates.django.forms.formsets' to be distributed and are
        already explicitly excluding 'django.forms.templates.django.forms.formsets' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.templates.django.forms.widgets' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.forms.templates.django.forms.widgets' 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.forms.templates.django.forms.widgets' 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.forms.templates.django.forms.widgets' to be distributed and are
        already explicitly excluding 'django.forms.templates.django.forms.widgets' 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/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.views.templates' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.views.templates' 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.views.templates' 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.views.templates' to be distributed and are
        already explicitly excluding 'django.views.templates' 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)
2025-04-22 17:58:53,974 root INFO creating build/lib/django/views/templates
2025-04-22 17:58:53,975 root INFO copying django/views/templates/default_urlconf.html -> build/lib/django/views/templates
2025-04-22 17:58:53,975 root INFO copying django/views/templates/technical_404.html -> build/lib/django/views/templates
2025-04-22 17:58:53,975 root INFO copying django/views/templates/technical_500.html -> build/lib/django/views/templates
2025-04-22 17:58:53,976 root INFO copying django/views/templates/technical_500.txt -> build/lib/django/views/templates
2025-04-22 17:58:53,976 root INFO copying django/dispatch/license.txt -> build/lib/django/dispatch
2025-04-22 17:58:53,976 root INFO creating build/lib/django/conf/app_template
2025-04-22 17:58:53,976 root INFO copying django/conf/app_template/__init__.py-tpl -> build/lib/django/conf/app_template
2025-04-22 17:58:53,977 root INFO copying django/conf/app_template/admin.py-tpl -> build/lib/django/conf/app_template
2025-04-22 17:58:53,977 root INFO copying django/conf/app_template/apps.py-tpl -> build/lib/django/conf/app_template
2025-04-22 17:58:53,977 root INFO copying django/conf/app_template/models.py-tpl -> build/lib/django/conf/app_template
2025-04-22 17:58:53,977 root INFO copying django/conf/app_template/tests.py-tpl -> build/lib/django/conf/app_template
2025-04-22 17:58:53,977 root INFO copying django/conf/app_template/views.py-tpl -> build/lib/django/conf/app_template
2025-04-22 17:58:53,978 root INFO creating build/lib/django/conf/app_template/migrations
2025-04-22 17:58:53,978 root INFO copying django/conf/app_template/migrations/__init__.py-tpl -> build/lib/django/conf/app_template/migrations
2025-04-22 17:58:53,978 root INFO creating build/lib/django/conf/project_template
2025-04-22 17:58:53,978 root INFO copying django/conf/project_template/manage.py-tpl -> build/lib/django/conf/project_template
2025-04-22 17:58:53,978 root INFO creating build/lib/django/conf/project_template/project_name
2025-04-22 17:58:53,979 root INFO copying django/conf/project_template/project_name/__init__.py-tpl -> build/lib/django/conf/project_template/project_name
2025-04-22 17:58:53,979 root INFO copying django/conf/project_template/project_name/asgi.py-tpl -> build/lib/django/conf/project_template/project_name
2025-04-22 17:58:53,979 root INFO copying django/conf/project_template/project_name/settings.py-tpl -> build/lib/django/conf/project_template/project_name
2025-04-22 17:58:53,979 root INFO copying django/conf/project_template/project_name/urls.py-tpl -> build/lib/django/conf/project_template/project_name
2025-04-22 17:58:53,979 root INFO copying django/conf/project_template/project_name/wsgi.py-tpl -> build/lib/django/conf/project_template/project_name
2025-04-22 17:58:53,980 root INFO creating build/lib/django/forms/jinja2/django/forms
2025-04-22 17:58:53,980 root INFO copying django/forms/jinja2/django/forms/attrs.html -> build/lib/django/forms/jinja2/django/forms
2025-04-22 17:58:53,980 root INFO copying django/forms/jinja2/django/forms/default.html -> build/lib/django/forms/jinja2/django/forms
2025-04-22 17:58:53,980 root INFO copying django/forms/jinja2/django/forms/div.html -> build/lib/django/forms/jinja2/django/forms
2025-04-22 17:58:53,980 root INFO copying django/forms/jinja2/django/forms/label.html -> build/lib/django/forms/jinja2/django/forms
2025-04-22 17:58:53,981 root INFO copying django/forms/jinja2/django/forms/p.html -> build/lib/django/forms/jinja2/django/forms
2025-04-22 17:58:53,981 root INFO copying django/forms/jinja2/django/forms/table.html -> build/lib/django/forms/jinja2/django/forms
2025-04-22 17:58:53,981 root INFO copying django/forms/jinja2/django/forms/ul.html -> build/lib/django/forms/jinja2/django/forms
2025-04-22 17:58:53,981 root INFO creating build/lib/django/forms/jinja2/django/forms/errors/dict
2025-04-22 17:58:53,982 root INFO copying django/forms/jinja2/django/forms/errors/dict/default.html -> build/lib/django/forms/jinja2/django/forms/errors/dict
2025-04-22 17:58:53,982 root INFO copying django/forms/jinja2/django/forms/errors/dict/text.txt -> build/lib/django/forms/jinja2/django/forms/errors/dict
2025-04-22 17:58:53,982 root INFO copying django/forms/jinja2/django/forms/errors/dict/ul.html -> build/lib/django/forms/jinja2/django/forms/errors/dict
2025-04-22 17:58:53,982 root INFO creating build/lib/django/forms/jinja2/django/forms/errors/list
2025-04-22 17:58:53,982 root INFO copying django/forms/jinja2/django/forms/errors/list/default.html -> build/lib/django/forms/jinja2/django/forms/errors/list
2025-04-22 17:58:53,983 root INFO copying django/forms/jinja2/django/forms/errors/list/text.txt -> build/lib/django/forms/jinja2/django/forms/errors/list
2025-04-22 17:58:53,983 root INFO copying django/forms/jinja2/django/forms/errors/list/ul.html -> build/lib/django/forms/jinja2/django/forms/errors/list
2025-04-22 17:58:53,983 root INFO creating build/lib/django/forms/jinja2/django/forms/formsets
2025-04-22 17:58:53,983 root INFO copying django/forms/jinja2/django/forms/formsets/default.html -> build/lib/django/forms/jinja2/django/forms/formsets
2025-04-22 17:58:53,983 root INFO copying django/forms/jinja2/django/forms/formsets/div.html -> build/lib/django/forms/jinja2/django/forms/formsets
2025-04-22 17:58:53,984 root INFO copying django/forms/jinja2/django/forms/formsets/p.html -> build/lib/django/forms/jinja2/django/forms/formsets
2025-04-22 17:58:53,984 root INFO copying django/forms/jinja2/django/forms/formsets/table.html -> build/lib/django/forms/jinja2/django/forms/formsets
2025-04-22 17:58:53,984 root INFO copying django/forms/jinja2/django/forms/formsets/ul.html -> build/lib/django/forms/jinja2/django/forms/formsets
2025-04-22 17:58:53,984 root INFO creating build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,984 root INFO copying django/forms/jinja2/django/forms/widgets/attrs.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,985 root INFO copying django/forms/jinja2/django/forms/widgets/checkbox.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,985 root INFO copying django/forms/jinja2/django/forms/widgets/checkbox_option.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,985 root INFO copying django/forms/jinja2/django/forms/widgets/checkbox_select.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,985 root INFO copying django/forms/jinja2/django/forms/widgets/clearable_file_input.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,985 root INFO copying django/forms/jinja2/django/forms/widgets/date.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,986 root INFO copying django/forms/jinja2/django/forms/widgets/datetime.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,986 root INFO copying django/forms/jinja2/django/forms/widgets/email.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,986 root INFO copying django/forms/jinja2/django/forms/widgets/file.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,986 root INFO copying django/forms/jinja2/django/forms/widgets/hidden.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,987 root INFO copying django/forms/jinja2/django/forms/widgets/input.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,987 root INFO copying django/forms/jinja2/django/forms/widgets/input_option.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,987 root INFO copying django/forms/jinja2/django/forms/widgets/multiple_hidden.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,987 root INFO copying django/forms/jinja2/django/forms/widgets/multiple_input.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,987 root INFO copying django/forms/jinja2/django/forms/widgets/multiwidget.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,988 root INFO copying django/forms/jinja2/django/forms/widgets/number.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,988 root INFO copying django/forms/jinja2/django/forms/widgets/password.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,988 root INFO copying django/forms/jinja2/django/forms/widgets/radio.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,988 root INFO copying django/forms/jinja2/django/forms/widgets/radio_option.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,988 root INFO copying django/forms/jinja2/django/forms/widgets/select.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,989 root INFO copying django/forms/jinja2/django/forms/widgets/select_date.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,989 root INFO copying django/forms/jinja2/django/forms/widgets/select_option.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,989 root INFO copying django/forms/jinja2/django/forms/widgets/splitdatetime.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,989 root INFO copying django/forms/jinja2/django/forms/widgets/splithiddendatetime.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,990 root INFO copying django/forms/jinja2/django/forms/widgets/text.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,990 root INFO copying django/forms/jinja2/django/forms/widgets/textarea.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,990 root INFO copying django/forms/jinja2/django/forms/widgets/time.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,990 root INFO copying django/forms/jinja2/django/forms/widgets/url.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:53,990 root INFO creating build/lib/django/forms/templates/django/forms
2025-04-22 17:58:53,991 root INFO copying django/forms/templates/django/forms/attrs.html -> build/lib/django/forms/templates/django/forms
2025-04-22 17:58:53,991 root INFO copying django/forms/templates/django/forms/default.html -> build/lib/django/forms/templates/django/forms
2025-04-22 17:58:53,991 root INFO copying django/forms/templates/django/forms/div.html -> build/lib/django/forms/templates/django/forms
2025-04-22 17:58:53,991 root INFO copying django/forms/templates/django/forms/label.html -> build/lib/django/forms/templates/django/forms
2025-04-22 17:58:53,991 root INFO copying django/forms/templates/django/forms/p.html -> build/lib/django/forms/templates/django/forms
2025-04-22 17:58:53,992 root INFO copying django/forms/templates/django/forms/table.html -> build/lib/django/forms/templates/django/forms
2025-04-22 17:58:53,992 root INFO copying django/forms/templates/django/forms/ul.html -> build/lib/django/forms/templates/django/forms
2025-04-22 17:58:53,992 root INFO creating build/lib/django/forms/templates/django/forms/errors/dict
2025-04-22 17:58:53,992 root INFO copying django/forms/templates/django/forms/errors/dict/default.html -> build/lib/django/forms/templates/django/forms/errors/dict
2025-04-22 17:58:53,992 root INFO copying django/forms/templates/django/forms/errors/dict/text.txt -> build/lib/django/forms/templates/django/forms/errors/dict
2025-04-22 17:58:53,993 root INFO copying django/forms/templates/django/forms/errors/dict/ul.html -> build/lib/django/forms/templates/django/forms/errors/dict
2025-04-22 17:58:53,993 root INFO creating build/lib/django/forms/templates/django/forms/errors/list
2025-04-22 17:58:53,993 root INFO copying django/forms/templates/django/forms/errors/list/default.html -> build/lib/django/forms/templates/django/forms/errors/list
2025-04-22 17:58:53,993 root INFO copying django/forms/templates/django/forms/errors/list/text.txt -> build/lib/django/forms/templates/django/forms/errors/list
2025-04-22 17:58:53,994 root INFO copying django/forms/templates/django/forms/errors/list/ul.html -> build/lib/django/forms/templates/django/forms/errors/list
2025-04-22 17:58:53,994 root INFO creating build/lib/django/forms/templates/django/forms/formsets
2025-04-22 17:58:53,994 root INFO copying django/forms/templates/django/forms/formsets/default.html -> build/lib/django/forms/templates/django/forms/formsets
2025-04-22 17:58:53,994 root INFO copying django/forms/templates/django/forms/formsets/div.html -> build/lib/django/forms/templates/django/forms/formsets
2025-04-22 17:58:53,994 root INFO copying django/forms/templates/django/forms/formsets/p.html -> build/lib/django/forms/templates/django/forms/formsets
2025-04-22 17:58:53,995 root INFO copying django/forms/templates/django/forms/formsets/table.html -> build/lib/django/forms/templates/django/forms/formsets
2025-04-22 17:58:53,995 root INFO copying django/forms/templates/django/forms/formsets/ul.html -> build/lib/django/forms/templates/django/forms/formsets
2025-04-22 17:58:53,995 root INFO creating build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,995 root INFO copying django/forms/templates/django/forms/widgets/attrs.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,995 root INFO copying django/forms/templates/django/forms/widgets/checkbox.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,996 root INFO copying django/forms/templates/django/forms/widgets/checkbox_option.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,996 root INFO copying django/forms/templates/django/forms/widgets/checkbox_select.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,996 root INFO copying django/forms/templates/django/forms/widgets/clearable_file_input.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,996 root INFO copying django/forms/templates/django/forms/widgets/date.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,996 root INFO copying django/forms/templates/django/forms/widgets/datetime.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,997 root INFO copying django/forms/templates/django/forms/widgets/email.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,997 root INFO copying django/forms/templates/django/forms/widgets/file.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,997 root INFO copying django/forms/templates/django/forms/widgets/hidden.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,997 root INFO copying django/forms/templates/django/forms/widgets/input.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,997 root INFO copying django/forms/templates/django/forms/widgets/input_option.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,998 root INFO copying django/forms/templates/django/forms/widgets/multiple_hidden.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,998 root INFO copying django/forms/templates/django/forms/widgets/multiple_input.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,998 root INFO copying django/forms/templates/django/forms/widgets/multiwidget.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,998 root INFO copying django/forms/templates/django/forms/widgets/number.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,999 root INFO copying django/forms/templates/django/forms/widgets/password.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,999 root INFO copying django/forms/templates/django/forms/widgets/radio.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,999 root INFO copying django/forms/templates/django/forms/widgets/radio_option.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,999 root INFO copying django/forms/templates/django/forms/widgets/select.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:53,999 root INFO copying django/forms/templates/django/forms/widgets/select_date.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:54,000 root INFO copying django/forms/templates/django/forms/widgets/select_option.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:54,000 root INFO copying django/forms/templates/django/forms/widgets/splitdatetime.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:54,000 root INFO copying django/forms/templates/django/forms/widgets/splithiddendatetime.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:54,000 root INFO copying django/forms/templates/django/forms/widgets/text.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:54,000 root INFO copying django/forms/templates/django/forms/widgets/textarea.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:54,001 root INFO copying django/forms/templates/django/forms/widgets/time.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:54,001 root INFO copying django/forms/templates/django/forms/widgets/url.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 17:58:54,001 root INFO creating build/lib/django/conf/locale/af/LC_MESSAGES
2025-04-22 17:58:54,001 root INFO copying django/conf/locale/af/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/af/LC_MESSAGES
2025-04-22 17:58:54,002 root INFO copying django/conf/locale/af/LC_MESSAGES/django.po -> build/lib/django/conf/locale/af/LC_MESSAGES
2025-04-22 17:58:54,002 root INFO creating build/lib/django/conf/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,002 root INFO copying django/conf/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,002 root INFO copying django/conf/locale/ast/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,003 root INFO creating build/lib/django/conf/locale/be/LC_MESSAGES
2025-04-22 17:58:54,003 root INFO copying django/conf/locale/be/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/be/LC_MESSAGES
2025-04-22 17:58:54,003 root INFO copying django/conf/locale/be/LC_MESSAGES/django.po -> build/lib/django/conf/locale/be/LC_MESSAGES
2025-04-22 17:58:54,003 root INFO creating build/lib/django/conf/locale/br/LC_MESSAGES
2025-04-22 17:58:54,004 root INFO copying django/conf/locale/br/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/br/LC_MESSAGES
2025-04-22 17:58:54,004 root INFO copying django/conf/locale/br/LC_MESSAGES/django.po -> build/lib/django/conf/locale/br/LC_MESSAGES
2025-04-22 17:58:54,004 root INFO creating build/lib/django/conf/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,004 root INFO copying django/conf/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,004 root INFO copying django/conf/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,005 root INFO creating build/lib/django/conf/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,005 root INFO copying django/conf/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,005 root INFO copying django/conf/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,005 root INFO creating build/lib/django/conf/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,006 root INFO copying django/conf/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,006 root INFO copying django/conf/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,006 root INFO creating build/lib/django/conf/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,006 root INFO copying django/conf/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,007 root INFO copying django/conf/locale/hy/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,007 root INFO creating build/lib/django/conf/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,007 root INFO copying django/conf/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,007 root INFO copying django/conf/locale/ia/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,008 root INFO creating build/lib/django/conf/locale/io/LC_MESSAGES
2025-04-22 17:58:54,008 root INFO copying django/conf/locale/io/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/io/LC_MESSAGES
2025-04-22 17:58:54,008 root INFO copying django/conf/locale/io/LC_MESSAGES/django.po -> build/lib/django/conf/locale/io/LC_MESSAGES
2025-04-22 17:58:54,008 root INFO creating build/lib/django/conf/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,008 root INFO copying django/conf/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,009 root INFO copying django/conf/locale/kab/LC_MESSAGES/django.po -> build/lib/django/conf/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,009 root INFO creating build/lib/django/conf/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,009 root INFO copying django/conf/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,009 root INFO copying django/conf/locale/kk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,010 root INFO creating build/lib/django/conf/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,010 root INFO copying django/conf/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,010 root INFO copying django/conf/locale/lb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,010 root INFO creating build/lib/django/conf/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,010 root INFO copying django/conf/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,011 root INFO copying django/conf/locale/mr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,011 root INFO creating build/lib/django/conf/locale/my/LC_MESSAGES
2025-04-22 17:58:54,011 root INFO copying django/conf/locale/my/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/my/LC_MESSAGES
2025-04-22 17:58:54,011 root INFO copying django/conf/locale/my/LC_MESSAGES/django.po -> build/lib/django/conf/locale/my/LC_MESSAGES
2025-04-22 17:58:54,012 root INFO creating build/lib/django/conf/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,012 root INFO copying django/conf/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,012 root INFO copying django/conf/locale/ne/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,012 root INFO creating build/lib/django/conf/locale/os/LC_MESSAGES
2025-04-22 17:58:54,013 root INFO copying django/conf/locale/os/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/os/LC_MESSAGES
2025-04-22 17:58:54,013 root INFO copying django/conf/locale/os/LC_MESSAGES/django.po -> build/lib/django/conf/locale/os/LC_MESSAGES
2025-04-22 17:58:54,013 root INFO creating build/lib/django/conf/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,013 root INFO copying django/conf/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,013 root INFO copying django/conf/locale/pa/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,014 root INFO creating build/lib/django/conf/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,014 root INFO copying django/conf/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,014 root INFO copying django/conf/locale/sw/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,014 root INFO creating build/lib/django/conf/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,015 root INFO copying django/conf/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,015 root INFO copying django/conf/locale/tt/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,015 root INFO creating build/lib/django/conf/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,015 root INFO copying django/conf/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,015 root INFO copying django/conf/locale/udm/LC_MESSAGES/django.po -> build/lib/django/conf/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,016 root INFO creating build/lib/django/conf/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,016 root INFO copying django/conf/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,016 root INFO copying django/conf/locale/ur/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,016 root INFO creating build/lib/django/conf/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,017 root INFO copying django/conf/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,017 root INFO copying django/conf/locale/lv/LC_MESSAGES/django.po -> build/lib/django/conf/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,017 root INFO creating build/lib/django/conf/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,017 root INFO copying django/conf/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,017 root INFO copying django/conf/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,018 root INFO creating build/lib/django/conf/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,018 root INFO copying django/conf/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,018 root INFO copying django/conf/locale/ca/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,018 root INFO creating build/lib/django/conf/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,019 root INFO copying django/conf/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,019 root INFO copying django/conf/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,019 root INFO creating build/lib/django/conf/locale/el/LC_MESSAGES
2025-04-22 17:58:54,019 root INFO copying django/conf/locale/el/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/el/LC_MESSAGES
2025-04-22 17:58:54,019 root INFO copying django/conf/locale/el/LC_MESSAGES/django.po -> build/lib/django/conf/locale/el/LC_MESSAGES
2025-04-22 17:58:54,020 root INFO creating build/lib/django/conf/locale/en/LC_MESSAGES
2025-04-22 17:58:54,020 root INFO copying django/conf/locale/en/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en/LC_MESSAGES
2025-04-22 17:58:54,020 root INFO copying django/conf/locale/en/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en/LC_MESSAGES
2025-04-22 17:58:54,020 root INFO creating build/lib/django/conf/locale/et/LC_MESSAGES
2025-04-22 17:58:54,021 root INFO copying django/conf/locale/et/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/et/LC_MESSAGES
2025-04-22 17:58:54,021 root INFO copying django/conf/locale/et/LC_MESSAGES/django.po -> build/lib/django/conf/locale/et/LC_MESSAGES
2025-04-22 17:58:54,021 root INFO creating build/lib/django/conf/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,021 root INFO copying django/conf/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,022 root INFO copying django/conf/locale/nn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,022 root INFO creating build/lib/django/conf/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,022 root INFO copying django/conf/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,022 root INFO copying django/conf/locale/cy/LC_MESSAGES/django.po -> build/lib/django/conf/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,022 root INFO creating build/lib/django/conf/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,023 root INFO copying django/conf/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,023 root INFO copying django/conf/locale/ko/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,023 root INFO creating build/lib/django/conf/locale/is/LC_MESSAGES
2025-04-22 17:58:54,023 root INFO copying django/conf/locale/is/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/is/LC_MESSAGES
2025-04-22 17:58:54,024 root INFO copying django/conf/locale/is/LC_MESSAGES/django.po -> build/lib/django/conf/locale/is/LC_MESSAGES
2025-04-22 17:58:54,024 root INFO creating build/lib/django/conf/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,024 root INFO copying django/conf/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,024 root INFO copying django/conf/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,024 root INFO creating build/lib/django/conf/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,025 root INFO copying django/conf/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,025 root INFO copying django/conf/locale/fy/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,025 root INFO creating build/lib/django/conf/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,025 root INFO copying django/conf/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,025 root INFO copying django/conf/locale/bg/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,026 root INFO creating build/lib/django/conf/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,026 root INFO copying django/conf/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,026 root INFO copying django/conf/locale/ga/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,026 root INFO creating build/lib/django/conf/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,026 root INFO copying django/conf/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,027 root INFO copying django/conf/locale/gl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,027 root INFO creating build/lib/django/conf/locale/ig/LC_MESSAGES
2025-04-22 17:58:54,027 root INFO copying django/conf/locale/ig/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ig/LC_MESSAGES
2025-04-22 17:58:54,027 root INFO copying django/conf/locale/ig/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ig/LC_MESSAGES
2025-04-22 17:58:54,028 root INFO creating build/lib/django/conf/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,028 root INFO copying django/conf/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,029 root INFO copying django/conf/locale/uk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,029 root INFO creating build/lib/django/conf/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,029 root INFO copying django/conf/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,030 root INFO copying django/conf/locale/uz/LC_MESSAGES/django.po -> build/lib/django/conf/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,030 root INFO creating build/lib/django/conf/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,030 root INFO copying django/conf/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,030 root INFO copying django/conf/locale/kn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,030 root INFO creating build/lib/django/conf/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,031 root INFO copying django/conf/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,031 root INFO copying django/conf/locale/ja/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,031 root INFO creating build/lib/django/conf/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,031 root INFO copying django/conf/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,032 root INFO copying django/conf/locale/cs/LC_MESSAGES/django.po -> build/lib/django/conf/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,032 root INFO creating build/lib/django/conf/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,032 root INFO copying django/conf/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,032 root INFO copying django/conf/locale/tr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,032 root INFO creating build/lib/django/conf/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,033 root INFO copying django/conf/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,033 root INFO copying django/conf/locale/sl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,033 root INFO creating build/lib/django/conf/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,033 root INFO copying django/conf/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,034 root INFO copying django/conf/locale/sq/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,034 root INFO creating build/lib/django/conf/locale/az/LC_MESSAGES
2025-04-22 17:58:54,034 root INFO copying django/conf/locale/az/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/az/LC_MESSAGES
2025-04-22 17:58:54,034 root INFO copying django/conf/locale/az/LC_MESSAGES/django.po -> build/lib/django/conf/locale/az/LC_MESSAGES
2025-04-22 17:58:54,035 root INFO creating build/lib/django/conf/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,035 root INFO copying django/conf/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,035 root INFO copying django/conf/locale/eo/LC_MESSAGES/django.po -> build/lib/django/conf/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,035 root INFO creating build/lib/django/conf/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,035 root INFO copying django/conf/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,036 root INFO copying django/conf/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,036 root INFO creating build/lib/django/conf/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,036 root INFO copying django/conf/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,036 root INFO copying django/conf/locale/pl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,037 root INFO creating build/lib/django/conf/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,037 root INFO copying django/conf/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,037 root INFO copying django/conf/locale/gd/LC_MESSAGES/django.po -> build/lib/django/conf/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,037 root INFO creating build/lib/django/conf/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,037 root INFO copying django/conf/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,038 root INFO copying django/conf/locale/hr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,038 root INFO creating build/lib/django/conf/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,038 root INFO copying django/conf/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,038 root INFO copying django/conf/locale/ru/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,039 root INFO creating build/lib/django/conf/locale/es/LC_MESSAGES
2025-04-22 17:58:54,039 root INFO copying django/conf/locale/es/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es/LC_MESSAGES
2025-04-22 17:58:54,039 root INFO copying django/conf/locale/es/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es/LC_MESSAGES
2025-04-22 17:58:54,039 root INFO creating build/lib/django/conf/locale/id/LC_MESSAGES
2025-04-22 17:58:54,040 root INFO copying django/conf/locale/id/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/id/LC_MESSAGES
2025-04-22 17:58:54,040 root INFO copying django/conf/locale/id/LC_MESSAGES/django.po -> build/lib/django/conf/locale/id/LC_MESSAGES
2025-04-22 17:58:54,040 root INFO creating build/lib/django/conf/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,040 root INFO copying django/conf/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,040 root INFO copying django/conf/locale/fi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,041 root INFO creating build/lib/django/conf/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,041 root INFO copying django/conf/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,041 root INFO copying django/conf/locale/mk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,041 root INFO creating build/lib/django/conf/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,042 root INFO copying django/conf/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,042 root INFO copying django/conf/locale/hi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,042 root INFO creating build/lib/django/conf/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,042 root INFO copying django/conf/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,042 root INFO copying django/conf/locale/sk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,043 root INFO creating build/lib/django/conf/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,043 root INFO copying django/conf/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,043 root INFO copying django/conf/locale/lt/LC_MESSAGES/django.po -> build/lib/django/conf/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,043 root INFO creating build/lib/django/conf/locale/de/LC_MESSAGES
2025-04-22 17:58:54,044 root INFO copying django/conf/locale/de/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/de/LC_MESSAGES
2025-04-22 17:58:54,044 root INFO copying django/conf/locale/de/LC_MESSAGES/django.po -> build/lib/django/conf/locale/de/LC_MESSAGES
2025-04-22 17:58:54,044 root INFO creating build/lib/django/conf/locale/it/LC_MESSAGES
2025-04-22 17:58:54,044 root INFO copying django/conf/locale/it/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/it/LC_MESSAGES
2025-04-22 17:58:54,044 root INFO copying django/conf/locale/it/LC_MESSAGES/django.po -> build/lib/django/conf/locale/it/LC_MESSAGES
2025-04-22 17:58:54,045 root INFO creating build/lib/django/conf/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,045 root INFO copying django/conf/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,045 root INFO copying django/conf/locale/sr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,045 root INFO creating build/lib/django/conf/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,046 root INFO copying django/conf/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,046 root INFO copying django/conf/locale/bs/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,046 root INFO creating build/lib/django/conf/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,046 root INFO copying django/conf/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,047 root INFO copying django/conf/locale/ro/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,047 root INFO creating build/lib/django/conf/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,047 root INFO copying django/conf/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,047 root INFO copying django/conf/locale/ky/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,048 root INFO creating build/lib/django/conf/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,048 root INFO copying django/conf/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,048 root INFO copying django/conf/locale/fr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,048 root INFO creating build/lib/django/conf/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,048 root INFO copying django/conf/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,049 root INFO copying django/conf/locale/ar/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,049 root INFO creating build/lib/django/conf/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,049 root INFO copying django/conf/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,049 root INFO copying django/conf/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,050 root INFO creating build/lib/django/conf/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,050 root INFO copying django/conf/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,050 root INFO copying django/conf/locale/vi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,050 root INFO creating build/lib/django/conf/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,051 root INFO copying django/conf/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,051 root INFO copying django/conf/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,051 root INFO creating build/lib/django/conf/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,051 root INFO copying django/conf/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,052 root INFO copying django/conf/locale/sv/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,052 root INFO creating build/lib/django/conf/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,052 root INFO copying django/conf/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,052 root INFO copying django/conf/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/conf/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,052 root INFO creating build/lib/django/conf/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,053 root INFO copying django/conf/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,053 root INFO copying django/conf/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,053 root INFO creating build/lib/django/conf/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,053 root INFO copying django/conf/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,054 root INFO copying django/conf/locale/ml/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,054 root INFO creating build/lib/django/conf/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,054 root INFO copying django/conf/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,054 root INFO copying django/conf/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,054 root INFO creating build/lib/django/conf/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,055 root INFO copying django/conf/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,055 root INFO copying django/conf/locale/ms/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,055 root INFO creating build/lib/django/conf/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,055 root INFO copying django/conf/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,056 root INFO copying django/conf/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/conf/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,056 root INFO creating build/lib/django/conf/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,056 root INFO copying django/conf/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,056 root INFO copying django/conf/locale/hu/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,057 root INFO creating build/lib/django/conf/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,057 root INFO copying django/conf/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,057 root INFO copying django/conf/locale/ta/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,057 root INFO creating build/lib/django/conf/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,057 root INFO copying django/conf/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,058 root INFO copying django/conf/locale/eu/LC_MESSAGES/django.po -> build/lib/django/conf/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,058 root INFO creating build/lib/django/conf/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,058 root INFO copying django/conf/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,058 root INFO copying django/conf/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,058 root INFO creating build/lib/django/conf/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,059 root INFO copying django/conf/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,059 root INFO copying django/conf/locale/tk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,059 root INFO creating build/lib/django/conf/locale/th/LC_MESSAGES
2025-04-22 17:58:54,059 root INFO copying django/conf/locale/th/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/th/LC_MESSAGES
2025-04-22 17:58:54,060 root INFO copying django/conf/locale/th/LC_MESSAGES/django.po -> build/lib/django/conf/locale/th/LC_MESSAGES
2025-04-22 17:58:54,060 root INFO creating build/lib/django/conf/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,060 root INFO copying django/conf/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,060 root INFO copying django/conf/locale/nb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,060 root INFO creating build/lib/django/conf/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,061 root INFO copying django/conf/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,061 root INFO copying django/conf/locale/mn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,061 root INFO creating build/lib/django/conf/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,061 root INFO copying django/conf/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,062 root INFO copying django/conf/locale/ka/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,062 root INFO creating build/lib/django/conf/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,062 root INFO copying django/conf/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,062 root INFO copying django/conf/locale/nl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,062 root INFO creating build/lib/django/conf/locale/te/LC_MESSAGES
2025-04-22 17:58:54,063 root INFO copying django/conf/locale/te/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/te/LC_MESSAGES
2025-04-22 17:58:54,063 root INFO copying django/conf/locale/te/LC_MESSAGES/django.po -> build/lib/django/conf/locale/te/LC_MESSAGES
2025-04-22 17:58:54,063 root INFO creating build/lib/django/conf/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,063 root INFO copying django/conf/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,064 root INFO copying django/conf/locale/pt/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,064 root INFO creating build/lib/django/conf/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,064 root INFO copying django/conf/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,064 root INFO copying django/conf/locale/bn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,065 root INFO creating build/lib/django/conf/locale/he/LC_MESSAGES
2025-04-22 17:58:54,065 root INFO copying django/conf/locale/he/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/he/LC_MESSAGES
2025-04-22 17:58:54,065 root INFO copying django/conf/locale/he/LC_MESSAGES/django.po -> build/lib/django/conf/locale/he/LC_MESSAGES
2025-04-22 17:58:54,065 root INFO creating build/lib/django/conf/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,065 root INFO copying django/conf/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,066 root INFO copying django/conf/locale/fa/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,066 root INFO creating build/lib/django/conf/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,066 root INFO copying django/conf/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,066 root INFO copying django/conf/locale/tg/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,067 root INFO creating build/lib/django/conf/locale/km/LC_MESSAGES
2025-04-22 17:58:54,067 root INFO copying django/conf/locale/km/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/km/LC_MESSAGES
2025-04-22 17:58:54,067 root INFO copying django/conf/locale/km/LC_MESSAGES/django.po -> build/lib/django/conf/locale/km/LC_MESSAGES
2025-04-22 17:58:54,067 root INFO creating build/lib/django/conf/locale/da/LC_MESSAGES
2025-04-22 17:58:54,067 root INFO copying django/conf/locale/da/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/da/LC_MESSAGES
2025-04-22 17:58:54,068 root INFO copying django/conf/locale/da/LC_MESSAGES/django.po -> build/lib/django/conf/locale/da/LC_MESSAGES
2025-04-22 17:58:54,068 root INFO copying django/contrib/auth/common-passwords.txt.gz -> build/lib/django/contrib/auth
2025-04-22 17:58:54,068 root INFO creating build/lib/django/contrib/auth/locale/af/LC_MESSAGES
2025-04-22 17:58:54,069 root INFO copying django/contrib/auth/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/af/LC_MESSAGES
2025-04-22 17:58:54,069 root INFO copying django/contrib/auth/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/af/LC_MESSAGES
2025-04-22 17:58:54,069 root INFO creating build/lib/django/contrib/auth/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,069 root INFO copying django/contrib/auth/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,069 root INFO copying django/contrib/auth/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,070 root INFO creating build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,070 root INFO copying django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,070 root INFO copying django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,070 root INFO creating build/lib/django/contrib/auth/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,071 root INFO copying django/contrib/auth/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,071 root INFO copying django/contrib/auth/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,071 root INFO creating build/lib/django/contrib/auth/locale/az/LC_MESSAGES
2025-04-22 17:58:54,071 root INFO copying django/contrib/auth/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/az/LC_MESSAGES
2025-04-22 17:58:54,071 root INFO copying django/contrib/auth/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/az/LC_MESSAGES
2025-04-22 17:58:54,072 root INFO creating build/lib/django/contrib/auth/locale/be/LC_MESSAGES
2025-04-22 17:58:54,072 root INFO copying django/contrib/auth/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/be/LC_MESSAGES
2025-04-22 17:58:54,072 root INFO copying django/contrib/auth/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/be/LC_MESSAGES
2025-04-22 17:58:54,072 root INFO creating build/lib/django/contrib/auth/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,072 root INFO copying django/contrib/auth/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,073 root INFO copying django/contrib/auth/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,073 root INFO creating build/lib/django/contrib/auth/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,073 root INFO copying django/contrib/auth/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,073 root INFO copying django/contrib/auth/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,073 root INFO creating build/lib/django/contrib/auth/locale/br/LC_MESSAGES
2025-04-22 17:58:54,074 root INFO copying django/contrib/auth/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/br/LC_MESSAGES
2025-04-22 17:58:54,074 root INFO copying django/contrib/auth/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/br/LC_MESSAGES
2025-04-22 17:58:54,074 root INFO creating build/lib/django/contrib/auth/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,074 root INFO copying django/contrib/auth/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,074 root INFO copying django/contrib/auth/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,075 root INFO creating build/lib/django/contrib/auth/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,075 root INFO copying django/contrib/auth/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,075 root INFO copying django/contrib/auth/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,075 root INFO creating build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,076 root INFO copying django/contrib/auth/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,076 root INFO copying django/contrib/auth/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,076 root INFO creating build/lib/django/contrib/auth/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,076 root INFO copying django/contrib/auth/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,077 root INFO copying django/contrib/auth/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,077 root INFO creating build/lib/django/contrib/auth/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,077 root INFO copying django/contrib/auth/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,077 root INFO copying django/contrib/auth/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,078 root INFO creating build/lib/django/contrib/auth/locale/da/LC_MESSAGES
2025-04-22 17:58:54,078 root INFO copying django/contrib/auth/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/da/LC_MESSAGES
2025-04-22 17:58:54,078 root INFO copying django/contrib/auth/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/da/LC_MESSAGES
2025-04-22 17:58:54,078 root INFO creating build/lib/django/contrib/auth/locale/de/LC_MESSAGES
2025-04-22 17:58:54,078 root INFO copying django/contrib/auth/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/de/LC_MESSAGES
2025-04-22 17:58:54,079 root INFO copying django/contrib/auth/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/de/LC_MESSAGES
2025-04-22 17:58:54,079 root INFO creating build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,079 root INFO copying django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,079 root INFO copying django/contrib/auth/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,080 root INFO creating build/lib/django/contrib/auth/locale/el/LC_MESSAGES
2025-04-22 17:58:54,080 root INFO copying django/contrib/auth/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/el/LC_MESSAGES
2025-04-22 17:58:54,080 root INFO copying django/contrib/auth/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/el/LC_MESSAGES
2025-04-22 17:58:54,080 root INFO creating build/lib/django/contrib/auth/locale/en/LC_MESSAGES
2025-04-22 17:58:54,081 root INFO copying django/contrib/auth/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/en/LC_MESSAGES
2025-04-22 17:58:54,081 root INFO copying django/contrib/auth/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/en/LC_MESSAGES
2025-04-22 17:58:54,081 root INFO creating build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,081 root INFO copying django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,082 root INFO copying django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,082 root INFO creating build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,082 root INFO copying django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,082 root INFO copying django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,082 root INFO creating build/lib/django/contrib/auth/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,083 root INFO copying django/contrib/auth/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,083 root INFO copying django/contrib/auth/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,083 root INFO creating build/lib/django/contrib/auth/locale/es/LC_MESSAGES
2025-04-22 17:58:54,083 root INFO copying django/contrib/auth/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es/LC_MESSAGES
2025-04-22 17:58:54,084 root INFO copying django/contrib/auth/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es/LC_MESSAGES
2025-04-22 17:58:54,084 root INFO creating build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,084 root INFO copying django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,084 root INFO copying django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,085 root INFO creating build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,085 root INFO copying django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,085 root INFO copying django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,085 root INFO creating build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,086 root INFO copying django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,086 root INFO copying django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,086 root INFO creating build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,086 root INFO copying django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,087 root INFO copying django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,087 root INFO creating build/lib/django/contrib/auth/locale/et/LC_MESSAGES
2025-04-22 17:58:54,087 root INFO copying django/contrib/auth/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/et/LC_MESSAGES
2025-04-22 17:58:54,087 root INFO copying django/contrib/auth/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/et/LC_MESSAGES
2025-04-22 17:58:54,087 root INFO creating build/lib/django/contrib/auth/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,088 root INFO copying django/contrib/auth/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,088 root INFO copying django/contrib/auth/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,088 root INFO creating build/lib/django/contrib/auth/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,088 root INFO copying django/contrib/auth/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,089 root INFO copying django/contrib/auth/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,089 root INFO creating build/lib/django/contrib/auth/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,089 root INFO copying django/contrib/auth/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,089 root INFO copying django/contrib/auth/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,090 root INFO creating build/lib/django/contrib/auth/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,090 root INFO copying django/contrib/auth/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,090 root INFO copying django/contrib/auth/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,090 root INFO creating build/lib/django/contrib/auth/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,090 root INFO copying django/contrib/auth/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,091 root INFO copying django/contrib/auth/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,091 root INFO creating build/lib/django/contrib/auth/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,091 root INFO copying django/contrib/auth/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,091 root INFO copying django/contrib/auth/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,092 root INFO creating build/lib/django/contrib/auth/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,092 root INFO copying django/contrib/auth/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,092 root INFO copying django/contrib/auth/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,092 root INFO creating build/lib/django/contrib/auth/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,093 root INFO copying django/contrib/auth/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,093 root INFO copying django/contrib/auth/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,093 root INFO creating build/lib/django/contrib/auth/locale/he/LC_MESSAGES
2025-04-22 17:58:54,093 root INFO copying django/contrib/auth/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/he/LC_MESSAGES
2025-04-22 17:58:54,094 root INFO copying django/contrib/auth/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/he/LC_MESSAGES
2025-04-22 17:58:54,094 root INFO creating build/lib/django/contrib/auth/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,094 root INFO copying django/contrib/auth/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,094 root INFO copying django/contrib/auth/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,095 root INFO creating build/lib/django/contrib/auth/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,095 root INFO copying django/contrib/auth/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,095 root INFO copying django/contrib/auth/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,095 root INFO creating build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,095 root INFO copying django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,096 root INFO copying django/contrib/auth/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,096 root INFO creating build/lib/django/contrib/auth/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,096 root INFO copying django/contrib/auth/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,096 root INFO copying django/contrib/auth/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,097 root INFO creating build/lib/django/contrib/auth/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,097 root INFO copying django/contrib/auth/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,097 root INFO copying django/contrib/auth/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,097 root INFO creating build/lib/django/contrib/auth/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,098 root INFO copying django/contrib/auth/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,098 root INFO copying django/contrib/auth/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,098 root INFO creating build/lib/django/contrib/auth/locale/id/LC_MESSAGES
2025-04-22 17:58:54,098 root INFO copying django/contrib/auth/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/id/LC_MESSAGES
2025-04-22 17:58:54,099 root INFO copying django/contrib/auth/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/id/LC_MESSAGES
2025-04-22 17:58:54,099 root INFO creating build/lib/django/contrib/auth/locale/io/LC_MESSAGES
2025-04-22 17:58:54,099 root INFO copying django/contrib/auth/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/io/LC_MESSAGES
2025-04-22 17:58:54,099 root INFO copying django/contrib/auth/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/io/LC_MESSAGES
2025-04-22 17:58:54,099 root INFO creating build/lib/django/contrib/auth/locale/is/LC_MESSAGES
2025-04-22 17:58:54,100 root INFO copying django/contrib/auth/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/is/LC_MESSAGES
2025-04-22 17:58:54,100 root INFO copying django/contrib/auth/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/is/LC_MESSAGES
2025-04-22 17:58:54,100 root INFO creating build/lib/django/contrib/auth/locale/it/LC_MESSAGES
2025-04-22 17:58:54,100 root INFO copying django/contrib/auth/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/it/LC_MESSAGES
2025-04-22 17:58:54,101 root INFO copying django/contrib/auth/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/it/LC_MESSAGES
2025-04-22 17:58:54,101 root INFO creating build/lib/django/contrib/auth/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,101 root INFO copying django/contrib/auth/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,101 root INFO copying django/contrib/auth/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,102 root INFO creating build/lib/django/contrib/auth/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,102 root INFO copying django/contrib/auth/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,102 root INFO copying django/contrib/auth/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,102 root INFO creating build/lib/django/contrib/auth/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,103 root INFO copying django/contrib/auth/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,103 root INFO copying django/contrib/auth/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,103 root INFO creating build/lib/django/contrib/auth/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,103 root INFO copying django/contrib/auth/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,104 root INFO copying django/contrib/auth/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,104 root INFO creating build/lib/django/contrib/auth/locale/km/LC_MESSAGES
2025-04-22 17:58:54,104 root INFO copying django/contrib/auth/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/km/LC_MESSAGES
2025-04-22 17:58:54,104 root INFO copying django/contrib/auth/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/km/LC_MESSAGES
2025-04-22 17:58:54,105 root INFO creating build/lib/django/contrib/auth/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,105 root INFO copying django/contrib/auth/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,105 root INFO copying django/contrib/auth/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,105 root INFO creating build/lib/django/contrib/auth/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,105 root INFO copying django/contrib/auth/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,106 root INFO copying django/contrib/auth/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,106 root INFO creating build/lib/django/contrib/auth/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,106 root INFO copying django/contrib/auth/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,106 root INFO copying django/contrib/auth/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,107 root INFO creating build/lib/django/contrib/auth/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,107 root INFO copying django/contrib/auth/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,107 root INFO copying django/contrib/auth/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,107 root INFO creating build/lib/django/contrib/auth/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,108 root INFO copying django/contrib/auth/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,108 root INFO copying django/contrib/auth/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,108 root INFO creating build/lib/django/contrib/auth/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,108 root INFO copying django/contrib/auth/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,109 root INFO copying django/contrib/auth/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,109 root INFO creating build/lib/django/contrib/auth/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,109 root INFO copying django/contrib/auth/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,109 root INFO copying django/contrib/auth/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,110 root INFO creating build/lib/django/contrib/auth/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,110 root INFO copying django/contrib/auth/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,110 root INFO copying django/contrib/auth/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,110 root INFO creating build/lib/django/contrib/auth/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,111 root INFO copying django/contrib/auth/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,111 root INFO copying django/contrib/auth/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,111 root INFO creating build/lib/django/contrib/auth/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,111 root INFO copying django/contrib/auth/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,111 root INFO copying django/contrib/auth/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,112 root INFO creating build/lib/django/contrib/auth/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,112 root INFO copying django/contrib/auth/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,112 root INFO copying django/contrib/auth/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,112 root INFO creating build/lib/django/contrib/auth/locale/my/LC_MESSAGES
2025-04-22 17:58:54,113 root INFO copying django/contrib/auth/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/my/LC_MESSAGES
2025-04-22 17:58:54,113 root INFO copying django/contrib/auth/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/my/LC_MESSAGES
2025-04-22 17:58:54,113 root INFO creating build/lib/django/contrib/auth/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,113 root INFO copying django/contrib/auth/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,114 root INFO copying django/contrib/auth/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,114 root INFO creating build/lib/django/contrib/auth/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,114 root INFO copying django/contrib/auth/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,114 root INFO copying django/contrib/auth/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,115 root INFO creating build/lib/django/contrib/auth/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,115 root INFO copying django/contrib/auth/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,115 root INFO copying django/contrib/auth/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,115 root INFO creating build/lib/django/contrib/auth/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,115 root INFO copying django/contrib/auth/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,116 root INFO copying django/contrib/auth/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,116 root INFO creating build/lib/django/contrib/auth/locale/os/LC_MESSAGES
2025-04-22 17:58:54,116 root INFO copying django/contrib/auth/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/os/LC_MESSAGES
2025-04-22 17:58:54,116 root INFO copying django/contrib/auth/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/os/LC_MESSAGES
2025-04-22 17:58:54,117 root INFO creating build/lib/django/contrib/auth/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,117 root INFO copying django/contrib/auth/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,117 root INFO copying django/contrib/auth/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,117 root INFO creating build/lib/django/contrib/auth/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,118 root INFO copying django/contrib/auth/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,118 root INFO copying django/contrib/auth/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,118 root INFO creating build/lib/django/contrib/auth/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,118 root INFO copying django/contrib/auth/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,119 root INFO copying django/contrib/auth/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,119 root INFO creating build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,119 root INFO copying django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,119 root INFO copying django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,120 root INFO creating build/lib/django/contrib/auth/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,120 root INFO copying django/contrib/auth/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,120 root INFO copying django/contrib/auth/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,120 root INFO creating build/lib/django/contrib/auth/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,121 root INFO copying django/contrib/auth/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,121 root INFO copying django/contrib/auth/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,121 root INFO creating build/lib/django/contrib/auth/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,121 root INFO copying django/contrib/auth/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,121 root INFO copying django/contrib/auth/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,122 root INFO creating build/lib/django/contrib/auth/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,122 root INFO copying django/contrib/auth/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,122 root INFO copying django/contrib/auth/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,122 root INFO creating build/lib/django/contrib/auth/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,123 root INFO copying django/contrib/auth/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,123 root INFO copying django/contrib/auth/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,123 root INFO creating build/lib/django/contrib/auth/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,123 root INFO copying django/contrib/auth/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,124 root INFO copying django/contrib/auth/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,124 root INFO creating build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,124 root INFO copying django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,124 root INFO copying django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,125 root INFO creating build/lib/django/contrib/auth/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,125 root INFO copying django/contrib/auth/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,125 root INFO copying django/contrib/auth/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,125 root INFO creating build/lib/django/contrib/auth/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,125 root INFO copying django/contrib/auth/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,126 root INFO copying django/contrib/auth/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,126 root INFO creating build/lib/django/contrib/auth/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,126 root INFO copying django/contrib/auth/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,126 root INFO copying django/contrib/auth/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,127 root INFO creating build/lib/django/contrib/auth/locale/te/LC_MESSAGES
2025-04-22 17:58:54,127 root INFO copying django/contrib/auth/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/te/LC_MESSAGES
2025-04-22 17:58:54,127 root INFO copying django/contrib/auth/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/te/LC_MESSAGES
2025-04-22 17:58:54,127 root INFO creating build/lib/django/contrib/auth/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,128 root INFO copying django/contrib/auth/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,128 root INFO copying django/contrib/auth/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,128 root INFO creating build/lib/django/contrib/auth/locale/th/LC_MESSAGES
2025-04-22 17:58:54,128 root INFO copying django/contrib/auth/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/th/LC_MESSAGES
2025-04-22 17:58:54,129 root INFO copying django/contrib/auth/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/th/LC_MESSAGES
2025-04-22 17:58:54,129 root INFO creating build/lib/django/contrib/auth/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,129 root INFO copying django/contrib/auth/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,129 root INFO copying django/contrib/auth/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,129 root INFO creating build/lib/django/contrib/auth/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,130 root INFO copying django/contrib/auth/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,130 root INFO copying django/contrib/auth/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,130 root INFO creating build/lib/django/contrib/auth/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,130 root INFO copying django/contrib/auth/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,131 root INFO copying django/contrib/auth/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,131 root INFO creating build/lib/django/contrib/auth/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,131 root INFO copying django/contrib/auth/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,131 root INFO copying django/contrib/auth/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,132 root INFO creating build/lib/django/contrib/auth/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,132 root INFO copying django/contrib/auth/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,132 root INFO copying django/contrib/auth/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,132 root INFO creating build/lib/django/contrib/auth/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,132 root INFO copying django/contrib/auth/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,133 root INFO copying django/contrib/auth/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,133 root INFO creating build/lib/django/contrib/auth/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,133 root INFO copying django/contrib/auth/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,134 root INFO copying django/contrib/auth/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,134 root INFO creating build/lib/django/contrib/auth/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,134 root INFO copying django/contrib/auth/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,134 root INFO copying django/contrib/auth/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,135 root INFO creating build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,135 root INFO copying django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,135 root INFO copying django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,135 root INFO creating build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,135 root INFO copying django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,136 root INFO copying django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,136 root INFO creating build/lib/django/contrib/auth/templates/auth/widgets
2025-04-22 17:58:54,136 root INFO copying django/contrib/auth/templates/auth/widgets/read_only_password_hash.html -> build/lib/django/contrib/auth/templates/auth/widgets
2025-04-22 17:58:54,136 root INFO creating build/lib/django/contrib/auth/templates/registration
2025-04-22 17:58:54,137 root INFO copying django/contrib/auth/templates/registration/password_reset_subject.txt -> build/lib/django/contrib/auth/templates/registration
2025-04-22 17:58:54,137 root INFO creating build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES
2025-04-22 17:58:54,137 root INFO copying django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES
2025-04-22 17:58:54,137 root INFO copying django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES
2025-04-22 17:58:54,137 root INFO creating build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,138 root INFO copying django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,138 root INFO copying django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,138 root INFO creating build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,138 root INFO copying django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,139 root INFO copying django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,139 root INFO creating build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,139 root INFO copying django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,139 root INFO copying django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,140 root INFO creating build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES
2025-04-22 17:58:54,140 root INFO copying django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES
2025-04-22 17:58:54,140 root INFO copying django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES
2025-04-22 17:58:54,140 root INFO creating build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES
2025-04-22 17:58:54,140 root INFO copying django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES
2025-04-22 17:58:54,141 root INFO copying django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES
2025-04-22 17:58:54,141 root INFO creating build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,141 root INFO copying django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,141 root INFO copying django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,142 root INFO creating build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,142 root INFO copying django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,142 root INFO copying django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,142 root INFO creating build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES
2025-04-22 17:58:54,142 root INFO copying django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES
2025-04-22 17:58:54,143 root INFO copying django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES
2025-04-22 17:58:54,143 root INFO creating build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,143 root INFO copying django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,143 root INFO copying django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,144 root INFO creating build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,144 root INFO copying django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,144 root INFO copying django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,144 root INFO creating build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,145 root INFO copying django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,145 root INFO copying django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,145 root INFO creating build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,145 root INFO copying django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,145 root INFO copying django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,146 root INFO creating build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,146 root INFO copying django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,146 root INFO copying django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,146 root INFO creating build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES
2025-04-22 17:58:54,147 root INFO copying django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES
2025-04-22 17:58:54,147 root INFO copying django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES
2025-04-22 17:58:54,147 root INFO creating build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES
2025-04-22 17:58:54,147 root INFO copying django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES
2025-04-22 17:58:54,148 root INFO copying django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES
2025-04-22 17:58:54,148 root INFO creating build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,148 root INFO copying django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,148 root INFO copying django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,148 root INFO creating build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES
2025-04-22 17:58:54,149 root INFO copying django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES
2025-04-22 17:58:54,149 root INFO copying django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES
2025-04-22 17:58:54,149 root INFO creating build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES
2025-04-22 17:58:54,149 root INFO copying django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES
2025-04-22 17:58:54,150 root INFO copying django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES
2025-04-22 17:58:54,150 root INFO creating build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,150 root INFO copying django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,150 root INFO copying django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,150 root INFO creating build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,151 root INFO copying django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,151 root INFO copying django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,151 root INFO creating build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,151 root INFO copying django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,152 root INFO copying django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,152 root INFO creating build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES
2025-04-22 17:58:54,152 root INFO copying django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES
2025-04-22 17:58:54,152 root INFO copying django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES
2025-04-22 17:58:54,153 root INFO creating build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,153 root INFO copying django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,153 root INFO copying django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,153 root INFO creating build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,153 root INFO copying django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,154 root INFO copying django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,154 root INFO creating build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,154 root INFO copying django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,154 root INFO copying django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,155 root INFO creating build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,155 root INFO copying django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,155 root INFO copying django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,155 root INFO creating build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES
2025-04-22 17:58:54,155 root INFO copying django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES
2025-04-22 17:58:54,156 root INFO copying django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES
2025-04-22 17:58:54,156 root INFO creating build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,156 root INFO copying django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,156 root INFO copying django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,157 root INFO creating build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,157 root INFO copying django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,157 root INFO copying django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,157 root INFO creating build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,157 root INFO copying django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,158 root INFO copying django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,158 root INFO creating build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,158 root INFO copying django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,158 root INFO copying django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,159 root INFO creating build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,159 root INFO copying django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,159 root INFO copying django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,159 root INFO creating build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,160 root INFO copying django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,160 root INFO copying django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,160 root INFO creating build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,160 root INFO copying django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,161 root INFO copying django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,161 root INFO creating build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,161 root INFO copying django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,161 root INFO copying django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,161 root INFO creating build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES
2025-04-22 17:58:54,162 root INFO copying django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES
2025-04-22 17:58:54,162 root INFO copying django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES
2025-04-22 17:58:54,162 root INFO creating build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,162 root INFO copying django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,163 root INFO copying django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,163 root INFO creating build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,163 root INFO copying django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,163 root INFO copying django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,163 root INFO creating build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,164 root INFO copying django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,164 root INFO copying django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,164 root INFO creating build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,164 root INFO copying django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,165 root INFO copying django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,165 root INFO creating build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,165 root INFO copying django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,165 root INFO copying django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,166 root INFO creating build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,166 root INFO copying django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,166 root INFO copying django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,166 root INFO creating build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES
2025-04-22 17:58:54,166 root INFO copying django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES
2025-04-22 17:58:54,167 root INFO copying django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES
2025-04-22 17:58:54,167 root INFO creating build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES
2025-04-22 17:58:54,167 root INFO copying django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES
2025-04-22 17:58:54,167 root INFO copying django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES
2025-04-22 17:58:54,168 root INFO creating build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES
2025-04-22 17:58:54,168 root INFO copying django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES
2025-04-22 17:58:54,168 root INFO copying django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES
2025-04-22 17:58:54,168 root INFO creating build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES
2025-04-22 17:58:54,168 root INFO copying django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES
2025-04-22 17:58:54,169 root INFO copying django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES
2025-04-22 17:58:54,169 root INFO creating build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,169 root INFO copying django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,169 root INFO copying django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,170 root INFO creating build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,170 root INFO copying django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,170 root INFO copying django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,170 root INFO creating build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,171 root INFO copying django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,171 root INFO copying django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,171 root INFO creating build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES
2025-04-22 17:58:54,171 root INFO copying django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES
2025-04-22 17:58:54,171 root INFO copying django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES
2025-04-22 17:58:54,172 root INFO creating build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,172 root INFO copying django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,172 root INFO copying django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,172 root INFO creating build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,173 root INFO copying django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,173 root INFO copying django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,173 root INFO creating build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,173 root INFO copying django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,174 root INFO copying django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,174 root INFO creating build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,174 root INFO copying django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,174 root INFO copying django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,174 root INFO creating build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,175 root INFO copying django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,175 root INFO copying django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,175 root INFO creating build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,175 root INFO copying django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,176 root INFO copying django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,176 root INFO creating build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,176 root INFO copying django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,176 root INFO copying django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,176 root INFO creating build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,177 root INFO copying django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,177 root INFO copying django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,177 root INFO creating build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,177 root INFO copying django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,178 root INFO copying django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,178 root INFO creating build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,178 root INFO copying django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,178 root INFO copying django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,178 root INFO creating build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,179 root INFO copying django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,179 root INFO copying django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,179 root INFO creating build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES
2025-04-22 17:58:54,179 root INFO copying django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES
2025-04-22 17:58:54,180 root INFO copying django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES
2025-04-22 17:58:54,180 root INFO creating build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,180 root INFO copying django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,180 root INFO copying django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,181 root INFO creating build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,181 root INFO copying django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,181 root INFO copying django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,181 root INFO creating build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,181 root INFO copying django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,182 root INFO copying django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,182 root INFO creating build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,182 root INFO copying django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,182 root INFO copying django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,183 root INFO creating build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES
2025-04-22 17:58:54,183 root INFO copying django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES
2025-04-22 17:58:54,183 root INFO copying django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES
2025-04-22 17:58:54,183 root INFO creating build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,183 root INFO copying django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,184 root INFO copying django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,184 root INFO creating build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,184 root INFO copying django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,184 root INFO copying django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,185 root INFO creating build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,185 root INFO copying django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,185 root INFO copying django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,185 root INFO creating build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,186 root INFO copying django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,186 root INFO copying django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,186 root INFO creating build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,186 root INFO copying django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,187 root INFO copying django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,187 root INFO creating build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,187 root INFO copying django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,187 root INFO copying django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,188 root INFO creating build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,188 root INFO copying django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,188 root INFO copying django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,188 root INFO creating build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,188 root INFO copying django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,189 root INFO copying django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,189 root INFO creating build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,189 root INFO copying django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,189 root INFO copying django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,190 root INFO creating build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,190 root INFO copying django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,190 root INFO copying django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,190 root INFO creating build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,191 root INFO copying django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,191 root INFO copying django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,191 root INFO creating build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,191 root INFO copying django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,192 root INFO copying django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,192 root INFO creating build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,192 root INFO copying django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,192 root INFO copying django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,192 root INFO creating build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,193 root INFO copying django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,193 root INFO copying django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,193 root INFO creating build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES
2025-04-22 17:58:54,193 root INFO copying django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES
2025-04-22 17:58:54,194 root INFO copying django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES
2025-04-22 17:58:54,194 root INFO creating build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,194 root INFO copying django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,194 root INFO copying django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,194 root INFO creating build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES
2025-04-22 17:58:54,195 root INFO copying django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES
2025-04-22 17:58:54,195 root INFO copying django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES
2025-04-22 17:58:54,195 root INFO creating build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,195 root INFO copying django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,196 root INFO copying django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,196 root INFO creating build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,196 root INFO copying django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,196 root INFO copying django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,197 root INFO creating build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,197 root INFO copying django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,197 root INFO copying django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,197 root INFO creating build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,197 root INFO copying django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,198 root INFO copying django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,198 root INFO creating build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,198 root INFO copying django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,198 root INFO copying django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,199 root INFO creating build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,199 root INFO copying django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,199 root INFO copying django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,199 root INFO creating build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,199 root INFO copying django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,200 root INFO copying django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,200 root INFO creating build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,200 root INFO copying django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,200 root INFO copying django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,201 root INFO creating build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,201 root INFO copying django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,201 root INFO copying django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,201 root INFO creating build/lib/django/contrib/redirects/locale/af/LC_MESSAGES
2025-04-22 17:58:54,201 root INFO copying django/contrib/redirects/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/af/LC_MESSAGES
2025-04-22 17:58:54,202 root INFO copying django/contrib/redirects/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/af/LC_MESSAGES
2025-04-22 17:58:54,202 root INFO creating build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,202 root INFO copying django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,202 root INFO copying django/contrib/redirects/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,203 root INFO creating build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,203 root INFO copying django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,203 root INFO copying django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,203 root INFO creating build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,204 root INFO copying django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,204 root INFO copying django/contrib/redirects/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,204 root INFO creating build/lib/django/contrib/redirects/locale/az/LC_MESSAGES
2025-04-22 17:58:54,204 root INFO copying django/contrib/redirects/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/az/LC_MESSAGES
2025-04-22 17:58:54,204 root INFO copying django/contrib/redirects/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/az/LC_MESSAGES
2025-04-22 17:58:54,205 root INFO creating build/lib/django/contrib/redirects/locale/be/LC_MESSAGES
2025-04-22 17:58:54,205 root INFO copying django/contrib/redirects/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/be/LC_MESSAGES
2025-04-22 17:58:54,205 root INFO copying django/contrib/redirects/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/be/LC_MESSAGES
2025-04-22 17:58:54,205 root INFO creating build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,206 root INFO copying django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,206 root INFO copying django/contrib/redirects/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,206 root INFO creating build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,206 root INFO copying django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,207 root INFO copying django/contrib/redirects/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,207 root INFO creating build/lib/django/contrib/redirects/locale/br/LC_MESSAGES
2025-04-22 17:58:54,207 root INFO copying django/contrib/redirects/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/br/LC_MESSAGES
2025-04-22 17:58:54,207 root INFO copying django/contrib/redirects/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/br/LC_MESSAGES
2025-04-22 17:58:54,207 root INFO creating build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,208 root INFO copying django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,208 root INFO copying django/contrib/redirects/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,208 root INFO creating build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,208 root INFO copying django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,209 root INFO copying django/contrib/redirects/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,209 root INFO creating build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,209 root INFO copying django/contrib/redirects/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,209 root INFO copying django/contrib/redirects/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,210 root INFO creating build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,210 root INFO copying django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,210 root INFO copying django/contrib/redirects/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,210 root INFO creating build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,210 root INFO copying django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,211 root INFO copying django/contrib/redirects/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,211 root INFO creating build/lib/django/contrib/redirects/locale/da/LC_MESSAGES
2025-04-22 17:58:54,211 root INFO copying django/contrib/redirects/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/da/LC_MESSAGES
2025-04-22 17:58:54,211 root INFO copying django/contrib/redirects/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/da/LC_MESSAGES
2025-04-22 17:58:54,212 root INFO creating build/lib/django/contrib/redirects/locale/de/LC_MESSAGES
2025-04-22 17:58:54,212 root INFO copying django/contrib/redirects/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/de/LC_MESSAGES
2025-04-22 17:58:54,212 root INFO copying django/contrib/redirects/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/de/LC_MESSAGES
2025-04-22 17:58:54,212 root INFO creating build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,212 root INFO copying django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,213 root INFO copying django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,213 root INFO creating build/lib/django/contrib/redirects/locale/el/LC_MESSAGES
2025-04-22 17:58:54,213 root INFO copying django/contrib/redirects/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/el/LC_MESSAGES
2025-04-22 17:58:54,213 root INFO copying django/contrib/redirects/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/el/LC_MESSAGES
2025-04-22 17:58:54,214 root INFO creating build/lib/django/contrib/redirects/locale/en/LC_MESSAGES
2025-04-22 17:58:54,214 root INFO copying django/contrib/redirects/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/en/LC_MESSAGES
2025-04-22 17:58:54,214 root INFO copying django/contrib/redirects/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/en/LC_MESSAGES
2025-04-22 17:58:54,214 root INFO creating build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,214 root INFO copying django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,215 root INFO copying django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,215 root INFO creating build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,215 root INFO copying django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,215 root INFO copying django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,216 root INFO creating build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,216 root INFO copying django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,216 root INFO copying django/contrib/redirects/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,216 root INFO creating build/lib/django/contrib/redirects/locale/es/LC_MESSAGES
2025-04-22 17:58:54,216 root INFO copying django/contrib/redirects/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es/LC_MESSAGES
2025-04-22 17:58:54,217 root INFO copying django/contrib/redirects/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es/LC_MESSAGES
2025-04-22 17:58:54,217 root INFO creating build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,217 root INFO copying django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,217 root INFO copying django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,218 root INFO creating build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,218 root INFO copying django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,218 root INFO copying django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,218 root INFO creating build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,219 root INFO copying django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,219 root INFO copying django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,219 root INFO creating build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,219 root INFO copying django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,220 root INFO copying django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,220 root INFO creating build/lib/django/contrib/redirects/locale/et/LC_MESSAGES
2025-04-22 17:58:54,220 root INFO copying django/contrib/redirects/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/et/LC_MESSAGES
2025-04-22 17:58:54,220 root INFO copying django/contrib/redirects/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/et/LC_MESSAGES
2025-04-22 17:58:54,221 root INFO creating build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,221 root INFO copying django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,221 root INFO copying django/contrib/redirects/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,221 root INFO creating build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,221 root INFO copying django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,222 root INFO copying django/contrib/redirects/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,222 root INFO creating build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,222 root INFO copying django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,222 root INFO copying django/contrib/redirects/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,223 root INFO creating build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,223 root INFO copying django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,223 root INFO copying django/contrib/redirects/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,223 root INFO creating build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,223 root INFO copying django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,224 root INFO copying django/contrib/redirects/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,224 root INFO creating build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,224 root INFO copying django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,224 root INFO copying django/contrib/redirects/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,225 root INFO creating build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,225 root INFO copying django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,225 root INFO copying django/contrib/redirects/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,225 root INFO creating build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,225 root INFO copying django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,226 root INFO copying django/contrib/redirects/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,226 root INFO creating build/lib/django/contrib/redirects/locale/he/LC_MESSAGES
2025-04-22 17:58:54,226 root INFO copying django/contrib/redirects/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/he/LC_MESSAGES
2025-04-22 17:58:54,226 root INFO copying django/contrib/redirects/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/he/LC_MESSAGES
2025-04-22 17:58:54,227 root INFO creating build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,227 root INFO copying django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,227 root INFO copying django/contrib/redirects/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,227 root INFO creating build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,228 root INFO copying django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,228 root INFO copying django/contrib/redirects/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,228 root INFO creating build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,228 root INFO copying django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,228 root INFO copying django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,229 root INFO creating build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,229 root INFO copying django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,229 root INFO copying django/contrib/redirects/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,230 root INFO creating build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,230 root INFO copying django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,230 root INFO copying django/contrib/redirects/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,230 root INFO creating build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,230 root INFO copying django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,231 root INFO copying django/contrib/redirects/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,231 root INFO creating build/lib/django/contrib/redirects/locale/id/LC_MESSAGES
2025-04-22 17:58:54,231 root INFO copying django/contrib/redirects/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/id/LC_MESSAGES
2025-04-22 17:58:54,231 root INFO copying django/contrib/redirects/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/id/LC_MESSAGES
2025-04-22 17:58:54,232 root INFO creating build/lib/django/contrib/redirects/locale/io/LC_MESSAGES
2025-04-22 17:58:54,232 root INFO copying django/contrib/redirects/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/io/LC_MESSAGES
2025-04-22 17:58:54,232 root INFO copying django/contrib/redirects/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/io/LC_MESSAGES
2025-04-22 17:58:54,232 root INFO creating build/lib/django/contrib/redirects/locale/is/LC_MESSAGES
2025-04-22 17:58:54,232 root INFO copying django/contrib/redirects/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/is/LC_MESSAGES
2025-04-22 17:58:54,233 root INFO copying django/contrib/redirects/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/is/LC_MESSAGES
2025-04-22 17:58:54,233 root INFO creating build/lib/django/contrib/redirects/locale/it/LC_MESSAGES
2025-04-22 17:58:54,233 root INFO copying django/contrib/redirects/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/it/LC_MESSAGES
2025-04-22 17:58:54,233 root INFO copying django/contrib/redirects/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/it/LC_MESSAGES
2025-04-22 17:58:54,234 root INFO creating build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,234 root INFO copying django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,234 root INFO copying django/contrib/redirects/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,234 root INFO creating build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,234 root INFO copying django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,235 root INFO copying django/contrib/redirects/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,235 root INFO creating build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,235 root INFO copying django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,235 root INFO copying django/contrib/redirects/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,236 root INFO creating build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,236 root INFO copying django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,236 root INFO copying django/contrib/redirects/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,236 root INFO creating build/lib/django/contrib/redirects/locale/km/LC_MESSAGES
2025-04-22 17:58:54,237 root INFO copying django/contrib/redirects/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/km/LC_MESSAGES
2025-04-22 17:58:54,237 root INFO copying django/contrib/redirects/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/km/LC_MESSAGES
2025-04-22 17:58:54,237 root INFO creating build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,237 root INFO copying django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,237 root INFO copying django/contrib/redirects/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,238 root INFO creating build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,238 root INFO copying django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,238 root INFO copying django/contrib/redirects/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,238 root INFO creating build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,239 root INFO copying django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,239 root INFO copying django/contrib/redirects/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,239 root INFO creating build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,239 root INFO copying django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,240 root INFO copying django/contrib/redirects/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,240 root INFO creating build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,240 root INFO copying django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,240 root INFO copying django/contrib/redirects/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,240 root INFO creating build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,241 root INFO copying django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,241 root INFO copying django/contrib/redirects/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,241 root INFO creating build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,241 root INFO copying django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,242 root INFO copying django/contrib/redirects/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,242 root INFO creating build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,242 root INFO copying django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,242 root INFO copying django/contrib/redirects/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,243 root INFO creating build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,243 root INFO copying django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,243 root INFO copying django/contrib/redirects/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,243 root INFO creating build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,243 root INFO copying django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,244 root INFO copying django/contrib/redirects/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,244 root INFO creating build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,244 root INFO copying django/contrib/redirects/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,244 root INFO copying django/contrib/redirects/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,245 root INFO creating build/lib/django/contrib/redirects/locale/my/LC_MESSAGES
2025-04-22 17:58:54,245 root INFO copying django/contrib/redirects/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/my/LC_MESSAGES
2025-04-22 17:58:54,245 root INFO copying django/contrib/redirects/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/my/LC_MESSAGES
2025-04-22 17:58:54,245 root INFO creating build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,245 root INFO copying django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,246 root INFO copying django/contrib/redirects/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,246 root INFO creating build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,246 root INFO copying django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,246 root INFO copying django/contrib/redirects/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,247 root INFO creating build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,247 root INFO copying django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,247 root INFO copying django/contrib/redirects/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,247 root INFO creating build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,247 root INFO copying django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,248 root INFO copying django/contrib/redirects/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,248 root INFO creating build/lib/django/contrib/redirects/locale/os/LC_MESSAGES
2025-04-22 17:58:54,248 root INFO copying django/contrib/redirects/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/os/LC_MESSAGES
2025-04-22 17:58:54,248 root INFO copying django/contrib/redirects/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/os/LC_MESSAGES
2025-04-22 17:58:54,249 root INFO creating build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,249 root INFO copying django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,249 root INFO copying django/contrib/redirects/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,249 root INFO creating build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,250 root INFO copying django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,250 root INFO copying django/contrib/redirects/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,250 root INFO creating build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,250 root INFO copying django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,251 root INFO copying django/contrib/redirects/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,251 root INFO creating build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,251 root INFO copying django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,251 root INFO copying django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,251 root INFO creating build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,252 root INFO copying django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,252 root INFO copying django/contrib/redirects/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,252 root INFO creating build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,252 root INFO copying django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,253 root INFO copying django/contrib/redirects/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,253 root INFO creating build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,253 root INFO copying django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,253 root INFO copying django/contrib/redirects/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,254 root INFO creating build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,254 root INFO copying django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,254 root INFO copying django/contrib/redirects/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,254 root INFO creating build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,255 root INFO copying django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,255 root INFO copying django/contrib/redirects/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,255 root INFO creating build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,255 root INFO copying django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,255 root INFO copying django/contrib/redirects/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,256 root INFO creating build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,256 root INFO copying django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,256 root INFO copying django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,256 root INFO creating build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,257 root INFO copying django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,257 root INFO copying django/contrib/redirects/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,257 root INFO creating build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,257 root INFO copying django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,258 root INFO copying django/contrib/redirects/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,258 root INFO creating build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,258 root INFO copying django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,258 root INFO copying django/contrib/redirects/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,258 root INFO creating build/lib/django/contrib/redirects/locale/te/LC_MESSAGES
2025-04-22 17:58:54,259 root INFO copying django/contrib/redirects/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/te/LC_MESSAGES
2025-04-22 17:58:54,259 root INFO copying django/contrib/redirects/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/te/LC_MESSAGES
2025-04-22 17:58:54,259 root INFO creating build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,259 root INFO copying django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,260 root INFO copying django/contrib/redirects/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,260 root INFO creating build/lib/django/contrib/redirects/locale/th/LC_MESSAGES
2025-04-22 17:58:54,260 root INFO copying django/contrib/redirects/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/th/LC_MESSAGES
2025-04-22 17:58:54,260 root INFO copying django/contrib/redirects/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/th/LC_MESSAGES
2025-04-22 17:58:54,261 root INFO creating build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,261 root INFO copying django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,261 root INFO copying django/contrib/redirects/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,261 root INFO creating build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,261 root INFO copying django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,262 root INFO copying django/contrib/redirects/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,262 root INFO creating build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,262 root INFO copying django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,262 root INFO copying django/contrib/redirects/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,263 root INFO creating build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,263 root INFO copying django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,263 root INFO copying django/contrib/redirects/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,263 root INFO creating build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,263 root INFO copying django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,264 root INFO copying django/contrib/redirects/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,264 root INFO creating build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,264 root INFO copying django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,264 root INFO copying django/contrib/redirects/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,265 root INFO creating build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,265 root INFO copying django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,265 root INFO copying django/contrib/redirects/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,265 root INFO creating build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,266 root INFO copying django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,266 root INFO copying django/contrib/redirects/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,266 root INFO creating build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,266 root INFO copying django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,266 root INFO copying django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,267 root INFO creating build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,267 root INFO copying django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,267 root INFO copying django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,267 root INFO creating build/lib/django/contrib/sites/locale/af/LC_MESSAGES
2025-04-22 17:58:54,268 root INFO copying django/contrib/sites/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/af/LC_MESSAGES
2025-04-22 17:58:54,268 root INFO copying django/contrib/sites/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/af/LC_MESSAGES
2025-04-22 17:58:54,268 root INFO creating build/lib/django/contrib/sites/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,268 root INFO copying django/contrib/sites/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,269 root INFO copying django/contrib/sites/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,269 root INFO creating build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,269 root INFO copying django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,269 root INFO copying django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,269 root INFO creating build/lib/django/contrib/sites/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,270 root INFO copying django/contrib/sites/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,270 root INFO copying django/contrib/sites/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,270 root INFO creating build/lib/django/contrib/sites/locale/az/LC_MESSAGES
2025-04-22 17:58:54,270 root INFO copying django/contrib/sites/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/az/LC_MESSAGES
2025-04-22 17:58:54,271 root INFO copying django/contrib/sites/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/az/LC_MESSAGES
2025-04-22 17:58:54,271 root INFO creating build/lib/django/contrib/sites/locale/be/LC_MESSAGES
2025-04-22 17:58:54,271 root INFO copying django/contrib/sites/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/be/LC_MESSAGES
2025-04-22 17:58:54,271 root INFO copying django/contrib/sites/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/be/LC_MESSAGES
2025-04-22 17:58:54,271 root INFO creating build/lib/django/contrib/sites/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,272 root INFO copying django/contrib/sites/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,272 root INFO copying django/contrib/sites/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,272 root INFO creating build/lib/django/contrib/sites/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,272 root INFO copying django/contrib/sites/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,273 root INFO copying django/contrib/sites/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,273 root INFO creating build/lib/django/contrib/sites/locale/br/LC_MESSAGES
2025-04-22 17:58:54,273 root INFO copying django/contrib/sites/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/br/LC_MESSAGES
2025-04-22 17:58:54,273 root INFO copying django/contrib/sites/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/br/LC_MESSAGES
2025-04-22 17:58:54,274 root INFO creating build/lib/django/contrib/sites/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,274 root INFO copying django/contrib/sites/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,274 root INFO copying django/contrib/sites/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,274 root INFO creating build/lib/django/contrib/sites/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,274 root INFO copying django/contrib/sites/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,275 root INFO copying django/contrib/sites/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,275 root INFO creating build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,275 root INFO copying django/contrib/sites/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,275 root INFO copying django/contrib/sites/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,276 root INFO creating build/lib/django/contrib/sites/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,276 root INFO copying django/contrib/sites/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,276 root INFO copying django/contrib/sites/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,276 root INFO creating build/lib/django/contrib/sites/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,276 root INFO copying django/contrib/sites/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,277 root INFO copying django/contrib/sites/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,277 root INFO creating build/lib/django/contrib/sites/locale/da/LC_MESSAGES
2025-04-22 17:58:54,277 root INFO copying django/contrib/sites/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/da/LC_MESSAGES
2025-04-22 17:58:54,277 root INFO copying django/contrib/sites/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/da/LC_MESSAGES
2025-04-22 17:58:54,278 root INFO creating build/lib/django/contrib/sites/locale/de/LC_MESSAGES
2025-04-22 17:58:54,278 root INFO copying django/contrib/sites/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/de/LC_MESSAGES
2025-04-22 17:58:54,278 root INFO copying django/contrib/sites/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/de/LC_MESSAGES
2025-04-22 17:58:54,278 root INFO creating build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,278 root INFO copying django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,279 root INFO copying django/contrib/sites/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,279 root INFO creating build/lib/django/contrib/sites/locale/el/LC_MESSAGES
2025-04-22 17:58:54,279 root INFO copying django/contrib/sites/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/el/LC_MESSAGES
2025-04-22 17:58:54,279 root INFO copying django/contrib/sites/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/el/LC_MESSAGES
2025-04-22 17:58:54,280 root INFO creating build/lib/django/contrib/sites/locale/en/LC_MESSAGES
2025-04-22 17:58:54,280 root INFO copying django/contrib/sites/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/en/LC_MESSAGES
2025-04-22 17:58:54,280 root INFO copying django/contrib/sites/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/en/LC_MESSAGES
2025-04-22 17:58:54,280 root INFO creating build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,280 root INFO copying django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,281 root INFO copying django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,281 root INFO creating build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,281 root INFO copying django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,281 root INFO copying django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,282 root INFO creating build/lib/django/contrib/sites/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,282 root INFO copying django/contrib/sites/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,282 root INFO copying django/contrib/sites/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,282 root INFO creating build/lib/django/contrib/sites/locale/es/LC_MESSAGES
2025-04-22 17:58:54,282 root INFO copying django/contrib/sites/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es/LC_MESSAGES
2025-04-22 17:58:54,283 root INFO copying django/contrib/sites/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es/LC_MESSAGES
2025-04-22 17:58:54,283 root INFO creating build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,283 root INFO copying django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,283 root INFO copying django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,284 root INFO creating build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,284 root INFO copying django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,284 root INFO copying django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,284 root INFO creating build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,285 root INFO copying django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,285 root INFO copying django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,285 root INFO creating build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,285 root INFO copying django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,285 root INFO copying django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,286 root INFO creating build/lib/django/contrib/sites/locale/et/LC_MESSAGES
2025-04-22 17:58:54,286 root INFO copying django/contrib/sites/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/et/LC_MESSAGES
2025-04-22 17:58:54,286 root INFO copying django/contrib/sites/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/et/LC_MESSAGES
2025-04-22 17:58:54,286 root INFO creating build/lib/django/contrib/sites/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,287 root INFO copying django/contrib/sites/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,287 root INFO copying django/contrib/sites/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,287 root INFO creating build/lib/django/contrib/sites/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,287 root INFO copying django/contrib/sites/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,287 root INFO copying django/contrib/sites/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,288 root INFO creating build/lib/django/contrib/sites/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,288 root INFO copying django/contrib/sites/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,288 root INFO copying django/contrib/sites/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,288 root INFO creating build/lib/django/contrib/sites/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,289 root INFO copying django/contrib/sites/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,289 root INFO copying django/contrib/sites/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,289 root INFO creating build/lib/django/contrib/sites/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,289 root INFO copying django/contrib/sites/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,290 root INFO copying django/contrib/sites/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,290 root INFO creating build/lib/django/contrib/sites/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,290 root INFO copying django/contrib/sites/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,290 root INFO copying django/contrib/sites/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,291 root INFO creating build/lib/django/contrib/sites/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,291 root INFO copying django/contrib/sites/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,291 root INFO copying django/contrib/sites/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,291 root INFO creating build/lib/django/contrib/sites/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,291 root INFO copying django/contrib/sites/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,292 root INFO copying django/contrib/sites/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,292 root INFO creating build/lib/django/contrib/sites/locale/he/LC_MESSAGES
2025-04-22 17:58:54,292 root INFO copying django/contrib/sites/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/he/LC_MESSAGES
2025-04-22 17:58:54,292 root INFO copying django/contrib/sites/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/he/LC_MESSAGES
2025-04-22 17:58:54,293 root INFO creating build/lib/django/contrib/sites/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,293 root INFO copying django/contrib/sites/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,293 root INFO copying django/contrib/sites/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,293 root INFO creating build/lib/django/contrib/sites/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,293 root INFO copying django/contrib/sites/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,294 root INFO copying django/contrib/sites/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,294 root INFO creating build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,294 root INFO copying django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,294 root INFO copying django/contrib/sites/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,295 root INFO creating build/lib/django/contrib/sites/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,295 root INFO copying django/contrib/sites/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,295 root INFO copying django/contrib/sites/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,295 root INFO creating build/lib/django/contrib/sites/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,295 root INFO copying django/contrib/sites/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,296 root INFO copying django/contrib/sites/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,296 root INFO creating build/lib/django/contrib/sites/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,296 root INFO copying django/contrib/sites/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,296 root INFO copying django/contrib/sites/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,297 root INFO creating build/lib/django/contrib/sites/locale/id/LC_MESSAGES
2025-04-22 17:58:54,297 root INFO copying django/contrib/sites/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/id/LC_MESSAGES
2025-04-22 17:58:54,297 root INFO copying django/contrib/sites/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/id/LC_MESSAGES
2025-04-22 17:58:54,297 root INFO creating build/lib/django/contrib/sites/locale/io/LC_MESSAGES
2025-04-22 17:58:54,297 root INFO copying django/contrib/sites/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/io/LC_MESSAGES
2025-04-22 17:58:54,298 root INFO copying django/contrib/sites/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/io/LC_MESSAGES
2025-04-22 17:58:54,298 root INFO creating build/lib/django/contrib/sites/locale/is/LC_MESSAGES
2025-04-22 17:58:54,298 root INFO copying django/contrib/sites/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/is/LC_MESSAGES
2025-04-22 17:58:54,298 root INFO copying django/contrib/sites/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/is/LC_MESSAGES
2025-04-22 17:58:54,299 root INFO creating build/lib/django/contrib/sites/locale/it/LC_MESSAGES
2025-04-22 17:58:54,299 root INFO copying django/contrib/sites/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/it/LC_MESSAGES
2025-04-22 17:58:54,299 root INFO copying django/contrib/sites/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/it/LC_MESSAGES
2025-04-22 17:58:54,299 root INFO creating build/lib/django/contrib/sites/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,300 root INFO copying django/contrib/sites/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,300 root INFO copying django/contrib/sites/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,300 root INFO creating build/lib/django/contrib/sites/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,300 root INFO copying django/contrib/sites/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,300 root INFO copying django/contrib/sites/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,301 root INFO creating build/lib/django/contrib/sites/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,301 root INFO copying django/contrib/sites/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,301 root INFO copying django/contrib/sites/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,301 root INFO creating build/lib/django/contrib/sites/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,302 root INFO copying django/contrib/sites/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,302 root INFO copying django/contrib/sites/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,302 root INFO creating build/lib/django/contrib/sites/locale/km/LC_MESSAGES
2025-04-22 17:58:54,302 root INFO copying django/contrib/sites/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/km/LC_MESSAGES
2025-04-22 17:58:54,302 root INFO copying django/contrib/sites/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/km/LC_MESSAGES
2025-04-22 17:58:54,303 root INFO creating build/lib/django/contrib/sites/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,303 root INFO copying django/contrib/sites/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,303 root INFO copying django/contrib/sites/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,303 root INFO creating build/lib/django/contrib/sites/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,304 root INFO copying django/contrib/sites/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,304 root INFO copying django/contrib/sites/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,304 root INFO creating build/lib/django/contrib/sites/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,304 root INFO copying django/contrib/sites/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,305 root INFO copying django/contrib/sites/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,305 root INFO creating build/lib/django/contrib/sites/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,305 root INFO copying django/contrib/sites/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,305 root INFO copying django/contrib/sites/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,305 root INFO creating build/lib/django/contrib/sites/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,306 root INFO copying django/contrib/sites/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,306 root INFO copying django/contrib/sites/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,306 root INFO creating build/lib/django/contrib/sites/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,306 root INFO copying django/contrib/sites/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,307 root INFO copying django/contrib/sites/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,307 root INFO creating build/lib/django/contrib/sites/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,307 root INFO copying django/contrib/sites/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,307 root INFO copying django/contrib/sites/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,307 root INFO creating build/lib/django/contrib/sites/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,308 root INFO copying django/contrib/sites/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,308 root INFO copying django/contrib/sites/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,308 root INFO creating build/lib/django/contrib/sites/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,308 root INFO copying django/contrib/sites/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,309 root INFO copying django/contrib/sites/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,309 root INFO creating build/lib/django/contrib/sites/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,309 root INFO copying django/contrib/sites/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,309 root INFO copying django/contrib/sites/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,310 root INFO creating build/lib/django/contrib/sites/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,310 root INFO copying django/contrib/sites/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,310 root INFO copying django/contrib/sites/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,310 root INFO creating build/lib/django/contrib/sites/locale/my/LC_MESSAGES
2025-04-22 17:58:54,310 root INFO copying django/contrib/sites/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/my/LC_MESSAGES
2025-04-22 17:58:54,311 root INFO copying django/contrib/sites/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/my/LC_MESSAGES
2025-04-22 17:58:54,311 root INFO creating build/lib/django/contrib/sites/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,311 root INFO copying django/contrib/sites/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,311 root INFO copying django/contrib/sites/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,312 root INFO creating build/lib/django/contrib/sites/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,312 root INFO copying django/contrib/sites/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,312 root INFO copying django/contrib/sites/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,312 root INFO creating build/lib/django/contrib/sites/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,312 root INFO copying django/contrib/sites/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,313 root INFO copying django/contrib/sites/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,313 root INFO creating build/lib/django/contrib/sites/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,313 root INFO copying django/contrib/sites/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,313 root INFO copying django/contrib/sites/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,314 root INFO creating build/lib/django/contrib/sites/locale/os/LC_MESSAGES
2025-04-22 17:58:54,314 root INFO copying django/contrib/sites/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/os/LC_MESSAGES
2025-04-22 17:58:54,314 root INFO copying django/contrib/sites/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/os/LC_MESSAGES
2025-04-22 17:58:54,314 root INFO creating build/lib/django/contrib/sites/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,314 root INFO copying django/contrib/sites/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,315 root INFO copying django/contrib/sites/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,315 root INFO creating build/lib/django/contrib/sites/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,315 root INFO copying django/contrib/sites/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,315 root INFO copying django/contrib/sites/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,316 root INFO creating build/lib/django/contrib/sites/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,316 root INFO copying django/contrib/sites/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,316 root INFO copying django/contrib/sites/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,316 root INFO creating build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,317 root INFO copying django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,317 root INFO copying django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,317 root INFO creating build/lib/django/contrib/sites/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,317 root INFO copying django/contrib/sites/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,317 root INFO copying django/contrib/sites/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,318 root INFO creating build/lib/django/contrib/sites/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,318 root INFO copying django/contrib/sites/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,318 root INFO copying django/contrib/sites/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,318 root INFO creating build/lib/django/contrib/sites/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,319 root INFO copying django/contrib/sites/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,319 root INFO copying django/contrib/sites/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,319 root INFO creating build/lib/django/contrib/sites/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,319 root INFO copying django/contrib/sites/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,320 root INFO copying django/contrib/sites/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,320 root INFO creating build/lib/django/contrib/sites/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,320 root INFO copying django/contrib/sites/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,320 root INFO copying django/contrib/sites/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,321 root INFO creating build/lib/django/contrib/sites/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,321 root INFO copying django/contrib/sites/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,321 root INFO copying django/contrib/sites/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,321 root INFO creating build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,321 root INFO copying django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,322 root INFO copying django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,322 root INFO creating build/lib/django/contrib/sites/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,322 root INFO copying django/contrib/sites/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,322 root INFO copying django/contrib/sites/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,323 root INFO creating build/lib/django/contrib/sites/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,323 root INFO copying django/contrib/sites/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,323 root INFO copying django/contrib/sites/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,323 root INFO creating build/lib/django/contrib/sites/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,323 root INFO copying django/contrib/sites/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,324 root INFO copying django/contrib/sites/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,324 root INFO creating build/lib/django/contrib/sites/locale/te/LC_MESSAGES
2025-04-22 17:58:54,324 root INFO copying django/contrib/sites/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/te/LC_MESSAGES
2025-04-22 17:58:54,324 root INFO copying django/contrib/sites/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/te/LC_MESSAGES
2025-04-22 17:58:54,325 root INFO creating build/lib/django/contrib/sites/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,325 root INFO copying django/contrib/sites/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,325 root INFO copying django/contrib/sites/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,325 root INFO creating build/lib/django/contrib/sites/locale/th/LC_MESSAGES
2025-04-22 17:58:54,325 root INFO copying django/contrib/sites/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/th/LC_MESSAGES
2025-04-22 17:58:54,326 root INFO copying django/contrib/sites/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/th/LC_MESSAGES
2025-04-22 17:58:54,326 root INFO creating build/lib/django/contrib/sites/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,326 root INFO copying django/contrib/sites/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,326 root INFO copying django/contrib/sites/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,327 root INFO creating build/lib/django/contrib/sites/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,327 root INFO copying django/contrib/sites/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,327 root INFO copying django/contrib/sites/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,327 root INFO creating build/lib/django/contrib/sites/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,327 root INFO copying django/contrib/sites/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,328 root INFO copying django/contrib/sites/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,328 root INFO creating build/lib/django/contrib/sites/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,328 root INFO copying django/contrib/sites/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,328 root INFO copying django/contrib/sites/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,329 root INFO creating build/lib/django/contrib/sites/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,329 root INFO copying django/contrib/sites/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,329 root INFO copying django/contrib/sites/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,329 root INFO creating build/lib/django/contrib/sites/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,330 root INFO copying django/contrib/sites/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,330 root INFO copying django/contrib/sites/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,330 root INFO creating build/lib/django/contrib/sites/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,330 root INFO copying django/contrib/sites/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,330 root INFO copying django/contrib/sites/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,331 root INFO creating build/lib/django/contrib/sites/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,331 root INFO copying django/contrib/sites/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,331 root INFO copying django/contrib/sites/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,331 root INFO creating build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,332 root INFO copying django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,332 root INFO copying django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,332 root INFO creating build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,332 root INFO copying django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,332 root INFO copying django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,333 root INFO creating build/lib/django/contrib/sitemaps/templates
2025-04-22 17:58:54,333 root INFO copying django/contrib/sitemaps/templates/sitemap.xml -> build/lib/django/contrib/sitemaps/templates
2025-04-22 17:58:54,333 root INFO copying django/contrib/sitemaps/templates/sitemap_index.xml -> build/lib/django/contrib/sitemaps/templates
2025-04-22 17:58:54,333 root INFO creating build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES
2025-04-22 17:58:54,334 root INFO copying django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES
2025-04-22 17:58:54,334 root INFO copying django/contrib/flatpages/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES
2025-04-22 17:58:54,334 root INFO creating build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,334 root INFO copying django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,335 root INFO copying django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,335 root INFO creating build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,335 root INFO copying django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,335 root INFO copying django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,336 root INFO creating build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,336 root INFO copying django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,336 root INFO copying django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,336 root INFO creating build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES
2025-04-22 17:58:54,337 root INFO copying django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES
2025-04-22 17:58:54,337 root INFO copying django/contrib/flatpages/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES
2025-04-22 17:58:54,337 root INFO creating build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES
2025-04-22 17:58:54,337 root INFO copying django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES
2025-04-22 17:58:54,337 root INFO copying django/contrib/flatpages/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES
2025-04-22 17:58:54,338 root INFO creating build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,338 root INFO copying django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,338 root INFO copying django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,338 root INFO creating build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,339 root INFO copying django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,339 root INFO copying django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,339 root INFO creating build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES
2025-04-22 17:58:54,339 root INFO copying django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES
2025-04-22 17:58:54,340 root INFO copying django/contrib/flatpages/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES
2025-04-22 17:58:54,340 root INFO creating build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,340 root INFO copying django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,340 root INFO copying django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,340 root INFO creating build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,341 root INFO copying django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,341 root INFO copying django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,341 root INFO creating build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,341 root INFO copying django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,342 root INFO copying django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,342 root INFO creating build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,342 root INFO copying django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,342 root INFO copying django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,342 root INFO creating build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,343 root INFO copying django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,343 root INFO copying django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,343 root INFO creating build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES
2025-04-22 17:58:54,343 root INFO copying django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES
2025-04-22 17:58:54,344 root INFO copying django/contrib/flatpages/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES
2025-04-22 17:58:54,344 root INFO creating build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES
2025-04-22 17:58:54,344 root INFO copying django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES
2025-04-22 17:58:54,344 root INFO copying django/contrib/flatpages/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES
2025-04-22 17:58:54,345 root INFO creating build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,345 root INFO copying django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,345 root INFO copying django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,345 root INFO creating build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES
2025-04-22 17:58:54,345 root INFO copying django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES
2025-04-22 17:58:54,346 root INFO copying django/contrib/flatpages/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES
2025-04-22 17:58:54,346 root INFO creating build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES
2025-04-22 17:58:54,346 root INFO copying django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES
2025-04-22 17:58:54,346 root INFO copying django/contrib/flatpages/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES
2025-04-22 17:58:54,347 root INFO creating build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,347 root INFO copying django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,347 root INFO copying django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,347 root INFO creating build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,348 root INFO copying django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,348 root INFO copying django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,348 root INFO creating build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,348 root INFO copying django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,348 root INFO copying django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,349 root INFO creating build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES
2025-04-22 17:58:54,349 root INFO copying django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES
2025-04-22 17:58:54,349 root INFO copying django/contrib/flatpages/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES
2025-04-22 17:58:54,349 root INFO creating build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,350 root INFO copying django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,350 root INFO copying django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,350 root INFO creating build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,350 root INFO copying django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,350 root INFO copying django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,351 root INFO creating build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,351 root INFO copying django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,351 root INFO copying django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,351 root INFO creating build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,352 root INFO copying django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,352 root INFO copying django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,352 root INFO creating build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES
2025-04-22 17:58:54,352 root INFO copying django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES
2025-04-22 17:58:54,352 root INFO copying django/contrib/flatpages/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES
2025-04-22 17:58:54,353 root INFO creating build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,353 root INFO copying django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,353 root INFO copying django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,353 root INFO creating build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,354 root INFO copying django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,354 root INFO copying django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,354 root INFO creating build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,354 root INFO copying django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,355 root INFO copying django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,355 root INFO creating build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,355 root INFO copying django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,355 root INFO copying django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,355 root INFO creating build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,356 root INFO copying django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,356 root INFO copying django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,356 root INFO creating build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,356 root INFO copying django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,357 root INFO copying django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,357 root INFO creating build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,357 root INFO copying django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,357 root INFO copying django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,358 root INFO creating build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,358 root INFO copying django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,358 root INFO copying django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,358 root INFO creating build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES
2025-04-22 17:58:54,358 root INFO copying django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES
2025-04-22 17:58:54,359 root INFO copying django/contrib/flatpages/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES
2025-04-22 17:58:54,359 root INFO creating build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,359 root INFO copying django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,359 root INFO copying django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,360 root INFO creating build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,360 root INFO copying django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,360 root INFO copying django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,360 root INFO creating build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,361 root INFO copying django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,361 root INFO copying django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,361 root INFO creating build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,361 root INFO copying django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,362 root INFO copying django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,362 root INFO creating build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,362 root INFO copying django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,362 root INFO copying django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,362 root INFO creating build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,363 root INFO copying django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,363 root INFO copying django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,363 root INFO creating build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES
2025-04-22 17:58:54,363 root INFO copying django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES
2025-04-22 17:58:54,364 root INFO copying django/contrib/flatpages/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES
2025-04-22 17:58:54,364 root INFO creating build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES
2025-04-22 17:58:54,364 root INFO copying django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES
2025-04-22 17:58:54,364 root INFO copying django/contrib/flatpages/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES
2025-04-22 17:58:54,364 root INFO creating build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES
2025-04-22 17:58:54,365 root INFO copying django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES
2025-04-22 17:58:54,365 root INFO copying django/contrib/flatpages/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES
2025-04-22 17:58:54,365 root INFO creating build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES
2025-04-22 17:58:54,365 root INFO copying django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES
2025-04-22 17:58:54,366 root INFO copying django/contrib/flatpages/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES
2025-04-22 17:58:54,366 root INFO creating build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,366 root INFO copying django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,366 root INFO copying django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,367 root INFO creating build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,367 root INFO copying django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,367 root INFO copying django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,367 root INFO creating build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,367 root INFO copying django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,368 root INFO copying django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,368 root INFO creating build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES
2025-04-22 17:58:54,368 root INFO copying django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES
2025-04-22 17:58:54,368 root INFO copying django/contrib/flatpages/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES
2025-04-22 17:58:54,369 root INFO creating build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,369 root INFO copying django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,369 root INFO copying django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,369 root INFO creating build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,370 root INFO copying django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,370 root INFO copying django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,370 root INFO creating build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,370 root INFO copying django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,370 root INFO copying django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,371 root INFO creating build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,371 root INFO copying django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,371 root INFO copying django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,371 root INFO creating build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,372 root INFO copying django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,372 root INFO copying django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,372 root INFO creating build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,372 root INFO copying django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,372 root INFO copying django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,373 root INFO creating build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,373 root INFO copying django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,373 root INFO copying django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,373 root INFO creating build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,374 root INFO copying django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,374 root INFO copying django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,374 root INFO creating build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,374 root INFO copying django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,375 root INFO copying django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,375 root INFO creating build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,375 root INFO copying django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,375 root INFO copying django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,375 root INFO creating build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,376 root INFO copying django/contrib/flatpages/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,376 root INFO copying django/contrib/flatpages/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,376 root INFO creating build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES
2025-04-22 17:58:54,376 root INFO copying django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES
2025-04-22 17:58:54,377 root INFO copying django/contrib/flatpages/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES
2025-04-22 17:58:54,377 root INFO creating build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,377 root INFO copying django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,377 root INFO copying django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,378 root INFO creating build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,378 root INFO copying django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,378 root INFO copying django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,378 root INFO creating build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,378 root INFO copying django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,379 root INFO copying django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,379 root INFO creating build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,379 root INFO copying django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,379 root INFO copying django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,380 root INFO creating build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES
2025-04-22 17:58:54,380 root INFO copying django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES
2025-04-22 17:58:54,380 root INFO copying django/contrib/flatpages/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES
2025-04-22 17:58:54,380 root INFO creating build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,380 root INFO copying django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,381 root INFO copying django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,381 root INFO creating build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,381 root INFO copying django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,381 root INFO copying django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,382 root INFO creating build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,382 root INFO copying django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,382 root INFO copying django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,382 root INFO creating build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,382 root INFO copying django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,383 root INFO copying django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,383 root INFO creating build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,383 root INFO copying django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,383 root INFO copying django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,384 root INFO creating build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,384 root INFO copying django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,384 root INFO copying django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,384 root INFO creating build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,385 root INFO copying django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,385 root INFO copying django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,385 root INFO creating build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,385 root INFO copying django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,385 root INFO copying django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,386 root INFO creating build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,386 root INFO copying django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,386 root INFO copying django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,386 root INFO creating build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,387 root INFO copying django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,387 root INFO copying django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,387 root INFO creating build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,387 root INFO copying django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,387 root INFO copying django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,388 root INFO creating build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,388 root INFO copying django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,388 root INFO copying django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,388 root INFO creating build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,389 root INFO copying django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,389 root INFO copying django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,389 root INFO creating build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,389 root INFO copying django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,390 root INFO copying django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,390 root INFO creating build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES
2025-04-22 17:58:54,390 root INFO copying django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES
2025-04-22 17:58:54,390 root INFO copying django/contrib/flatpages/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES
2025-04-22 17:58:54,390 root INFO creating build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,391 root INFO copying django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,391 root INFO copying django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,391 root INFO creating build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES
2025-04-22 17:58:54,391 root INFO copying django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES
2025-04-22 17:58:54,392 root INFO copying django/contrib/flatpages/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES
2025-04-22 17:58:54,392 root INFO creating build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,392 root INFO copying django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,392 root INFO copying django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,392 root INFO creating build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,393 root INFO copying django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,393 root INFO copying django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,393 root INFO creating build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,393 root INFO copying django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,394 root INFO copying django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,394 root INFO creating build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,394 root INFO copying django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,394 root INFO copying django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,395 root INFO creating build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,395 root INFO copying django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,395 root INFO copying django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,395 root INFO creating build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,395 root INFO copying django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,396 root INFO copying django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,396 root INFO creating build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,396 root INFO copying django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,396 root INFO copying django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,397 root INFO creating build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,397 root INFO copying django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,397 root INFO copying django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,397 root INFO creating build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,398 root INFO copying django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,398 root INFO copying django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,398 root INFO creating build/lib/django/contrib/sessions/locale/af/LC_MESSAGES
2025-04-22 17:58:54,398 root INFO copying django/contrib/sessions/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/af/LC_MESSAGES
2025-04-22 17:58:54,399 root INFO copying django/contrib/sessions/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/af/LC_MESSAGES
2025-04-22 17:58:54,399 root INFO creating build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,399 root INFO copying django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,399 root INFO copying django/contrib/sessions/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,399 root INFO creating build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,400 root INFO copying django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,400 root INFO copying django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,400 root INFO creating build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,400 root INFO copying django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,401 root INFO copying django/contrib/sessions/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,401 root INFO creating build/lib/django/contrib/sessions/locale/az/LC_MESSAGES
2025-04-22 17:58:54,401 root INFO copying django/contrib/sessions/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/az/LC_MESSAGES
2025-04-22 17:58:54,401 root INFO copying django/contrib/sessions/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/az/LC_MESSAGES
2025-04-22 17:58:54,401 root INFO creating build/lib/django/contrib/sessions/locale/be/LC_MESSAGES
2025-04-22 17:58:54,402 root INFO copying django/contrib/sessions/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/be/LC_MESSAGES
2025-04-22 17:58:54,402 root INFO copying django/contrib/sessions/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/be/LC_MESSAGES
2025-04-22 17:58:54,402 root INFO creating build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,402 root INFO copying django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,403 root INFO copying django/contrib/sessions/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,403 root INFO creating build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,403 root INFO copying django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,403 root INFO copying django/contrib/sessions/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,404 root INFO creating build/lib/django/contrib/sessions/locale/br/LC_MESSAGES
2025-04-22 17:58:54,404 root INFO copying django/contrib/sessions/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/br/LC_MESSAGES
2025-04-22 17:58:54,404 root INFO copying django/contrib/sessions/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/br/LC_MESSAGES
2025-04-22 17:58:54,404 root INFO creating build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,404 root INFO copying django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,405 root INFO copying django/contrib/sessions/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,405 root INFO creating build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,405 root INFO copying django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,405 root INFO copying django/contrib/sessions/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,406 root INFO creating build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,406 root INFO copying django/contrib/sessions/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,406 root INFO copying django/contrib/sessions/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,406 root INFO creating build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,406 root INFO copying django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,407 root INFO copying django/contrib/sessions/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,407 root INFO creating build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,407 root INFO copying django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,407 root INFO copying django/contrib/sessions/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,408 root INFO creating build/lib/django/contrib/sessions/locale/da/LC_MESSAGES
2025-04-22 17:58:54,408 root INFO copying django/contrib/sessions/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/da/LC_MESSAGES
2025-04-22 17:58:54,408 root INFO copying django/contrib/sessions/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/da/LC_MESSAGES
2025-04-22 17:58:54,408 root INFO creating build/lib/django/contrib/sessions/locale/de/LC_MESSAGES
2025-04-22 17:58:54,408 root INFO copying django/contrib/sessions/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/de/LC_MESSAGES
2025-04-22 17:58:54,409 root INFO copying django/contrib/sessions/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/de/LC_MESSAGES
2025-04-22 17:58:54,409 root INFO creating build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,409 root INFO copying django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,409 root INFO copying django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,410 root INFO creating build/lib/django/contrib/sessions/locale/el/LC_MESSAGES
2025-04-22 17:58:54,410 root INFO copying django/contrib/sessions/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/el/LC_MESSAGES
2025-04-22 17:58:54,410 root INFO copying django/contrib/sessions/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/el/LC_MESSAGES
2025-04-22 17:58:54,410 root INFO creating build/lib/django/contrib/sessions/locale/en/LC_MESSAGES
2025-04-22 17:58:54,411 root INFO copying django/contrib/sessions/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/en/LC_MESSAGES
2025-04-22 17:58:54,411 root INFO copying django/contrib/sessions/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/en/LC_MESSAGES
2025-04-22 17:58:54,411 root INFO creating build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,411 root INFO copying django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,412 root INFO copying django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,412 root INFO creating build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,412 root INFO copying django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,412 root INFO copying django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,412 root INFO creating build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,413 root INFO copying django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,413 root INFO copying django/contrib/sessions/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,413 root INFO creating build/lib/django/contrib/sessions/locale/es/LC_MESSAGES
2025-04-22 17:58:54,413 root INFO copying django/contrib/sessions/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es/LC_MESSAGES
2025-04-22 17:58:54,414 root INFO copying django/contrib/sessions/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es/LC_MESSAGES
2025-04-22 17:58:54,414 root INFO creating build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,414 root INFO copying django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,414 root INFO copying django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,414 root INFO creating build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,415 root INFO copying django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,415 root INFO copying django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,415 root INFO creating build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,415 root INFO copying django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,416 root INFO copying django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,416 root INFO creating build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,416 root INFO copying django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,416 root INFO copying django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,417 root INFO creating build/lib/django/contrib/sessions/locale/et/LC_MESSAGES
2025-04-22 17:58:54,417 root INFO copying django/contrib/sessions/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/et/LC_MESSAGES
2025-04-22 17:58:54,417 root INFO copying django/contrib/sessions/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/et/LC_MESSAGES
2025-04-22 17:58:54,417 root INFO creating build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,417 root INFO copying django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,418 root INFO copying django/contrib/sessions/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,418 root INFO creating build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,418 root INFO copying django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,418 root INFO copying django/contrib/sessions/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,419 root INFO creating build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,419 root INFO copying django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,419 root INFO copying django/contrib/sessions/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,419 root INFO creating build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,419 root INFO copying django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,420 root INFO copying django/contrib/sessions/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,420 root INFO creating build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,420 root INFO copying django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,420 root INFO copying django/contrib/sessions/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,421 root INFO creating build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,421 root INFO copying django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,421 root INFO copying django/contrib/sessions/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,421 root INFO creating build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,421 root INFO copying django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,422 root INFO copying django/contrib/sessions/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,422 root INFO creating build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,422 root INFO copying django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,422 root INFO copying django/contrib/sessions/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,423 root INFO creating build/lib/django/contrib/sessions/locale/he/LC_MESSAGES
2025-04-22 17:58:54,423 root INFO copying django/contrib/sessions/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/he/LC_MESSAGES
2025-04-22 17:58:54,423 root INFO copying django/contrib/sessions/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/he/LC_MESSAGES
2025-04-22 17:58:54,423 root INFO creating build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,423 root INFO copying django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,424 root INFO copying django/contrib/sessions/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,424 root INFO creating build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,424 root INFO copying django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,424 root INFO copying django/contrib/sessions/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,425 root INFO creating build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,425 root INFO copying django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,425 root INFO copying django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,425 root INFO creating build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,425 root INFO copying django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,426 root INFO copying django/contrib/sessions/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,426 root INFO creating build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,426 root INFO copying django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,426 root INFO copying django/contrib/sessions/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,427 root INFO creating build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,427 root INFO copying django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,427 root INFO copying django/contrib/sessions/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,427 root INFO creating build/lib/django/contrib/sessions/locale/id/LC_MESSAGES
2025-04-22 17:58:54,427 root INFO copying django/contrib/sessions/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/id/LC_MESSAGES
2025-04-22 17:58:54,428 root INFO copying django/contrib/sessions/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/id/LC_MESSAGES
2025-04-22 17:58:54,428 root INFO creating build/lib/django/contrib/sessions/locale/io/LC_MESSAGES
2025-04-22 17:58:54,428 root INFO copying django/contrib/sessions/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/io/LC_MESSAGES
2025-04-22 17:58:54,428 root INFO copying django/contrib/sessions/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/io/LC_MESSAGES
2025-04-22 17:58:54,429 root INFO creating build/lib/django/contrib/sessions/locale/is/LC_MESSAGES
2025-04-22 17:58:54,429 root INFO copying django/contrib/sessions/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/is/LC_MESSAGES
2025-04-22 17:58:54,429 root INFO copying django/contrib/sessions/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/is/LC_MESSAGES
2025-04-22 17:58:54,429 root INFO creating build/lib/django/contrib/sessions/locale/it/LC_MESSAGES
2025-04-22 17:58:54,429 root INFO copying django/contrib/sessions/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/it/LC_MESSAGES
2025-04-22 17:58:54,430 root INFO copying django/contrib/sessions/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/it/LC_MESSAGES
2025-04-22 17:58:54,430 root INFO creating build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,430 root INFO copying django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,430 root INFO copying django/contrib/sessions/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,431 root INFO creating build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,431 root INFO copying django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,431 root INFO copying django/contrib/sessions/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,431 root INFO creating build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,431 root INFO copying django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,432 root INFO copying django/contrib/sessions/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,432 root INFO creating build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,432 root INFO copying django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,432 root INFO copying django/contrib/sessions/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,433 root INFO creating build/lib/django/contrib/sessions/locale/km/LC_MESSAGES
2025-04-22 17:58:54,433 root INFO copying django/contrib/sessions/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/km/LC_MESSAGES
2025-04-22 17:58:54,433 root INFO copying django/contrib/sessions/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/km/LC_MESSAGES
2025-04-22 17:58:54,433 root INFO creating build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,433 root INFO copying django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,434 root INFO copying django/contrib/sessions/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,434 root INFO creating build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,434 root INFO copying django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,434 root INFO copying django/contrib/sessions/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,435 root INFO creating build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,435 root INFO copying django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,435 root INFO copying django/contrib/sessions/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,435 root INFO creating build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,435 root INFO copying django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,436 root INFO copying django/contrib/sessions/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,436 root INFO creating build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,436 root INFO copying django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,437 root INFO copying django/contrib/sessions/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,437 root INFO creating build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,437 root INFO copying django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,437 root INFO copying django/contrib/sessions/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,437 root INFO creating build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,438 root INFO copying django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,438 root INFO copying django/contrib/sessions/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,438 root INFO creating build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,438 root INFO copying django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,439 root INFO copying django/contrib/sessions/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,439 root INFO creating build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,439 root INFO copying django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,439 root INFO copying django/contrib/sessions/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,440 root INFO creating build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,440 root INFO copying django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,440 root INFO copying django/contrib/sessions/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,440 root INFO creating build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,440 root INFO copying django/contrib/sessions/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,441 root INFO copying django/contrib/sessions/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,441 root INFO creating build/lib/django/contrib/sessions/locale/my/LC_MESSAGES
2025-04-22 17:58:54,441 root INFO copying django/contrib/sessions/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/my/LC_MESSAGES
2025-04-22 17:58:54,441 root INFO copying django/contrib/sessions/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/my/LC_MESSAGES
2025-04-22 17:58:54,441 root INFO creating build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,442 root INFO copying django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,442 root INFO copying django/contrib/sessions/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,442 root INFO creating build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,442 root INFO copying django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,443 root INFO copying django/contrib/sessions/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,443 root INFO creating build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,443 root INFO copying django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,443 root INFO copying django/contrib/sessions/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,444 root INFO creating build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,444 root INFO copying django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,444 root INFO copying django/contrib/sessions/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,444 root INFO creating build/lib/django/contrib/sessions/locale/os/LC_MESSAGES
2025-04-22 17:58:54,444 root INFO copying django/contrib/sessions/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/os/LC_MESSAGES
2025-04-22 17:58:54,445 root INFO copying django/contrib/sessions/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/os/LC_MESSAGES
2025-04-22 17:58:54,445 root INFO creating build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,445 root INFO copying django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,445 root INFO copying django/contrib/sessions/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,446 root INFO creating build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,446 root INFO copying django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,446 root INFO copying django/contrib/sessions/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,446 root INFO creating build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,446 root INFO copying django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,447 root INFO copying django/contrib/sessions/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,447 root INFO creating build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,447 root INFO copying django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,447 root INFO copying django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,448 root INFO creating build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,448 root INFO copying django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,448 root INFO copying django/contrib/sessions/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,448 root INFO creating build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,448 root INFO copying django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,449 root INFO copying django/contrib/sessions/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,449 root INFO creating build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,449 root INFO copying django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,449 root INFO copying django/contrib/sessions/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,450 root INFO creating build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,450 root INFO copying django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,450 root INFO copying django/contrib/sessions/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,450 root INFO creating build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,451 root INFO copying django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,451 root INFO copying django/contrib/sessions/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,451 root INFO creating build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,451 root INFO copying django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,451 root INFO copying django/contrib/sessions/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,452 root INFO creating build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,452 root INFO copying django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,452 root INFO copying django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,452 root INFO creating build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,452 root INFO copying django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,453 root INFO copying django/contrib/sessions/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,453 root INFO creating build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,453 root INFO copying django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,453 root INFO copying django/contrib/sessions/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,454 root INFO creating build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,454 root INFO copying django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,454 root INFO copying django/contrib/sessions/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,454 root INFO creating build/lib/django/contrib/sessions/locale/te/LC_MESSAGES
2025-04-22 17:58:54,455 root INFO copying django/contrib/sessions/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/te/LC_MESSAGES
2025-04-22 17:58:54,455 root INFO copying django/contrib/sessions/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/te/LC_MESSAGES
2025-04-22 17:58:54,455 root INFO creating build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,455 root INFO copying django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,455 root INFO copying django/contrib/sessions/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,456 root INFO creating build/lib/django/contrib/sessions/locale/th/LC_MESSAGES
2025-04-22 17:58:54,456 root INFO copying django/contrib/sessions/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/th/LC_MESSAGES
2025-04-22 17:58:54,456 root INFO copying django/contrib/sessions/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/th/LC_MESSAGES
2025-04-22 17:58:54,456 root INFO creating build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,457 root INFO copying django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,457 root INFO copying django/contrib/sessions/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,457 root INFO creating build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,457 root INFO copying django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,458 root INFO copying django/contrib/sessions/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,458 root INFO creating build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,458 root INFO copying django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,458 root INFO copying django/contrib/sessions/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,458 root INFO creating build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,459 root INFO copying django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,459 root INFO copying django/contrib/sessions/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,459 root INFO creating build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,459 root INFO copying django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,460 root INFO copying django/contrib/sessions/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,460 root INFO creating build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,460 root INFO copying django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,460 root INFO copying django/contrib/sessions/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,461 root INFO creating build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,461 root INFO copying django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,461 root INFO copying django/contrib/sessions/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,461 root INFO creating build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,461 root INFO copying django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,462 root INFO copying django/contrib/sessions/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,462 root INFO creating build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,462 root INFO copying django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,462 root INFO copying django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,463 root INFO creating build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,463 root INFO copying django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,463 root INFO copying django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,463 root INFO creating build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES
2025-04-22 17:58:54,463 root INFO copying django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES
2025-04-22 17:58:54,464 root INFO copying django/contrib/admindocs/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES
2025-04-22 17:58:54,464 root INFO creating build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,464 root INFO copying django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,464 root INFO copying django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,465 root INFO creating build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,465 root INFO copying django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,465 root INFO copying django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,465 root INFO creating build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,466 root INFO copying django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,466 root INFO copying django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,466 root INFO creating build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES
2025-04-22 17:58:54,466 root INFO copying django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES
2025-04-22 17:58:54,467 root INFO copying django/contrib/admindocs/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES
2025-04-22 17:58:54,467 root INFO creating build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES
2025-04-22 17:58:54,467 root INFO copying django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES
2025-04-22 17:58:54,467 root INFO copying django/contrib/admindocs/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES
2025-04-22 17:58:54,467 root INFO creating build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,468 root INFO copying django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,468 root INFO copying django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,468 root INFO creating build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,468 root INFO copying django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,469 root INFO copying django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,469 root INFO creating build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES
2025-04-22 17:58:54,469 root INFO copying django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES
2025-04-22 17:58:54,469 root INFO copying django/contrib/admindocs/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES
2025-04-22 17:58:54,470 root INFO creating build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,470 root INFO copying django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,470 root INFO copying django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,470 root INFO creating build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,470 root INFO copying django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,471 root INFO copying django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,471 root INFO creating build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,471 root INFO copying django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,471 root INFO copying django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,472 root INFO creating build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,472 root INFO copying django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,472 root INFO copying django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,472 root INFO creating build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,473 root INFO copying django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,473 root INFO copying django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,473 root INFO creating build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES
2025-04-22 17:58:54,473 root INFO copying django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES
2025-04-22 17:58:54,474 root INFO copying django/contrib/admindocs/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES
2025-04-22 17:58:54,474 root INFO creating build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES
2025-04-22 17:58:54,474 root INFO copying django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES
2025-04-22 17:58:54,474 root INFO copying django/contrib/admindocs/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES
2025-04-22 17:58:54,474 root INFO creating build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,475 root INFO copying django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,475 root INFO copying django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,475 root INFO creating build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES
2025-04-22 17:58:54,475 root INFO copying django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES
2025-04-22 17:58:54,476 root INFO copying django/contrib/admindocs/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES
2025-04-22 17:58:54,476 root INFO creating build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES
2025-04-22 17:58:54,476 root INFO copying django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES
2025-04-22 17:58:54,476 root INFO copying django/contrib/admindocs/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES
2025-04-22 17:58:54,477 root INFO creating build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,477 root INFO copying django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,477 root INFO copying django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,477 root INFO creating build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,477 root INFO copying django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,478 root INFO copying django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,478 root INFO creating build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,478 root INFO copying django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,478 root INFO copying django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,479 root INFO creating build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES
2025-04-22 17:58:54,479 root INFO copying django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES
2025-04-22 17:58:54,479 root INFO copying django/contrib/admindocs/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES
2025-04-22 17:58:54,479 root INFO creating build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,480 root INFO copying django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,480 root INFO copying django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,480 root INFO creating build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,480 root INFO copying django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,481 root INFO copying django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,481 root INFO creating build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,481 root INFO copying django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,481 root INFO copying django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,481 root INFO creating build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,482 root INFO copying django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,482 root INFO copying django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,482 root INFO creating build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES
2025-04-22 17:58:54,482 root INFO copying django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES
2025-04-22 17:58:54,483 root INFO copying django/contrib/admindocs/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES
2025-04-22 17:58:54,483 root INFO creating build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,483 root INFO copying django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,484 root INFO copying django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,484 root INFO creating build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,484 root INFO copying django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,484 root INFO copying django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,484 root INFO creating build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,485 root INFO copying django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,485 root INFO copying django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,485 root INFO creating build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,485 root INFO copying django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,486 root INFO copying django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,486 root INFO creating build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,486 root INFO copying django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,486 root INFO copying django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,487 root INFO creating build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,487 root INFO copying django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,487 root INFO copying django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,487 root INFO creating build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,487 root INFO copying django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,488 root INFO copying django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,488 root INFO creating build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,488 root INFO copying django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,488 root INFO copying django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,489 root INFO creating build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES
2025-04-22 17:58:54,489 root INFO copying django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES
2025-04-22 17:58:54,489 root INFO copying django/contrib/admindocs/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES
2025-04-22 17:58:54,489 root INFO creating build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,490 root INFO copying django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,490 root INFO copying django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,490 root INFO creating build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,490 root INFO copying django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,491 root INFO copying django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,491 root INFO creating build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,491 root INFO copying django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,491 root INFO copying django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,491 root INFO creating build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,492 root INFO copying django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,492 root INFO copying django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,492 root INFO creating build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,492 root INFO copying django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,493 root INFO copying django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,493 root INFO creating build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES
2025-04-22 17:58:54,493 root INFO copying django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES
2025-04-22 17:58:54,493 root INFO copying django/contrib/admindocs/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES
2025-04-22 17:58:54,494 root INFO creating build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES
2025-04-22 17:58:54,494 root INFO copying django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES
2025-04-22 17:58:54,494 root INFO copying django/contrib/admindocs/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES
2025-04-22 17:58:54,494 root INFO creating build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES
2025-04-22 17:58:54,494 root INFO copying django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES
2025-04-22 17:58:54,495 root INFO copying django/contrib/admindocs/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES
2025-04-22 17:58:54,495 root INFO creating build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES
2025-04-22 17:58:54,495 root INFO copying django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES
2025-04-22 17:58:54,495 root INFO copying django/contrib/admindocs/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES
2025-04-22 17:58:54,496 root INFO creating build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,496 root INFO copying django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,496 root INFO copying django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,496 root INFO creating build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,497 root INFO copying django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,497 root INFO copying django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,497 root INFO creating build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,497 root INFO copying django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,497 root INFO copying django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,498 root INFO creating build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,498 root INFO copying django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,498 root INFO copying django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,498 root INFO creating build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES
2025-04-22 17:58:54,499 root INFO copying django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES
2025-04-22 17:58:54,499 root INFO copying django/contrib/admindocs/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES
2025-04-22 17:58:54,499 root INFO creating build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,499 root INFO copying django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,500 root INFO copying django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,500 root INFO creating build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,500 root INFO copying django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,500 root INFO copying django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,501 root INFO creating build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,501 root INFO copying django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,501 root INFO copying django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,501 root INFO creating build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,502 root INFO copying django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,502 root INFO copying django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,502 root INFO creating build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,502 root INFO copying django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,502 root INFO copying django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,503 root INFO creating build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,503 root INFO copying django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,503 root INFO copying django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,503 root INFO creating build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,504 root INFO copying django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,504 root INFO copying django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,504 root INFO creating build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,504 root INFO copying django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,505 root INFO copying django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,505 root INFO creating build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,505 root INFO copying django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,505 root INFO copying django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,505 root INFO creating build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,506 root INFO copying django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,506 root INFO copying django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,506 root INFO creating build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,506 root INFO copying django/contrib/admindocs/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,507 root INFO copying django/contrib/admindocs/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,507 root INFO creating build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES
2025-04-22 17:58:54,507 root INFO copying django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES
2025-04-22 17:58:54,507 root INFO copying django/contrib/admindocs/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES
2025-04-22 17:58:54,508 root INFO creating build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,508 root INFO copying django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,508 root INFO copying django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,508 root INFO creating build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,508 root INFO copying django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,509 root INFO copying django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,509 root INFO creating build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,509 root INFO copying django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,509 root INFO copying django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,510 root INFO creating build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,510 root INFO copying django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,510 root INFO copying django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,510 root INFO creating build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES
2025-04-22 17:58:54,511 root INFO copying django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES
2025-04-22 17:58:54,511 root INFO copying django/contrib/admindocs/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES
2025-04-22 17:58:54,511 root INFO creating build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,511 root INFO copying django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,512 root INFO copying django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,512 root INFO creating build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,512 root INFO copying django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,512 root INFO copying django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,512 root INFO creating build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,513 root INFO copying django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,513 root INFO copying django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,513 root INFO creating build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,513 root INFO copying django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,514 root INFO copying django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,514 root INFO creating build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,514 root INFO copying django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,514 root INFO copying django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,515 root INFO creating build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,515 root INFO copying django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,515 root INFO copying django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,515 root INFO creating build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,516 root INFO copying django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,516 root INFO copying django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,516 root INFO creating build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,516 root INFO copying django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,517 root INFO copying django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,517 root INFO creating build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,517 root INFO copying django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,517 root INFO copying django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,517 root INFO creating build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,518 root INFO copying django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,518 root INFO copying django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,518 root INFO creating build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,518 root INFO copying django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,519 root INFO copying django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,519 root INFO creating build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,519 root INFO copying django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,519 root INFO copying django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,520 root INFO creating build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,520 root INFO copying django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,520 root INFO copying django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,520 root INFO creating build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,520 root INFO copying django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,521 root INFO copying django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,521 root INFO creating build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES
2025-04-22 17:58:54,521 root INFO copying django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES
2025-04-22 17:58:54,521 root INFO copying django/contrib/admindocs/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES
2025-04-22 17:58:54,522 root INFO creating build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,522 root INFO copying django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,522 root INFO copying django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,522 root INFO creating build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES
2025-04-22 17:58:54,522 root INFO copying django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES
2025-04-22 17:58:54,523 root INFO copying django/contrib/admindocs/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES
2025-04-22 17:58:54,523 root INFO creating build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,523 root INFO copying django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,523 root INFO copying django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,524 root INFO creating build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,524 root INFO copying django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,524 root INFO copying django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,524 root INFO creating build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,525 root INFO copying django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,525 root INFO copying django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,525 root INFO creating build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,525 root INFO copying django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,526 root INFO copying django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,526 root INFO creating build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,526 root INFO copying django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,526 root INFO copying django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,527 root INFO creating build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,527 root INFO copying django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,527 root INFO copying django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,527 root INFO creating build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,527 root INFO copying django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,528 root INFO copying django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,528 root INFO creating build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,528 root INFO copying django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,528 root INFO copying django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,529 root INFO creating build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:54,529 root INFO copying django/contrib/admindocs/templates/admin_doc/bookmarklets.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:54,529 root INFO copying django/contrib/admindocs/templates/admin_doc/index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:54,529 root INFO copying django/contrib/admindocs/templates/admin_doc/missing_docutils.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:54,530 root INFO copying django/contrib/admindocs/templates/admin_doc/model_detail.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:54,530 root INFO copying django/contrib/admindocs/templates/admin_doc/model_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:54,530 root INFO copying django/contrib/admindocs/templates/admin_doc/template_detail.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:54,530 root INFO copying django/contrib/admindocs/templates/admin_doc/template_filter_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:54,531 root INFO copying django/contrib/admindocs/templates/admin_doc/template_tag_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:54,531 root INFO copying django/contrib/admindocs/templates/admin_doc/view_detail.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:54,531 root INFO copying django/contrib/admindocs/templates/admin_doc/view_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:54,531 root INFO creating build/lib/django/contrib/postgres/jinja2/postgres/widgets
2025-04-22 17:58:54,532 root INFO copying django/contrib/postgres/jinja2/postgres/widgets/split_array.html -> build/lib/django/contrib/postgres/jinja2/postgres/widgets
2025-04-22 17:58:54,532 root INFO creating build/lib/django/contrib/postgres/locale/af/LC_MESSAGES
2025-04-22 17:58:54,532 root INFO copying django/contrib/postgres/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/af/LC_MESSAGES
2025-04-22 17:58:54,532 root INFO copying django/contrib/postgres/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/af/LC_MESSAGES
2025-04-22 17:58:54,533 root INFO creating build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,533 root INFO copying django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,533 root INFO copying django/contrib/postgres/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,533 root INFO creating build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,533 root INFO copying django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,534 root INFO copying django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,534 root INFO creating build/lib/django/contrib/postgres/locale/az/LC_MESSAGES
2025-04-22 17:58:54,534 root INFO copying django/contrib/postgres/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/az/LC_MESSAGES
2025-04-22 17:58:54,534 root INFO copying django/contrib/postgres/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/az/LC_MESSAGES
2025-04-22 17:58:54,535 root INFO creating build/lib/django/contrib/postgres/locale/be/LC_MESSAGES
2025-04-22 17:58:54,535 root INFO copying django/contrib/postgres/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/be/LC_MESSAGES
2025-04-22 17:58:54,535 root INFO copying django/contrib/postgres/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/be/LC_MESSAGES
2025-04-22 17:58:54,535 root INFO creating build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,536 root INFO copying django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,536 root INFO copying django/contrib/postgres/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,536 root INFO creating build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,536 root INFO copying django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,537 root INFO copying django/contrib/postgres/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,537 root INFO creating build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,537 root INFO copying django/contrib/postgres/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,537 root INFO copying django/contrib/postgres/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,537 root INFO creating build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,538 root INFO copying django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,538 root INFO copying django/contrib/postgres/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,538 root INFO creating build/lib/django/contrib/postgres/locale/da/LC_MESSAGES
2025-04-22 17:58:54,538 root INFO copying django/contrib/postgres/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/da/LC_MESSAGES
2025-04-22 17:58:54,539 root INFO copying django/contrib/postgres/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/da/LC_MESSAGES
2025-04-22 17:58:54,539 root INFO creating build/lib/django/contrib/postgres/locale/de/LC_MESSAGES
2025-04-22 17:58:54,539 root INFO copying django/contrib/postgres/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/de/LC_MESSAGES
2025-04-22 17:58:54,539 root INFO copying django/contrib/postgres/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/de/LC_MESSAGES
2025-04-22 17:58:54,539 root INFO creating build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,540 root INFO copying django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,540 root INFO copying django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,540 root INFO creating build/lib/django/contrib/postgres/locale/el/LC_MESSAGES
2025-04-22 17:58:54,540 root INFO copying django/contrib/postgres/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/el/LC_MESSAGES
2025-04-22 17:58:54,541 root INFO copying django/contrib/postgres/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/el/LC_MESSAGES
2025-04-22 17:58:54,541 root INFO creating build/lib/django/contrib/postgres/locale/en/LC_MESSAGES
2025-04-22 17:58:54,541 root INFO copying django/contrib/postgres/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/en/LC_MESSAGES
2025-04-22 17:58:54,541 root INFO copying django/contrib/postgres/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/en/LC_MESSAGES
2025-04-22 17:58:54,542 root INFO creating build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,542 root INFO copying django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,542 root INFO copying django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,542 root INFO creating build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,542 root INFO copying django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,543 root INFO copying django/contrib/postgres/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,543 root INFO creating build/lib/django/contrib/postgres/locale/es/LC_MESSAGES
2025-04-22 17:58:54,543 root INFO copying django/contrib/postgres/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/es/LC_MESSAGES
2025-04-22 17:58:54,543 root INFO copying django/contrib/postgres/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/es/LC_MESSAGES
2025-04-22 17:58:54,544 root INFO creating build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,544 root INFO copying django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,544 root INFO copying django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,544 root INFO creating build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,544 root INFO copying django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,545 root INFO copying django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,545 root INFO creating build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,545 root INFO copying django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,545 root INFO copying django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,546 root INFO creating build/lib/django/contrib/postgres/locale/et/LC_MESSAGES
2025-04-22 17:58:54,546 root INFO copying django/contrib/postgres/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/et/LC_MESSAGES
2025-04-22 17:58:54,546 root INFO copying django/contrib/postgres/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/et/LC_MESSAGES
2025-04-22 17:58:54,546 root INFO creating build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,547 root INFO copying django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,547 root INFO copying django/contrib/postgres/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,547 root INFO creating build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,547 root INFO copying django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,547 root INFO copying django/contrib/postgres/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,548 root INFO creating build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,548 root INFO copying django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,548 root INFO copying django/contrib/postgres/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,548 root INFO creating build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,549 root INFO copying django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,549 root INFO copying django/contrib/postgres/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,549 root INFO creating build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,549 root INFO copying django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,549 root INFO copying django/contrib/postgres/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,550 root INFO creating build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,550 root INFO copying django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,550 root INFO copying django/contrib/postgres/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,550 root INFO creating build/lib/django/contrib/postgres/locale/he/LC_MESSAGES
2025-04-22 17:58:54,551 root INFO copying django/contrib/postgres/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/he/LC_MESSAGES
2025-04-22 17:58:54,551 root INFO copying django/contrib/postgres/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/he/LC_MESSAGES
2025-04-22 17:58:54,551 root INFO creating build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,551 root INFO copying django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,552 root INFO copying django/contrib/postgres/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,552 root INFO creating build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,552 root INFO copying django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,552 root INFO copying django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,552 root INFO creating build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,553 root INFO copying django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,553 root INFO copying django/contrib/postgres/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,553 root INFO creating build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,553 root INFO copying django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,554 root INFO copying django/contrib/postgres/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,554 root INFO creating build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,554 root INFO copying django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,554 root INFO copying django/contrib/postgres/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,554 root INFO creating build/lib/django/contrib/postgres/locale/id/LC_MESSAGES
2025-04-22 17:58:54,555 root INFO copying django/contrib/postgres/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/id/LC_MESSAGES
2025-04-22 17:58:54,555 root INFO copying django/contrib/postgres/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/id/LC_MESSAGES
2025-04-22 17:58:54,555 root INFO creating build/lib/django/contrib/postgres/locale/is/LC_MESSAGES
2025-04-22 17:58:54,555 root INFO copying django/contrib/postgres/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/is/LC_MESSAGES
2025-04-22 17:58:54,556 root INFO copying django/contrib/postgres/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/is/LC_MESSAGES
2025-04-22 17:58:54,556 root INFO creating build/lib/django/contrib/postgres/locale/it/LC_MESSAGES
2025-04-22 17:58:54,556 root INFO copying django/contrib/postgres/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/it/LC_MESSAGES
2025-04-22 17:58:54,556 root INFO copying django/contrib/postgres/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/it/LC_MESSAGES
2025-04-22 17:58:54,557 root INFO creating build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,557 root INFO copying django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,557 root INFO copying django/contrib/postgres/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,557 root INFO creating build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,557 root INFO copying django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,558 root INFO copying django/contrib/postgres/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,558 root INFO creating build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,558 root INFO copying django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,558 root INFO copying django/contrib/postgres/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,559 root INFO creating build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,559 root INFO copying django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,559 root INFO copying django/contrib/postgres/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,559 root INFO creating build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,560 root INFO copying django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,560 root INFO copying django/contrib/postgres/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,560 root INFO creating build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,560 root INFO copying django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,561 root INFO copying django/contrib/postgres/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,561 root INFO creating build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,561 root INFO copying django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,561 root INFO copying django/contrib/postgres/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,561 root INFO creating build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,562 root INFO copying django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,562 root INFO copying django/contrib/postgres/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,562 root INFO creating build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,562 root INFO copying django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,562 root INFO copying django/contrib/postgres/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,563 root INFO creating build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,563 root INFO copying django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,563 root INFO copying django/contrib/postgres/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,563 root INFO creating build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,564 root INFO copying django/contrib/postgres/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,564 root INFO copying django/contrib/postgres/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,564 root INFO creating build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,564 root INFO copying django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,565 root INFO copying django/contrib/postgres/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,565 root INFO creating build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,565 root INFO copying django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,565 root INFO copying django/contrib/postgres/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,565 root INFO creating build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,566 root INFO copying django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,566 root INFO copying django/contrib/postgres/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,566 root INFO creating build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,566 root INFO copying django/contrib/postgres/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,567 root INFO copying django/contrib/postgres/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,567 root INFO creating build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,567 root INFO copying django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,567 root INFO copying django/contrib/postgres/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,568 root INFO creating build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,568 root INFO copying django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,568 root INFO copying django/contrib/postgres/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,568 root INFO creating build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,569 root INFO copying django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,569 root INFO copying django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,569 root INFO creating build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,569 root INFO copying django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,569 root INFO copying django/contrib/postgres/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,570 root INFO creating build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,570 root INFO copying django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,570 root INFO copying django/contrib/postgres/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,570 root INFO creating build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,571 root INFO copying django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,571 root INFO copying django/contrib/postgres/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,571 root INFO creating build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,571 root INFO copying django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,572 root INFO copying django/contrib/postgres/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,572 root INFO creating build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,572 root INFO copying django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,572 root INFO copying django/contrib/postgres/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,572 root INFO creating build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,573 root INFO copying django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,573 root INFO copying django/contrib/postgres/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,573 root INFO creating build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,573 root INFO copying django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,574 root INFO copying django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,574 root INFO creating build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,574 root INFO copying django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,574 root INFO copying django/contrib/postgres/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,575 root INFO creating build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,575 root INFO copying django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,575 root INFO copying django/contrib/postgres/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,575 root INFO creating build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,575 root INFO copying django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,576 root INFO copying django/contrib/postgres/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,576 root INFO creating build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,576 root INFO copying django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,576 root INFO copying django/contrib/postgres/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,577 root INFO creating build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,577 root INFO copying django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,577 root INFO copying django/contrib/postgres/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,577 root INFO creating build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,578 root INFO copying django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,578 root INFO copying django/contrib/postgres/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,578 root INFO creating build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,578 root INFO copying django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,578 root INFO copying django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,579 root INFO creating build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,579 root INFO copying django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,579 root INFO copying django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,579 root INFO creating build/lib/django/contrib/postgres/templates/postgres/widgets
2025-04-22 17:58:54,580 root INFO copying django/contrib/postgres/templates/postgres/widgets/split_array.html -> build/lib/django/contrib/postgres/templates/postgres/widgets
2025-04-22 17:58:54,580 root INFO creating build/lib/django/contrib/gis/locale/af/LC_MESSAGES
2025-04-22 17:58:54,580 root INFO copying django/contrib/gis/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/af/LC_MESSAGES
2025-04-22 17:58:54,580 root INFO copying django/contrib/gis/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/af/LC_MESSAGES
2025-04-22 17:58:54,581 root INFO creating build/lib/django/contrib/gis/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,581 root INFO copying django/contrib/gis/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,581 root INFO copying django/contrib/gis/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,581 root INFO creating build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,582 root INFO copying django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,582 root INFO copying django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,582 root INFO creating build/lib/django/contrib/gis/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,582 root INFO copying django/contrib/gis/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,582 root INFO copying django/contrib/gis/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,583 root INFO creating build/lib/django/contrib/gis/locale/az/LC_MESSAGES
2025-04-22 17:58:54,583 root INFO copying django/contrib/gis/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/az/LC_MESSAGES
2025-04-22 17:58:54,583 root INFO copying django/contrib/gis/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/az/LC_MESSAGES
2025-04-22 17:58:54,583 root INFO creating build/lib/django/contrib/gis/locale/be/LC_MESSAGES
2025-04-22 17:58:54,584 root INFO copying django/contrib/gis/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/be/LC_MESSAGES
2025-04-22 17:58:54,584 root INFO copying django/contrib/gis/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/be/LC_MESSAGES
2025-04-22 17:58:54,584 root INFO creating build/lib/django/contrib/gis/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,584 root INFO copying django/contrib/gis/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,585 root INFO copying django/contrib/gis/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,585 root INFO creating build/lib/django/contrib/gis/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,585 root INFO copying django/contrib/gis/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,585 root INFO copying django/contrib/gis/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,585 root INFO creating build/lib/django/contrib/gis/locale/br/LC_MESSAGES
2025-04-22 17:58:54,586 root INFO copying django/contrib/gis/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/br/LC_MESSAGES
2025-04-22 17:58:54,586 root INFO copying django/contrib/gis/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/br/LC_MESSAGES
2025-04-22 17:58:54,586 root INFO creating build/lib/django/contrib/gis/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,586 root INFO copying django/contrib/gis/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,587 root INFO copying django/contrib/gis/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,587 root INFO creating build/lib/django/contrib/gis/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,587 root INFO copying django/contrib/gis/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,587 root INFO copying django/contrib/gis/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,587 root INFO creating build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,588 root INFO copying django/contrib/gis/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,588 root INFO copying django/contrib/gis/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,588 root INFO creating build/lib/django/contrib/gis/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,588 root INFO copying django/contrib/gis/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,589 root INFO copying django/contrib/gis/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,589 root INFO creating build/lib/django/contrib/gis/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,589 root INFO copying django/contrib/gis/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,589 root INFO copying django/contrib/gis/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,590 root INFO creating build/lib/django/contrib/gis/locale/da/LC_MESSAGES
2025-04-22 17:58:54,590 root INFO copying django/contrib/gis/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/da/LC_MESSAGES
2025-04-22 17:58:54,590 root INFO copying django/contrib/gis/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/da/LC_MESSAGES
2025-04-22 17:58:54,590 root INFO creating build/lib/django/contrib/gis/locale/de/LC_MESSAGES
2025-04-22 17:58:54,590 root INFO copying django/contrib/gis/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/de/LC_MESSAGES
2025-04-22 17:58:54,591 root INFO copying django/contrib/gis/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/de/LC_MESSAGES
2025-04-22 17:58:54,591 root INFO creating build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,591 root INFO copying django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,591 root INFO copying django/contrib/gis/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,592 root INFO creating build/lib/django/contrib/gis/locale/el/LC_MESSAGES
2025-04-22 17:58:54,592 root INFO copying django/contrib/gis/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/el/LC_MESSAGES
2025-04-22 17:58:54,592 root INFO copying django/contrib/gis/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/el/LC_MESSAGES
2025-04-22 17:58:54,592 root INFO creating build/lib/django/contrib/gis/locale/en/LC_MESSAGES
2025-04-22 17:58:54,592 root INFO copying django/contrib/gis/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/en/LC_MESSAGES
2025-04-22 17:58:54,593 root INFO copying django/contrib/gis/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/en/LC_MESSAGES
2025-04-22 17:58:54,593 root INFO creating build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,593 root INFO copying django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,593 root INFO copying django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,594 root INFO creating build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,594 root INFO copying django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,594 root INFO copying django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,594 root INFO creating build/lib/django/contrib/gis/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,594 root INFO copying django/contrib/gis/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,595 root INFO copying django/contrib/gis/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,595 root INFO creating build/lib/django/contrib/gis/locale/es/LC_MESSAGES
2025-04-22 17:58:54,595 root INFO copying django/contrib/gis/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es/LC_MESSAGES
2025-04-22 17:58:54,595 root INFO copying django/contrib/gis/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es/LC_MESSAGES
2025-04-22 17:58:54,596 root INFO creating build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,596 root INFO copying django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,596 root INFO copying django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,596 root INFO creating build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,597 root INFO copying django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,597 root INFO copying django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,597 root INFO creating build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,597 root INFO copying django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,597 root INFO copying django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,598 root INFO creating build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,598 root INFO copying django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,598 root INFO copying django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,598 root INFO creating build/lib/django/contrib/gis/locale/et/LC_MESSAGES
2025-04-22 17:58:54,599 root INFO copying django/contrib/gis/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/et/LC_MESSAGES
2025-04-22 17:58:54,599 root INFO copying django/contrib/gis/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/et/LC_MESSAGES
2025-04-22 17:58:54,599 root INFO creating build/lib/django/contrib/gis/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,599 root INFO copying django/contrib/gis/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,600 root INFO copying django/contrib/gis/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,600 root INFO creating build/lib/django/contrib/gis/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,600 root INFO copying django/contrib/gis/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,600 root INFO copying django/contrib/gis/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,600 root INFO creating build/lib/django/contrib/gis/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,601 root INFO copying django/contrib/gis/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,601 root INFO copying django/contrib/gis/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,601 root INFO creating build/lib/django/contrib/gis/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,601 root INFO copying django/contrib/gis/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,602 root INFO copying django/contrib/gis/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,602 root INFO creating build/lib/django/contrib/gis/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,602 root INFO copying django/contrib/gis/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,602 root INFO copying django/contrib/gis/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,602 root INFO creating build/lib/django/contrib/gis/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,603 root INFO copying django/contrib/gis/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,603 root INFO copying django/contrib/gis/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,603 root INFO creating build/lib/django/contrib/gis/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,604 root INFO copying django/contrib/gis/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,604 root INFO copying django/contrib/gis/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,604 root INFO creating build/lib/django/contrib/gis/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,604 root INFO copying django/contrib/gis/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,605 root INFO copying django/contrib/gis/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,605 root INFO creating build/lib/django/contrib/gis/locale/he/LC_MESSAGES
2025-04-22 17:58:54,605 root INFO copying django/contrib/gis/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/he/LC_MESSAGES
2025-04-22 17:58:54,605 root INFO copying django/contrib/gis/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/he/LC_MESSAGES
2025-04-22 17:58:54,605 root INFO creating build/lib/django/contrib/gis/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,606 root INFO copying django/contrib/gis/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,606 root INFO copying django/contrib/gis/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,606 root INFO creating build/lib/django/contrib/gis/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,606 root INFO copying django/contrib/gis/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,607 root INFO copying django/contrib/gis/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,607 root INFO creating build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,607 root INFO copying django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,607 root INFO copying django/contrib/gis/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,607 root INFO creating build/lib/django/contrib/gis/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,608 root INFO copying django/contrib/gis/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,608 root INFO copying django/contrib/gis/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,608 root INFO creating build/lib/django/contrib/gis/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,608 root INFO copying django/contrib/gis/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,609 root INFO copying django/contrib/gis/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,609 root INFO creating build/lib/django/contrib/gis/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,609 root INFO copying django/contrib/gis/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,609 root INFO copying django/contrib/gis/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,610 root INFO creating build/lib/django/contrib/gis/locale/id/LC_MESSAGES
2025-04-22 17:58:54,610 root INFO copying django/contrib/gis/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/id/LC_MESSAGES
2025-04-22 17:58:54,610 root INFO copying django/contrib/gis/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/id/LC_MESSAGES
2025-04-22 17:58:54,610 root INFO creating build/lib/django/contrib/gis/locale/io/LC_MESSAGES
2025-04-22 17:58:54,610 root INFO copying django/contrib/gis/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/io/LC_MESSAGES
2025-04-22 17:58:54,611 root INFO copying django/contrib/gis/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/io/LC_MESSAGES
2025-04-22 17:58:54,611 root INFO creating build/lib/django/contrib/gis/locale/is/LC_MESSAGES
2025-04-22 17:58:54,611 root INFO copying django/contrib/gis/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/is/LC_MESSAGES
2025-04-22 17:58:54,611 root INFO copying django/contrib/gis/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/is/LC_MESSAGES
2025-04-22 17:58:54,612 root INFO creating build/lib/django/contrib/gis/locale/it/LC_MESSAGES
2025-04-22 17:58:54,612 root INFO copying django/contrib/gis/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/it/LC_MESSAGES
2025-04-22 17:58:54,612 root INFO copying django/contrib/gis/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/it/LC_MESSAGES
2025-04-22 17:58:54,612 root INFO creating build/lib/django/contrib/gis/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,612 root INFO copying django/contrib/gis/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,613 root INFO copying django/contrib/gis/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,613 root INFO creating build/lib/django/contrib/gis/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,613 root INFO copying django/contrib/gis/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,613 root INFO copying django/contrib/gis/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,614 root INFO creating build/lib/django/contrib/gis/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,614 root INFO copying django/contrib/gis/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,614 root INFO copying django/contrib/gis/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,614 root INFO creating build/lib/django/contrib/gis/locale/km/LC_MESSAGES
2025-04-22 17:58:54,615 root INFO copying django/contrib/gis/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/km/LC_MESSAGES
2025-04-22 17:58:54,615 root INFO copying django/contrib/gis/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/km/LC_MESSAGES
2025-04-22 17:58:54,615 root INFO creating build/lib/django/contrib/gis/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,615 root INFO copying django/contrib/gis/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,616 root INFO copying django/contrib/gis/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,616 root INFO creating build/lib/django/contrib/gis/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,616 root INFO copying django/contrib/gis/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,616 root INFO copying django/contrib/gis/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,616 root INFO creating build/lib/django/contrib/gis/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,617 root INFO copying django/contrib/gis/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,617 root INFO copying django/contrib/gis/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,617 root INFO creating build/lib/django/contrib/gis/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,617 root INFO copying django/contrib/gis/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,618 root INFO copying django/contrib/gis/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,618 root INFO creating build/lib/django/contrib/gis/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,618 root INFO copying django/contrib/gis/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,618 root INFO copying django/contrib/gis/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,619 root INFO creating build/lib/django/contrib/gis/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,619 root INFO copying django/contrib/gis/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,619 root INFO copying django/contrib/gis/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,619 root INFO creating build/lib/django/contrib/gis/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,619 root INFO copying django/contrib/gis/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,620 root INFO copying django/contrib/gis/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,620 root INFO creating build/lib/django/contrib/gis/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,620 root INFO copying django/contrib/gis/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,620 root INFO copying django/contrib/gis/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,621 root INFO creating build/lib/django/contrib/gis/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,621 root INFO copying django/contrib/gis/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,621 root INFO copying django/contrib/gis/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,621 root INFO creating build/lib/django/contrib/gis/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,621 root INFO copying django/contrib/gis/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,622 root INFO copying django/contrib/gis/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,622 root INFO creating build/lib/django/contrib/gis/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,622 root INFO copying django/contrib/gis/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,622 root INFO copying django/contrib/gis/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,623 root INFO creating build/lib/django/contrib/gis/locale/my/LC_MESSAGES
2025-04-22 17:58:54,623 root INFO copying django/contrib/gis/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/my/LC_MESSAGES
2025-04-22 17:58:54,623 root INFO copying django/contrib/gis/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/my/LC_MESSAGES
2025-04-22 17:58:54,623 root INFO creating build/lib/django/contrib/gis/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,624 root INFO copying django/contrib/gis/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,624 root INFO copying django/contrib/gis/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,624 root INFO creating build/lib/django/contrib/gis/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,624 root INFO copying django/contrib/gis/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,624 root INFO copying django/contrib/gis/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,625 root INFO creating build/lib/django/contrib/gis/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,625 root INFO copying django/contrib/gis/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,625 root INFO copying django/contrib/gis/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,625 root INFO creating build/lib/django/contrib/gis/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,626 root INFO copying django/contrib/gis/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,626 root INFO copying django/contrib/gis/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,626 root INFO creating build/lib/django/contrib/gis/locale/os/LC_MESSAGES
2025-04-22 17:58:54,626 root INFO copying django/contrib/gis/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/os/LC_MESSAGES
2025-04-22 17:58:54,627 root INFO copying django/contrib/gis/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/os/LC_MESSAGES
2025-04-22 17:58:54,627 root INFO creating build/lib/django/contrib/gis/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,627 root INFO copying django/contrib/gis/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,627 root INFO copying django/contrib/gis/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,627 root INFO creating build/lib/django/contrib/gis/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,628 root INFO copying django/contrib/gis/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,628 root INFO copying django/contrib/gis/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,628 root INFO creating build/lib/django/contrib/gis/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,628 root INFO copying django/contrib/gis/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,629 root INFO copying django/contrib/gis/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,629 root INFO creating build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,629 root INFO copying django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,629 root INFO copying django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,630 root INFO creating build/lib/django/contrib/gis/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,630 root INFO copying django/contrib/gis/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,630 root INFO copying django/contrib/gis/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,630 root INFO creating build/lib/django/contrib/gis/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,630 root INFO copying django/contrib/gis/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,631 root INFO copying django/contrib/gis/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,631 root INFO creating build/lib/django/contrib/gis/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,631 root INFO copying django/contrib/gis/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,631 root INFO copying django/contrib/gis/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,632 root INFO creating build/lib/django/contrib/gis/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,632 root INFO copying django/contrib/gis/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,632 root INFO copying django/contrib/gis/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,632 root INFO creating build/lib/django/contrib/gis/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,632 root INFO copying django/contrib/gis/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,633 root INFO copying django/contrib/gis/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,633 root INFO creating build/lib/django/contrib/gis/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,633 root INFO copying django/contrib/gis/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,633 root INFO copying django/contrib/gis/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,634 root INFO creating build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,634 root INFO copying django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,634 root INFO copying django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,634 root INFO creating build/lib/django/contrib/gis/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,635 root INFO copying django/contrib/gis/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,635 root INFO copying django/contrib/gis/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,635 root INFO creating build/lib/django/contrib/gis/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,635 root INFO copying django/contrib/gis/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,635 root INFO copying django/contrib/gis/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,636 root INFO creating build/lib/django/contrib/gis/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,636 root INFO copying django/contrib/gis/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,636 root INFO copying django/contrib/gis/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,636 root INFO creating build/lib/django/contrib/gis/locale/te/LC_MESSAGES
2025-04-22 17:58:54,637 root INFO copying django/contrib/gis/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/te/LC_MESSAGES
2025-04-22 17:58:54,637 root INFO copying django/contrib/gis/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/te/LC_MESSAGES
2025-04-22 17:58:54,637 root INFO creating build/lib/django/contrib/gis/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,637 root INFO copying django/contrib/gis/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,638 root INFO copying django/contrib/gis/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,638 root INFO creating build/lib/django/contrib/gis/locale/th/LC_MESSAGES
2025-04-22 17:58:54,638 root INFO copying django/contrib/gis/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/th/LC_MESSAGES
2025-04-22 17:58:54,638 root INFO copying django/contrib/gis/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/th/LC_MESSAGES
2025-04-22 17:58:54,638 root INFO creating build/lib/django/contrib/gis/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,639 root INFO copying django/contrib/gis/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,639 root INFO copying django/contrib/gis/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,639 root INFO creating build/lib/django/contrib/gis/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,639 root INFO copying django/contrib/gis/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,640 root INFO copying django/contrib/gis/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,640 root INFO creating build/lib/django/contrib/gis/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,640 root INFO copying django/contrib/gis/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,640 root INFO copying django/contrib/gis/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,641 root INFO creating build/lib/django/contrib/gis/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,641 root INFO copying django/contrib/gis/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,641 root INFO copying django/contrib/gis/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,641 root INFO creating build/lib/django/contrib/gis/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,641 root INFO copying django/contrib/gis/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,642 root INFO copying django/contrib/gis/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,642 root INFO creating build/lib/django/contrib/gis/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,642 root INFO copying django/contrib/gis/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,642 root INFO copying django/contrib/gis/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,643 root INFO creating build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,643 root INFO copying django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,643 root INFO copying django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,643 root INFO creating build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,643 root INFO copying django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,644 root INFO copying django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,644 root INFO creating build/lib/django/contrib/gis/static/gis/css
2025-04-22 17:58:54,644 root INFO copying django/contrib/gis/static/gis/css/ol3.css -> build/lib/django/contrib/gis/static/gis/css
2025-04-22 17:58:54,644 root INFO creating build/lib/django/contrib/gis/static/gis/img
2025-04-22 17:58:54,645 root INFO copying django/contrib/gis/static/gis/img/draw_line_off.svg -> build/lib/django/contrib/gis/static/gis/img
2025-04-22 17:58:54,645 root INFO copying django/contrib/gis/static/gis/img/draw_line_on.svg -> build/lib/django/contrib/gis/static/gis/img
2025-04-22 17:58:54,645 root INFO copying django/contrib/gis/static/gis/img/draw_point_off.svg -> build/lib/django/contrib/gis/static/gis/img
2025-04-22 17:58:54,645 root INFO copying django/contrib/gis/static/gis/img/draw_point_on.svg -> build/lib/django/contrib/gis/static/gis/img
2025-04-22 17:58:54,646 root INFO copying django/contrib/gis/static/gis/img/draw_polygon_off.svg -> build/lib/django/contrib/gis/static/gis/img
2025-04-22 17:58:54,646 root INFO copying django/contrib/gis/static/gis/img/draw_polygon_on.svg -> build/lib/django/contrib/gis/static/gis/img
2025-04-22 17:58:54,646 root INFO creating build/lib/django/contrib/gis/static/gis/js
2025-04-22 17:58:54,646 root INFO copying django/contrib/gis/static/gis/js/OLMapWidget.js -> build/lib/django/contrib/gis/static/gis/js
2025-04-22 17:58:54,646 root INFO creating build/lib/django/contrib/gis/templates/gis
2025-04-22 17:58:54,647 root INFO copying django/contrib/gis/templates/gis/openlayers-osm.html -> build/lib/django/contrib/gis/templates/gis
2025-04-22 17:58:54,647 root INFO copying django/contrib/gis/templates/gis/openlayers.html -> build/lib/django/contrib/gis/templates/gis
2025-04-22 17:58:54,647 root INFO creating build/lib/django/contrib/gis/templates/gis/admin
2025-04-22 17:58:54,647 root INFO copying django/contrib/gis/templates/gis/admin/openlayers.html -> build/lib/django/contrib/gis/templates/gis/admin
2025-04-22 17:58:54,648 root INFO copying django/contrib/gis/templates/gis/admin/openlayers.js -> build/lib/django/contrib/gis/templates/gis/admin
2025-04-22 17:58:54,648 root INFO copying django/contrib/gis/templates/gis/admin/osm.html -> build/lib/django/contrib/gis/templates/gis/admin
2025-04-22 17:58:54,648 root INFO copying django/contrib/gis/templates/gis/admin/osm.js -> build/lib/django/contrib/gis/templates/gis/admin
2025-04-22 17:58:54,648 root INFO creating build/lib/django/contrib/gis/templates/gis/kml
2025-04-22 17:58:54,648 root INFO copying django/contrib/gis/templates/gis/kml/base.kml -> build/lib/django/contrib/gis/templates/gis/kml
2025-04-22 17:58:54,649 root INFO copying django/contrib/gis/templates/gis/kml/placemarks.kml -> build/lib/django/contrib/gis/templates/gis/kml
2025-04-22 17:58:54,649 root INFO creating build/lib/django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 17:58:54,649 root INFO copying django/contrib/admin/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 17:58:54,649 root INFO copying django/contrib/admin/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 17:58:54,650 root INFO copying django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 17:58:54,650 root INFO copying django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 17:58:54,650 root INFO creating build/lib/django/contrib/admin/locale/am/LC_MESSAGES
2025-04-22 17:58:54,650 root INFO copying django/contrib/admin/locale/am/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/am/LC_MESSAGES
2025-04-22 17:58:54,651 root INFO copying django/contrib/admin/locale/am/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/am/LC_MESSAGES
2025-04-22 17:58:54,651 root INFO creating build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,651 root INFO copying django/contrib/admin/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,651 root INFO copying django/contrib/admin/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,652 root INFO copying django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,652 root INFO copying django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,652 root INFO creating build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,652 root INFO copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,653 root INFO copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,653 root INFO copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,653 root INFO copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,654 root INFO creating build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,654 root INFO copying django/contrib/admin/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,654 root INFO copying django/contrib/admin/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,654 root INFO copying django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,655 root INFO copying django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,655 root INFO creating build/lib/django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 17:58:54,655 root INFO copying django/contrib/admin/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 17:58:54,655 root INFO copying django/contrib/admin/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 17:58:54,656 root INFO copying django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 17:58:54,656 root INFO copying django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 17:58:54,656 root INFO creating build/lib/django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 17:58:54,656 root INFO copying django/contrib/admin/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 17:58:54,657 root INFO copying django/contrib/admin/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 17:58:54,657 root INFO copying django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 17:58:54,657 root INFO copying django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 17:58:54,657 root INFO creating build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,658 root INFO copying django/contrib/admin/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,658 root INFO copying django/contrib/admin/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,658 root INFO copying django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,659 root INFO copying django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,659 root INFO creating build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,659 root INFO copying django/contrib/admin/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,659 root INFO copying django/contrib/admin/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,660 root INFO copying django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,660 root INFO copying django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,660 root INFO creating build/lib/django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 17:58:54,660 root INFO copying django/contrib/admin/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 17:58:54,661 root INFO copying django/contrib/admin/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 17:58:54,661 root INFO copying django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 17:58:54,661 root INFO copying django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 17:58:54,661 root INFO creating build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,661 root INFO copying django/contrib/admin/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,662 root INFO copying django/contrib/admin/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,662 root INFO copying django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,662 root INFO copying django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,662 root INFO creating build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,663 root INFO copying django/contrib/admin/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,663 root INFO copying django/contrib/admin/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,663 root INFO copying django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,664 root INFO copying django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,664 root INFO creating build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,664 root INFO copying django/contrib/admin/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,664 root INFO copying django/contrib/admin/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,665 root INFO copying django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,665 root INFO copying django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,665 root INFO creating build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,665 root INFO copying django/contrib/admin/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,666 root INFO copying django/contrib/admin/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,666 root INFO copying django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,666 root INFO copying django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,666 root INFO creating build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,667 root INFO copying django/contrib/admin/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,667 root INFO copying django/contrib/admin/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,667 root INFO copying django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,667 root INFO copying django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,668 root INFO creating build/lib/django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 17:58:54,668 root INFO copying django/contrib/admin/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 17:58:54,668 root INFO copying django/contrib/admin/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 17:58:54,668 root INFO copying django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 17:58:54,669 root INFO copying django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 17:58:54,669 root INFO creating build/lib/django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 17:58:54,669 root INFO copying django/contrib/admin/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 17:58:54,669 root INFO copying django/contrib/admin/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 17:58:54,670 root INFO copying django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 17:58:54,670 root INFO copying django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 17:58:54,670 root INFO creating build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,670 root INFO copying django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,671 root INFO copying django/contrib/admin/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,671 root INFO copying django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,671 root INFO copying django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,672 root INFO creating build/lib/django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 17:58:54,672 root INFO copying django/contrib/admin/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 17:58:54,672 root INFO copying django/contrib/admin/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 17:58:54,672 root INFO copying django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 17:58:54,673 root INFO copying django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 17:58:54,673 root INFO creating build/lib/django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 17:58:54,673 root INFO copying django/contrib/admin/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 17:58:54,673 root INFO copying django/contrib/admin/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 17:58:54,674 root INFO copying django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 17:58:54,674 root INFO copying django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 17:58:54,674 root INFO creating build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,674 root INFO copying django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,675 root INFO copying django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,675 root INFO copying django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,675 root INFO copying django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,675 root INFO creating build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,676 root INFO copying django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,676 root INFO copying django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,676 root INFO copying django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,676 root INFO copying django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,677 root INFO creating build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,677 root INFO copying django/contrib/admin/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,677 root INFO copying django/contrib/admin/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,677 root INFO copying django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,678 root INFO copying django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,678 root INFO creating build/lib/django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 17:58:54,678 root INFO copying django/contrib/admin/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 17:58:54,678 root INFO copying django/contrib/admin/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 17:58:54,679 root INFO copying django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 17:58:54,679 root INFO copying django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 17:58:54,679 root INFO creating build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,679 root INFO copying django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,680 root INFO copying django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,680 root INFO copying django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,680 root INFO copying django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,680 root INFO creating build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,681 root INFO copying django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,681 root INFO copying django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,681 root INFO copying django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,681 root INFO copying django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,682 root INFO creating build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,682 root INFO copying django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,682 root INFO copying django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,682 root INFO copying django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,683 root INFO copying django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,683 root INFO creating build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,683 root INFO copying django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,683 root INFO copying django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,684 root INFO copying django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,684 root INFO copying django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,684 root INFO creating build/lib/django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 17:58:54,684 root INFO copying django/contrib/admin/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 17:58:54,685 root INFO copying django/contrib/admin/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 17:58:54,685 root INFO copying django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 17:58:54,685 root INFO copying django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 17:58:54,685 root INFO creating build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,686 root INFO copying django/contrib/admin/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,686 root INFO copying django/contrib/admin/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,686 root INFO copying django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,687 root INFO copying django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,687 root INFO creating build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,687 root INFO copying django/contrib/admin/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,687 root INFO copying django/contrib/admin/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,688 root INFO copying django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,688 root INFO copying django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,688 root INFO creating build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,688 root INFO copying django/contrib/admin/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,689 root INFO copying django/contrib/admin/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,689 root INFO copying django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,689 root INFO copying django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,689 root INFO creating build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,690 root INFO copying django/contrib/admin/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,690 root INFO copying django/contrib/admin/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,690 root INFO copying django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,690 root INFO copying django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,691 root INFO creating build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,691 root INFO copying django/contrib/admin/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,691 root INFO copying django/contrib/admin/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,691 root INFO copying django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,692 root INFO copying django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,692 root INFO creating build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,692 root INFO copying django/contrib/admin/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,692 root INFO copying django/contrib/admin/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,693 root INFO copying django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,693 root INFO copying django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,693 root INFO creating build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,693 root INFO copying django/contrib/admin/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,694 root INFO copying django/contrib/admin/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,694 root INFO copying django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,694 root INFO copying django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,695 root INFO creating build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,695 root INFO copying django/contrib/admin/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,695 root INFO copying django/contrib/admin/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,695 root INFO copying django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,696 root INFO copying django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,696 root INFO creating build/lib/django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 17:58:54,696 root INFO copying django/contrib/admin/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 17:58:54,696 root INFO copying django/contrib/admin/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 17:58:54,697 root INFO copying django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 17:58:54,697 root INFO copying django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 17:58:54,697 root INFO creating build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,697 root INFO copying django/contrib/admin/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,698 root INFO copying django/contrib/admin/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,698 root INFO copying django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,698 root INFO copying django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,698 root INFO creating build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,699 root INFO copying django/contrib/admin/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,699 root INFO copying django/contrib/admin/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,699 root INFO copying django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,699 root INFO copying django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,700 root INFO creating build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,700 root INFO copying django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,700 root INFO copying django/contrib/admin/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,700 root INFO copying django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,701 root INFO copying django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,701 root INFO creating build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,701 root INFO copying django/contrib/admin/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,701 root INFO copying django/contrib/admin/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,702 root INFO copying django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,702 root INFO copying django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,702 root INFO creating build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,702 root INFO copying django/contrib/admin/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,703 root INFO copying django/contrib/admin/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,703 root INFO copying django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,703 root INFO copying django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,704 root INFO creating build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,704 root INFO copying django/contrib/admin/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,704 root INFO copying django/contrib/admin/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,704 root INFO copying django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,705 root INFO copying django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,705 root INFO creating build/lib/django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 17:58:54,705 root INFO copying django/contrib/admin/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 17:58:54,705 root INFO copying django/contrib/admin/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 17:58:54,706 root INFO copying django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 17:58:54,706 root INFO copying django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 17:58:54,706 root INFO creating build/lib/django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 17:58:54,706 root INFO copying django/contrib/admin/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 17:58:54,707 root INFO copying django/contrib/admin/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 17:58:54,707 root INFO copying django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 17:58:54,707 root INFO copying django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 17:58:54,707 root INFO creating build/lib/django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 17:58:54,707 root INFO copying django/contrib/admin/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 17:58:54,708 root INFO copying django/contrib/admin/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 17:58:54,708 root INFO copying django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 17:58:54,708 root INFO copying django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 17:58:54,709 root INFO creating build/lib/django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 17:58:54,709 root INFO copying django/contrib/admin/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 17:58:54,709 root INFO copying django/contrib/admin/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 17:58:54,709 root INFO copying django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 17:58:54,710 root INFO copying django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 17:58:54,710 root INFO creating build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,710 root INFO copying django/contrib/admin/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,710 root INFO copying django/contrib/admin/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,711 root INFO copying django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,711 root INFO copying django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,711 root INFO creating build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,711 root INFO copying django/contrib/admin/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,712 root INFO copying django/contrib/admin/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,712 root INFO copying django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,712 root INFO copying django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,712 root INFO creating build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,713 root INFO copying django/contrib/admin/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,713 root INFO copying django/contrib/admin/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,713 root INFO copying django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,714 root INFO copying django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 17:58:54,714 root INFO creating build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,714 root INFO copying django/contrib/admin/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,714 root INFO copying django/contrib/admin/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,715 root INFO copying django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,715 root INFO copying django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,715 root INFO creating build/lib/django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 17:58:54,715 root INFO copying django/contrib/admin/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 17:58:54,715 root INFO copying django/contrib/admin/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 17:58:54,716 root INFO copying django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 17:58:54,716 root INFO copying django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 17:58:54,716 root INFO creating build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,716 root INFO copying django/contrib/admin/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,717 root INFO copying django/contrib/admin/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,717 root INFO copying django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,717 root INFO copying django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,717 root INFO creating build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,718 root INFO copying django/contrib/admin/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,718 root INFO copying django/contrib/admin/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,718 root INFO copying django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,718 root INFO copying django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,719 root INFO creating build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,719 root INFO copying django/contrib/admin/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,719 root INFO copying django/contrib/admin/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,720 root INFO copying django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,720 root INFO copying django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,720 root INFO creating build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,720 root INFO copying django/contrib/admin/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,721 root INFO copying django/contrib/admin/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,721 root INFO copying django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,721 root INFO copying django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,721 root INFO creating build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,721 root INFO copying django/contrib/admin/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,722 root INFO copying django/contrib/admin/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,722 root INFO copying django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,722 root INFO copying django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,723 root INFO creating build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,723 root INFO copying django/contrib/admin/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,723 root INFO copying django/contrib/admin/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,723 root INFO copying django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,724 root INFO copying django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,724 root INFO creating build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,724 root INFO copying django/contrib/admin/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,724 root INFO copying django/contrib/admin/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,725 root INFO copying django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,725 root INFO copying django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,725 root INFO creating build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,725 root INFO copying django/contrib/admin/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,726 root INFO copying django/contrib/admin/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,726 root INFO copying django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,726 root INFO copying django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,726 root INFO creating build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,727 root INFO copying django/contrib/admin/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,727 root INFO copying django/contrib/admin/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,727 root INFO copying django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,727 root INFO copying django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,728 root INFO creating build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,728 root INFO copying django/contrib/admin/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,728 root INFO copying django/contrib/admin/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,728 root INFO copying django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,729 root INFO copying django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,729 root INFO creating build/lib/django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,729 root INFO copying django/contrib/admin/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,729 root INFO copying django/contrib/admin/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,730 root INFO copying django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,730 root INFO copying django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,730 root INFO creating build/lib/django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 17:58:54,730 root INFO copying django/contrib/admin/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 17:58:54,731 root INFO copying django/contrib/admin/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 17:58:54,731 root INFO copying django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 17:58:54,731 root INFO copying django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 17:58:54,731 root INFO creating build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,732 root INFO copying django/contrib/admin/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,732 root INFO copying django/contrib/admin/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,732 root INFO copying django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,732 root INFO copying django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,733 root INFO creating build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,733 root INFO copying django/contrib/admin/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,733 root INFO copying django/contrib/admin/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,733 root INFO copying django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,734 root INFO copying django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,734 root INFO creating build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,734 root INFO copying django/contrib/admin/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,734 root INFO copying django/contrib/admin/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,735 root INFO copying django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,735 root INFO copying django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,735 root INFO creating build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,735 root INFO copying django/contrib/admin/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,736 root INFO copying django/contrib/admin/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,736 root INFO copying django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,736 root INFO copying django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,736 root INFO creating build/lib/django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 17:58:54,737 root INFO copying django/contrib/admin/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 17:58:54,737 root INFO copying django/contrib/admin/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 17:58:54,737 root INFO copying django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 17:58:54,737 root INFO copying django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 17:58:54,738 root INFO creating build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,738 root INFO copying django/contrib/admin/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,738 root INFO copying django/contrib/admin/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,738 root INFO copying django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,739 root INFO copying django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,739 root INFO creating build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,739 root INFO copying django/contrib/admin/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,739 root INFO copying django/contrib/admin/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,740 root INFO copying django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,740 root INFO copying django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,740 root INFO creating build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,740 root INFO copying django/contrib/admin/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,741 root INFO copying django/contrib/admin/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,741 root INFO copying django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,741 root INFO copying django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,741 root INFO creating build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,742 root INFO copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,742 root INFO copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,742 root INFO copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,742 root INFO copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,743 root INFO creating build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,743 root INFO copying django/contrib/admin/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,743 root INFO copying django/contrib/admin/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,744 root INFO copying django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,744 root INFO copying django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,744 root INFO creating build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,744 root INFO copying django/contrib/admin/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,744 root INFO copying django/contrib/admin/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,745 root INFO copying django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,745 root INFO copying django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,745 root INFO creating build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,745 root INFO copying django/contrib/admin/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,746 root INFO copying django/contrib/admin/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,746 root INFO copying django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,746 root INFO copying django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,747 root INFO creating build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,747 root INFO copying django/contrib/admin/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,747 root INFO copying django/contrib/admin/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,747 root INFO copying django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,748 root INFO copying django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,748 root INFO creating build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,748 root INFO copying django/contrib/admin/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,748 root INFO copying django/contrib/admin/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,749 root INFO copying django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,749 root INFO copying django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,749 root INFO creating build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,749 root INFO copying django/contrib/admin/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,750 root INFO copying django/contrib/admin/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,750 root INFO copying django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,750 root INFO copying django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,750 root INFO creating build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,751 root INFO copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,751 root INFO copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,751 root INFO copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,751 root INFO copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,752 root INFO creating build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,752 root INFO copying django/contrib/admin/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,752 root INFO copying django/contrib/admin/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,752 root INFO copying django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,753 root INFO copying django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,753 root INFO creating build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,753 root INFO copying django/contrib/admin/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,753 root INFO copying django/contrib/admin/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,754 root INFO copying django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,754 root INFO copying django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,754 root INFO creating build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,754 root INFO copying django/contrib/admin/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,755 root INFO copying django/contrib/admin/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,755 root INFO copying django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,755 root INFO copying django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,755 root INFO creating build/lib/django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 17:58:54,756 root INFO copying django/contrib/admin/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 17:58:54,756 root INFO copying django/contrib/admin/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 17:58:54,756 root INFO copying django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 17:58:54,757 root INFO copying django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 17:58:54,757 root INFO creating build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,757 root INFO copying django/contrib/admin/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,757 root INFO copying django/contrib/admin/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,758 root INFO copying django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,758 root INFO copying django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,758 root INFO creating build/lib/django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 17:58:54,758 root INFO copying django/contrib/admin/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 17:58:54,759 root INFO copying django/contrib/admin/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 17:58:54,759 root INFO copying django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 17:58:54,759 root INFO copying django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 17:58:54,760 root INFO creating build/lib/django/contrib/admin/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,760 root INFO copying django/contrib/admin/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,760 root INFO copying django/contrib/admin/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,760 root INFO creating build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,761 root INFO copying django/contrib/admin/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,761 root INFO copying django/contrib/admin/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,761 root INFO copying django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,762 root INFO copying django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,762 root INFO creating build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,762 root INFO copying django/contrib/admin/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,762 root INFO copying django/contrib/admin/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,763 root INFO copying django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,763 root INFO copying django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,763 root INFO creating build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,763 root INFO copying django/contrib/admin/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,764 root INFO copying django/contrib/admin/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,764 root INFO copying django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,764 root INFO copying django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,765 root INFO creating build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,765 root INFO copying django/contrib/admin/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,765 root INFO copying django/contrib/admin/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,765 root INFO copying django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,766 root INFO copying django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,766 root INFO creating build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,766 root INFO copying django/contrib/admin/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,767 root INFO copying django/contrib/admin/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,767 root INFO copying django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,767 root INFO copying django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,768 root INFO creating build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,768 root INFO copying django/contrib/admin/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,768 root INFO copying django/contrib/admin/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,768 root INFO copying django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,769 root INFO copying django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,769 root INFO creating build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,769 root INFO copying django/contrib/admin/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,769 root INFO copying django/contrib/admin/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,770 root INFO copying django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,770 root INFO copying django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,770 root INFO creating build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,770 root INFO copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,771 root INFO copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,771 root INFO copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,771 root INFO copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,772 root INFO creating build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,772 root INFO copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,772 root INFO copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,772 root INFO copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,773 root INFO copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,773 root INFO creating build/lib/django/contrib/admin/static/admin/css
2025-04-22 17:58:54,773 root INFO copying django/contrib/admin/static/admin/css/autocomplete.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 17:58:54,773 root INFO copying django/contrib/admin/static/admin/css/base.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 17:58:54,774 root INFO copying django/contrib/admin/static/admin/css/changelists.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 17:58:54,774 root INFO copying django/contrib/admin/static/admin/css/dark_mode.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 17:58:54,774 root INFO copying django/contrib/admin/static/admin/css/dashboard.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 17:58:54,775 root INFO copying django/contrib/admin/static/admin/css/forms.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 17:58:54,775 root INFO copying django/contrib/admin/static/admin/css/login.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 17:58:54,775 root INFO copying django/contrib/admin/static/admin/css/nav_sidebar.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 17:58:54,775 root INFO copying django/contrib/admin/static/admin/css/responsive.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 17:58:54,776 root INFO copying django/contrib/admin/static/admin/css/responsive_rtl.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 17:58:54,776 root INFO copying django/contrib/admin/static/admin/css/rtl.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 17:58:54,776 root INFO copying django/contrib/admin/static/admin/css/widgets.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 17:58:54,776 root INFO creating build/lib/django/contrib/admin/static/admin/css/vendor/select2
2025-04-22 17:58:54,777 root INFO copying django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md -> build/lib/django/contrib/admin/static/admin/css/vendor/select2
2025-04-22 17:58:54,777 root INFO copying django/contrib/admin/static/admin/css/vendor/select2/select2.css -> build/lib/django/contrib/admin/static/admin/css/vendor/select2
2025-04-22 17:58:54,777 root INFO copying django/contrib/admin/static/admin/css/vendor/select2/select2.min.css -> build/lib/django/contrib/admin/static/admin/css/vendor/select2
2025-04-22 17:58:54,777 root INFO creating build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,777 root INFO copying django/contrib/admin/static/admin/img/LICENSE -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,778 root INFO copying django/contrib/admin/static/admin/img/README.txt -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,778 root INFO copying django/contrib/admin/static/admin/img/calendar-icons.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,778 root INFO copying django/contrib/admin/static/admin/img/icon-addlink.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,778 root INFO copying django/contrib/admin/static/admin/img/icon-alert.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,779 root INFO copying django/contrib/admin/static/admin/img/icon-calendar.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,779 root INFO copying django/contrib/admin/static/admin/img/icon-changelink.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,779 root INFO copying django/contrib/admin/static/admin/img/icon-clock.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,779 root INFO copying django/contrib/admin/static/admin/img/icon-deletelink.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,780 root INFO copying django/contrib/admin/static/admin/img/icon-no.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,780 root INFO copying django/contrib/admin/static/admin/img/icon-unknown-alt.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,780 root INFO copying django/contrib/admin/static/admin/img/icon-unknown.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,780 root INFO copying django/contrib/admin/static/admin/img/icon-viewlink.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,781 root INFO copying django/contrib/admin/static/admin/img/icon-yes.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,781 root INFO copying django/contrib/admin/static/admin/img/inline-delete.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,781 root INFO copying django/contrib/admin/static/admin/img/search.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,781 root INFO copying django/contrib/admin/static/admin/img/selector-icons.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,782 root INFO copying django/contrib/admin/static/admin/img/sorting-icons.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,782 root INFO copying django/contrib/admin/static/admin/img/tooltag-add.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,782 root INFO copying django/contrib/admin/static/admin/img/tooltag-arrowright.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 17:58:54,782 root INFO creating build/lib/django/contrib/admin/static/admin/img/gis
2025-04-22 17:58:54,783 root INFO copying django/contrib/admin/static/admin/img/gis/move_vertex_off.svg -> build/lib/django/contrib/admin/static/admin/img/gis
2025-04-22 17:58:54,783 root INFO copying django/contrib/admin/static/admin/img/gis/move_vertex_on.svg -> build/lib/django/contrib/admin/static/admin/img/gis
2025-04-22 17:58:54,783 root INFO creating build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,783 root INFO copying django/contrib/admin/static/admin/js/SelectBox.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,783 root INFO copying django/contrib/admin/static/admin/js/SelectFilter2.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,784 root INFO copying django/contrib/admin/static/admin/js/actions.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,784 root INFO copying django/contrib/admin/static/admin/js/autocomplete.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,784 root INFO copying django/contrib/admin/static/admin/js/calendar.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,785 root INFO copying django/contrib/admin/static/admin/js/cancel.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,785 root INFO copying django/contrib/admin/static/admin/js/change_form.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,785 root INFO copying django/contrib/admin/static/admin/js/collapse.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,785 root INFO copying django/contrib/admin/static/admin/js/core.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,786 root INFO copying django/contrib/admin/static/admin/js/filters.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,786 root INFO copying django/contrib/admin/static/admin/js/inlines.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,786 root INFO copying django/contrib/admin/static/admin/js/jquery.init.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,786 root INFO copying django/contrib/admin/static/admin/js/nav_sidebar.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,787 root INFO copying django/contrib/admin/static/admin/js/popup_response.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,787 root INFO copying django/contrib/admin/static/admin/js/prepopulate.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,787 root INFO copying django/contrib/admin/static/admin/js/prepopulate_init.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,787 root INFO copying django/contrib/admin/static/admin/js/theme.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,788 root INFO copying django/contrib/admin/static/admin/js/urlify.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 17:58:54,788 root INFO creating build/lib/django/contrib/admin/static/admin/js/admin
2025-04-22 17:58:54,788 root INFO copying django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js -> build/lib/django/contrib/admin/static/admin/js/admin
2025-04-22 17:58:54,788 root INFO copying django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js -> build/lib/django/contrib/admin/static/admin/js/admin
2025-04-22 17:58:54,789 root INFO creating build/lib/django/contrib/admin/static/admin/js/vendor/jquery
2025-04-22 17:58:54,789 root INFO copying django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt -> build/lib/django/contrib/admin/static/admin/js/vendor/jquery
2025-04-22 17:58:54,789 root INFO copying django/contrib/admin/static/admin/js/vendor/jquery/jquery.js -> build/lib/django/contrib/admin/static/admin/js/vendor/jquery
2025-04-22 17:58:54,790 root INFO copying django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js -> build/lib/django/contrib/admin/static/admin/js/vendor/jquery
2025-04-22 17:58:54,790 root INFO creating build/lib/django/contrib/admin/static/admin/js/vendor/select2
2025-04-22 17:58:54,790 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md -> build/lib/django/contrib/admin/static/admin/js/vendor/select2
2025-04-22 17:58:54,791 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/select2.full.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2
2025-04-22 17:58:54,791 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2
2025-04-22 17:58:54,791 root INFO creating build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,792 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,792 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,792 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,792 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,793 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,793 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,793 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,793 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,794 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,794 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,794 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,794 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,795 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,795 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,795 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,795 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,796 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,796 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,796 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,796 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,797 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,797 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,797 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,797 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,798 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,798 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,798 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,798 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,799 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,799 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,799 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,800 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,800 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,800 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,800 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,801 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,801 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,801 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,801 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,802 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,802 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,802 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,802 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,803 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,803 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,803 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,803 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,804 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,804 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,804 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,804 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,805 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,805 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,805 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,805 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,806 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,806 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,806 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,806 root INFO copying django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:54,807 root INFO creating build/lib/django/contrib/admin/static/admin/js/vendor/xregexp
2025-04-22 17:58:54,807 root INFO copying django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt -> build/lib/django/contrib/admin/static/admin/js/vendor/xregexp
2025-04-22 17:58:54,807 root INFO copying django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js -> build/lib/django/contrib/admin/static/admin/js/vendor/xregexp
2025-04-22 17:58:54,808 root INFO copying django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js -> build/lib/django/contrib/admin/static/admin/js/vendor/xregexp
2025-04-22 17:58:54,808 root INFO creating build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,809 root INFO copying django/contrib/admin/templates/admin/404.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,809 root INFO copying django/contrib/admin/templates/admin/500.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,809 root INFO copying django/contrib/admin/templates/admin/actions.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,809 root INFO copying django/contrib/admin/templates/admin/app_index.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,810 root INFO copying django/contrib/admin/templates/admin/app_list.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,810 root INFO copying django/contrib/admin/templates/admin/base.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,810 root INFO copying django/contrib/admin/templates/admin/base_site.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,810 root INFO copying django/contrib/admin/templates/admin/change_form.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,811 root INFO copying django/contrib/admin/templates/admin/change_form_object_tools.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,811 root INFO copying django/contrib/admin/templates/admin/change_list.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,811 root INFO copying django/contrib/admin/templates/admin/change_list_object_tools.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,811 root INFO copying django/contrib/admin/templates/admin/change_list_results.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,812 root INFO copying django/contrib/admin/templates/admin/color_theme_toggle.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,812 root INFO copying django/contrib/admin/templates/admin/date_hierarchy.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,812 root INFO copying django/contrib/admin/templates/admin/delete_confirmation.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,812 root INFO copying django/contrib/admin/templates/admin/delete_selected_confirmation.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,813 root INFO copying django/contrib/admin/templates/admin/filter.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,813 root INFO copying django/contrib/admin/templates/admin/index.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,813 root INFO copying django/contrib/admin/templates/admin/invalid_setup.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,813 root INFO copying django/contrib/admin/templates/admin/login.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,814 root INFO copying django/contrib/admin/templates/admin/nav_sidebar.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,814 root INFO copying django/contrib/admin/templates/admin/object_history.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,814 root INFO copying django/contrib/admin/templates/admin/pagination.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,814 root INFO copying django/contrib/admin/templates/admin/popup_response.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,815 root INFO copying django/contrib/admin/templates/admin/prepopulated_fields_js.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,815 root INFO copying django/contrib/admin/templates/admin/search_form.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,815 root INFO copying django/contrib/admin/templates/admin/submit_line.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 17:58:54,815 root INFO creating build/lib/django/contrib/admin/templates/admin/auth/user
2025-04-22 17:58:54,815 root INFO copying django/contrib/admin/templates/admin/auth/user/add_form.html -> build/lib/django/contrib/admin/templates/admin/auth/user
2025-04-22 17:58:54,816 root INFO copying django/contrib/admin/templates/admin/auth/user/change_password.html -> build/lib/django/contrib/admin/templates/admin/auth/user
2025-04-22 17:58:54,816 root INFO creating build/lib/django/contrib/admin/templates/admin/edit_inline
2025-04-22 17:58:54,816 root INFO copying django/contrib/admin/templates/admin/edit_inline/stacked.html -> build/lib/django/contrib/admin/templates/admin/edit_inline
2025-04-22 17:58:54,816 root INFO copying django/contrib/admin/templates/admin/edit_inline/tabular.html -> build/lib/django/contrib/admin/templates/admin/edit_inline
2025-04-22 17:58:54,817 root INFO creating build/lib/django/contrib/admin/templates/admin/includes
2025-04-22 17:58:54,817 root INFO copying django/contrib/admin/templates/admin/includes/fieldset.html -> build/lib/django/contrib/admin/templates/admin/includes
2025-04-22 17:58:54,817 root INFO copying django/contrib/admin/templates/admin/includes/object_delete_summary.html -> build/lib/django/contrib/admin/templates/admin/includes
2025-04-22 17:58:54,817 root INFO creating build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:54,817 root INFO copying django/contrib/admin/templates/admin/widgets/clearable_file_input.html -> build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:54,818 root INFO copying django/contrib/admin/templates/admin/widgets/date.html -> build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:54,818 root INFO copying django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html -> build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:54,818 root INFO copying django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html -> build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:54,818 root INFO copying django/contrib/admin/templates/admin/widgets/radio.html -> build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:54,819 root INFO copying django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html -> build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:54,819 root INFO copying django/contrib/admin/templates/admin/widgets/split_datetime.html -> build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:54,819 root INFO copying django/contrib/admin/templates/admin/widgets/time.html -> build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:54,820 root INFO copying django/contrib/admin/templates/admin/widgets/url.html -> build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:54,820 root INFO creating build/lib/django/contrib/admin/templates/registration
2025-04-22 17:58:54,820 root INFO copying django/contrib/admin/templates/registration/logged_out.html -> build/lib/django/contrib/admin/templates/registration
2025-04-22 17:58:54,820 root INFO copying django/contrib/admin/templates/registration/password_change_done.html -> build/lib/django/contrib/admin/templates/registration
2025-04-22 17:58:54,820 root INFO copying django/contrib/admin/templates/registration/password_change_form.html -> build/lib/django/contrib/admin/templates/registration
2025-04-22 17:58:54,821 root INFO copying django/contrib/admin/templates/registration/password_reset_complete.html -> build/lib/django/contrib/admin/templates/registration
2025-04-22 17:58:54,821 root INFO copying django/contrib/admin/templates/registration/password_reset_confirm.html -> build/lib/django/contrib/admin/templates/registration
2025-04-22 17:58:54,821 root INFO copying django/contrib/admin/templates/registration/password_reset_done.html -> build/lib/django/contrib/admin/templates/registration
2025-04-22 17:58:54,821 root INFO copying django/contrib/admin/templates/registration/password_reset_email.html -> build/lib/django/contrib/admin/templates/registration
2025-04-22 17:58:54,822 root INFO copying django/contrib/admin/templates/registration/password_reset_form.html -> build/lib/django/contrib/admin/templates/registration
2025-04-22 17:58:54,822 root INFO creating build/lib/django/contrib/humanize/locale/af/LC_MESSAGES
2025-04-22 17:58:54,822 root INFO copying django/contrib/humanize/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/af/LC_MESSAGES
2025-04-22 17:58:54,822 root INFO copying django/contrib/humanize/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/af/LC_MESSAGES
2025-04-22 17:58:54,823 root INFO creating build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,823 root INFO copying django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,823 root INFO copying django/contrib/humanize/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES
2025-04-22 17:58:54,824 root INFO creating build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,824 root INFO copying django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,824 root INFO copying django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:54,824 root INFO creating build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,825 root INFO copying django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,825 root INFO copying django/contrib/humanize/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES
2025-04-22 17:58:54,825 root INFO creating build/lib/django/contrib/humanize/locale/az/LC_MESSAGES
2025-04-22 17:58:54,825 root INFO copying django/contrib/humanize/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/az/LC_MESSAGES
2025-04-22 17:58:54,826 root INFO copying django/contrib/humanize/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/az/LC_MESSAGES
2025-04-22 17:58:54,826 root INFO creating build/lib/django/contrib/humanize/locale/be/LC_MESSAGES
2025-04-22 17:58:54,826 root INFO copying django/contrib/humanize/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/be/LC_MESSAGES
2025-04-22 17:58:54,826 root INFO copying django/contrib/humanize/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/be/LC_MESSAGES
2025-04-22 17:58:54,827 root INFO creating build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,827 root INFO copying django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,827 root INFO copying django/contrib/humanize/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES
2025-04-22 17:58:54,827 root INFO creating build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,827 root INFO copying django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,828 root INFO copying django/contrib/humanize/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES
2025-04-22 17:58:54,828 root INFO creating build/lib/django/contrib/humanize/locale/br/LC_MESSAGES
2025-04-22 17:58:54,828 root INFO copying django/contrib/humanize/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/br/LC_MESSAGES
2025-04-22 17:58:54,828 root INFO copying django/contrib/humanize/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/br/LC_MESSAGES
2025-04-22 17:58:54,829 root INFO creating build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,829 root INFO copying django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,829 root INFO copying django/contrib/humanize/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES
2025-04-22 17:58:54,829 root INFO creating build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,830 root INFO copying django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,830 root INFO copying django/contrib/humanize/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,830 root INFO creating build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,830 root INFO copying django/contrib/humanize/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,830 root INFO copying django/contrib/humanize/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES
2025-04-22 17:58:54,831 root INFO creating build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,831 root INFO copying django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,831 root INFO copying django/contrib/humanize/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES
2025-04-22 17:58:54,831 root INFO creating build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,832 root INFO copying django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,832 root INFO copying django/contrib/humanize/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES
2025-04-22 17:58:54,832 root INFO creating build/lib/django/contrib/humanize/locale/da/LC_MESSAGES
2025-04-22 17:58:54,832 root INFO copying django/contrib/humanize/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/da/LC_MESSAGES
2025-04-22 17:58:54,833 root INFO copying django/contrib/humanize/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/da/LC_MESSAGES
2025-04-22 17:58:54,833 root INFO creating build/lib/django/contrib/humanize/locale/de/LC_MESSAGES
2025-04-22 17:58:54,833 root INFO copying django/contrib/humanize/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/de/LC_MESSAGES
2025-04-22 17:58:54,833 root INFO copying django/contrib/humanize/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/de/LC_MESSAGES
2025-04-22 17:58:54,834 root INFO creating build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,834 root INFO copying django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,834 root INFO copying django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES
2025-04-22 17:58:54,834 root INFO creating build/lib/django/contrib/humanize/locale/el/LC_MESSAGES
2025-04-22 17:58:54,835 root INFO copying django/contrib/humanize/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/el/LC_MESSAGES
2025-04-22 17:58:54,835 root INFO copying django/contrib/humanize/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/el/LC_MESSAGES
2025-04-22 17:58:54,835 root INFO creating build/lib/django/contrib/humanize/locale/en/LC_MESSAGES
2025-04-22 17:58:54,835 root INFO copying django/contrib/humanize/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/en/LC_MESSAGES
2025-04-22 17:58:54,836 root INFO copying django/contrib/humanize/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/en/LC_MESSAGES
2025-04-22 17:58:54,836 root INFO creating build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,836 root INFO copying django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,836 root INFO copying django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,837 root INFO creating build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,837 root INFO copying django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,837 root INFO copying django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,837 root INFO creating build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,838 root INFO copying django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,838 root INFO copying django/contrib/humanize/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES
2025-04-22 17:58:54,838 root INFO creating build/lib/django/contrib/humanize/locale/es/LC_MESSAGES
2025-04-22 17:58:54,838 root INFO copying django/contrib/humanize/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es/LC_MESSAGES
2025-04-22 17:58:54,839 root INFO copying django/contrib/humanize/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es/LC_MESSAGES
2025-04-22 17:58:54,839 root INFO creating build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,839 root INFO copying django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,839 root INFO copying django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:54,840 root INFO creating build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,840 root INFO copying django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,840 root INFO copying django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:54,840 root INFO creating build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,840 root INFO copying django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,841 root INFO copying django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:54,841 root INFO creating build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,841 root INFO copying django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,841 root INFO copying django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,842 root INFO creating build/lib/django/contrib/humanize/locale/et/LC_MESSAGES
2025-04-22 17:58:54,842 root INFO copying django/contrib/humanize/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/et/LC_MESSAGES
2025-04-22 17:58:54,842 root INFO copying django/contrib/humanize/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/et/LC_MESSAGES
2025-04-22 17:58:54,842 root INFO creating build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,843 root INFO copying django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,843 root INFO copying django/contrib/humanize/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES
2025-04-22 17:58:54,843 root INFO creating build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,843 root INFO copying django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,844 root INFO copying django/contrib/humanize/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES
2025-04-22 17:58:54,844 root INFO creating build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,844 root INFO copying django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,844 root INFO copying django/contrib/humanize/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES
2025-04-22 17:58:54,845 root INFO creating build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,845 root INFO copying django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,845 root INFO copying django/contrib/humanize/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES
2025-04-22 17:58:54,845 root INFO creating build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,845 root INFO copying django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,846 root INFO copying django/contrib/humanize/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES
2025-04-22 17:58:54,846 root INFO creating build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,846 root INFO copying django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,847 root INFO copying django/contrib/humanize/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES
2025-04-22 17:58:54,847 root INFO creating build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,847 root INFO copying django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,847 root INFO copying django/contrib/humanize/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES
2025-04-22 17:58:54,847 root INFO creating build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,848 root INFO copying django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,848 root INFO copying django/contrib/humanize/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES
2025-04-22 17:58:54,848 root INFO creating build/lib/django/contrib/humanize/locale/he/LC_MESSAGES
2025-04-22 17:58:54,848 root INFO copying django/contrib/humanize/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/he/LC_MESSAGES
2025-04-22 17:58:54,849 root INFO copying django/contrib/humanize/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/he/LC_MESSAGES
2025-04-22 17:58:54,849 root INFO creating build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,849 root INFO copying django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,849 root INFO copying django/contrib/humanize/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES
2025-04-22 17:58:54,850 root INFO creating build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,850 root INFO copying django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,850 root INFO copying django/contrib/humanize/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES
2025-04-22 17:58:54,850 root INFO creating build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,850 root INFO copying django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,851 root INFO copying django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES
2025-04-22 17:58:54,851 root INFO creating build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,851 root INFO copying django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,851 root INFO copying django/contrib/humanize/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES
2025-04-22 17:58:54,852 root INFO creating build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,852 root INFO copying django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,852 root INFO copying django/contrib/humanize/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES
2025-04-22 17:58:54,852 root INFO creating build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,853 root INFO copying django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,853 root INFO copying django/contrib/humanize/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES
2025-04-22 17:58:54,853 root INFO creating build/lib/django/contrib/humanize/locale/id/LC_MESSAGES
2025-04-22 17:58:54,853 root INFO copying django/contrib/humanize/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/id/LC_MESSAGES
2025-04-22 17:58:54,854 root INFO copying django/contrib/humanize/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/id/LC_MESSAGES
2025-04-22 17:58:54,854 root INFO creating build/lib/django/contrib/humanize/locale/io/LC_MESSAGES
2025-04-22 17:58:54,854 root INFO copying django/contrib/humanize/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/io/LC_MESSAGES
2025-04-22 17:58:54,854 root INFO copying django/contrib/humanize/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/io/LC_MESSAGES
2025-04-22 17:58:54,855 root INFO creating build/lib/django/contrib/humanize/locale/is/LC_MESSAGES
2025-04-22 17:58:54,855 root INFO copying django/contrib/humanize/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/is/LC_MESSAGES
2025-04-22 17:58:54,855 root INFO copying django/contrib/humanize/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/is/LC_MESSAGES
2025-04-22 17:58:54,855 root INFO creating build/lib/django/contrib/humanize/locale/it/LC_MESSAGES
2025-04-22 17:58:54,855 root INFO copying django/contrib/humanize/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/it/LC_MESSAGES
2025-04-22 17:58:54,856 root INFO copying django/contrib/humanize/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/it/LC_MESSAGES
2025-04-22 17:58:54,856 root INFO creating build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,856 root INFO copying django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,856 root INFO copying django/contrib/humanize/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES
2025-04-22 17:58:54,857 root INFO creating build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,857 root INFO copying django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,857 root INFO copying django/contrib/humanize/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES
2025-04-22 17:58:54,857 root INFO creating build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,858 root INFO copying django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,858 root INFO copying django/contrib/humanize/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES
2025-04-22 17:58:54,858 root INFO creating build/lib/django/contrib/humanize/locale/km/LC_MESSAGES
2025-04-22 17:58:54,858 root INFO copying django/contrib/humanize/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/km/LC_MESSAGES
2025-04-22 17:58:54,859 root INFO copying django/contrib/humanize/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/km/LC_MESSAGES
2025-04-22 17:58:54,859 root INFO creating build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,859 root INFO copying django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,859 root INFO copying django/contrib/humanize/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES
2025-04-22 17:58:54,860 root INFO creating build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,860 root INFO copying django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,860 root INFO copying django/contrib/humanize/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES
2025-04-22 17:58:54,860 root INFO creating build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,860 root INFO copying django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,861 root INFO copying django/contrib/humanize/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES
2025-04-22 17:58:54,861 root INFO creating build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,861 root INFO copying django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,861 root INFO copying django/contrib/humanize/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,862 root INFO creating build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,862 root INFO copying django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,862 root INFO copying django/contrib/humanize/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES
2025-04-22 17:58:54,862 root INFO creating build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,863 root INFO copying django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,863 root INFO copying django/contrib/humanize/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,863 root INFO creating build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,863 root INFO copying django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,864 root INFO copying django/contrib/humanize/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES
2025-04-22 17:58:54,864 root INFO creating build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,864 root INFO copying django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,864 root INFO copying django/contrib/humanize/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES
2025-04-22 17:58:54,865 root INFO creating build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,865 root INFO copying django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,865 root INFO copying django/contrib/humanize/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES
2025-04-22 17:58:54,865 root INFO creating build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,865 root INFO copying django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,866 root INFO copying django/contrib/humanize/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,866 root INFO creating build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,866 root INFO copying django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,867 root INFO copying django/contrib/humanize/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES
2025-04-22 17:58:54,867 root INFO creating build/lib/django/contrib/humanize/locale/my/LC_MESSAGES
2025-04-22 17:58:54,867 root INFO copying django/contrib/humanize/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/my/LC_MESSAGES
2025-04-22 17:58:54,867 root INFO copying django/contrib/humanize/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/my/LC_MESSAGES
2025-04-22 17:58:54,868 root INFO creating build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,868 root INFO copying django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,868 root INFO copying django/contrib/humanize/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES
2025-04-22 17:58:54,868 root INFO creating build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,868 root INFO copying django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,869 root INFO copying django/contrib/humanize/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES
2025-04-22 17:58:54,869 root INFO creating build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,869 root INFO copying django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,869 root INFO copying django/contrib/humanize/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES
2025-04-22 17:58:54,870 root INFO creating build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,870 root INFO copying django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,870 root INFO copying django/contrib/humanize/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES
2025-04-22 17:58:54,870 root INFO creating build/lib/django/contrib/humanize/locale/os/LC_MESSAGES
2025-04-22 17:58:54,871 root INFO copying django/contrib/humanize/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/os/LC_MESSAGES
2025-04-22 17:58:54,871 root INFO copying django/contrib/humanize/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/os/LC_MESSAGES
2025-04-22 17:58:54,871 root INFO creating build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,871 root INFO copying django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,872 root INFO copying django/contrib/humanize/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES
2025-04-22 17:58:54,872 root INFO creating build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,872 root INFO copying django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,872 root INFO copying django/contrib/humanize/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES
2025-04-22 17:58:54,873 root INFO creating build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,873 root INFO copying django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,873 root INFO copying django/contrib/humanize/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES
2025-04-22 17:58:54,873 root INFO creating build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,873 root INFO copying django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,874 root INFO copying django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:54,874 root INFO creating build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,874 root INFO copying django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,874 root INFO copying django/contrib/humanize/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES
2025-04-22 17:58:54,875 root INFO creating build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,875 root INFO copying django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,875 root INFO copying django/contrib/humanize/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES
2025-04-22 17:58:54,875 root INFO creating build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,876 root INFO copying django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,876 root INFO copying django/contrib/humanize/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES
2025-04-22 17:58:54,876 root INFO creating build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,876 root INFO copying django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,877 root INFO copying django/contrib/humanize/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES
2025-04-22 17:58:54,877 root INFO creating build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,877 root INFO copying django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,877 root INFO copying django/contrib/humanize/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES
2025-04-22 17:58:54,878 root INFO creating build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,878 root INFO copying django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,878 root INFO copying django/contrib/humanize/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES
2025-04-22 17:58:54,878 root INFO creating build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,878 root INFO copying django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,879 root INFO copying django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:54,879 root INFO creating build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,879 root INFO copying django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,879 root INFO copying django/contrib/humanize/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES
2025-04-22 17:58:54,880 root INFO creating build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,880 root INFO copying django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,880 root INFO copying django/contrib/humanize/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,880 root INFO creating build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,881 root INFO copying django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,881 root INFO copying django/contrib/humanize/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES
2025-04-22 17:58:54,881 root INFO creating build/lib/django/contrib/humanize/locale/te/LC_MESSAGES
2025-04-22 17:58:54,881 root INFO copying django/contrib/humanize/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/te/LC_MESSAGES
2025-04-22 17:58:54,882 root INFO copying django/contrib/humanize/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/te/LC_MESSAGES
2025-04-22 17:58:54,882 root INFO creating build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,882 root INFO copying django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,882 root INFO copying django/contrib/humanize/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES
2025-04-22 17:58:54,882 root INFO creating build/lib/django/contrib/humanize/locale/th/LC_MESSAGES
2025-04-22 17:58:54,883 root INFO copying django/contrib/humanize/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/th/LC_MESSAGES
2025-04-22 17:58:54,883 root INFO copying django/contrib/humanize/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/th/LC_MESSAGES
2025-04-22 17:58:54,883 root INFO creating build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,883 root INFO copying django/contrib/humanize/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,884 root INFO copying django/contrib/humanize/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES
2025-04-22 17:58:54,884 root INFO creating build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,884 root INFO copying django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,884 root INFO copying django/contrib/humanize/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES
2025-04-22 17:58:54,885 root INFO creating build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,885 root INFO copying django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,885 root INFO copying django/contrib/humanize/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES
2025-04-22 17:58:54,885 root INFO creating build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,885 root INFO copying django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,886 root INFO copying django/contrib/humanize/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES
2025-04-22 17:58:54,886 root INFO creating build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,886 root INFO copying django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,886 root INFO copying django/contrib/humanize/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES
2025-04-22 17:58:54,887 root INFO creating build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,887 root INFO copying django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,887 root INFO copying django/contrib/humanize/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES
2025-04-22 17:58:54,887 root INFO creating build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,888 root INFO copying django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,888 root INFO copying django/contrib/humanize/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES
2025-04-22 17:58:54,888 root INFO creating build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,888 root INFO copying django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,889 root INFO copying django/contrib/humanize/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES
2025-04-22 17:58:54,889 root INFO creating build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,889 root INFO copying django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,889 root INFO copying django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:54,890 root INFO creating build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,890 root INFO copying django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,890 root INFO copying django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:54,892 root INFO copying django/contrib/gis/geos/LICENSE -> build/lib/django/contrib/gis/geos
2025-04-22 17:58:54,892 root INFO copying django/contrib/gis/gdal/LICENSE -> build/lib/django/contrib/gis/gdal
2025-04-22 17:58:54,923 root INFO installing to build/bdist.linux-armv8l/wheel
2025-04-22 17:58:54,923 root INFO running install
2025-04-22 17:58:54,933 root INFO running install_lib
2025-04-22 17:58:54,937 root INFO creating build/bdist.linux-armv8l/wheel
2025-04-22 17:58:54,937 root INFO creating build/bdist.linux-armv8l/wheel/django
2025-04-22 17:58:54,937 root INFO copying build/lib/django/__init__.py -> build/bdist.linux-armv8l/wheel/./django
2025-04-22 17:58:54,938 root INFO creating build/bdist.linux-armv8l/wheel/django/db
2025-04-22 17:58:54,938 root INFO copying build/lib/django/db/__init__.py -> build/bdist.linux-armv8l/wheel/./django/db
2025-04-22 17:58:54,938 root INFO creating build/bdist.linux-armv8l/wheel/django/db/models
2025-04-22 17:58:54,938 root INFO copying build/lib/django/db/models/__init__.py -> build/bdist.linux-armv8l/wheel/./django/db/models
2025-04-22 17:58:54,939 root INFO copying build/lib/django/db/models/options.py -> build/bdist.linux-armv8l/wheel/./django/db/models
2025-04-22 17:58:54,939 root INFO copying build/lib/django/db/models/enums.py -> build/bdist.linux-armv8l/wheel/./django/db/models
2025-04-22 17:58:54,939 root INFO copying build/lib/django/db/models/signals.py -> build/bdist.linux-armv8l/wheel/./django/db/models
2025-04-22 17:58:54,939 root INFO copying build/lib/django/db/models/query.py -> build/bdist.linux-armv8l/wheel/./django/db/models
2025-04-22 17:58:54,940 root INFO copying build/lib/django/db/models/lookups.py -> build/bdist.linux-armv8l/wheel/./django/db/models
2025-04-22 17:58:54,940 root INFO copying build/lib/django/db/models/manager.py -> build/bdist.linux-armv8l/wheel/./django/db/models
2025-04-22 17:58:54,940 root INFO creating build/bdist.linux-armv8l/wheel/django/db/models/functions
2025-04-22 17:58:54,940 root INFO copying build/lib/django/db/models/functions/__init__.py -> build/bdist.linux-armv8l/wheel/./django/db/models/functions
2025-04-22 17:58:54,941 root INFO copying build/lib/django/db/models/functions/datetime.py -> build/bdist.linux-armv8l/wheel/./django/db/models/functions
2025-04-22 17:58:54,941 root INFO copying build/lib/django/db/models/functions/window.py -> build/bdist.linux-armv8l/wheel/./django/db/models/functions
2025-04-22 17:58:54,941 root INFO copying build/lib/django/db/models/functions/comparison.py -> build/bdist.linux-armv8l/wheel/./django/db/models/functions
2025-04-22 17:58:54,941 root INFO copying build/lib/django/db/models/functions/math.py -> build/bdist.linux-armv8l/wheel/./django/db/models/functions
2025-04-22 17:58:54,941 root INFO copying build/lib/django/db/models/functions/text.py -> build/bdist.linux-armv8l/wheel/./django/db/models/functions
2025-04-22 17:58:54,942 root INFO copying build/lib/django/db/models/functions/mixins.py -> build/bdist.linux-armv8l/wheel/./django/db/models/functions
2025-04-22 17:58:54,942 root INFO creating build/bdist.linux-armv8l/wheel/django/db/models/sql
2025-04-22 17:58:54,942 root INFO copying build/lib/django/db/models/sql/__init__.py -> build/bdist.linux-armv8l/wheel/./django/db/models/sql
2025-04-22 17:58:54,942 root INFO copying build/lib/django/db/models/sql/query.py -> build/bdist.linux-armv8l/wheel/./django/db/models/sql
2025-04-22 17:58:54,943 root INFO copying build/lib/django/db/models/sql/compiler.py -> build/bdist.linux-armv8l/wheel/./django/db/models/sql
2025-04-22 17:58:54,943 root INFO copying build/lib/django/db/models/sql/subqueries.py -> build/bdist.linux-armv8l/wheel/./django/db/models/sql
2025-04-22 17:58:54,943 root INFO copying build/lib/django/db/models/sql/datastructures.py -> build/bdist.linux-armv8l/wheel/./django/db/models/sql
2025-04-22 17:58:54,943 root INFO copying build/lib/django/db/models/sql/where.py -> build/bdist.linux-armv8l/wheel/./django/db/models/sql
2025-04-22 17:58:54,944 root INFO copying build/lib/django/db/models/sql/constants.py -> build/bdist.linux-armv8l/wheel/./django/db/models/sql
2025-04-22 17:58:54,944 root INFO copying build/lib/django/db/models/indexes.py -> build/bdist.linux-armv8l/wheel/./django/db/models
2025-04-22 17:58:54,944 root INFO copying build/lib/django/db/models/utils.py -> build/bdist.linux-armv8l/wheel/./django/db/models
2025-04-22 17:58:54,944 root INFO creating build/bdist.linux-armv8l/wheel/django/db/models/fields
2025-04-22 17:58:54,944 root INFO copying build/lib/django/db/models/fields/__init__.py -> build/bdist.linux-armv8l/wheel/./django/db/models/fields
2025-04-22 17:58:54,945 root INFO copying build/lib/django/db/models/fields/related_descriptors.py -> build/bdist.linux-armv8l/wheel/./django/db/models/fields
2025-04-22 17:58:54,945 root INFO copying build/lib/django/db/models/fields/json.py -> build/bdist.linux-armv8l/wheel/./django/db/models/fields
2025-04-22 17:58:54,945 root INFO copying build/lib/django/db/models/fields/related_lookups.py -> build/bdist.linux-armv8l/wheel/./django/db/models/fields
2025-04-22 17:58:54,946 root INFO copying build/lib/django/db/models/fields/proxy.py -> build/bdist.linux-armv8l/wheel/./django/db/models/fields
2025-04-22 17:58:54,946 root INFO copying build/lib/django/db/models/fields/reverse_related.py -> build/bdist.linux-armv8l/wheel/./django/db/models/fields
2025-04-22 17:58:54,946 root INFO copying build/lib/django/db/models/fields/files.py -> build/bdist.linux-armv8l/wheel/./django/db/models/fields
2025-04-22 17:58:54,946 root INFO copying build/lib/django/db/models/fields/related.py -> build/bdist.linux-armv8l/wheel/./django/db/models/fields
2025-04-22 17:58:54,947 root INFO copying build/lib/django/db/models/fields/mixins.py -> build/bdist.linux-armv8l/wheel/./django/db/models/fields
2025-04-22 17:58:54,947 root INFO copying build/lib/django/db/models/deletion.py -> build/bdist.linux-armv8l/wheel/./django/db/models
2025-04-22 17:58:54,947 root INFO copying build/lib/django/db/models/expressions.py -> build/bdist.linux-armv8l/wheel/./django/db/models
2025-04-22 17:58:54,947 root INFO copying build/lib/django/db/models/constraints.py -> build/bdist.linux-armv8l/wheel/./django/db/models
2025-04-22 17:58:54,947 root INFO copying build/lib/django/db/models/query_utils.py -> build/bdist.linux-armv8l/wheel/./django/db/models
2025-04-22 17:58:54,948 root INFO copying build/lib/django/db/models/constants.py -> build/bdist.linux-armv8l/wheel/./django/db/models
2025-04-22 17:58:54,948 root INFO copying build/lib/django/db/models/base.py -> build/bdist.linux-armv8l/wheel/./django/db/models
2025-04-22 17:58:54,948 root INFO copying build/lib/django/db/models/aggregates.py -> build/bdist.linux-armv8l/wheel/./django/db/models
2025-04-22 17:58:54,949 root INFO creating build/bdist.linux-armv8l/wheel/django/db/migrations
2025-04-22 17:58:54,949 root INFO copying build/lib/django/db/migrations/__init__.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations
2025-04-22 17:58:54,949 root INFO copying build/lib/django/db/migrations/state.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations
2025-04-22 17:58:54,949 root INFO copying build/lib/django/db/migrations/graph.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations
2025-04-22 17:58:54,949 root INFO copying build/lib/django/db/migrations/writer.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations
2025-04-22 17:58:54,950 root INFO copying build/lib/django/db/migrations/serializer.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations
2025-04-22 17:58:54,950 root INFO copying build/lib/django/db/migrations/loader.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations
2025-04-22 17:58:54,950 root INFO copying build/lib/django/db/migrations/executor.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations
2025-04-22 17:58:54,950 root INFO copying build/lib/django/db/migrations/exceptions.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations
2025-04-22 17:58:54,950 root INFO copying build/lib/django/db/migrations/optimizer.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations
2025-04-22 17:58:54,951 root INFO copying build/lib/django/db/migrations/utils.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations
2025-04-22 17:58:54,951 root INFO copying build/lib/django/db/migrations/recorder.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations
2025-04-22 17:58:54,951 root INFO copying build/lib/django/db/migrations/migration.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations
2025-04-22 17:58:54,951 root INFO copying build/lib/django/db/migrations/autodetector.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations
2025-04-22 17:58:54,952 root INFO copying build/lib/django/db/migrations/questioner.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations
2025-04-22 17:58:54,952 root INFO creating build/bdist.linux-armv8l/wheel/django/db/migrations/operations
2025-04-22 17:58:54,952 root INFO copying build/lib/django/db/migrations/operations/__init__.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations/operations
2025-04-22 17:58:54,952 root INFO copying build/lib/django/db/migrations/operations/models.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations/operations
2025-04-22 17:58:54,953 root INFO copying build/lib/django/db/migrations/operations/fields.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations/operations
2025-04-22 17:58:54,953 root INFO copying build/lib/django/db/migrations/operations/special.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations/operations
2025-04-22 17:58:54,953 root INFO copying build/lib/django/db/migrations/operations/base.py -> build/bdist.linux-armv8l/wheel/./django/db/migrations/operations
2025-04-22 17:58:54,953 root INFO copying build/lib/django/db/utils.py -> build/bdist.linux-armv8l/wheel/./django/db
2025-04-22 17:58:54,953 root INFO copying build/lib/django/db/transaction.py -> build/bdist.linux-armv8l/wheel/./django/db
2025-04-22 17:58:54,954 root INFO creating build/bdist.linux-armv8l/wheel/django/db/backends
2025-04-22 17:58:54,954 root INFO copying build/lib/django/db/backends/__init__.py -> build/bdist.linux-armv8l/wheel/./django/db/backends
2025-04-22 17:58:54,954 root INFO copying build/lib/django/db/backends/signals.py -> build/bdist.linux-armv8l/wheel/./django/db/backends
2025-04-22 17:58:54,954 root INFO creating build/bdist.linux-armv8l/wheel/django/db/backends/base
2025-04-22 17:58:54,955 root INFO copying build/lib/django/db/backends/base/__init__.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/base
2025-04-22 17:58:54,955 root INFO copying build/lib/django/db/backends/base/schema.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/base
2025-04-22 17:58:54,955 root INFO copying build/lib/django/db/backends/base/features.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/base
2025-04-22 17:58:54,955 root INFO copying build/lib/django/db/backends/base/operations.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/base
2025-04-22 17:58:54,955 root INFO copying build/lib/django/db/backends/base/validation.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/base
2025-04-22 17:58:54,956 root INFO copying build/lib/django/db/backends/base/creation.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/base
2025-04-22 17:58:54,956 root INFO copying build/lib/django/db/backends/base/introspection.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/base
2025-04-22 17:58:54,956 root INFO copying build/lib/django/db/backends/base/base.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/base
2025-04-22 17:58:54,956 root INFO copying build/lib/django/db/backends/base/client.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/base
2025-04-22 17:58:54,957 root INFO copying build/lib/django/db/backends/ddl_references.py -> build/bdist.linux-armv8l/wheel/./django/db/backends
2025-04-22 17:58:54,957 root INFO copying build/lib/django/db/backends/utils.py -> build/bdist.linux-armv8l/wheel/./django/db/backends
2025-04-22 17:58:54,957 root INFO creating build/bdist.linux-armv8l/wheel/django/db/backends/postgresql
2025-04-22 17:58:54,957 root INFO copying build/lib/django/db/backends/postgresql/__init__.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/postgresql
2025-04-22 17:58:54,957 root INFO copying build/lib/django/db/backends/postgresql/schema.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/postgresql
2025-04-22 17:58:54,958 root INFO copying build/lib/django/db/backends/postgresql/features.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/postgresql
2025-04-22 17:58:54,958 root INFO copying build/lib/django/db/backends/postgresql/operations.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/postgresql
2025-04-22 17:58:54,958 root INFO copying build/lib/django/db/backends/postgresql/psycopg_any.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/postgresql
2025-04-22 17:58:54,958 root INFO copying build/lib/django/db/backends/postgresql/creation.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/postgresql
2025-04-22 17:58:54,958 root INFO copying build/lib/django/db/backends/postgresql/introspection.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/postgresql
2025-04-22 17:58:54,959 root INFO copying build/lib/django/db/backends/postgresql/base.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/postgresql
2025-04-22 17:58:54,959 root INFO copying build/lib/django/db/backends/postgresql/client.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/postgresql
2025-04-22 17:58:54,959 root INFO creating build/bdist.linux-armv8l/wheel/django/db/backends/dummy
2025-04-22 17:58:54,959 root INFO copying build/lib/django/db/backends/dummy/__init__.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/dummy
2025-04-22 17:58:54,960 root INFO copying build/lib/django/db/backends/dummy/features.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/dummy
2025-04-22 17:58:54,960 root INFO copying build/lib/django/db/backends/dummy/base.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/dummy
2025-04-22 17:58:54,960 root INFO creating build/bdist.linux-armv8l/wheel/django/db/backends/sqlite3
2025-04-22 17:58:54,960 root INFO copying build/lib/django/db/backends/sqlite3/__init__.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/sqlite3
2025-04-22 17:58:54,960 root INFO copying build/lib/django/db/backends/sqlite3/schema.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/sqlite3
2025-04-22 17:58:54,961 root INFO copying build/lib/django/db/backends/sqlite3/features.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/sqlite3
2025-04-22 17:58:54,961 root INFO copying build/lib/django/db/backends/sqlite3/operations.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/sqlite3
2025-04-22 17:58:54,961 root INFO copying build/lib/django/db/backends/sqlite3/creation.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/sqlite3
2025-04-22 17:58:54,961 root INFO copying build/lib/django/db/backends/sqlite3/introspection.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/sqlite3
2025-04-22 17:58:54,961 root INFO copying build/lib/django/db/backends/sqlite3/_functions.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/sqlite3
2025-04-22 17:58:54,962 root INFO copying build/lib/django/db/backends/sqlite3/base.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/sqlite3
2025-04-22 17:58:54,962 root INFO copying build/lib/django/db/backends/sqlite3/client.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/sqlite3
2025-04-22 17:58:54,962 root INFO creating build/bdist.linux-armv8l/wheel/django/db/backends/oracle
2025-04-22 17:58:54,962 root INFO copying build/lib/django/db/backends/oracle/__init__.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/oracle
2025-04-22 17:58:54,962 root INFO copying build/lib/django/db/backends/oracle/functions.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/oracle
2025-04-22 17:58:54,963 root INFO copying build/lib/django/db/backends/oracle/schema.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/oracle
2025-04-22 17:58:54,963 root INFO copying build/lib/django/db/backends/oracle/features.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/oracle
2025-04-22 17:58:54,963 root INFO copying build/lib/django/db/backends/oracle/operations.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/oracle
2025-04-22 17:58:54,963 root INFO copying build/lib/django/db/backends/oracle/utils.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/oracle
2025-04-22 17:58:54,964 root INFO copying build/lib/django/db/backends/oracle/validation.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/oracle
2025-04-22 17:58:54,964 root INFO copying build/lib/django/db/backends/oracle/creation.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/oracle
2025-04-22 17:58:54,964 root INFO copying build/lib/django/db/backends/oracle/introspection.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/oracle
2025-04-22 17:58:54,964 root INFO copying build/lib/django/db/backends/oracle/base.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/oracle
2025-04-22 17:58:54,964 root INFO copying build/lib/django/db/backends/oracle/client.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/oracle
2025-04-22 17:58:54,965 root INFO creating build/bdist.linux-armv8l/wheel/django/db/backends/mysql
2025-04-22 17:58:54,965 root INFO copying build/lib/django/db/backends/mysql/__init__.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/mysql
2025-04-22 17:58:54,965 root INFO copying build/lib/django/db/backends/mysql/compiler.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/mysql
2025-04-22 17:58:54,965 root INFO copying build/lib/django/db/backends/mysql/schema.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/mysql
2025-04-22 17:58:54,965 root INFO copying build/lib/django/db/backends/mysql/features.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/mysql
2025-04-22 17:58:54,966 root INFO copying build/lib/django/db/backends/mysql/operations.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/mysql
2025-04-22 17:58:54,966 root INFO copying build/lib/django/db/backends/mysql/validation.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/mysql
2025-04-22 17:58:54,966 root INFO copying build/lib/django/db/backends/mysql/creation.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/mysql
2025-04-22 17:58:54,966 root INFO copying build/lib/django/db/backends/mysql/introspection.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/mysql
2025-04-22 17:58:54,967 root INFO copying build/lib/django/db/backends/mysql/base.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/mysql
2025-04-22 17:58:54,967 root INFO copying build/lib/django/db/backends/mysql/client.py -> build/bdist.linux-armv8l/wheel/./django/db/backends/mysql
2025-04-22 17:58:54,967 root INFO creating build/bdist.linux-armv8l/wheel/django/views
2025-04-22 17:58:54,967 root INFO copying build/lib/django/views/__init__.py -> build/bdist.linux-armv8l/wheel/./django/views
2025-04-22 17:58:54,967 root INFO copying build/lib/django/views/i18n.py -> build/bdist.linux-armv8l/wheel/./django/views
2025-04-22 17:58:54,968 root INFO copying build/lib/django/views/defaults.py -> build/bdist.linux-armv8l/wheel/./django/views
2025-04-22 17:58:54,968 root INFO creating build/bdist.linux-armv8l/wheel/django/views/generic
2025-04-22 17:58:54,968 root INFO copying build/lib/django/views/generic/__init__.py -> build/bdist.linux-armv8l/wheel/./django/views/generic
2025-04-22 17:58:54,968 root INFO copying build/lib/django/views/generic/list.py -> build/bdist.linux-armv8l/wheel/./django/views/generic
2025-04-22 17:58:54,968 root INFO copying build/lib/django/views/generic/detail.py -> build/bdist.linux-armv8l/wheel/./django/views/generic
2025-04-22 17:58:54,969 root INFO copying build/lib/django/views/generic/base.py -> build/bdist.linux-armv8l/wheel/./django/views/generic
2025-04-22 17:58:54,969 root INFO copying build/lib/django/views/generic/dates.py -> build/bdist.linux-armv8l/wheel/./django/views/generic
2025-04-22 17:58:54,969 root INFO copying build/lib/django/views/generic/edit.py -> build/bdist.linux-armv8l/wheel/./django/views/generic
2025-04-22 17:58:54,969 root INFO copying build/lib/django/views/csrf.py -> build/bdist.linux-armv8l/wheel/./django/views
2025-04-22 17:58:54,970 root INFO creating build/bdist.linux-armv8l/wheel/django/views/templates
2025-04-22 17:58:54,970 root INFO copying build/lib/django/views/templates/technical_500.html -> build/bdist.linux-armv8l/wheel/./django/views/templates
2025-04-22 17:58:54,970 root INFO copying build/lib/django/views/templates/technical_500.txt -> build/bdist.linux-armv8l/wheel/./django/views/templates
2025-04-22 17:58:54,970 root INFO copying build/lib/django/views/templates/technical_404.html -> build/bdist.linux-armv8l/wheel/./django/views/templates
2025-04-22 17:58:54,970 root INFO copying build/lib/django/views/templates/default_urlconf.html -> build/bdist.linux-armv8l/wheel/./django/views/templates
2025-04-22 17:58:54,971 root INFO creating build/bdist.linux-armv8l/wheel/django/views/decorators
2025-04-22 17:58:54,971 root INFO copying build/lib/django/views/decorators/__init__.py -> build/bdist.linux-armv8l/wheel/./django/views/decorators
2025-04-22 17:58:54,971 root INFO copying build/lib/django/views/decorators/cache.py -> build/bdist.linux-armv8l/wheel/./django/views/decorators
2025-04-22 17:58:54,971 root INFO copying build/lib/django/views/decorators/http.py -> build/bdist.linux-armv8l/wheel/./django/views/decorators
2025-04-22 17:58:54,971 root INFO copying build/lib/django/views/decorators/vary.py -> build/bdist.linux-armv8l/wheel/./django/views/decorators
2025-04-22 17:58:54,972 root INFO copying build/lib/django/views/decorators/gzip.py -> build/bdist.linux-armv8l/wheel/./django/views/decorators
2025-04-22 17:58:54,972 root INFO copying build/lib/django/views/decorators/csrf.py -> build/bdist.linux-armv8l/wheel/./django/views/decorators
2025-04-22 17:58:54,972 root INFO copying build/lib/django/views/decorators/clickjacking.py -> build/bdist.linux-armv8l/wheel/./django/views/decorators
2025-04-22 17:58:54,972 root INFO copying build/lib/django/views/decorators/debug.py -> build/bdist.linux-armv8l/wheel/./django/views/decorators
2025-04-22 17:58:54,972 root INFO copying build/lib/django/views/decorators/common.py -> build/bdist.linux-armv8l/wheel/./django/views/decorators
2025-04-22 17:58:54,973 root INFO copying build/lib/django/views/static.py -> build/bdist.linux-armv8l/wheel/./django/views
2025-04-22 17:58:54,973 root INFO copying build/lib/django/views/debug.py -> build/bdist.linux-armv8l/wheel/./django/views
2025-04-22 17:58:54,973 root INFO creating build/bdist.linux-armv8l/wheel/django/middleware
2025-04-22 17:58:54,973 root INFO copying build/lib/django/middleware/__init__.py -> build/bdist.linux-armv8l/wheel/./django/middleware
2025-04-22 17:58:54,973 root INFO copying build/lib/django/middleware/locale.py -> build/bdist.linux-armv8l/wheel/./django/middleware
2025-04-22 17:58:54,974 root INFO copying build/lib/django/middleware/cache.py -> build/bdist.linux-armv8l/wheel/./django/middleware
2025-04-22 17:58:54,974 root INFO copying build/lib/django/middleware/http.py -> build/bdist.linux-armv8l/wheel/./django/middleware
2025-04-22 17:58:54,974 root INFO copying build/lib/django/middleware/security.py -> build/bdist.linux-armv8l/wheel/./django/middleware
2025-04-22 17:58:54,974 root INFO copying build/lib/django/middleware/gzip.py -> build/bdist.linux-armv8l/wheel/./django/middleware
2025-04-22 17:58:54,974 root INFO copying build/lib/django/middleware/csrf.py -> build/bdist.linux-armv8l/wheel/./django/middleware
2025-04-22 17:58:54,975 root INFO copying build/lib/django/middleware/clickjacking.py -> build/bdist.linux-armv8l/wheel/./django/middleware
2025-04-22 17:58:54,975 root INFO copying build/lib/django/middleware/common.py -> build/bdist.linux-armv8l/wheel/./django/middleware
2025-04-22 17:58:54,975 root INFO creating build/bdist.linux-armv8l/wheel/django/http
2025-04-22 17:58:54,975 root INFO copying build/lib/django/http/__init__.py -> build/bdist.linux-armv8l/wheel/./django/http
2025-04-22 17:58:54,975 root INFO copying build/lib/django/http/response.py -> build/bdist.linux-armv8l/wheel/./django/http
2025-04-22 17:58:54,976 root INFO copying build/lib/django/http/multipartparser.py -> build/bdist.linux-armv8l/wheel/./django/http
2025-04-22 17:58:54,976 root INFO copying build/lib/django/http/cookie.py -> build/bdist.linux-armv8l/wheel/./django/http
2025-04-22 17:58:54,976 root INFO copying build/lib/django/http/request.py -> build/bdist.linux-armv8l/wheel/./django/http
2025-04-22 17:58:54,976 root INFO creating build/bdist.linux-armv8l/wheel/django/dispatch
2025-04-22 17:58:54,977 root INFO copying build/lib/django/dispatch/__init__.py -> build/bdist.linux-armv8l/wheel/./django/dispatch
2025-04-22 17:58:54,977 root INFO copying build/lib/django/dispatch/dispatcher.py -> build/bdist.linux-armv8l/wheel/./django/dispatch
2025-04-22 17:58:54,977 root INFO copying build/lib/django/dispatch/license.txt -> build/bdist.linux-armv8l/wheel/./django/dispatch
2025-04-22 17:58:54,977 root INFO creating build/bdist.linux-armv8l/wheel/django/urls
2025-04-22 17:58:54,977 root INFO copying build/lib/django/urls/__init__.py -> build/bdist.linux-armv8l/wheel/./django/urls
2025-04-22 17:58:54,978 root INFO copying build/lib/django/urls/converters.py -> build/bdist.linux-armv8l/wheel/./django/urls
2025-04-22 17:58:54,978 root INFO copying build/lib/django/urls/exceptions.py -> build/bdist.linux-armv8l/wheel/./django/urls
2025-04-22 17:58:54,978 root INFO copying build/lib/django/urls/conf.py -> build/bdist.linux-armv8l/wheel/./django/urls
2025-04-22 17:58:54,978 root INFO copying build/lib/django/urls/utils.py -> build/bdist.linux-armv8l/wheel/./django/urls
2025-04-22 17:58:54,978 root INFO copying build/lib/django/urls/resolvers.py -> build/bdist.linux-armv8l/wheel/./django/urls
2025-04-22 17:58:54,979 root INFO copying build/lib/django/urls/base.py -> build/bdist.linux-armv8l/wheel/./django/urls
2025-04-22 17:58:54,979 root INFO creating build/bdist.linux-armv8l/wheel/django/template
2025-04-22 17:58:54,979 root INFO copying build/lib/django/template/__init__.py -> build/bdist.linux-armv8l/wheel/./django/template
2025-04-22 17:58:54,979 root INFO copying build/lib/django/template/library.py -> build/bdist.linux-armv8l/wheel/./django/template
2025-04-22 17:58:54,980 root INFO copying build/lib/django/template/engine.py -> build/bdist.linux-armv8l/wheel/./django/template
2025-04-22 17:58:54,980 root INFO copying build/lib/django/template/response.py -> build/bdist.linux-armv8l/wheel/./django/template
2025-04-22 17:58:54,980 root INFO copying build/lib/django/template/loader_tags.py -> build/bdist.linux-armv8l/wheel/./django/template
2025-04-22 17:58:54,980 root INFO copying build/lib/django/template/loader.py -> build/bdist.linux-armv8l/wheel/./django/template
2025-04-22 17:58:54,980 root INFO copying build/lib/django/template/autoreload.py -> build/bdist.linux-armv8l/wheel/./django/template
2025-04-22 17:58:54,980 root INFO copying build/lib/django/template/exceptions.py -> build/bdist.linux-armv8l/wheel/./django/template
2025-04-22 17:58:54,981 root INFO copying build/lib/django/template/smartif.py -> build/bdist.linux-armv8l/wheel/./django/template
2025-04-22 17:58:54,981 root INFO copying build/lib/django/template/defaulttags.py -> build/bdist.linux-armv8l/wheel/./django/template
2025-04-22 17:58:54,981 root INFO copying build/lib/django/template/context.py -> build/bdist.linux-armv8l/wheel/./django/template
2025-04-22 17:58:54,981 root INFO copying build/lib/django/template/utils.py -> build/bdist.linux-armv8l/wheel/./django/template
2025-04-22 17:58:54,981 root INFO copying build/lib/django/template/defaultfilters.py -> build/bdist.linux-armv8l/wheel/./django/template
2025-04-22 17:58:54,982 root INFO creating build/bdist.linux-armv8l/wheel/django/template/loaders
2025-04-22 17:58:54,982 root INFO copying build/lib/django/template/loaders/__init__.py -> build/bdist.linux-armv8l/wheel/./django/template/loaders
2025-04-22 17:58:54,982 root INFO copying build/lib/django/template/loaders/locmem.py -> build/bdist.linux-armv8l/wheel/./django/template/loaders
2025-04-22 17:58:54,982 root INFO copying build/lib/django/template/loaders/cached.py -> build/bdist.linux-armv8l/wheel/./django/template/loaders
2025-04-22 17:58:54,983 root INFO copying build/lib/django/template/loaders/app_directories.py -> build/bdist.linux-armv8l/wheel/./django/template/loaders
2025-04-22 17:58:54,983 root INFO copying build/lib/django/template/loaders/filesystem.py -> build/bdist.linux-armv8l/wheel/./django/template/loaders
2025-04-22 17:58:54,983 root INFO copying build/lib/django/template/loaders/base.py -> build/bdist.linux-armv8l/wheel/./django/template/loaders
2025-04-22 17:58:54,983 root INFO copying build/lib/django/template/context_processors.py -> build/bdist.linux-armv8l/wheel/./django/template
2025-04-22 17:58:54,983 root INFO creating build/bdist.linux-armv8l/wheel/django/template/backends
2025-04-22 17:58:54,984 root INFO copying build/lib/django/template/backends/__init__.py -> build/bdist.linux-armv8l/wheel/./django/template/backends
2025-04-22 17:58:54,984 root INFO copying build/lib/django/template/backends/jinja2.py -> build/bdist.linux-armv8l/wheel/./django/template/backends
2025-04-22 17:58:54,984 root INFO copying build/lib/django/template/backends/utils.py -> build/bdist.linux-armv8l/wheel/./django/template/backends
2025-04-22 17:58:54,984 root INFO copying build/lib/django/template/backends/django.py -> build/bdist.linux-armv8l/wheel/./django/template/backends
2025-04-22 17:58:54,984 root INFO copying build/lib/django/template/backends/base.py -> build/bdist.linux-armv8l/wheel/./django/template/backends
2025-04-22 17:58:54,984 root INFO copying build/lib/django/template/backends/dummy.py -> build/bdist.linux-armv8l/wheel/./django/template/backends
2025-04-22 17:58:54,985 root INFO copying build/lib/django/template/base.py -> build/bdist.linux-armv8l/wheel/./django/template
2025-04-22 17:58:54,985 root INFO creating build/bdist.linux-armv8l/wheel/django/conf
2025-04-22 17:58:54,985 root INFO copying build/lib/django/conf/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf
2025-04-22 17:58:54,985 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/urls
2025-04-22 17:58:54,986 root INFO copying build/lib/django/conf/urls/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/urls
2025-04-22 17:58:54,986 root INFO copying build/lib/django/conf/urls/i18n.py -> build/bdist.linux-armv8l/wheel/./django/conf/urls
2025-04-22 17:58:54,986 root INFO copying build/lib/django/conf/urls/static.py -> build/bdist.linux-armv8l/wheel/./django/conf/urls
2025-04-22 17:58:54,986 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale
2025-04-22 17:58:54,986 root INFO copying build/lib/django/conf/locale/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale
2025-04-22 17:58:54,987 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/lv
2025-04-22 17:58:54,987 root INFO copying build/lib/django/conf/locale/lv/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/lv
2025-04-22 17:58:54,987 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,987 root INFO copying build/lib/django/conf/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,988 root INFO copying build/lib/django/conf/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/lv/LC_MESSAGES
2025-04-22 17:58:54,988 root INFO copying build/lib/django/conf/locale/lv/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/lv
2025-04-22 17:58:54,988 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/es_PR
2025-04-22 17:58:54,988 root INFO copying build/lib/django/conf/locale/es_PR/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_PR
2025-04-22 17:58:54,988 root INFO copying build/lib/django/conf/locale/es_PR/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_PR
2025-04-22 17:58:54,989 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/sw
2025-04-22 17:58:54,989 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,989 root INFO copying build/lib/django/conf/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,989 root INFO copying build/lib/django/conf/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sw/LC_MESSAGES
2025-04-22 17:58:54,990 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/en_AU
2025-04-22 17:58:54,990 root INFO copying build/lib/django/conf/locale/en_AU/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/en_AU
2025-04-22 17:58:54,990 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,990 root INFO copying build/lib/django/conf/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,990 root INFO copying build/lib/django/conf/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:54,991 root INFO copying build/lib/django/conf/locale/en_AU/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/en_AU
2025-04-22 17:58:54,991 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/mr
2025-04-22 17:58:54,991 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,991 root INFO copying build/lib/django/conf/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,991 root INFO copying build/lib/django/conf/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/mr/LC_MESSAGES
2025-04-22 17:58:54,992 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/de_CH
2025-04-22 17:58:54,992 root INFO copying build/lib/django/conf/locale/de_CH/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/de_CH
2025-04-22 17:58:54,992 root INFO copying build/lib/django/conf/locale/de_CH/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/de_CH
2025-04-22 17:58:54,992 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/lb
2025-04-22 17:58:54,992 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,993 root INFO copying build/lib/django/conf/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,993 root INFO copying build/lib/django/conf/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/lb/LC_MESSAGES
2025-04-22 17:58:54,993 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ca
2025-04-22 17:58:54,993 root INFO copying build/lib/django/conf/locale/ca/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ca
2025-04-22 17:58:54,994 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,994 root INFO copying build/lib/django/conf/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,994 root INFO copying build/lib/django/conf/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ca/LC_MESSAGES
2025-04-22 17:58:54,994 root INFO copying build/lib/django/conf/locale/ca/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ca
2025-04-22 17:58:54,994 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/en_GB
2025-04-22 17:58:54,995 root INFO copying build/lib/django/conf/locale/en_GB/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/en_GB
2025-04-22 17:58:54,995 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,995 root INFO copying build/lib/django/conf/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,995 root INFO copying build/lib/django/conf/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:54,995 root INFO copying build/lib/django/conf/locale/en_GB/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/en_GB
2025-04-22 17:58:54,996 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/el
2025-04-22 17:58:54,996 root INFO copying build/lib/django/conf/locale/el/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/el
2025-04-22 17:58:54,996 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/el/LC_MESSAGES
2025-04-22 17:58:54,996 root INFO copying build/lib/django/conf/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/el/LC_MESSAGES
2025-04-22 17:58:54,997 root INFO copying build/lib/django/conf/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/el/LC_MESSAGES
2025-04-22 17:58:54,997 root INFO copying build/lib/django/conf/locale/el/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/el
2025-04-22 17:58:54,997 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/es_VE
2025-04-22 17:58:54,997 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,997 root INFO copying build/lib/django/conf/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,998 root INFO copying build/lib/django/conf/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:54,998 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/af
2025-04-22 17:58:54,998 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/af/LC_MESSAGES
2025-04-22 17:58:54,998 root INFO copying build/lib/django/conf/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/af/LC_MESSAGES
2025-04-22 17:58:54,999 root INFO copying build/lib/django/conf/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/af/LC_MESSAGES
2025-04-22 17:58:54,999 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/en
2025-04-22 17:58:54,999 root INFO copying build/lib/django/conf/locale/en/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/en
2025-04-22 17:58:54,999 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/en/LC_MESSAGES
2025-04-22 17:58:54,999 root INFO copying build/lib/django/conf/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/en/LC_MESSAGES
2025-04-22 17:58:55,000 root INFO copying build/lib/django/conf/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/en/LC_MESSAGES
2025-04-22 17:58:55,000 root INFO copying build/lib/django/conf/locale/en/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/en
2025-04-22 17:58:55,000 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/dsb
2025-04-22 17:58:55,000 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,000 root INFO copying build/lib/django/conf/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,001 root INFO copying build/lib/django/conf/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,001 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/et
2025-04-22 17:58:55,001 root INFO copying build/lib/django/conf/locale/et/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/et
2025-04-22 17:58:55,001 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/et/LC_MESSAGES
2025-04-22 17:58:55,002 root INFO copying build/lib/django/conf/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/et/LC_MESSAGES
2025-04-22 17:58:55,002 root INFO copying build/lib/django/conf/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/et/LC_MESSAGES
2025-04-22 17:58:55,002 root INFO copying build/lib/django/conf/locale/et/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/et
2025-04-22 17:58:55,002 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/nn
2025-04-22 17:58:55,003 root INFO copying build/lib/django/conf/locale/nn/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/nn
2025-04-22 17:58:55,003 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,003 root INFO copying build/lib/django/conf/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,003 root INFO copying build/lib/django/conf/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,004 root INFO copying build/lib/django/conf/locale/nn/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/nn
2025-04-22 17:58:55,004 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/cy
2025-04-22 17:58:55,004 root INFO copying build/lib/django/conf/locale/cy/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/cy
2025-04-22 17:58:55,004 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,004 root INFO copying build/lib/django/conf/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,005 root INFO copying build/lib/django/conf/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,005 root INFO copying build/lib/django/conf/locale/cy/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/cy
2025-04-22 17:58:55,005 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ko
2025-04-22 17:58:55,005 root INFO copying build/lib/django/conf/locale/ko/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ko
2025-04-22 17:58:55,006 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,006 root INFO copying build/lib/django/conf/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,006 root INFO copying build/lib/django/conf/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,006 root INFO copying build/lib/django/conf/locale/ko/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ko
2025-04-22 17:58:55,007 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/is
2025-04-22 17:58:55,007 root INFO copying build/lib/django/conf/locale/is/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/is
2025-04-22 17:58:55,007 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/is/LC_MESSAGES
2025-04-22 17:58:55,007 root INFO copying build/lib/django/conf/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/is/LC_MESSAGES
2025-04-22 17:58:55,007 root INFO copying build/lib/django/conf/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/is/LC_MESSAGES
2025-04-22 17:58:55,008 root INFO copying build/lib/django/conf/locale/is/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/is
2025-04-22 17:58:55,008 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/pa
2025-04-22 17:58:55,008 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,008 root INFO copying build/lib/django/conf/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,008 root INFO copying build/lib/django/conf/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,009 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/tt
2025-04-22 17:58:55,009 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,009 root INFO copying build/lib/django/conf/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,009 root INFO copying build/lib/django/conf/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,010 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ne
2025-04-22 17:58:55,010 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,010 root INFO copying build/lib/django/conf/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,010 root INFO copying build/lib/django/conf/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,010 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/sr_Latn
2025-04-22 17:58:55,011 root INFO copying build/lib/django/conf/locale/sr_Latn/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sr_Latn
2025-04-22 17:58:55,011 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,011 root INFO copying build/lib/django/conf/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,011 root INFO copying build/lib/django/conf/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,012 root INFO copying build/lib/django/conf/locale/sr_Latn/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sr_Latn
2025-04-22 17:58:55,012 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/fy
2025-04-22 17:58:55,012 root INFO copying build/lib/django/conf/locale/fy/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/fy
2025-04-22 17:58:55,012 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,012 root INFO copying build/lib/django/conf/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,013 root INFO copying build/lib/django/conf/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,013 root INFO copying build/lib/django/conf/locale/fy/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/fy
2025-04-22 17:58:55,013 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/bg
2025-04-22 17:58:55,013 root INFO copying build/lib/django/conf/locale/bg/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/bg
2025-04-22 17:58:55,013 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,014 root INFO copying build/lib/django/conf/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,014 root INFO copying build/lib/django/conf/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,014 root INFO copying build/lib/django/conf/locale/bg/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/bg
2025-04-22 17:58:55,014 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ga
2025-04-22 17:58:55,015 root INFO copying build/lib/django/conf/locale/ga/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ga
2025-04-22 17:58:55,015 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,015 root INFO copying build/lib/django/conf/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,015 root INFO copying build/lib/django/conf/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,015 root INFO copying build/lib/django/conf/locale/ga/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ga
2025-04-22 17:58:55,016 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/gl
2025-04-22 17:58:55,016 root INFO copying build/lib/django/conf/locale/gl/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/gl
2025-04-22 17:58:55,016 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,016 root INFO copying build/lib/django/conf/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,017 root INFO copying build/lib/django/conf/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,017 root INFO copying build/lib/django/conf/locale/gl/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/gl
2025-04-22 17:58:55,017 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ig
2025-04-22 17:58:55,017 root INFO copying build/lib/django/conf/locale/ig/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ig
2025-04-22 17:58:55,017 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ig/LC_MESSAGES
2025-04-22 17:58:55,018 root INFO copying build/lib/django/conf/locale/ig/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ig/LC_MESSAGES
2025-04-22 17:58:55,018 root INFO copying build/lib/django/conf/locale/ig/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ig/LC_MESSAGES
2025-04-22 17:58:55,018 root INFO copying build/lib/django/conf/locale/ig/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ig
2025-04-22 17:58:55,018 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/uk
2025-04-22 17:58:55,018 root INFO copying build/lib/django/conf/locale/uk/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/uk
2025-04-22 17:58:55,019 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,019 root INFO copying build/lib/django/conf/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,019 root INFO copying build/lib/django/conf/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,019 root INFO copying build/lib/django/conf/locale/uk/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/uk
2025-04-22 17:58:55,020 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/uz
2025-04-22 17:58:55,020 root INFO copying build/lib/django/conf/locale/uz/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/uz
2025-04-22 17:58:55,020 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,020 root INFO copying build/lib/django/conf/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,020 root INFO copying build/lib/django/conf/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,021 root INFO copying build/lib/django/conf/locale/uz/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/uz
2025-04-22 17:58:55,021 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/kn
2025-04-22 17:58:55,021 root INFO copying build/lib/django/conf/locale/kn/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/kn
2025-04-22 17:58:55,021 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,021 root INFO copying build/lib/django/conf/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,022 root INFO copying build/lib/django/conf/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,022 root INFO copying build/lib/django/conf/locale/kn/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/kn
2025-04-22 17:58:55,022 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ja
2025-04-22 17:58:55,022 root INFO copying build/lib/django/conf/locale/ja/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ja
2025-04-22 17:58:55,023 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,023 root INFO copying build/lib/django/conf/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,023 root INFO copying build/lib/django/conf/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,023 root INFO copying build/lib/django/conf/locale/ja/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ja
2025-04-22 17:58:55,024 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/cs
2025-04-22 17:58:55,024 root INFO copying build/lib/django/conf/locale/cs/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/cs
2025-04-22 17:58:55,024 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,024 root INFO copying build/lib/django/conf/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,024 root INFO copying build/lib/django/conf/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,025 root INFO copying build/lib/django/conf/locale/cs/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/cs
2025-04-22 17:58:55,025 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/os
2025-04-22 17:58:55,025 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/os/LC_MESSAGES
2025-04-22 17:58:55,025 root INFO copying build/lib/django/conf/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/os/LC_MESSAGES
2025-04-22 17:58:55,025 root INFO copying build/lib/django/conf/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/os/LC_MESSAGES
2025-04-22 17:58:55,026 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/tr
2025-04-22 17:58:55,026 root INFO copying build/lib/django/conf/locale/tr/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/tr
2025-04-22 17:58:55,026 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,026 root INFO copying build/lib/django/conf/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,027 root INFO copying build/lib/django/conf/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,027 root INFO copying build/lib/django/conf/locale/tr/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/tr
2025-04-22 17:58:55,027 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/io
2025-04-22 17:58:55,027 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/io/LC_MESSAGES
2025-04-22 17:58:55,027 root INFO copying build/lib/django/conf/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/io/LC_MESSAGES
2025-04-22 17:58:55,028 root INFO copying build/lib/django/conf/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/io/LC_MESSAGES
2025-04-22 17:58:55,028 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/sl
2025-04-22 17:58:55,028 root INFO copying build/lib/django/conf/locale/sl/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sl
2025-04-22 17:58:55,028 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,029 root INFO copying build/lib/django/conf/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,029 root INFO copying build/lib/django/conf/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,029 root INFO copying build/lib/django/conf/locale/sl/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sl
2025-04-22 17:58:55,029 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/sq
2025-04-22 17:58:55,030 root INFO copying build/lib/django/conf/locale/sq/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sq
2025-04-22 17:58:55,030 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,030 root INFO copying build/lib/django/conf/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,030 root INFO copying build/lib/django/conf/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,030 root INFO copying build/lib/django/conf/locale/sq/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sq
2025-04-22 17:58:55,031 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/az
2025-04-22 17:58:55,031 root INFO copying build/lib/django/conf/locale/az/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/az
2025-04-22 17:58:55,031 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/az/LC_MESSAGES
2025-04-22 17:58:55,031 root INFO copying build/lib/django/conf/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/az/LC_MESSAGES
2025-04-22 17:58:55,032 root INFO copying build/lib/django/conf/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/az/LC_MESSAGES
2025-04-22 17:58:55,032 root INFO copying build/lib/django/conf/locale/az/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/az
2025-04-22 17:58:55,032 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/eo
2025-04-22 17:58:55,032 root INFO copying build/lib/django/conf/locale/eo/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/eo
2025-04-22 17:58:55,032 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,033 root INFO copying build/lib/django/conf/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,033 root INFO copying build/lib/django/conf/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,033 root INFO copying build/lib/django/conf/locale/eo/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/eo
2025-04-22 17:58:55,033 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/pt_BR
2025-04-22 17:58:55,034 root INFO copying build/lib/django/conf/locale/pt_BR/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/pt_BR
2025-04-22 17:58:55,034 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,034 root INFO copying build/lib/django/conf/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,034 root INFO copying build/lib/django/conf/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,034 root INFO copying build/lib/django/conf/locale/pt_BR/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/pt_BR
2025-04-22 17:58:55,035 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/pl
2025-04-22 17:58:55,035 root INFO copying build/lib/django/conf/locale/pl/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/pl
2025-04-22 17:58:55,035 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,035 root INFO copying build/lib/django/conf/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,035 root INFO copying build/lib/django/conf/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,036 root INFO copying build/lib/django/conf/locale/pl/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/pl
2025-04-22 17:58:55,036 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/gd
2025-04-22 17:58:55,036 root INFO copying build/lib/django/conf/locale/gd/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/gd
2025-04-22 17:58:55,036 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,037 root INFO copying build/lib/django/conf/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,037 root INFO copying build/lib/django/conf/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,037 root INFO copying build/lib/django/conf/locale/gd/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/gd
2025-04-22 17:58:55,037 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/hr
2025-04-22 17:58:55,037 root INFO copying build/lib/django/conf/locale/hr/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/hr
2025-04-22 17:58:55,038 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,038 root INFO copying build/lib/django/conf/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,038 root INFO copying build/lib/django/conf/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,038 root INFO copying build/lib/django/conf/locale/hr/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/hr
2025-04-22 17:58:55,039 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ru
2025-04-22 17:58:55,039 root INFO copying build/lib/django/conf/locale/ru/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ru
2025-04-22 17:58:55,039 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,039 root INFO copying build/lib/django/conf/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,039 root INFO copying build/lib/django/conf/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,040 root INFO copying build/lib/django/conf/locale/ru/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ru
2025-04-22 17:58:55,040 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/es
2025-04-22 17:58:55,040 root INFO copying build/lib/django/conf/locale/es/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es
2025-04-22 17:58:55,040 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/es/LC_MESSAGES
2025-04-22 17:58:55,041 root INFO copying build/lib/django/conf/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es/LC_MESSAGES
2025-04-22 17:58:55,041 root INFO copying build/lib/django/conf/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es/LC_MESSAGES
2025-04-22 17:58:55,041 root INFO copying build/lib/django/conf/locale/es/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es
2025-04-22 17:58:55,041 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/id
2025-04-22 17:58:55,042 root INFO copying build/lib/django/conf/locale/id/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/id
2025-04-22 17:58:55,042 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/id/LC_MESSAGES
2025-04-22 17:58:55,042 root INFO copying build/lib/django/conf/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/id/LC_MESSAGES
2025-04-22 17:58:55,042 root INFO copying build/lib/django/conf/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/id/LC_MESSAGES
2025-04-22 17:58:55,042 root INFO copying build/lib/django/conf/locale/id/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/id
2025-04-22 17:58:55,043 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/fi
2025-04-22 17:58:55,043 root INFO copying build/lib/django/conf/locale/fi/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/fi
2025-04-22 17:58:55,043 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,043 root INFO copying build/lib/django/conf/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,043 root INFO copying build/lib/django/conf/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,044 root INFO copying build/lib/django/conf/locale/fi/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/fi
2025-04-22 17:58:55,044 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/mk
2025-04-22 17:58:55,044 root INFO copying build/lib/django/conf/locale/mk/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/mk
2025-04-22 17:58:55,044 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,045 root INFO copying build/lib/django/conf/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,045 root INFO copying build/lib/django/conf/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,045 root INFO copying build/lib/django/conf/locale/mk/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/mk
2025-04-22 17:58:55,045 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/hi
2025-04-22 17:58:55,045 root INFO copying build/lib/django/conf/locale/hi/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/hi
2025-04-22 17:58:55,046 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,046 root INFO copying build/lib/django/conf/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,046 root INFO copying build/lib/django/conf/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,047 root INFO copying build/lib/django/conf/locale/hi/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/hi
2025-04-22 17:58:55,047 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/kab
2025-04-22 17:58:55,047 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,047 root INFO copying build/lib/django/conf/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,047 root INFO copying build/lib/django/conf/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,048 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/hsb
2025-04-22 17:58:55,048 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,048 root INFO copying build/lib/django/conf/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,048 root INFO copying build/lib/django/conf/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,049 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/sk
2025-04-22 17:58:55,049 root INFO copying build/lib/django/conf/locale/sk/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sk
2025-04-22 17:58:55,049 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,049 root INFO copying build/lib/django/conf/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,049 root INFO copying build/lib/django/conf/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,050 root INFO copying build/lib/django/conf/locale/sk/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sk
2025-04-22 17:58:55,050 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/lt
2025-04-22 17:58:55,050 root INFO copying build/lib/django/conf/locale/lt/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/lt
2025-04-22 17:58:55,050 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,050 root INFO copying build/lib/django/conf/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,051 root INFO copying build/lib/django/conf/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,051 root INFO copying build/lib/django/conf/locale/lt/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/lt
2025-04-22 17:58:55,051 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/de
2025-04-22 17:58:55,051 root INFO copying build/lib/django/conf/locale/de/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/de
2025-04-22 17:58:55,052 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/de/LC_MESSAGES
2025-04-22 17:58:55,052 root INFO copying build/lib/django/conf/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/de/LC_MESSAGES
2025-04-22 17:58:55,052 root INFO copying build/lib/django/conf/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/de/LC_MESSAGES
2025-04-22 17:58:55,052 root INFO copying build/lib/django/conf/locale/de/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/de
2025-04-22 17:58:55,053 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/it
2025-04-22 17:58:55,053 root INFO copying build/lib/django/conf/locale/it/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/it
2025-04-22 17:58:55,053 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/it/LC_MESSAGES
2025-04-22 17:58:55,053 root INFO copying build/lib/django/conf/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/it/LC_MESSAGES
2025-04-22 17:58:55,053 root INFO copying build/lib/django/conf/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/it/LC_MESSAGES
2025-04-22 17:58:55,054 root INFO copying build/lib/django/conf/locale/it/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/it
2025-04-22 17:58:55,054 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/my
2025-04-22 17:58:55,054 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/my/LC_MESSAGES
2025-04-22 17:58:55,054 root INFO copying build/lib/django/conf/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/my/LC_MESSAGES
2025-04-22 17:58:55,055 root INFO copying build/lib/django/conf/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/my/LC_MESSAGES
2025-04-22 17:58:55,055 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/sr
2025-04-22 17:58:55,055 root INFO copying build/lib/django/conf/locale/sr/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sr
2025-04-22 17:58:55,055 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,055 root INFO copying build/lib/django/conf/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,056 root INFO copying build/lib/django/conf/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,056 root INFO copying build/lib/django/conf/locale/sr/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sr
2025-04-22 17:58:55,056 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/bs
2025-04-22 17:58:55,056 root INFO copying build/lib/django/conf/locale/bs/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/bs
2025-04-22 17:58:55,057 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,057 root INFO copying build/lib/django/conf/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,057 root INFO copying build/lib/django/conf/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,057 root INFO copying build/lib/django/conf/locale/bs/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/bs
2025-04-22 17:58:55,057 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/es_NI
2025-04-22 17:58:55,058 root INFO copying build/lib/django/conf/locale/es_NI/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_NI
2025-04-22 17:58:55,058 root INFO copying build/lib/django/conf/locale/es_NI/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_NI
2025-04-22 17:58:55,058 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ro
2025-04-22 17:58:55,058 root INFO copying build/lib/django/conf/locale/ro/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ro
2025-04-22 17:58:55,059 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,059 root INFO copying build/lib/django/conf/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,059 root INFO copying build/lib/django/conf/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,059 root INFO copying build/lib/django/conf/locale/ro/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ro
2025-04-22 17:58:55,060 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ky
2025-04-22 17:58:55,060 root INFO copying build/lib/django/conf/locale/ky/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ky
2025-04-22 17:58:55,060 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,060 root INFO copying build/lib/django/conf/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,060 root INFO copying build/lib/django/conf/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,061 root INFO copying build/lib/django/conf/locale/ky/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ky
2025-04-22 17:58:55,061 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/fr
2025-04-22 17:58:55,061 root INFO copying build/lib/django/conf/locale/fr/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/fr
2025-04-22 17:58:55,061 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,062 root INFO copying build/lib/django/conf/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,062 root INFO copying build/lib/django/conf/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,062 root INFO copying build/lib/django/conf/locale/fr/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/fr
2025-04-22 17:58:55,062 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ar
2025-04-22 17:58:55,062 root INFO copying build/lib/django/conf/locale/ar/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ar
2025-04-22 17:58:55,063 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,063 root INFO copying build/lib/django/conf/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,063 root INFO copying build/lib/django/conf/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,063 root INFO copying build/lib/django/conf/locale/ar/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ar
2025-04-22 17:58:55,064 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/hy
2025-04-22 17:58:55,064 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,064 root INFO copying build/lib/django/conf/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,064 root INFO copying build/lib/django/conf/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,065 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/es_AR
2025-04-22 17:58:55,065 root INFO copying build/lib/django/conf/locale/es_AR/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_AR
2025-04-22 17:58:55,065 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,065 root INFO copying build/lib/django/conf/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,065 root INFO copying build/lib/django/conf/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,066 root INFO copying build/lib/django/conf/locale/es_AR/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_AR
2025-04-22 17:58:55,066 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/vi
2025-04-22 17:58:55,066 root INFO copying build/lib/django/conf/locale/vi/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/vi
2025-04-22 17:58:55,066 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,067 root INFO copying build/lib/django/conf/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,067 root INFO copying build/lib/django/conf/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,067 root INFO copying build/lib/django/conf/locale/vi/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/vi
2025-04-22 17:58:55,067 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ckb
2025-04-22 17:58:55,068 root INFO copying build/lib/django/conf/locale/ckb/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ckb
2025-04-22 17:58:55,068 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,068 root INFO copying build/lib/django/conf/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,068 root INFO copying build/lib/django/conf/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,068 root INFO copying build/lib/django/conf/locale/ckb/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ckb
2025-04-22 17:58:55,069 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/sv
2025-04-22 17:58:55,069 root INFO copying build/lib/django/conf/locale/sv/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sv
2025-04-22 17:58:55,069 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,070 root INFO copying build/lib/django/conf/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,070 root INFO copying build/lib/django/conf/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,070 root INFO copying build/lib/django/conf/locale/sv/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/sv
2025-04-22 17:58:55,070 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/zh_Hant
2025-04-22 17:58:55,071 root INFO copying build/lib/django/conf/locale/zh_Hant/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/zh_Hant
2025-04-22 17:58:55,071 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,071 root INFO copying build/lib/django/conf/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,071 root INFO copying build/lib/django/conf/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,071 root INFO copying build/lib/django/conf/locale/zh_Hant/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/zh_Hant
2025-04-22 17:58:55,072 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/kk
2025-04-22 17:58:55,072 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,072 root INFO copying build/lib/django/conf/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,072 root INFO copying build/lib/django/conf/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,073 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/es_CO
2025-04-22 17:58:55,073 root INFO copying build/lib/django/conf/locale/es_CO/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_CO
2025-04-22 17:58:55,073 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,073 root INFO copying build/lib/django/conf/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,074 root INFO copying build/lib/django/conf/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,074 root INFO copying build/lib/django/conf/locale/es_CO/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_CO
2025-04-22 17:58:55,074 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/be
2025-04-22 17:58:55,074 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/be/LC_MESSAGES
2025-04-22 17:58:55,075 root INFO copying build/lib/django/conf/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/be/LC_MESSAGES
2025-04-22 17:58:55,075 root INFO copying build/lib/django/conf/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/be/LC_MESSAGES
2025-04-22 17:58:55,075 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/udm
2025-04-22 17:58:55,075 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,076 root INFO copying build/lib/django/conf/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,076 root INFO copying build/lib/django/conf/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,076 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ml
2025-04-22 17:58:55,076 root INFO copying build/lib/django/conf/locale/ml/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ml
2025-04-22 17:58:55,077 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,077 root INFO copying build/lib/django/conf/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,077 root INFO copying build/lib/django/conf/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,077 root INFO copying build/lib/django/conf/locale/ml/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ml
2025-04-22 17:58:55,078 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ar_DZ
2025-04-22 17:58:55,078 root INFO copying build/lib/django/conf/locale/ar_DZ/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ar_DZ
2025-04-22 17:58:55,078 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,078 root INFO copying build/lib/django/conf/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,079 root INFO copying build/lib/django/conf/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,079 root INFO copying build/lib/django/conf/locale/ar_DZ/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ar_DZ
2025-04-22 17:58:55,079 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ms
2025-04-22 17:58:55,079 root INFO copying build/lib/django/conf/locale/ms/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ms
2025-04-22 17:58:55,080 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,080 root INFO copying build/lib/django/conf/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,080 root INFO copying build/lib/django/conf/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,080 root INFO copying build/lib/django/conf/locale/ms/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ms
2025-04-22 17:58:55,081 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ast
2025-04-22 17:58:55,081 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,081 root INFO copying build/lib/django/conf/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,081 root INFO copying build/lib/django/conf/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,082 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/zh_Hans
2025-04-22 17:58:55,082 root INFO copying build/lib/django/conf/locale/zh_Hans/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/zh_Hans
2025-04-22 17:58:55,082 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,082 root INFO copying build/lib/django/conf/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,082 root INFO copying build/lib/django/conf/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,083 root INFO copying build/lib/django/conf/locale/zh_Hans/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/zh_Hans
2025-04-22 17:58:55,083 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ur
2025-04-22 17:58:55,083 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,083 root INFO copying build/lib/django/conf/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,084 root INFO copying build/lib/django/conf/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,084 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ia
2025-04-22 17:58:55,084 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,084 root INFO copying build/lib/django/conf/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,084 root INFO copying build/lib/django/conf/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,085 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/hu
2025-04-22 17:58:55,085 root INFO copying build/lib/django/conf/locale/hu/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/hu
2025-04-22 17:58:55,085 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,085 root INFO copying build/lib/django/conf/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,086 root INFO copying build/lib/django/conf/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,086 root INFO copying build/lib/django/conf/locale/hu/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/hu
2025-04-22 17:58:55,086 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ta
2025-04-22 17:58:55,086 root INFO copying build/lib/django/conf/locale/ta/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ta
2025-04-22 17:58:55,086 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,087 root INFO copying build/lib/django/conf/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,087 root INFO copying build/lib/django/conf/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,087 root INFO copying build/lib/django/conf/locale/ta/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ta
2025-04-22 17:58:55,087 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/eu
2025-04-22 17:58:55,087 root INFO copying build/lib/django/conf/locale/eu/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/eu
2025-04-22 17:58:55,088 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,088 root INFO copying build/lib/django/conf/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,088 root INFO copying build/lib/django/conf/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,088 root INFO copying build/lib/django/conf/locale/eu/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/eu
2025-04-22 17:58:55,089 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/es_MX
2025-04-22 17:58:55,089 root INFO copying build/lib/django/conf/locale/es_MX/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_MX
2025-04-22 17:58:55,089 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,089 root INFO copying build/lib/django/conf/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,089 root INFO copying build/lib/django/conf/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,090 root INFO copying build/lib/django/conf/locale/es_MX/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/es_MX
2025-04-22 17:58:55,090 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/tk
2025-04-22 17:58:55,090 root INFO copying build/lib/django/conf/locale/tk/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/tk
2025-04-22 17:58:55,090 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,090 root INFO copying build/lib/django/conf/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,091 root INFO copying build/lib/django/conf/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,091 root INFO copying build/lib/django/conf/locale/tk/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/tk
2025-04-22 17:58:55,091 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/th
2025-04-22 17:58:55,091 root INFO copying build/lib/django/conf/locale/th/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/th
2025-04-22 17:58:55,092 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/th/LC_MESSAGES
2025-04-22 17:58:55,092 root INFO copying build/lib/django/conf/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/th/LC_MESSAGES
2025-04-22 17:58:55,092 root INFO copying build/lib/django/conf/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/th/LC_MESSAGES
2025-04-22 17:58:55,092 root INFO copying build/lib/django/conf/locale/th/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/th
2025-04-22 17:58:55,092 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/nb
2025-04-22 17:58:55,093 root INFO copying build/lib/django/conf/locale/nb/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/nb
2025-04-22 17:58:55,093 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,093 root INFO copying build/lib/django/conf/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,093 root INFO copying build/lib/django/conf/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,094 root INFO copying build/lib/django/conf/locale/nb/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/nb
2025-04-22 17:58:55,094 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/mn
2025-04-22 17:58:55,094 root INFO copying build/lib/django/conf/locale/mn/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/mn
2025-04-22 17:58:55,094 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,094 root INFO copying build/lib/django/conf/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,095 root INFO copying build/lib/django/conf/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,095 root INFO copying build/lib/django/conf/locale/mn/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/mn
2025-04-22 17:58:55,095 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ka
2025-04-22 17:58:55,095 root INFO copying build/lib/django/conf/locale/ka/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ka
2025-04-22 17:58:55,095 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,096 root INFO copying build/lib/django/conf/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,096 root INFO copying build/lib/django/conf/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,096 root INFO copying build/lib/django/conf/locale/ka/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/ka
2025-04-22 17:58:55,096 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/nl
2025-04-22 17:58:55,097 root INFO copying build/lib/django/conf/locale/nl/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/nl
2025-04-22 17:58:55,097 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,097 root INFO copying build/lib/django/conf/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,097 root INFO copying build/lib/django/conf/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,097 root INFO copying build/lib/django/conf/locale/nl/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/nl
2025-04-22 17:58:55,098 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/te
2025-04-22 17:58:55,098 root INFO copying build/lib/django/conf/locale/te/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/te
2025-04-22 17:58:55,098 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/te/LC_MESSAGES
2025-04-22 17:58:55,098 root INFO copying build/lib/django/conf/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/te/LC_MESSAGES
2025-04-22 17:58:55,099 root INFO copying build/lib/django/conf/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/te/LC_MESSAGES
2025-04-22 17:58:55,099 root INFO copying build/lib/django/conf/locale/te/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/te
2025-04-22 17:58:55,099 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/pt
2025-04-22 17:58:55,099 root INFO copying build/lib/django/conf/locale/pt/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/pt
2025-04-22 17:58:55,099 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,100 root INFO copying build/lib/django/conf/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,100 root INFO copying build/lib/django/conf/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,100 root INFO copying build/lib/django/conf/locale/pt/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/pt
2025-04-22 17:58:55,100 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/bn
2025-04-22 17:58:55,100 root INFO copying build/lib/django/conf/locale/bn/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/bn
2025-04-22 17:58:55,101 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,101 root INFO copying build/lib/django/conf/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,101 root INFO copying build/lib/django/conf/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,101 root INFO copying build/lib/django/conf/locale/bn/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/bn
2025-04-22 17:58:55,102 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/he
2025-04-22 17:58:55,102 root INFO copying build/lib/django/conf/locale/he/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/he
2025-04-22 17:58:55,102 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/he/LC_MESSAGES
2025-04-22 17:58:55,102 root INFO copying build/lib/django/conf/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/he/LC_MESSAGES
2025-04-22 17:58:55,103 root INFO copying build/lib/django/conf/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/he/LC_MESSAGES
2025-04-22 17:58:55,103 root INFO copying build/lib/django/conf/locale/he/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/he
2025-04-22 17:58:55,103 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/br
2025-04-22 17:58:55,103 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/br/LC_MESSAGES
2025-04-22 17:58:55,104 root INFO copying build/lib/django/conf/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/br/LC_MESSAGES
2025-04-22 17:58:55,104 root INFO copying build/lib/django/conf/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/br/LC_MESSAGES
2025-04-22 17:58:55,104 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/fa
2025-04-22 17:58:55,104 root INFO copying build/lib/django/conf/locale/fa/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/fa
2025-04-22 17:58:55,104 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,105 root INFO copying build/lib/django/conf/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,105 root INFO copying build/lib/django/conf/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,105 root INFO copying build/lib/django/conf/locale/fa/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/fa
2025-04-22 17:58:55,105 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/tg
2025-04-22 17:58:55,106 root INFO copying build/lib/django/conf/locale/tg/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/tg
2025-04-22 17:58:55,106 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,106 root INFO copying build/lib/django/conf/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,106 root INFO copying build/lib/django/conf/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,107 root INFO copying build/lib/django/conf/locale/tg/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/tg
2025-04-22 17:58:55,107 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/km
2025-04-22 17:58:55,107 root INFO copying build/lib/django/conf/locale/km/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/km
2025-04-22 17:58:55,107 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/km/LC_MESSAGES
2025-04-22 17:58:55,107 root INFO copying build/lib/django/conf/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/km/LC_MESSAGES
2025-04-22 17:58:55,108 root INFO copying build/lib/django/conf/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/km/LC_MESSAGES
2025-04-22 17:58:55,108 root INFO copying build/lib/django/conf/locale/km/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/km
2025-04-22 17:58:55,108 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/da
2025-04-22 17:58:55,108 root INFO copying build/lib/django/conf/locale/da/__init__.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/da
2025-04-22 17:58:55,108 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/locale/da/LC_MESSAGES
2025-04-22 17:58:55,109 root INFO copying build/lib/django/conf/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/conf/locale/da/LC_MESSAGES
2025-04-22 17:58:55,109 root INFO copying build/lib/django/conf/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/conf/locale/da/LC_MESSAGES
2025-04-22 17:58:55,109 root INFO copying build/lib/django/conf/locale/da/formats.py -> build/bdist.linux-armv8l/wheel/./django/conf/locale/da
2025-04-22 17:58:55,109 root INFO copying build/lib/django/conf/global_settings.py -> build/bdist.linux-armv8l/wheel/./django/conf
2025-04-22 17:58:55,110 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/app_template
2025-04-22 17:58:55,110 root INFO copying build/lib/django/conf/app_template/apps.py-tpl -> build/bdist.linux-armv8l/wheel/./django/conf/app_template
2025-04-22 17:58:55,110 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/app_template/migrations
2025-04-22 17:58:55,110 root INFO copying build/lib/django/conf/app_template/migrations/__init__.py-tpl -> build/bdist.linux-armv8l/wheel/./django/conf/app_template/migrations
2025-04-22 17:58:55,110 root INFO copying build/lib/django/conf/app_template/views.py-tpl -> build/bdist.linux-armv8l/wheel/./django/conf/app_template
2025-04-22 17:58:55,111 root INFO copying build/lib/django/conf/app_template/__init__.py-tpl -> build/bdist.linux-armv8l/wheel/./django/conf/app_template
2025-04-22 17:58:55,111 root INFO copying build/lib/django/conf/app_template/admin.py-tpl -> build/bdist.linux-armv8l/wheel/./django/conf/app_template
2025-04-22 17:58:55,111 root INFO copying build/lib/django/conf/app_template/tests.py-tpl -> build/bdist.linux-armv8l/wheel/./django/conf/app_template
2025-04-22 17:58:55,111 root INFO copying build/lib/django/conf/app_template/models.py-tpl -> build/bdist.linux-armv8l/wheel/./django/conf/app_template
2025-04-22 17:58:55,111 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/project_template
2025-04-22 17:58:55,112 root INFO creating build/bdist.linux-armv8l/wheel/django/conf/project_template/project_name
2025-04-22 17:58:55,112 root INFO copying build/lib/django/conf/project_template/project_name/asgi.py-tpl -> build/bdist.linux-armv8l/wheel/./django/conf/project_template/project_name
2025-04-22 17:58:55,112 root INFO copying build/lib/django/conf/project_template/project_name/urls.py-tpl -> build/bdist.linux-armv8l/wheel/./django/conf/project_template/project_name
2025-04-22 17:58:55,112 root INFO copying build/lib/django/conf/project_template/project_name/settings.py-tpl -> build/bdist.linux-armv8l/wheel/./django/conf/project_template/project_name
2025-04-22 17:58:55,112 root INFO copying build/lib/django/conf/project_template/project_name/wsgi.py-tpl -> build/bdist.linux-armv8l/wheel/./django/conf/project_template/project_name
2025-04-22 17:58:55,113 root INFO copying build/lib/django/conf/project_template/project_name/__init__.py-tpl -> build/bdist.linux-armv8l/wheel/./django/conf/project_template/project_name
2025-04-22 17:58:55,113 root INFO copying build/lib/django/conf/project_template/manage.py-tpl -> build/bdist.linux-armv8l/wheel/./django/conf/project_template
2025-04-22 17:58:55,113 root INFO creating build/bdist.linux-armv8l/wheel/django/utils
2025-04-22 17:58:55,113 root INFO copying build/lib/django/utils/datetime_safe.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,113 root INFO copying build/lib/django/utils/__init__.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,114 root INFO copying build/lib/django/utils/itercompat.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,114 root INFO copying build/lib/django/utils/functional.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,114 root INFO copying build/lib/django/utils/hashable.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,114 root INFO creating build/bdist.linux-armv8l/wheel/django/utils/translation
2025-04-22 17:58:55,114 root INFO copying build/lib/django/utils/translation/__init__.py -> build/bdist.linux-armv8l/wheel/./django/utils/translation
2025-04-22 17:58:55,115 root INFO copying build/lib/django/utils/translation/template.py -> build/bdist.linux-armv8l/wheel/./django/utils/translation
2025-04-22 17:58:55,115 root INFO copying build/lib/django/utils/translation/reloader.py -> build/bdist.linux-armv8l/wheel/./django/utils/translation
2025-04-22 17:58:55,115 root INFO copying build/lib/django/utils/translation/trans_null.py -> build/bdist.linux-armv8l/wheel/./django/utils/translation
2025-04-22 17:58:55,115 root INFO copying build/lib/django/utils/translation/trans_real.py -> build/bdist.linux-armv8l/wheel/./django/utils/translation
2025-04-22 17:58:55,115 root INFO copying build/lib/django/utils/log.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,116 root INFO copying build/lib/django/utils/_os.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,116 root INFO copying build/lib/django/utils/dateparse.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,116 root INFO copying build/lib/django/utils/decorators.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,116 root INFO copying build/lib/django/utils/topological_sort.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,116 root INFO copying build/lib/django/utils/deprecation.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,117 root INFO copying build/lib/django/utils/formats.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,117 root INFO copying build/lib/django/utils/autoreload.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,117 root INFO copying build/lib/django/utils/timezone.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,117 root INFO copying build/lib/django/utils/timesince.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,117 root INFO copying build/lib/django/utils/cache.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,118 root INFO copying build/lib/django/utils/version.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,118 root INFO copying build/lib/django/utils/datastructures.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,118 root INFO copying build/lib/django/utils/dateformat.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,118 root INFO copying build/lib/django/utils/html.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,118 root INFO copying build/lib/django/utils/termcolors.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,119 root INFO copying build/lib/django/utils/tree.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,119 root INFO copying build/lib/django/utils/http.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,119 root INFO copying build/lib/django/utils/ipv6.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,119 root INFO copying build/lib/django/utils/asyncio.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,119 root INFO copying build/lib/django/utils/connection.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,119 root INFO copying build/lib/django/utils/lorem_ipsum.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,120 root INFO copying build/lib/django/utils/baseconv.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,120 root INFO copying build/lib/django/utils/numberformat.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,120 root INFO copying build/lib/django/utils/inspect.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,120 root INFO copying build/lib/django/utils/feedgenerator.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,120 root INFO copying build/lib/django/utils/duration.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,121 root INFO copying build/lib/django/utils/deconstruct.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,121 root INFO copying build/lib/django/utils/safestring.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,121 root INFO copying build/lib/django/utils/module_loading.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,121 root INFO copying build/lib/django/utils/archive.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,121 root INFO copying build/lib/django/utils/crypto.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,121 root INFO copying build/lib/django/utils/regex_helper.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,122 root INFO copying build/lib/django/utils/dates.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,122 root INFO copying build/lib/django/utils/xmlutils.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,122 root INFO copying build/lib/django/utils/encoding.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,122 root INFO copying build/lib/django/utils/jslex.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,122 root INFO copying build/lib/django/utils/text.py -> build/bdist.linux-armv8l/wheel/./django/utils
2025-04-22 17:58:55,123 root INFO creating build/bdist.linux-armv8l/wheel/django/templatetags
2025-04-22 17:58:55,123 root INFO copying build/lib/django/templatetags/__init__.py -> build/bdist.linux-armv8l/wheel/./django/templatetags
2025-04-22 17:58:55,123 root INFO copying build/lib/django/templatetags/tz.py -> build/bdist.linux-armv8l/wheel/./django/templatetags
2025-04-22 17:58:55,123 root INFO copying build/lib/django/templatetags/i18n.py -> build/bdist.linux-armv8l/wheel/./django/templatetags
2025-04-22 17:58:55,124 root INFO copying build/lib/django/templatetags/cache.py -> build/bdist.linux-armv8l/wheel/./django/templatetags
2025-04-22 17:58:55,124 root INFO copying build/lib/django/templatetags/static.py -> build/bdist.linux-armv8l/wheel/./django/templatetags
2025-04-22 17:58:55,124 root INFO copying build/lib/django/templatetags/l10n.py -> build/bdist.linux-armv8l/wheel/./django/templatetags
2025-04-22 17:58:55,124 root INFO copying build/lib/django/__main__.py -> build/bdist.linux-armv8l/wheel/./django
2025-04-22 17:58:55,124 root INFO creating build/bdist.linux-armv8l/wheel/django/test
2025-04-22 17:58:55,125 root INFO copying build/lib/django/test/__init__.py -> build/bdist.linux-armv8l/wheel/./django/test
2025-04-22 17:58:55,125 root INFO copying build/lib/django/test/signals.py -> build/bdist.linux-armv8l/wheel/./django/test
2025-04-22 17:58:55,125 root INFO copying build/lib/django/test/selenium.py -> build/bdist.linux-armv8l/wheel/./django/test
2025-04-22 17:58:55,125 root INFO copying build/lib/django/test/testcases.py -> build/bdist.linux-armv8l/wheel/./django/test
2025-04-22 17:58:55,125 root INFO copying build/lib/django/test/html.py -> build/bdist.linux-armv8l/wheel/./django/test
2025-04-22 17:58:55,126 root INFO copying build/lib/django/test/utils.py -> build/bdist.linux-armv8l/wheel/./django/test
2025-04-22 17:58:55,126 root INFO copying build/lib/django/test/runner.py -> build/bdist.linux-armv8l/wheel/./django/test
2025-04-22 17:58:55,126 root INFO copying build/lib/django/test/client.py -> build/bdist.linux-armv8l/wheel/./django/test
2025-04-22 17:58:55,127 root INFO copying build/lib/django/shortcuts.py -> build/bdist.linux-armv8l/wheel/./django
2025-04-22 17:58:55,127 root INFO creating build/bdist.linux-armv8l/wheel/django/core
2025-04-22 17:58:55,127 root INFO copying build/lib/django/core/__init__.py -> build/bdist.linux-armv8l/wheel/./django/core
2025-04-22 17:58:55,127 root INFO copying build/lib/django/core/signals.py -> build/bdist.linux-armv8l/wheel/./django/core
2025-04-22 17:58:55,127 root INFO creating build/bdist.linux-armv8l/wheel/django/core/files
2025-04-22 17:58:55,128 root INFO copying build/lib/django/core/files/__init__.py -> build/bdist.linux-armv8l/wheel/./django/core/files
2025-04-22 17:58:55,128 root INFO copying build/lib/django/core/files/uploadhandler.py -> build/bdist.linux-armv8l/wheel/./django/core/files
2025-04-22 17:58:55,128 root INFO creating build/bdist.linux-armv8l/wheel/django/core/files/storage
2025-04-22 17:58:55,128 root INFO copying build/lib/django/core/files/storage/__init__.py -> build/bdist.linux-armv8l/wheel/./django/core/files/storage
2025-04-22 17:58:55,128 root INFO copying build/lib/django/core/files/storage/handler.py -> build/bdist.linux-armv8l/wheel/./django/core/files/storage
2025-04-22 17:58:55,129 root INFO copying build/lib/django/core/files/storage/memory.py -> build/bdist.linux-armv8l/wheel/./django/core/files/storage
2025-04-22 17:58:55,129 root INFO copying build/lib/django/core/files/storage/filesystem.py -> build/bdist.linux-armv8l/wheel/./django/core/files/storage
2025-04-22 17:58:55,129 root INFO copying build/lib/django/core/files/storage/base.py -> build/bdist.linux-armv8l/wheel/./django/core/files/storage
2025-04-22 17:58:55,129 root INFO copying build/lib/django/core/files/storage/mixins.py -> build/bdist.linux-armv8l/wheel/./django/core/files/storage
2025-04-22 17:58:55,130 root INFO copying build/lib/django/core/files/uploadedfile.py -> build/bdist.linux-armv8l/wheel/./django/core/files
2025-04-22 17:58:55,130 root INFO copying build/lib/django/core/files/utils.py -> build/bdist.linux-armv8l/wheel/./django/core/files
2025-04-22 17:58:55,130 root INFO copying build/lib/django/core/files/temp.py -> build/bdist.linux-armv8l/wheel/./django/core/files
2025-04-22 17:58:55,130 root INFO copying build/lib/django/core/files/move.py -> build/bdist.linux-armv8l/wheel/./django/core/files
2025-04-22 17:58:55,130 root INFO copying build/lib/django/core/files/locks.py -> build/bdist.linux-armv8l/wheel/./django/core/files
2025-04-22 17:58:55,130 root INFO copying build/lib/django/core/files/base.py -> build/bdist.linux-armv8l/wheel/./django/core/files
2025-04-22 17:58:55,131 root INFO copying build/lib/django/core/files/images.py -> build/bdist.linux-armv8l/wheel/./django/core/files
2025-04-22 17:58:55,131 root INFO creating build/bdist.linux-armv8l/wheel/django/core/handlers
2025-04-22 17:58:55,131 root INFO copying build/lib/django/core/handlers/__init__.py -> build/bdist.linux-armv8l/wheel/./django/core/handlers
2025-04-22 17:58:55,131 root INFO copying build/lib/django/core/handlers/asgi.py -> build/bdist.linux-armv8l/wheel/./django/core/handlers
2025-04-22 17:58:55,132 root INFO copying build/lib/django/core/handlers/exception.py -> build/bdist.linux-armv8l/wheel/./django/core/handlers
2025-04-22 17:58:55,132 root INFO copying build/lib/django/core/handlers/wsgi.py -> build/bdist.linux-armv8l/wheel/./django/core/handlers
2025-04-22 17:58:55,132 root INFO copying build/lib/django/core/handlers/base.py -> build/bdist.linux-armv8l/wheel/./django/core/handlers
2025-04-22 17:58:55,132 root INFO copying build/lib/django/core/asgi.py -> build/bdist.linux-armv8l/wheel/./django/core
2025-04-22 17:58:55,132 root INFO copying build/lib/django/core/validators.py -> build/bdist.linux-armv8l/wheel/./django/core
2025-04-22 17:58:55,132 root INFO copying build/lib/django/core/exceptions.py -> build/bdist.linux-armv8l/wheel/./django/core
2025-04-22 17:58:55,133 root INFO creating build/bdist.linux-armv8l/wheel/django/core/servers
2025-04-22 17:58:55,133 root INFO copying build/lib/django/core/servers/__init__.py -> build/bdist.linux-armv8l/wheel/./django/core/servers
2025-04-22 17:58:55,133 root INFO copying build/lib/django/core/servers/basehttp.py -> build/bdist.linux-armv8l/wheel/./django/core/servers
2025-04-22 17:58:55,133 root INFO creating build/bdist.linux-armv8l/wheel/django/core/mail
2025-04-22 17:58:55,134 root INFO copying build/lib/django/core/mail/__init__.py -> build/bdist.linux-armv8l/wheel/./django/core/mail
2025-04-22 17:58:55,134 root INFO copying build/lib/django/core/mail/utils.py -> build/bdist.linux-armv8l/wheel/./django/core/mail
2025-04-22 17:58:55,134 root INFO copying build/lib/django/core/mail/message.py -> build/bdist.linux-armv8l/wheel/./django/core/mail
2025-04-22 17:58:55,134 root INFO creating build/bdist.linux-armv8l/wheel/django/core/mail/backends
2025-04-22 17:58:55,134 root INFO copying build/lib/django/core/mail/backends/__init__.py -> build/bdist.linux-armv8l/wheel/./django/core/mail/backends
2025-04-22 17:58:55,135 root INFO copying build/lib/django/core/mail/backends/locmem.py -> build/bdist.linux-armv8l/wheel/./django/core/mail/backends
2025-04-22 17:58:55,135 root INFO copying build/lib/django/core/mail/backends/base.py -> build/bdist.linux-armv8l/wheel/./django/core/mail/backends
2025-04-22 17:58:55,135 root INFO copying build/lib/django/core/mail/backends/console.py -> build/bdist.linux-armv8l/wheel/./django/core/mail/backends
2025-04-22 17:58:55,135 root INFO copying build/lib/django/core/mail/backends/dummy.py -> build/bdist.linux-armv8l/wheel/./django/core/mail/backends
2025-04-22 17:58:55,135 root INFO copying build/lib/django/core/mail/backends/smtp.py -> build/bdist.linux-armv8l/wheel/./django/core/mail/backends
2025-04-22 17:58:55,136 root INFO copying build/lib/django/core/mail/backends/filebased.py -> build/bdist.linux-armv8l/wheel/./django/core/mail/backends
2025-04-22 17:58:55,136 root INFO creating build/bdist.linux-armv8l/wheel/django/core/cache
2025-04-22 17:58:55,136 root INFO copying build/lib/django/core/cache/__init__.py -> build/bdist.linux-armv8l/wheel/./django/core/cache
2025-04-22 17:58:55,136 root INFO copying build/lib/django/core/cache/utils.py -> build/bdist.linux-armv8l/wheel/./django/core/cache
2025-04-22 17:58:55,137 root INFO creating build/bdist.linux-armv8l/wheel/django/core/cache/backends
2025-04-22 17:58:55,137 root INFO copying build/lib/django/core/cache/backends/__init__.py -> build/bdist.linux-armv8l/wheel/./django/core/cache/backends
2025-04-22 17:58:55,137 root INFO copying build/lib/django/core/cache/backends/locmem.py -> build/bdist.linux-armv8l/wheel/./django/core/cache/backends
2025-04-22 17:58:55,137 root INFO copying build/lib/django/core/cache/backends/db.py -> build/bdist.linux-armv8l/wheel/./django/core/cache/backends
2025-04-22 17:58:55,137 root INFO copying build/lib/django/core/cache/backends/memcached.py -> build/bdist.linux-armv8l/wheel/./django/core/cache/backends
2025-04-22 17:58:55,137 root INFO copying build/lib/django/core/cache/backends/redis.py -> build/bdist.linux-armv8l/wheel/./django/core/cache/backends
2025-04-22 17:58:55,138 root INFO copying build/lib/django/core/cache/backends/base.py -> build/bdist.linux-armv8l/wheel/./django/core/cache/backends
2025-04-22 17:58:55,138 root INFO copying build/lib/django/core/cache/backends/dummy.py -> build/bdist.linux-armv8l/wheel/./django/core/cache/backends
2025-04-22 17:58:55,138 root INFO copying build/lib/django/core/cache/backends/filebased.py -> build/bdist.linux-armv8l/wheel/./django/core/cache/backends
2025-04-22 17:58:55,138 root INFO copying build/lib/django/core/paginator.py -> build/bdist.linux-armv8l/wheel/./django/core
2025-04-22 17:58:55,139 root INFO creating build/bdist.linux-armv8l/wheel/django/core/management
2025-04-22 17:58:55,139 root INFO copying build/lib/django/core/management/__init__.py -> build/bdist.linux-armv8l/wheel/./django/core/management
2025-04-22 17:58:55,139 root INFO copying build/lib/django/core/management/color.py -> build/bdist.linux-armv8l/wheel/./django/core/management
2025-04-22 17:58:55,139 root INFO copying build/lib/django/core/management/utils.py -> build/bdist.linux-armv8l/wheel/./django/core/management
2025-04-22 17:58:55,139 root INFO copying build/lib/django/core/management/sql.py -> build/bdist.linux-armv8l/wheel/./django/core/management
2025-04-22 17:58:55,140 root INFO creating build/bdist.linux-armv8l/wheel/django/core/management/commands
2025-04-22 17:58:55,140 root INFO copying build/lib/django/core/management/commands/__init__.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,140 root INFO copying build/lib/django/core/management/commands/sqlmigrate.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,140 root INFO copying build/lib/django/core/management/commands/startapp.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,140 root INFO copying build/lib/django/core/management/commands/showmigrations.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,141 root INFO copying build/lib/django/core/management/commands/optimizemigration.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,141 root INFO copying build/lib/django/core/management/commands/dumpdata.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,141 root INFO copying build/lib/django/core/management/commands/migrate.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,141 root INFO copying build/lib/django/core/management/commands/shell.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,141 root INFO copying build/lib/django/core/management/commands/loaddata.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,142 root INFO copying build/lib/django/core/management/commands/createcachetable.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,142 root INFO copying build/lib/django/core/management/commands/dbshell.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,142 root INFO copying build/lib/django/core/management/commands/inspectdb.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,142 root INFO copying build/lib/django/core/management/commands/compilemessages.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,142 root INFO copying build/lib/django/core/management/commands/startproject.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,143 root INFO copying build/lib/django/core/management/commands/testserver.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,143 root INFO copying build/lib/django/core/management/commands/flush.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,143 root INFO copying build/lib/django/core/management/commands/diffsettings.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,143 root INFO copying build/lib/django/core/management/commands/sqlflush.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,143 root INFO copying build/lib/django/core/management/commands/makemigrations.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,144 root INFO copying build/lib/django/core/management/commands/sqlsequencereset.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,144 root INFO copying build/lib/django/core/management/commands/makemessages.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,144 root INFO copying build/lib/django/core/management/commands/runserver.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,144 root INFO copying build/lib/django/core/management/commands/check.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,144 root INFO copying build/lib/django/core/management/commands/sendtestemail.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,144 root INFO copying build/lib/django/core/management/commands/squashmigrations.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,145 root INFO copying build/lib/django/core/management/commands/test.py -> build/bdist.linux-armv8l/wheel/./django/core/management/commands
2025-04-22 17:58:55,145 root INFO copying build/lib/django/core/management/templates.py -> build/bdist.linux-armv8l/wheel/./django/core/management
2025-04-22 17:58:55,145 root INFO copying build/lib/django/core/management/base.py -> build/bdist.linux-armv8l/wheel/./django/core/management
2025-04-22 17:58:55,145 root INFO copying build/lib/django/core/wsgi.py -> build/bdist.linux-armv8l/wheel/./django/core
2025-04-22 17:58:55,146 root INFO creating build/bdist.linux-armv8l/wheel/django/core/serializers
2025-04-22 17:58:55,146 root INFO copying build/lib/django/core/serializers/python.py -> build/bdist.linux-armv8l/wheel/./django/core/serializers
2025-04-22 17:58:55,146 root INFO copying build/lib/django/core/serializers/__init__.py -> build/bdist.linux-armv8l/wheel/./django/core/serializers
2025-04-22 17:58:55,146 root INFO copying build/lib/django/core/serializers/xml_serializer.py -> build/bdist.linux-armv8l/wheel/./django/core/serializers
2025-04-22 17:58:55,146 root INFO copying build/lib/django/core/serializers/jsonl.py -> build/bdist.linux-armv8l/wheel/./django/core/serializers
2025-04-22 17:58:55,147 root INFO copying build/lib/django/core/serializers/json.py -> build/bdist.linux-armv8l/wheel/./django/core/serializers
2025-04-22 17:58:55,147 root INFO copying build/lib/django/core/serializers/pyyaml.py -> build/bdist.linux-armv8l/wheel/./django/core/serializers
2025-04-22 17:58:55,147 root INFO copying build/lib/django/core/serializers/base.py -> build/bdist.linux-armv8l/wheel/./django/core/serializers
2025-04-22 17:58:55,147 root INFO creating build/bdist.linux-armv8l/wheel/django/core/checks
2025-04-22 17:58:55,148 root INFO copying build/lib/django/core/checks/__init__.py -> build/bdist.linux-armv8l/wheel/./django/core/checks
2025-04-22 17:58:55,148 root INFO copying build/lib/django/core/checks/registry.py -> build/bdist.linux-armv8l/wheel/./django/core/checks
2025-04-22 17:58:55,148 root INFO copying build/lib/django/core/checks/database.py -> build/bdist.linux-armv8l/wheel/./django/core/checks
2025-04-22 17:58:55,148 root INFO copying build/lib/django/core/checks/messages.py -> build/bdist.linux-armv8l/wheel/./django/core/checks
2025-04-22 17:58:55,148 root INFO copying build/lib/django/core/checks/urls.py -> build/bdist.linux-armv8l/wheel/./django/core/checks
2025-04-22 17:58:55,149 root INFO creating build/bdist.linux-armv8l/wheel/django/core/checks/compatibility
2025-04-22 17:58:55,149 root INFO copying build/lib/django/core/checks/compatibility/__init__.py -> build/bdist.linux-armv8l/wheel/./django/core/checks/compatibility
2025-04-22 17:58:55,149 root INFO copying build/lib/django/core/checks/compatibility/django_4_0.py -> build/bdist.linux-armv8l/wheel/./django/core/checks/compatibility
2025-04-22 17:58:55,149 root INFO creating build/bdist.linux-armv8l/wheel/django/core/checks/security
2025-04-22 17:58:55,150 root INFO copying build/lib/django/core/checks/security/__init__.py -> build/bdist.linux-armv8l/wheel/./django/core/checks/security
2025-04-22 17:58:55,150 root INFO copying build/lib/django/core/checks/security/sessions.py -> build/bdist.linux-armv8l/wheel/./django/core/checks/security
2025-04-22 17:58:55,150 root INFO copying build/lib/django/core/checks/security/csrf.py -> build/bdist.linux-armv8l/wheel/./django/core/checks/security
2025-04-22 17:58:55,150 root INFO copying build/lib/django/core/checks/security/base.py -> build/bdist.linux-armv8l/wheel/./django/core/checks/security
2025-04-22 17:58:55,150 root INFO copying build/lib/django/core/checks/model_checks.py -> build/bdist.linux-armv8l/wheel/./django/core/checks
2025-04-22 17:58:55,150 root INFO copying build/lib/django/core/checks/caches.py -> build/bdist.linux-armv8l/wheel/./django/core/checks
2025-04-22 17:58:55,151 root INFO copying build/lib/django/core/checks/translation.py -> build/bdist.linux-armv8l/wheel/./django/core/checks
2025-04-22 17:58:55,151 root INFO copying build/lib/django/core/checks/templates.py -> build/bdist.linux-armv8l/wheel/./django/core/checks
2025-04-22 17:58:55,151 root INFO copying build/lib/django/core/checks/async_checks.py -> build/bdist.linux-armv8l/wheel/./django/core/checks
2025-04-22 17:58:55,151 root INFO copying build/lib/django/core/checks/files.py -> build/bdist.linux-armv8l/wheel/./django/core/checks
2025-04-22 17:58:55,151 root INFO copying build/lib/django/core/signing.py -> build/bdist.linux-armv8l/wheel/./django/core
2025-04-22 17:58:55,152 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib
2025-04-22 17:58:55,152 root INFO copying build/lib/django/contrib/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib
2025-04-22 17:58:55,152 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth
2025-04-22 17:58:55,152 root INFO copying build/lib/django/contrib/auth/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,153 root INFO copying build/lib/django/contrib/auth/hashers.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,153 root INFO copying build/lib/django/contrib/auth/signals.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,153 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/handlers
2025-04-22 17:58:55,153 root INFO copying build/lib/django/contrib/auth/handlers/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/handlers
2025-04-22 17:58:55,153 root INFO copying build/lib/django/contrib/auth/handlers/modwsgi.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/handlers
2025-04-22 17:58:55,154 root INFO copying build/lib/django/contrib/auth/middleware.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,154 root INFO copying build/lib/django/contrib/auth/views.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,154 root INFO copying build/lib/django/contrib/auth/forms.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,154 root INFO copying build/lib/django/contrib/auth/validators.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,154 root INFO copying build/lib/django/contrib/auth/decorators.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,155 root INFO copying build/lib/django/contrib/auth/models.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,155 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/migrations
2025-04-22 17:58:55,155 root INFO copying build/lib/django/contrib/auth/migrations/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/migrations
2025-04-22 17:58:55,155 root INFO copying build/lib/django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/migrations
2025-04-22 17:58:55,155 root INFO copying build/lib/django/contrib/auth/migrations/0002_alter_permission_name_max_length.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/migrations
2025-04-22 17:58:55,156 root INFO copying build/lib/django/contrib/auth/migrations/0008_alter_user_username_max_length.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/migrations
2025-04-22 17:58:55,156 root INFO copying build/lib/django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/migrations
2025-04-22 17:58:55,156 root INFO copying build/lib/django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/migrations
2025-04-22 17:58:55,156 root INFO copying build/lib/django/contrib/auth/migrations/0006_require_contenttypes_0002.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/migrations
2025-04-22 17:58:55,156 root INFO copying build/lib/django/contrib/auth/migrations/0011_update_proxy_permissions.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/migrations
2025-04-22 17:58:55,157 root INFO copying build/lib/django/contrib/auth/migrations/0005_alter_user_last_login_null.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/migrations
2025-04-22 17:58:55,157 root INFO copying build/lib/django/contrib/auth/migrations/0001_initial.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/migrations
2025-04-22 17:58:55,157 root INFO copying build/lib/django/contrib/auth/migrations/0010_alter_group_name_max_length.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/migrations
2025-04-22 17:58:55,157 root INFO copying build/lib/django/contrib/auth/migrations/0003_alter_user_email_max_length.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/migrations
2025-04-22 17:58:55,157 root INFO copying build/lib/django/contrib/auth/migrations/0004_alter_user_username_opts.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/migrations
2025-04-22 17:58:55,157 root INFO copying build/lib/django/contrib/auth/backends.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,158 root INFO copying build/lib/django/contrib/auth/apps.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,158 root INFO copying build/lib/django/contrib/auth/urls.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,158 root INFO copying build/lib/django/contrib/auth/admin.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,158 root INFO copying build/lib/django/contrib/auth/common-passwords.txt.gz -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,159 root INFO copying build/lib/django/contrib/auth/checks.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,159 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/management
2025-04-22 17:58:55,159 root INFO copying build/lib/django/contrib/auth/management/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/management
2025-04-22 17:58:55,159 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/management/commands
2025-04-22 17:58:55,160 root INFO copying build/lib/django/contrib/auth/management/commands/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/management/commands
2025-04-22 17:58:55,160 root INFO copying build/lib/django/contrib/auth/management/commands/createsuperuser.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/management/commands
2025-04-22 17:58:55,160 root INFO copying build/lib/django/contrib/auth/management/commands/changepassword.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/management/commands
2025-04-22 17:58:55,160 root INFO copying build/lib/django/contrib/auth/context_processors.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,160 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale
2025-04-22 17:58:55,161 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/lv
2025-04-22 17:58:55,161 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,161 root INFO copying build/lib/django/contrib/auth/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,161 root INFO copying build/lib/django/contrib/auth/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,162 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/sw
2025-04-22 17:58:55,162 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,162 root INFO copying build/lib/django/contrib/auth/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,162 root INFO copying build/lib/django/contrib/auth/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,162 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/en_AU
2025-04-22 17:58:55,163 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,163 root INFO copying build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,163 root INFO copying build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,163 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/mr
2025-04-22 17:58:55,163 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,164 root INFO copying build/lib/django/contrib/auth/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,164 root INFO copying build/lib/django/contrib/auth/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,164 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/lb
2025-04-22 17:58:55,164 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,164 root INFO copying build/lib/django/contrib/auth/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,165 root INFO copying build/lib/django/contrib/auth/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,165 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ca
2025-04-22 17:58:55,165 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,165 root INFO copying build/lib/django/contrib/auth/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,165 root INFO copying build/lib/django/contrib/auth/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,166 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/en_GB
2025-04-22 17:58:55,166 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,166 root INFO copying build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,166 root INFO copying build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,167 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/el
2025-04-22 17:58:55,167 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/el/LC_MESSAGES
2025-04-22 17:58:55,167 root INFO copying build/lib/django/contrib/auth/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/el/LC_MESSAGES
2025-04-22 17:58:55,167 root INFO copying build/lib/django/contrib/auth/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/el/LC_MESSAGES
2025-04-22 17:58:55,167 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/es_VE
2025-04-22 17:58:55,168 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,168 root INFO copying build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,168 root INFO copying build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,168 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/af
2025-04-22 17:58:55,168 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/af/LC_MESSAGES
2025-04-22 17:58:55,169 root INFO copying build/lib/django/contrib/auth/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/af/LC_MESSAGES
2025-04-22 17:58:55,169 root INFO copying build/lib/django/contrib/auth/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/af/LC_MESSAGES
2025-04-22 17:58:55,169 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/en
2025-04-22 17:58:55,169 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/en/LC_MESSAGES
2025-04-22 17:58:55,169 root INFO copying build/lib/django/contrib/auth/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/en/LC_MESSAGES
2025-04-22 17:58:55,170 root INFO copying build/lib/django/contrib/auth/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/en/LC_MESSAGES
2025-04-22 17:58:55,170 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/dsb
2025-04-22 17:58:55,170 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,170 root INFO copying build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,171 root INFO copying build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,171 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/et
2025-04-22 17:58:55,171 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/et/LC_MESSAGES
2025-04-22 17:58:55,171 root INFO copying build/lib/django/contrib/auth/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/et/LC_MESSAGES
2025-04-22 17:58:55,171 root INFO copying build/lib/django/contrib/auth/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/et/LC_MESSAGES
2025-04-22 17:58:55,172 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/nn
2025-04-22 17:58:55,172 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,172 root INFO copying build/lib/django/contrib/auth/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,172 root INFO copying build/lib/django/contrib/auth/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,172 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/cy
2025-04-22 17:58:55,173 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,173 root INFO copying build/lib/django/contrib/auth/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,173 root INFO copying build/lib/django/contrib/auth/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,173 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ko
2025-04-22 17:58:55,174 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,174 root INFO copying build/lib/django/contrib/auth/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,174 root INFO copying build/lib/django/contrib/auth/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,174 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/is
2025-04-22 17:58:55,174 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/is/LC_MESSAGES
2025-04-22 17:58:55,175 root INFO copying build/lib/django/contrib/auth/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/is/LC_MESSAGES
2025-04-22 17:58:55,175 root INFO copying build/lib/django/contrib/auth/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/is/LC_MESSAGES
2025-04-22 17:58:55,175 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/pa
2025-04-22 17:58:55,175 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,175 root INFO copying build/lib/django/contrib/auth/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,176 root INFO copying build/lib/django/contrib/auth/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,176 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/tt
2025-04-22 17:58:55,176 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,176 root INFO copying build/lib/django/contrib/auth/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,177 root INFO copying build/lib/django/contrib/auth/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,177 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ne
2025-04-22 17:58:55,177 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,177 root INFO copying build/lib/django/contrib/auth/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,177 root INFO copying build/lib/django/contrib/auth/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,178 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/sr_Latn
2025-04-22 17:58:55,178 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,178 root INFO copying build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,178 root INFO copying build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,179 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/fy
2025-04-22 17:58:55,179 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,179 root INFO copying build/lib/django/contrib/auth/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,179 root INFO copying build/lib/django/contrib/auth/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,179 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/bg
2025-04-22 17:58:55,180 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,180 root INFO copying build/lib/django/contrib/auth/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,180 root INFO copying build/lib/django/contrib/auth/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,180 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ga
2025-04-22 17:58:55,181 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,181 root INFO copying build/lib/django/contrib/auth/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,181 root INFO copying build/lib/django/contrib/auth/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,181 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/gl
2025-04-22 17:58:55,181 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,181 root INFO copying build/lib/django/contrib/auth/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,182 root INFO copying build/lib/django/contrib/auth/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,182 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/uk
2025-04-22 17:58:55,182 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,182 root INFO copying build/lib/django/contrib/auth/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,183 root INFO copying build/lib/django/contrib/auth/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,183 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/uz
2025-04-22 17:58:55,183 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,183 root INFO copying build/lib/django/contrib/auth/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,184 root INFO copying build/lib/django/contrib/auth/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,184 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/kn
2025-04-22 17:58:55,184 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,184 root INFO copying build/lib/django/contrib/auth/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,184 root INFO copying build/lib/django/contrib/auth/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,185 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ja
2025-04-22 17:58:55,185 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,185 root INFO copying build/lib/django/contrib/auth/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,185 root INFO copying build/lib/django/contrib/auth/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,186 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/cs
2025-04-22 17:58:55,186 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,186 root INFO copying build/lib/django/contrib/auth/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,186 root INFO copying build/lib/django/contrib/auth/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,186 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/os
2025-04-22 17:58:55,187 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/os/LC_MESSAGES
2025-04-22 17:58:55,187 root INFO copying build/lib/django/contrib/auth/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/os/LC_MESSAGES
2025-04-22 17:58:55,187 root INFO copying build/lib/django/contrib/auth/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/os/LC_MESSAGES
2025-04-22 17:58:55,187 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/tr
2025-04-22 17:58:55,187 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,188 root INFO copying build/lib/django/contrib/auth/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,188 root INFO copying build/lib/django/contrib/auth/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,188 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/io
2025-04-22 17:58:55,188 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/io/LC_MESSAGES
2025-04-22 17:58:55,188 root INFO copying build/lib/django/contrib/auth/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/io/LC_MESSAGES
2025-04-22 17:58:55,189 root INFO copying build/lib/django/contrib/auth/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/io/LC_MESSAGES
2025-04-22 17:58:55,189 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/sl
2025-04-22 17:58:55,189 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,189 root INFO copying build/lib/django/contrib/auth/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,190 root INFO copying build/lib/django/contrib/auth/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,190 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/sq
2025-04-22 17:58:55,190 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,190 root INFO copying build/lib/django/contrib/auth/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,190 root INFO copying build/lib/django/contrib/auth/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,191 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/az
2025-04-22 17:58:55,191 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/az/LC_MESSAGES
2025-04-22 17:58:55,191 root INFO copying build/lib/django/contrib/auth/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/az/LC_MESSAGES
2025-04-22 17:58:55,191 root INFO copying build/lib/django/contrib/auth/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/az/LC_MESSAGES
2025-04-22 17:58:55,191 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/eo
2025-04-22 17:58:55,192 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,192 root INFO copying build/lib/django/contrib/auth/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,192 root INFO copying build/lib/django/contrib/auth/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,192 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/pt_BR
2025-04-22 17:58:55,192 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,193 root INFO copying build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,193 root INFO copying build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,193 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/pl
2025-04-22 17:58:55,193 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,193 root INFO copying build/lib/django/contrib/auth/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,194 root INFO copying build/lib/django/contrib/auth/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,194 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/gd
2025-04-22 17:58:55,194 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,194 root INFO copying build/lib/django/contrib/auth/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,195 root INFO copying build/lib/django/contrib/auth/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,195 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/hr
2025-04-22 17:58:55,195 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,195 root INFO copying build/lib/django/contrib/auth/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,195 root INFO copying build/lib/django/contrib/auth/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,196 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ru
2025-04-22 17:58:55,196 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,196 root INFO copying build/lib/django/contrib/auth/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,196 root INFO copying build/lib/django/contrib/auth/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,197 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/es
2025-04-22 17:58:55,197 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/es/LC_MESSAGES
2025-04-22 17:58:55,197 root INFO copying build/lib/django/contrib/auth/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/es/LC_MESSAGES
2025-04-22 17:58:55,197 root INFO copying build/lib/django/contrib/auth/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/es/LC_MESSAGES
2025-04-22 17:58:55,197 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/id
2025-04-22 17:58:55,198 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/id/LC_MESSAGES
2025-04-22 17:58:55,198 root INFO copying build/lib/django/contrib/auth/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/id/LC_MESSAGES
2025-04-22 17:58:55,198 root INFO copying build/lib/django/contrib/auth/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/id/LC_MESSAGES
2025-04-22 17:58:55,198 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/fi
2025-04-22 17:58:55,198 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,199 root INFO copying build/lib/django/contrib/auth/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,199 root INFO copying build/lib/django/contrib/auth/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,199 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/mk
2025-04-22 17:58:55,199 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,199 root INFO copying build/lib/django/contrib/auth/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,200 root INFO copying build/lib/django/contrib/auth/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,200 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/hi
2025-04-22 17:58:55,200 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,200 root INFO copying build/lib/django/contrib/auth/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,201 root INFO copying build/lib/django/contrib/auth/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,201 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/kab
2025-04-22 17:58:55,201 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,201 root INFO copying build/lib/django/contrib/auth/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,201 root INFO copying build/lib/django/contrib/auth/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,202 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/hsb
2025-04-22 17:58:55,202 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,202 root INFO copying build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,202 root INFO copying build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,202 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/sk
2025-04-22 17:58:55,203 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,203 root INFO copying build/lib/django/contrib/auth/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,203 root INFO copying build/lib/django/contrib/auth/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,203 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/lt
2025-04-22 17:58:55,203 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,204 root INFO copying build/lib/django/contrib/auth/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,204 root INFO copying build/lib/django/contrib/auth/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,204 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/de
2025-04-22 17:58:55,204 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/de/LC_MESSAGES
2025-04-22 17:58:55,204 root INFO copying build/lib/django/contrib/auth/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/de/LC_MESSAGES
2025-04-22 17:58:55,205 root INFO copying build/lib/django/contrib/auth/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/de/LC_MESSAGES
2025-04-22 17:58:55,205 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/it
2025-04-22 17:58:55,205 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/it/LC_MESSAGES
2025-04-22 17:58:55,205 root INFO copying build/lib/django/contrib/auth/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/it/LC_MESSAGES
2025-04-22 17:58:55,206 root INFO copying build/lib/django/contrib/auth/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/it/LC_MESSAGES
2025-04-22 17:58:55,206 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/my
2025-04-22 17:58:55,206 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/my/LC_MESSAGES
2025-04-22 17:58:55,206 root INFO copying build/lib/django/contrib/auth/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/my/LC_MESSAGES
2025-04-22 17:58:55,206 root INFO copying build/lib/django/contrib/auth/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/my/LC_MESSAGES
2025-04-22 17:58:55,207 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/sr
2025-04-22 17:58:55,207 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,207 root INFO copying build/lib/django/contrib/auth/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,207 root INFO copying build/lib/django/contrib/auth/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,208 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/bs
2025-04-22 17:58:55,208 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,208 root INFO copying build/lib/django/contrib/auth/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,208 root INFO copying build/lib/django/contrib/auth/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,208 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ro
2025-04-22 17:58:55,209 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,209 root INFO copying build/lib/django/contrib/auth/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,209 root INFO copying build/lib/django/contrib/auth/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,209 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ky
2025-04-22 17:58:55,210 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,210 root INFO copying build/lib/django/contrib/auth/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,210 root INFO copying build/lib/django/contrib/auth/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,210 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/fr
2025-04-22 17:58:55,212 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,213 root INFO copying build/lib/django/contrib/auth/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,213 root INFO copying build/lib/django/contrib/auth/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,213 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ar
2025-04-22 17:58:55,213 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,214 root INFO copying build/lib/django/contrib/auth/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,214 root INFO copying build/lib/django/contrib/auth/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,214 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/hy
2025-04-22 17:58:55,214 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,214 root INFO copying build/lib/django/contrib/auth/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,215 root INFO copying build/lib/django/contrib/auth/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,215 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/es_AR
2025-04-22 17:58:55,215 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,215 root INFO copying build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,216 root INFO copying build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,216 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/vi
2025-04-22 17:58:55,216 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,216 root INFO copying build/lib/django/contrib/auth/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,216 root INFO copying build/lib/django/contrib/auth/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,217 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ckb
2025-04-22 17:58:55,217 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,217 root INFO copying build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,217 root INFO copying build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,218 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/sv
2025-04-22 17:58:55,218 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,218 root INFO copying build/lib/django/contrib/auth/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,218 root INFO copying build/lib/django/contrib/auth/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,218 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/zh_Hant
2025-04-22 17:58:55,219 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,219 root INFO copying build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,219 root INFO copying build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,219 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/kk
2025-04-22 17:58:55,220 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,220 root INFO copying build/lib/django/contrib/auth/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,220 root INFO copying build/lib/django/contrib/auth/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,220 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/es_CO
2025-04-22 17:58:55,220 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,221 root INFO copying build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,221 root INFO copying build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,221 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/be
2025-04-22 17:58:55,221 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/be/LC_MESSAGES
2025-04-22 17:58:55,221 root INFO copying build/lib/django/contrib/auth/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/be/LC_MESSAGES
2025-04-22 17:58:55,222 root INFO copying build/lib/django/contrib/auth/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/be/LC_MESSAGES
2025-04-22 17:58:55,222 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/udm
2025-04-22 17:58:55,222 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,222 root INFO copying build/lib/django/contrib/auth/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,222 root INFO copying build/lib/django/contrib/auth/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,223 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ml
2025-04-22 17:58:55,223 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,223 root INFO copying build/lib/django/contrib/auth/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,223 root INFO copying build/lib/django/contrib/auth/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,224 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ar_DZ
2025-04-22 17:58:55,224 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,224 root INFO copying build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,224 root INFO copying build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,225 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ms
2025-04-22 17:58:55,225 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,225 root INFO copying build/lib/django/contrib/auth/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,225 root INFO copying build/lib/django/contrib/auth/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,225 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ast
2025-04-22 17:58:55,226 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,226 root INFO copying build/lib/django/contrib/auth/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,226 root INFO copying build/lib/django/contrib/auth/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,226 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/zh_Hans
2025-04-22 17:58:55,226 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,227 root INFO copying build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,227 root INFO copying build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,227 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ur
2025-04-22 17:58:55,227 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,227 root INFO copying build/lib/django/contrib/auth/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,228 root INFO copying build/lib/django/contrib/auth/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,228 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ia
2025-04-22 17:58:55,228 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,228 root INFO copying build/lib/django/contrib/auth/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,229 root INFO copying build/lib/django/contrib/auth/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,229 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/hu
2025-04-22 17:58:55,229 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,229 root INFO copying build/lib/django/contrib/auth/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,229 root INFO copying build/lib/django/contrib/auth/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,230 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ta
2025-04-22 17:58:55,230 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,230 root INFO copying build/lib/django/contrib/auth/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,230 root INFO copying build/lib/django/contrib/auth/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,231 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/eu
2025-04-22 17:58:55,231 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,231 root INFO copying build/lib/django/contrib/auth/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,231 root INFO copying build/lib/django/contrib/auth/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,231 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/es_MX
2025-04-22 17:58:55,232 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,232 root INFO copying build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,232 root INFO copying build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,232 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/tk
2025-04-22 17:58:55,232 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,233 root INFO copying build/lib/django/contrib/auth/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,233 root INFO copying build/lib/django/contrib/auth/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,233 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/th
2025-04-22 17:58:55,233 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/th/LC_MESSAGES
2025-04-22 17:58:55,233 root INFO copying build/lib/django/contrib/auth/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/th/LC_MESSAGES
2025-04-22 17:58:55,234 root INFO copying build/lib/django/contrib/auth/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/th/LC_MESSAGES
2025-04-22 17:58:55,234 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/nb
2025-04-22 17:58:55,234 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,234 root INFO copying build/lib/django/contrib/auth/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,234 root INFO copying build/lib/django/contrib/auth/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,235 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/mn
2025-04-22 17:58:55,235 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,235 root INFO copying build/lib/django/contrib/auth/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,235 root INFO copying build/lib/django/contrib/auth/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,236 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ka
2025-04-22 17:58:55,236 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,236 root INFO copying build/lib/django/contrib/auth/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,236 root INFO copying build/lib/django/contrib/auth/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,236 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/nl
2025-04-22 17:58:55,237 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,237 root INFO copying build/lib/django/contrib/auth/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,237 root INFO copying build/lib/django/contrib/auth/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,237 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/te
2025-04-22 17:58:55,238 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/te/LC_MESSAGES
2025-04-22 17:58:55,238 root INFO copying build/lib/django/contrib/auth/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/te/LC_MESSAGES
2025-04-22 17:58:55,238 root INFO copying build/lib/django/contrib/auth/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/te/LC_MESSAGES
2025-04-22 17:58:55,238 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/pt
2025-04-22 17:58:55,238 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,239 root INFO copying build/lib/django/contrib/auth/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,239 root INFO copying build/lib/django/contrib/auth/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,239 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/bn
2025-04-22 17:58:55,239 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,239 root INFO copying build/lib/django/contrib/auth/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,240 root INFO copying build/lib/django/contrib/auth/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,240 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/he
2025-04-22 17:58:55,240 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/he/LC_MESSAGES
2025-04-22 17:58:55,240 root INFO copying build/lib/django/contrib/auth/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/he/LC_MESSAGES
2025-04-22 17:58:55,240 root INFO copying build/lib/django/contrib/auth/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/he/LC_MESSAGES
2025-04-22 17:58:55,241 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/br
2025-04-22 17:58:55,241 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/br/LC_MESSAGES
2025-04-22 17:58:55,241 root INFO copying build/lib/django/contrib/auth/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/br/LC_MESSAGES
2025-04-22 17:58:55,241 root INFO copying build/lib/django/contrib/auth/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/br/LC_MESSAGES
2025-04-22 17:58:55,242 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/fa
2025-04-22 17:58:55,242 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,242 root INFO copying build/lib/django/contrib/auth/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,242 root INFO copying build/lib/django/contrib/auth/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,242 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/tg
2025-04-22 17:58:55,243 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,243 root INFO copying build/lib/django/contrib/auth/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,243 root INFO copying build/lib/django/contrib/auth/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,243 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/km
2025-04-22 17:58:55,243 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/km/LC_MESSAGES
2025-04-22 17:58:55,244 root INFO copying build/lib/django/contrib/auth/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/km/LC_MESSAGES
2025-04-22 17:58:55,244 root INFO copying build/lib/django/contrib/auth/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/km/LC_MESSAGES
2025-04-22 17:58:55,244 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/da
2025-04-22 17:58:55,244 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/locale/da/LC_MESSAGES
2025-04-22 17:58:55,244 root INFO copying build/lib/django/contrib/auth/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/da/LC_MESSAGES
2025-04-22 17:58:55,245 root INFO copying build/lib/django/contrib/auth/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/locale/da/LC_MESSAGES
2025-04-22 17:58:55,245 root INFO copying build/lib/django/contrib/auth/tokens.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,245 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/templates
2025-04-22 17:58:55,245 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/templates/auth
2025-04-22 17:58:55,246 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/templates/auth/widgets
2025-04-22 17:58:55,246 root INFO copying build/lib/django/contrib/auth/templates/auth/widgets/read_only_password_hash.html -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/templates/auth/widgets
2025-04-22 17:58:55,246 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/auth/templates/registration
2025-04-22 17:58:55,246 root INFO copying build/lib/django/contrib/auth/templates/registration/password_reset_subject.txt -> build/bdist.linux-armv8l/wheel/./django/contrib/auth/templates/registration
2025-04-22 17:58:55,246 root INFO copying build/lib/django/contrib/auth/base_user.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,247 root INFO copying build/lib/django/contrib/auth/password_validation.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,247 root INFO copying build/lib/django/contrib/auth/mixins.py -> build/bdist.linux-armv8l/wheel/./django/contrib/auth
2025-04-22 17:58:55,247 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes
2025-04-22 17:58:55,247 root INFO copying build/lib/django/contrib/contenttypes/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes
2025-04-22 17:58:55,248 root INFO copying build/lib/django/contrib/contenttypes/views.py -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes
2025-04-22 17:58:55,248 root INFO copying build/lib/django/contrib/contenttypes/forms.py -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes
2025-04-22 17:58:55,248 root INFO copying build/lib/django/contrib/contenttypes/models.py -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes
2025-04-22 17:58:55,248 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/migrations
2025-04-22 17:58:55,248 root INFO copying build/lib/django/contrib/contenttypes/migrations/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/migrations
2025-04-22 17:58:55,249 root INFO copying build/lib/django/contrib/contenttypes/migrations/0001_initial.py -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/migrations
2025-04-22 17:58:55,249 root INFO copying build/lib/django/contrib/contenttypes/migrations/0002_remove_content_type_name.py -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/migrations
2025-04-22 17:58:55,249 root INFO copying build/lib/django/contrib/contenttypes/apps.py -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes
2025-04-22 17:58:55,249 root INFO copying build/lib/django/contrib/contenttypes/admin.py -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes
2025-04-22 17:58:55,249 root INFO copying build/lib/django/contrib/contenttypes/checks.py -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes
2025-04-22 17:58:55,250 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/management
2025-04-22 17:58:55,250 root INFO copying build/lib/django/contrib/contenttypes/management/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/management
2025-04-22 17:58:55,250 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/management/commands
2025-04-22 17:58:55,250 root INFO copying build/lib/django/contrib/contenttypes/management/commands/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/management/commands
2025-04-22 17:58:55,250 root INFO copying build/lib/django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/management/commands
2025-04-22 17:58:55,251 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale
2025-04-22 17:58:55,251 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/lv
2025-04-22 17:58:55,251 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,251 root INFO copying build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,252 root INFO copying build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,252 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/sw
2025-04-22 17:58:55,252 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,252 root INFO copying build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,252 root INFO copying build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,253 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/en_AU
2025-04-22 17:58:55,253 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,253 root INFO copying build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,253 root INFO copying build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,254 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/mr
2025-04-22 17:58:55,254 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,254 root INFO copying build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,254 root INFO copying build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,254 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/lb
2025-04-22 17:58:55,255 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,255 root INFO copying build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,255 root INFO copying build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,255 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ca
2025-04-22 17:58:55,256 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,256 root INFO copying build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,256 root INFO copying build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,256 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/en_GB
2025-04-22 17:58:55,256 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,257 root INFO copying build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,257 root INFO copying build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,257 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/el
2025-04-22 17:58:55,257 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/el/LC_MESSAGES
2025-04-22 17:58:55,257 root INFO copying build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/el/LC_MESSAGES
2025-04-22 17:58:55,258 root INFO copying build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/el/LC_MESSAGES
2025-04-22 17:58:55,258 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/es_VE
2025-04-22 17:58:55,258 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,258 root INFO copying build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,258 root INFO copying build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,259 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/af
2025-04-22 17:58:55,259 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/af/LC_MESSAGES
2025-04-22 17:58:55,259 root INFO copying build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/af/LC_MESSAGES
2025-04-22 17:58:55,259 root INFO copying build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/af/LC_MESSAGES
2025-04-22 17:58:55,259 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/en
2025-04-22 17:58:55,260 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/en/LC_MESSAGES
2025-04-22 17:58:55,260 root INFO copying build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/en/LC_MESSAGES
2025-04-22 17:58:55,260 root INFO copying build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/en/LC_MESSAGES
2025-04-22 17:58:55,260 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/dsb
2025-04-22 17:58:55,260 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,261 root INFO copying build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,261 root INFO copying build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,261 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/et
2025-04-22 17:58:55,261 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/et/LC_MESSAGES
2025-04-22 17:58:55,261 root INFO copying build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/et/LC_MESSAGES
2025-04-22 17:58:55,262 root INFO copying build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/et/LC_MESSAGES
2025-04-22 17:58:55,262 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/nn
2025-04-22 17:58:55,262 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,262 root INFO copying build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,262 root INFO copying build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,263 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/cy
2025-04-22 17:58:55,263 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,263 root INFO copying build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,263 root INFO copying build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,264 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ko
2025-04-22 17:58:55,264 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,264 root INFO copying build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,264 root INFO copying build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,264 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/is
2025-04-22 17:58:55,265 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/is/LC_MESSAGES
2025-04-22 17:58:55,265 root INFO copying build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/is/LC_MESSAGES
2025-04-22 17:58:55,265 root INFO copying build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/is/LC_MESSAGES
2025-04-22 17:58:55,265 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/pa
2025-04-22 17:58:55,265 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,266 root INFO copying build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,266 root INFO copying build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,266 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/tt
2025-04-22 17:58:55,266 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,266 root INFO copying build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,267 root INFO copying build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,267 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ne
2025-04-22 17:58:55,267 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,267 root INFO copying build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,267 root INFO copying build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,268 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/sr_Latn
2025-04-22 17:58:55,268 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,268 root INFO copying build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,268 root INFO copying build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,268 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/fy
2025-04-22 17:58:55,269 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,269 root INFO copying build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,269 root INFO copying build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,269 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/bg
2025-04-22 17:58:55,270 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,270 root INFO copying build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,270 root INFO copying build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,270 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ga
2025-04-22 17:58:55,270 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,271 root INFO copying build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,271 root INFO copying build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,271 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/gl
2025-04-22 17:58:55,271 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,271 root INFO copying build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,272 root INFO copying build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,272 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/uk
2025-04-22 17:58:55,272 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,272 root INFO copying build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,272 root INFO copying build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,273 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/kn
2025-04-22 17:58:55,273 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,273 root INFO copying build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,273 root INFO copying build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,273 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ja
2025-04-22 17:58:55,274 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,274 root INFO copying build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,274 root INFO copying build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,274 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/cs
2025-04-22 17:58:55,275 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,275 root INFO copying build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,275 root INFO copying build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,275 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/os
2025-04-22 17:58:55,275 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/os/LC_MESSAGES
2025-04-22 17:58:55,275 root INFO copying build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/os/LC_MESSAGES
2025-04-22 17:58:55,276 root INFO copying build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/os/LC_MESSAGES
2025-04-22 17:58:55,276 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/tr
2025-04-22 17:58:55,276 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,276 root INFO copying build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,277 root INFO copying build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,277 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/io
2025-04-22 17:58:55,277 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/io/LC_MESSAGES
2025-04-22 17:58:55,277 root INFO copying build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/io/LC_MESSAGES
2025-04-22 17:58:55,277 root INFO copying build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/io/LC_MESSAGES
2025-04-22 17:58:55,278 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/sl
2025-04-22 17:58:55,278 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,278 root INFO copying build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,278 root INFO copying build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,278 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/sq
2025-04-22 17:58:55,279 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,279 root INFO copying build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,279 root INFO copying build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,279 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/az
2025-04-22 17:58:55,279 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/az/LC_MESSAGES
2025-04-22 17:58:55,280 root INFO copying build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/az/LC_MESSAGES
2025-04-22 17:58:55,280 root INFO copying build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/az/LC_MESSAGES
2025-04-22 17:58:55,280 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/eo
2025-04-22 17:58:55,280 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,280 root INFO copying build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,281 root INFO copying build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,281 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/pt_BR
2025-04-22 17:58:55,281 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,281 root INFO copying build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,281 root INFO copying build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,282 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/pl
2025-04-22 17:58:55,282 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,282 root INFO copying build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,282 root INFO copying build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,283 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/gd
2025-04-22 17:58:55,283 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,283 root INFO copying build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,283 root INFO copying build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,283 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/hr
2025-04-22 17:58:55,284 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,284 root INFO copying build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,284 root INFO copying build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,284 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ru
2025-04-22 17:58:55,284 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,285 root INFO copying build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,285 root INFO copying build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,285 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/es
2025-04-22 17:58:55,285 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/es/LC_MESSAGES
2025-04-22 17:58:55,285 root INFO copying build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/es/LC_MESSAGES
2025-04-22 17:58:55,286 root INFO copying build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/es/LC_MESSAGES
2025-04-22 17:58:55,286 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/id
2025-04-22 17:58:55,286 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/id/LC_MESSAGES
2025-04-22 17:58:55,286 root INFO copying build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/id/LC_MESSAGES
2025-04-22 17:58:55,287 root INFO copying build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/id/LC_MESSAGES
2025-04-22 17:58:55,287 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/fi
2025-04-22 17:58:55,287 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,287 root INFO copying build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,287 root INFO copying build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,288 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/mk
2025-04-22 17:58:55,288 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,288 root INFO copying build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,288 root INFO copying build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,289 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/hi
2025-04-22 17:58:55,289 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,289 root INFO copying build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,289 root INFO copying build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,289 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/hsb
2025-04-22 17:58:55,290 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,290 root INFO copying build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,290 root INFO copying build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,290 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/sk
2025-04-22 17:58:55,290 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,291 root INFO copying build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,291 root INFO copying build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,291 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/lt
2025-04-22 17:58:55,291 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,291 root INFO copying build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,292 root INFO copying build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,292 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/de
2025-04-22 17:58:55,292 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/de/LC_MESSAGES
2025-04-22 17:58:55,292 root INFO copying build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/de/LC_MESSAGES
2025-04-22 17:58:55,292 root INFO copying build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/de/LC_MESSAGES
2025-04-22 17:58:55,293 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/it
2025-04-22 17:58:55,293 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/it/LC_MESSAGES
2025-04-22 17:58:55,293 root INFO copying build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/it/LC_MESSAGES
2025-04-22 17:58:55,293 root INFO copying build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/it/LC_MESSAGES
2025-04-22 17:58:55,294 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/my
2025-04-22 17:58:55,294 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/my/LC_MESSAGES
2025-04-22 17:58:55,294 root INFO copying build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/my/LC_MESSAGES
2025-04-22 17:58:55,294 root INFO copying build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/my/LC_MESSAGES
2025-04-22 17:58:55,294 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/sr
2025-04-22 17:58:55,295 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,295 root INFO copying build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,295 root INFO copying build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,295 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/bs
2025-04-22 17:58:55,295 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,296 root INFO copying build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,296 root INFO copying build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,296 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ro
2025-04-22 17:58:55,296 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,296 root INFO copying build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,297 root INFO copying build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,297 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ky
2025-04-22 17:58:55,297 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,297 root INFO copying build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,297 root INFO copying build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,298 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/fr
2025-04-22 17:58:55,298 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,298 root INFO copying build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,298 root INFO copying build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,299 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ar
2025-04-22 17:58:55,299 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,299 root INFO copying build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,299 root INFO copying build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,299 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/hy
2025-04-22 17:58:55,300 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,300 root INFO copying build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,300 root INFO copying build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,300 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/es_AR
2025-04-22 17:58:55,300 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,301 root INFO copying build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,301 root INFO copying build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,301 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/vi
2025-04-22 17:58:55,301 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,301 root INFO copying build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,302 root INFO copying build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,302 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ckb
2025-04-22 17:58:55,302 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,302 root INFO copying build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,302 root INFO copying build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,303 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/sv
2025-04-22 17:58:55,303 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,303 root INFO copying build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,303 root INFO copying build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,304 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/zh_Hant
2025-04-22 17:58:55,304 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,304 root INFO copying build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,304 root INFO copying build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,304 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/kk
2025-04-22 17:58:55,305 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,305 root INFO copying build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,305 root INFO copying build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,305 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/es_CO
2025-04-22 17:58:55,305 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,306 root INFO copying build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,306 root INFO copying build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,306 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/be
2025-04-22 17:58:55,306 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/be/LC_MESSAGES
2025-04-22 17:58:55,306 root INFO copying build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/be/LC_MESSAGES
2025-04-22 17:58:55,307 root INFO copying build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/be/LC_MESSAGES
2025-04-22 17:58:55,307 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/udm
2025-04-22 17:58:55,307 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,307 root INFO copying build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,307 root INFO copying build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,308 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ml
2025-04-22 17:58:55,308 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,308 root INFO copying build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,308 root INFO copying build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,309 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ar_DZ
2025-04-22 17:58:55,309 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,309 root INFO copying build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,309 root INFO copying build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,309 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ms
2025-04-22 17:58:55,310 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,310 root INFO copying build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,310 root INFO copying build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,310 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ast
2025-04-22 17:58:55,311 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,311 root INFO copying build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,311 root INFO copying build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,311 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/zh_Hans
2025-04-22 17:58:55,311 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,312 root INFO copying build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,312 root INFO copying build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,312 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ur
2025-04-22 17:58:55,312 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,312 root INFO copying build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,313 root INFO copying build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,313 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ia
2025-04-22 17:58:55,313 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,313 root INFO copying build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,314 root INFO copying build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,314 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/hu
2025-04-22 17:58:55,314 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,314 root INFO copying build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,314 root INFO copying build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,315 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ta
2025-04-22 17:58:55,315 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,315 root INFO copying build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,315 root INFO copying build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,316 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/eu
2025-04-22 17:58:55,316 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,316 root INFO copying build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,316 root INFO copying build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,316 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/es_MX
2025-04-22 17:58:55,317 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,317 root INFO copying build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,317 root INFO copying build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,317 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/tk
2025-04-22 17:58:55,317 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,318 root INFO copying build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,318 root INFO copying build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,318 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/th
2025-04-22 17:58:55,318 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/th/LC_MESSAGES
2025-04-22 17:58:55,318 root INFO copying build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/th/LC_MESSAGES
2025-04-22 17:58:55,319 root INFO copying build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/th/LC_MESSAGES
2025-04-22 17:58:55,319 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/nb
2025-04-22 17:58:55,319 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,319 root INFO copying build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,319 root INFO copying build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,320 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/mn
2025-04-22 17:58:55,320 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,320 root INFO copying build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,320 root INFO copying build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,321 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ka
2025-04-22 17:58:55,321 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,321 root INFO copying build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,321 root INFO copying build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,321 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/nl
2025-04-22 17:58:55,322 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,322 root INFO copying build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,322 root INFO copying build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,322 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/te
2025-04-22 17:58:55,322 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/te/LC_MESSAGES
2025-04-22 17:58:55,322 root INFO copying build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/te/LC_MESSAGES
2025-04-22 17:58:55,323 root INFO copying build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/te/LC_MESSAGES
2025-04-22 17:58:55,323 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/pt
2025-04-22 17:58:55,323 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,323 root INFO copying build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,324 root INFO copying build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,324 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/bn
2025-04-22 17:58:55,324 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,324 root INFO copying build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,324 root INFO copying build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,325 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/he
2025-04-22 17:58:55,325 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/he/LC_MESSAGES
2025-04-22 17:58:55,325 root INFO copying build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/he/LC_MESSAGES
2025-04-22 17:58:55,325 root INFO copying build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/he/LC_MESSAGES
2025-04-22 17:58:55,325 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/br
2025-04-22 17:58:55,326 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/br/LC_MESSAGES
2025-04-22 17:58:55,326 root INFO copying build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/br/LC_MESSAGES
2025-04-22 17:58:55,326 root INFO copying build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/br/LC_MESSAGES
2025-04-22 17:58:55,326 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/fa
2025-04-22 17:58:55,327 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,327 root INFO copying build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,327 root INFO copying build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,327 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/tg
2025-04-22 17:58:55,327 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,327 root INFO copying build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,328 root INFO copying build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,328 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/km
2025-04-22 17:58:55,328 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/km/LC_MESSAGES
2025-04-22 17:58:55,328 root INFO copying build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/km/LC_MESSAGES
2025-04-22 17:58:55,328 root INFO copying build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/km/LC_MESSAGES
2025-04-22 17:58:55,329 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/da
2025-04-22 17:58:55,329 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/contenttypes/locale/da/LC_MESSAGES
2025-04-22 17:58:55,329 root INFO copying build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/da/LC_MESSAGES
2025-04-22 17:58:55,329 root INFO copying build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes/locale/da/LC_MESSAGES
2025-04-22 17:58:55,330 root INFO copying build/lib/django/contrib/contenttypes/fields.py -> build/bdist.linux-armv8l/wheel/./django/contrib/contenttypes
2025-04-22 17:58:55,330 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects
2025-04-22 17:58:55,330 root INFO copying build/lib/django/contrib/redirects/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects
2025-04-22 17:58:55,330 root INFO copying build/lib/django/contrib/redirects/middleware.py -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects
2025-04-22 17:58:55,331 root INFO copying build/lib/django/contrib/redirects/models.py -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects
2025-04-22 17:58:55,331 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/migrations
2025-04-22 17:58:55,331 root INFO copying build/lib/django/contrib/redirects/migrations/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/migrations
2025-04-22 17:58:55,331 root INFO copying build/lib/django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/migrations
2025-04-22 17:58:55,331 root INFO copying build/lib/django/contrib/redirects/migrations/0001_initial.py -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/migrations
2025-04-22 17:58:55,332 root INFO copying build/lib/django/contrib/redirects/apps.py -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects
2025-04-22 17:58:55,332 root INFO copying build/lib/django/contrib/redirects/admin.py -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects
2025-04-22 17:58:55,332 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale
2025-04-22 17:58:55,332 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/lv
2025-04-22 17:58:55,332 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,333 root INFO copying build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,333 root INFO copying build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,333 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/sw
2025-04-22 17:58:55,333 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,333 root INFO copying build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,334 root INFO copying build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,334 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/en_AU
2025-04-22 17:58:55,334 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,334 root INFO copying build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,335 root INFO copying build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,335 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/mr
2025-04-22 17:58:55,335 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,335 root INFO copying build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,335 root INFO copying build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,336 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/lb
2025-04-22 17:58:55,336 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,336 root INFO copying build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,336 root INFO copying build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,337 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ca
2025-04-22 17:58:55,337 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,337 root INFO copying build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,337 root INFO copying build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,337 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/en_GB
2025-04-22 17:58:55,338 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,338 root INFO copying build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,338 root INFO copying build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,338 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/el
2025-04-22 17:58:55,339 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/el/LC_MESSAGES
2025-04-22 17:58:55,339 root INFO copying build/lib/django/contrib/redirects/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/el/LC_MESSAGES
2025-04-22 17:58:55,339 root INFO copying build/lib/django/contrib/redirects/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/el/LC_MESSAGES
2025-04-22 17:58:55,339 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/es_VE
2025-04-22 17:58:55,339 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,339 root INFO copying build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,340 root INFO copying build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,340 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/af
2025-04-22 17:58:55,340 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/af/LC_MESSAGES
2025-04-22 17:58:55,340 root INFO copying build/lib/django/contrib/redirects/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/af/LC_MESSAGES
2025-04-22 17:58:55,341 root INFO copying build/lib/django/contrib/redirects/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/af/LC_MESSAGES
2025-04-22 17:58:55,341 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/en
2025-04-22 17:58:55,341 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/en/LC_MESSAGES
2025-04-22 17:58:55,341 root INFO copying build/lib/django/contrib/redirects/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/en/LC_MESSAGES
2025-04-22 17:58:55,341 root INFO copying build/lib/django/contrib/redirects/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/en/LC_MESSAGES
2025-04-22 17:58:55,342 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/dsb
2025-04-22 17:58:55,342 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,342 root INFO copying build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,342 root INFO copying build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,342 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/et
2025-04-22 17:58:55,343 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/et/LC_MESSAGES
2025-04-22 17:58:55,343 root INFO copying build/lib/django/contrib/redirects/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/et/LC_MESSAGES
2025-04-22 17:58:55,343 root INFO copying build/lib/django/contrib/redirects/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/et/LC_MESSAGES
2025-04-22 17:58:55,343 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/nn
2025-04-22 17:58:55,344 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,344 root INFO copying build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,344 root INFO copying build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,344 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/cy
2025-04-22 17:58:55,344 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,344 root INFO copying build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,345 root INFO copying build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,345 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ko
2025-04-22 17:58:55,345 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,345 root INFO copying build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,345 root INFO copying build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,346 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/is
2025-04-22 17:58:55,346 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/is/LC_MESSAGES
2025-04-22 17:58:55,346 root INFO copying build/lib/django/contrib/redirects/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/is/LC_MESSAGES
2025-04-22 17:58:55,346 root INFO copying build/lib/django/contrib/redirects/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/is/LC_MESSAGES
2025-04-22 17:58:55,347 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/pa
2025-04-22 17:58:55,347 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,347 root INFO copying build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,347 root INFO copying build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,347 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/tt
2025-04-22 17:58:55,348 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,348 root INFO copying build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,348 root INFO copying build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,348 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ne
2025-04-22 17:58:55,348 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,349 root INFO copying build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,349 root INFO copying build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,349 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/sr_Latn
2025-04-22 17:58:55,349 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,349 root INFO copying build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,350 root INFO copying build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,350 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/fy
2025-04-22 17:58:55,350 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,350 root INFO copying build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,351 root INFO copying build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,351 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/bg
2025-04-22 17:58:55,351 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,351 root INFO copying build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,351 root INFO copying build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,352 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ga
2025-04-22 17:58:55,352 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,352 root INFO copying build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,352 root INFO copying build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,352 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/gl
2025-04-22 17:58:55,353 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,353 root INFO copying build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,353 root INFO copying build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,353 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/uk
2025-04-22 17:58:55,354 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,354 root INFO copying build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,354 root INFO copying build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,354 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/uz
2025-04-22 17:58:55,354 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,354 root INFO copying build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,355 root INFO copying build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,355 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/kn
2025-04-22 17:58:55,355 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,355 root INFO copying build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,355 root INFO copying build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,356 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ja
2025-04-22 17:58:55,356 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,356 root INFO copying build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,356 root INFO copying build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,357 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/cs
2025-04-22 17:58:55,357 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,357 root INFO copying build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,357 root INFO copying build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,357 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/os
2025-04-22 17:58:55,358 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/os/LC_MESSAGES
2025-04-22 17:58:55,358 root INFO copying build/lib/django/contrib/redirects/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/os/LC_MESSAGES
2025-04-22 17:58:55,358 root INFO copying build/lib/django/contrib/redirects/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/os/LC_MESSAGES
2025-04-22 17:58:55,358 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/tr
2025-04-22 17:58:55,358 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,359 root INFO copying build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,359 root INFO copying build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,359 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/io
2025-04-22 17:58:55,359 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/io/LC_MESSAGES
2025-04-22 17:58:55,360 root INFO copying build/lib/django/contrib/redirects/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/io/LC_MESSAGES
2025-04-22 17:58:55,360 root INFO copying build/lib/django/contrib/redirects/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/io/LC_MESSAGES
2025-04-22 17:58:55,360 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/sl
2025-04-22 17:58:55,360 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,360 root INFO copying build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,361 root INFO copying build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,361 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/sq
2025-04-22 17:58:55,361 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,361 root INFO copying build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,361 root INFO copying build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,362 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/az
2025-04-22 17:58:55,362 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/az/LC_MESSAGES
2025-04-22 17:58:55,362 root INFO copying build/lib/django/contrib/redirects/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/az/LC_MESSAGES
2025-04-22 17:58:55,362 root INFO copying build/lib/django/contrib/redirects/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/az/LC_MESSAGES
2025-04-22 17:58:55,363 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/eo
2025-04-22 17:58:55,363 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,363 root INFO copying build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,363 root INFO copying build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,363 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/pt_BR
2025-04-22 17:58:55,364 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,364 root INFO copying build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,364 root INFO copying build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,364 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/pl
2025-04-22 17:58:55,364 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,365 root INFO copying build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,365 root INFO copying build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,365 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/gd
2025-04-22 17:58:55,365 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,365 root INFO copying build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,366 root INFO copying build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,366 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/hr
2025-04-22 17:58:55,366 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,366 root INFO copying build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,366 root INFO copying build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,367 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ru
2025-04-22 17:58:55,367 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,367 root INFO copying build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,367 root INFO copying build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,368 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/es
2025-04-22 17:58:55,368 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/es/LC_MESSAGES
2025-04-22 17:58:55,368 root INFO copying build/lib/django/contrib/redirects/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/es/LC_MESSAGES
2025-04-22 17:58:55,368 root INFO copying build/lib/django/contrib/redirects/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/es/LC_MESSAGES
2025-04-22 17:58:55,368 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/id
2025-04-22 17:58:55,369 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/id/LC_MESSAGES
2025-04-22 17:58:55,369 root INFO copying build/lib/django/contrib/redirects/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/id/LC_MESSAGES
2025-04-22 17:58:55,369 root INFO copying build/lib/django/contrib/redirects/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/id/LC_MESSAGES
2025-04-22 17:58:55,369 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/fi
2025-04-22 17:58:55,369 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,370 root INFO copying build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,370 root INFO copying build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,370 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/mk
2025-04-22 17:58:55,370 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,370 root INFO copying build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,371 root INFO copying build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,371 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/hi
2025-04-22 17:58:55,371 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,371 root INFO copying build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,371 root INFO copying build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,372 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/kab
2025-04-22 17:58:55,372 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,372 root INFO copying build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,372 root INFO copying build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,372 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/hsb
2025-04-22 17:58:55,373 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,373 root INFO copying build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,373 root INFO copying build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,373 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/sk
2025-04-22 17:58:55,374 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,374 root INFO copying build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,374 root INFO copying build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,374 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/lt
2025-04-22 17:58:55,374 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,375 root INFO copying build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,375 root INFO copying build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,375 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/de
2025-04-22 17:58:55,375 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/de/LC_MESSAGES
2025-04-22 17:58:55,375 root INFO copying build/lib/django/contrib/redirects/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/de/LC_MESSAGES
2025-04-22 17:58:55,376 root INFO copying build/lib/django/contrib/redirects/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/de/LC_MESSAGES
2025-04-22 17:58:55,376 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/it
2025-04-22 17:58:55,376 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/it/LC_MESSAGES
2025-04-22 17:58:55,376 root INFO copying build/lib/django/contrib/redirects/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/it/LC_MESSAGES
2025-04-22 17:58:55,376 root INFO copying build/lib/django/contrib/redirects/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/it/LC_MESSAGES
2025-04-22 17:58:55,377 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/my
2025-04-22 17:58:55,377 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/my/LC_MESSAGES
2025-04-22 17:58:55,377 root INFO copying build/lib/django/contrib/redirects/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/my/LC_MESSAGES
2025-04-22 17:58:55,377 root INFO copying build/lib/django/contrib/redirects/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/my/LC_MESSAGES
2025-04-22 17:58:55,378 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/sr
2025-04-22 17:58:55,378 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,378 root INFO copying build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,378 root INFO copying build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,378 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/bs
2025-04-22 17:58:55,379 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,379 root INFO copying build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,379 root INFO copying build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,379 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ro
2025-04-22 17:58:55,380 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,380 root INFO copying build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,380 root INFO copying build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,380 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ky
2025-04-22 17:58:55,380 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,381 root INFO copying build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,381 root INFO copying build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,381 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/fr
2025-04-22 17:58:55,381 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,381 root INFO copying build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,382 root INFO copying build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,382 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ar
2025-04-22 17:58:55,382 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,382 root INFO copying build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,382 root INFO copying build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,383 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/hy
2025-04-22 17:58:55,383 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,383 root INFO copying build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,383 root INFO copying build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,383 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/es_AR
2025-04-22 17:58:55,384 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,384 root INFO copying build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,384 root INFO copying build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,384 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/vi
2025-04-22 17:58:55,384 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,385 root INFO copying build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,385 root INFO copying build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,385 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ckb
2025-04-22 17:58:55,385 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,385 root INFO copying build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,386 root INFO copying build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,386 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/sv
2025-04-22 17:58:55,386 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,386 root INFO copying build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,386 root INFO copying build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,387 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/zh_Hant
2025-04-22 17:58:55,387 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,387 root INFO copying build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,387 root INFO copying build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,388 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/kk
2025-04-22 17:58:55,388 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,388 root INFO copying build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,388 root INFO copying build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,388 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/es_CO
2025-04-22 17:58:55,389 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,389 root INFO copying build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,389 root INFO copying build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,389 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/be
2025-04-22 17:58:55,389 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/be/LC_MESSAGES
2025-04-22 17:58:55,390 root INFO copying build/lib/django/contrib/redirects/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/be/LC_MESSAGES
2025-04-22 17:58:55,390 root INFO copying build/lib/django/contrib/redirects/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/be/LC_MESSAGES
2025-04-22 17:58:55,390 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/udm
2025-04-22 17:58:55,390 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,390 root INFO copying build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,391 root INFO copying build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,391 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ml
2025-04-22 17:58:55,391 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,391 root INFO copying build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,391 root INFO copying build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,392 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ar_DZ
2025-04-22 17:58:55,392 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,392 root INFO copying build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,392 root INFO copying build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,392 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ms
2025-04-22 17:58:55,393 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,393 root INFO copying build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,393 root INFO copying build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,393 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ast
2025-04-22 17:58:55,394 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,394 root INFO copying build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,394 root INFO copying build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,394 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/zh_Hans
2025-04-22 17:58:55,394 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,395 root INFO copying build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,395 root INFO copying build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,395 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ur
2025-04-22 17:58:55,395 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,395 root INFO copying build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,396 root INFO copying build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,396 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ia
2025-04-22 17:58:55,396 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,396 root INFO copying build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,396 root INFO copying build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,397 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/hu
2025-04-22 17:58:55,397 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,397 root INFO copying build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,397 root INFO copying build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,397 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ta
2025-04-22 17:58:55,398 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,398 root INFO copying build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,398 root INFO copying build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,398 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/eu
2025-04-22 17:58:55,398 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,399 root INFO copying build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,399 root INFO copying build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,399 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/es_MX
2025-04-22 17:58:55,399 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,400 root INFO copying build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,400 root INFO copying build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,400 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/tk
2025-04-22 17:58:55,400 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,400 root INFO copying build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,401 root INFO copying build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,401 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/th
2025-04-22 17:58:55,401 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/th/LC_MESSAGES
2025-04-22 17:58:55,401 root INFO copying build/lib/django/contrib/redirects/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/th/LC_MESSAGES
2025-04-22 17:58:55,401 root INFO copying build/lib/django/contrib/redirects/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/th/LC_MESSAGES
2025-04-22 17:58:55,402 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/nb
2025-04-22 17:58:55,402 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,402 root INFO copying build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,402 root INFO copying build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,403 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/mn
2025-04-22 17:58:55,403 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,403 root INFO copying build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,403 root INFO copying build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,403 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ka
2025-04-22 17:58:55,404 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,404 root INFO copying build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,404 root INFO copying build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,404 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/nl
2025-04-22 17:58:55,404 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,405 root INFO copying build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,405 root INFO copying build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,405 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/te
2025-04-22 17:58:55,405 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/te/LC_MESSAGES
2025-04-22 17:58:55,405 root INFO copying build/lib/django/contrib/redirects/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/te/LC_MESSAGES
2025-04-22 17:58:55,406 root INFO copying build/lib/django/contrib/redirects/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/te/LC_MESSAGES
2025-04-22 17:58:55,406 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/pt
2025-04-22 17:58:55,406 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,406 root INFO copying build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,406 root INFO copying build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,407 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/bn
2025-04-22 17:58:55,407 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,407 root INFO copying build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,407 root INFO copying build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,408 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/he
2025-04-22 17:58:55,408 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/he/LC_MESSAGES
2025-04-22 17:58:55,408 root INFO copying build/lib/django/contrib/redirects/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/he/LC_MESSAGES
2025-04-22 17:58:55,408 root INFO copying build/lib/django/contrib/redirects/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/he/LC_MESSAGES
2025-04-22 17:58:55,408 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/br
2025-04-22 17:58:55,409 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/br/LC_MESSAGES
2025-04-22 17:58:55,409 root INFO copying build/lib/django/contrib/redirects/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/br/LC_MESSAGES
2025-04-22 17:58:55,409 root INFO copying build/lib/django/contrib/redirects/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/br/LC_MESSAGES
2025-04-22 17:58:55,409 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/fa
2025-04-22 17:58:55,409 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,410 root INFO copying build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,410 root INFO copying build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,410 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/tg
2025-04-22 17:58:55,410 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,410 root INFO copying build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,411 root INFO copying build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,411 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/km
2025-04-22 17:58:55,411 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/km/LC_MESSAGES
2025-04-22 17:58:55,411 root INFO copying build/lib/django/contrib/redirects/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/km/LC_MESSAGES
2025-04-22 17:58:55,411 root INFO copying build/lib/django/contrib/redirects/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/km/LC_MESSAGES
2025-04-22 17:58:55,412 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/da
2025-04-22 17:58:55,412 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/redirects/locale/da/LC_MESSAGES
2025-04-22 17:58:55,412 root INFO copying build/lib/django/contrib/redirects/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/da/LC_MESSAGES
2025-04-22 17:58:55,412 root INFO copying build/lib/django/contrib/redirects/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/redirects/locale/da/LC_MESSAGES
2025-04-22 17:58:55,413 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/messages
2025-04-22 17:58:55,413 root INFO copying build/lib/django/contrib/messages/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/messages
2025-04-22 17:58:55,413 root INFO copying build/lib/django/contrib/messages/middleware.py -> build/bdist.linux-armv8l/wheel/./django/contrib/messages
2025-04-22 17:58:55,413 root INFO copying build/lib/django/contrib/messages/views.py -> build/bdist.linux-armv8l/wheel/./django/contrib/messages
2025-04-22 17:58:55,413 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/messages/storage
2025-04-22 17:58:55,414 root INFO copying build/lib/django/contrib/messages/storage/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/messages/storage
2025-04-22 17:58:55,414 root INFO copying build/lib/django/contrib/messages/storage/session.py -> build/bdist.linux-armv8l/wheel/./django/contrib/messages/storage
2025-04-22 17:58:55,414 root INFO copying build/lib/django/contrib/messages/storage/cookie.py -> build/bdist.linux-armv8l/wheel/./django/contrib/messages/storage
2025-04-22 17:58:55,414 root INFO copying build/lib/django/contrib/messages/storage/fallback.py -> build/bdist.linux-armv8l/wheel/./django/contrib/messages/storage
2025-04-22 17:58:55,414 root INFO copying build/lib/django/contrib/messages/storage/base.py -> build/bdist.linux-armv8l/wheel/./django/contrib/messages/storage
2025-04-22 17:58:55,415 root INFO copying build/lib/django/contrib/messages/apps.py -> build/bdist.linux-armv8l/wheel/./django/contrib/messages
2025-04-22 17:58:55,415 root INFO copying build/lib/django/contrib/messages/utils.py -> build/bdist.linux-armv8l/wheel/./django/contrib/messages
2025-04-22 17:58:55,415 root INFO copying build/lib/django/contrib/messages/api.py -> build/bdist.linux-armv8l/wheel/./django/contrib/messages
2025-04-22 17:58:55,415 root INFO copying build/lib/django/contrib/messages/context_processors.py -> build/bdist.linux-armv8l/wheel/./django/contrib/messages
2025-04-22 17:58:55,415 root INFO copying build/lib/django/contrib/messages/constants.py -> build/bdist.linux-armv8l/wheel/./django/contrib/messages
2025-04-22 17:58:55,416 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites
2025-04-22 17:58:55,416 root INFO copying build/lib/django/contrib/sites/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sites
2025-04-22 17:58:55,416 root INFO copying build/lib/django/contrib/sites/managers.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sites
2025-04-22 17:58:55,416 root INFO copying build/lib/django/contrib/sites/middleware.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sites
2025-04-22 17:58:55,416 root INFO copying build/lib/django/contrib/sites/models.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sites
2025-04-22 17:58:55,417 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/migrations
2025-04-22 17:58:55,417 root INFO copying build/lib/django/contrib/sites/migrations/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/migrations
2025-04-22 17:58:55,417 root INFO copying build/lib/django/contrib/sites/migrations/0001_initial.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/migrations
2025-04-22 17:58:55,417 root INFO copying build/lib/django/contrib/sites/migrations/0002_alter_domain_unique.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/migrations
2025-04-22 17:58:55,417 root INFO copying build/lib/django/contrib/sites/apps.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sites
2025-04-22 17:58:55,418 root INFO copying build/lib/django/contrib/sites/admin.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sites
2025-04-22 17:58:55,418 root INFO copying build/lib/django/contrib/sites/checks.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sites
2025-04-22 17:58:55,418 root INFO copying build/lib/django/contrib/sites/management.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sites
2025-04-22 17:58:55,418 root INFO copying build/lib/django/contrib/sites/requests.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sites
2025-04-22 17:58:55,418 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale
2025-04-22 17:58:55,419 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/lv
2025-04-22 17:58:55,419 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,419 root INFO copying build/lib/django/contrib/sites/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,419 root INFO copying build/lib/django/contrib/sites/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,419 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/sw
2025-04-22 17:58:55,420 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,420 root INFO copying build/lib/django/contrib/sites/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,420 root INFO copying build/lib/django/contrib/sites/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,420 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/en_AU
2025-04-22 17:58:55,421 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,421 root INFO copying build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,421 root INFO copying build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,421 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/mr
2025-04-22 17:58:55,421 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,421 root INFO copying build/lib/django/contrib/sites/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,422 root INFO copying build/lib/django/contrib/sites/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,422 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/lb
2025-04-22 17:58:55,422 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,422 root INFO copying build/lib/django/contrib/sites/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,422 root INFO copying build/lib/django/contrib/sites/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,423 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ca
2025-04-22 17:58:55,423 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,423 root INFO copying build/lib/django/contrib/sites/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,423 root INFO copying build/lib/django/contrib/sites/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,424 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/en_GB
2025-04-22 17:58:55,424 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,424 root INFO copying build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,424 root INFO copying build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,424 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/el
2025-04-22 17:58:55,425 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/el/LC_MESSAGES
2025-04-22 17:58:55,425 root INFO copying build/lib/django/contrib/sites/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/el/LC_MESSAGES
2025-04-22 17:58:55,425 root INFO copying build/lib/django/contrib/sites/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/el/LC_MESSAGES
2025-04-22 17:58:55,425 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/es_VE
2025-04-22 17:58:55,425 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,426 root INFO copying build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,426 root INFO copying build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,426 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/af
2025-04-22 17:58:55,426 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/af/LC_MESSAGES
2025-04-22 17:58:55,426 root INFO copying build/lib/django/contrib/sites/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/af/LC_MESSAGES
2025-04-22 17:58:55,427 root INFO copying build/lib/django/contrib/sites/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/af/LC_MESSAGES
2025-04-22 17:58:55,427 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/en
2025-04-22 17:58:55,427 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/en/LC_MESSAGES
2025-04-22 17:58:55,427 root INFO copying build/lib/django/contrib/sites/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/en/LC_MESSAGES
2025-04-22 17:58:55,427 root INFO copying build/lib/django/contrib/sites/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/en/LC_MESSAGES
2025-04-22 17:58:55,428 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/dsb
2025-04-22 17:58:55,428 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,428 root INFO copying build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,428 root INFO copying build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,429 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/et
2025-04-22 17:58:55,429 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/et/LC_MESSAGES
2025-04-22 17:58:55,429 root INFO copying build/lib/django/contrib/sites/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/et/LC_MESSAGES
2025-04-22 17:58:55,429 root INFO copying build/lib/django/contrib/sites/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/et/LC_MESSAGES
2025-04-22 17:58:55,429 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/nn
2025-04-22 17:58:55,430 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,430 root INFO copying build/lib/django/contrib/sites/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,430 root INFO copying build/lib/django/contrib/sites/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,430 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/cy
2025-04-22 17:58:55,430 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,430 root INFO copying build/lib/django/contrib/sites/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,431 root INFO copying build/lib/django/contrib/sites/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,431 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ko
2025-04-22 17:58:55,431 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,431 root INFO copying build/lib/django/contrib/sites/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,431 root INFO copying build/lib/django/contrib/sites/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,432 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/is
2025-04-22 17:58:55,432 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/is/LC_MESSAGES
2025-04-22 17:58:55,432 root INFO copying build/lib/django/contrib/sites/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/is/LC_MESSAGES
2025-04-22 17:58:55,432 root INFO copying build/lib/django/contrib/sites/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/is/LC_MESSAGES
2025-04-22 17:58:55,433 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/pa
2025-04-22 17:58:55,433 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,433 root INFO copying build/lib/django/contrib/sites/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,433 root INFO copying build/lib/django/contrib/sites/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,433 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/tt
2025-04-22 17:58:55,434 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,434 root INFO copying build/lib/django/contrib/sites/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,434 root INFO copying build/lib/django/contrib/sites/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,434 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ne
2025-04-22 17:58:55,434 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,435 root INFO copying build/lib/django/contrib/sites/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,435 root INFO copying build/lib/django/contrib/sites/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,435 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/sr_Latn
2025-04-22 17:58:55,435 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,435 root INFO copying build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,436 root INFO copying build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,436 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/fy
2025-04-22 17:58:55,436 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,436 root INFO copying build/lib/django/contrib/sites/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,436 root INFO copying build/lib/django/contrib/sites/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,437 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/bg
2025-04-22 17:58:55,437 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,437 root INFO copying build/lib/django/contrib/sites/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,437 root INFO copying build/lib/django/contrib/sites/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,437 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ga
2025-04-22 17:58:55,438 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,438 root INFO copying build/lib/django/contrib/sites/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,438 root INFO copying build/lib/django/contrib/sites/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,438 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/gl
2025-04-22 17:58:55,439 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,439 root INFO copying build/lib/django/contrib/sites/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,439 root INFO copying build/lib/django/contrib/sites/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,439 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/uk
2025-04-22 17:58:55,439 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,439 root INFO copying build/lib/django/contrib/sites/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,440 root INFO copying build/lib/django/contrib/sites/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,440 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/uz
2025-04-22 17:58:55,440 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,440 root INFO copying build/lib/django/contrib/sites/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,441 root INFO copying build/lib/django/contrib/sites/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,441 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/kn
2025-04-22 17:58:55,441 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,441 root INFO copying build/lib/django/contrib/sites/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,441 root INFO copying build/lib/django/contrib/sites/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,442 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ja
2025-04-22 17:58:55,442 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,442 root INFO copying build/lib/django/contrib/sites/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,442 root INFO copying build/lib/django/contrib/sites/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,442 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/cs
2025-04-22 17:58:55,443 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,443 root INFO copying build/lib/django/contrib/sites/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,443 root INFO copying build/lib/django/contrib/sites/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,443 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/os
2025-04-22 17:58:55,444 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/os/LC_MESSAGES
2025-04-22 17:58:55,444 root INFO copying build/lib/django/contrib/sites/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/os/LC_MESSAGES
2025-04-22 17:58:55,444 root INFO copying build/lib/django/contrib/sites/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/os/LC_MESSAGES
2025-04-22 17:58:55,444 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/tr
2025-04-22 17:58:55,444 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,445 root INFO copying build/lib/django/contrib/sites/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,445 root INFO copying build/lib/django/contrib/sites/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,445 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/io
2025-04-22 17:58:55,445 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/io/LC_MESSAGES
2025-04-22 17:58:55,445 root INFO copying build/lib/django/contrib/sites/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/io/LC_MESSAGES
2025-04-22 17:58:55,446 root INFO copying build/lib/django/contrib/sites/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/io/LC_MESSAGES
2025-04-22 17:58:55,446 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/sl
2025-04-22 17:58:55,446 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,446 root INFO copying build/lib/django/contrib/sites/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,446 root INFO copying build/lib/django/contrib/sites/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,447 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/sq
2025-04-22 17:58:55,447 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,447 root INFO copying build/lib/django/contrib/sites/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,447 root INFO copying build/lib/django/contrib/sites/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,447 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/az
2025-04-22 17:58:55,448 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/az/LC_MESSAGES
2025-04-22 17:58:55,448 root INFO copying build/lib/django/contrib/sites/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/az/LC_MESSAGES
2025-04-22 17:58:55,448 root INFO copying build/lib/django/contrib/sites/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/az/LC_MESSAGES
2025-04-22 17:58:55,448 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/eo
2025-04-22 17:58:55,448 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,449 root INFO copying build/lib/django/contrib/sites/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,449 root INFO copying build/lib/django/contrib/sites/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,449 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/pt_BR
2025-04-22 17:58:55,449 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,449 root INFO copying build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,450 root INFO copying build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,450 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/pl
2025-04-22 17:58:55,450 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,450 root INFO copying build/lib/django/contrib/sites/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,450 root INFO copying build/lib/django/contrib/sites/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,451 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/gd
2025-04-22 17:58:55,451 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,451 root INFO copying build/lib/django/contrib/sites/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,451 root INFO copying build/lib/django/contrib/sites/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,451 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/hr
2025-04-22 17:58:55,452 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,452 root INFO copying build/lib/django/contrib/sites/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,452 root INFO copying build/lib/django/contrib/sites/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,452 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ru
2025-04-22 17:58:55,452 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,453 root INFO copying build/lib/django/contrib/sites/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,453 root INFO copying build/lib/django/contrib/sites/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,453 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/es
2025-04-22 17:58:55,453 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/es/LC_MESSAGES
2025-04-22 17:58:55,453 root INFO copying build/lib/django/contrib/sites/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/es/LC_MESSAGES
2025-04-22 17:58:55,454 root INFO copying build/lib/django/contrib/sites/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/es/LC_MESSAGES
2025-04-22 17:58:55,454 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/id
2025-04-22 17:58:55,454 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/id/LC_MESSAGES
2025-04-22 17:58:55,454 root INFO copying build/lib/django/contrib/sites/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/id/LC_MESSAGES
2025-04-22 17:58:55,454 root INFO copying build/lib/django/contrib/sites/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/id/LC_MESSAGES
2025-04-22 17:58:55,455 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/fi
2025-04-22 17:58:55,455 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,455 root INFO copying build/lib/django/contrib/sites/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,455 root INFO copying build/lib/django/contrib/sites/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,456 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/mk
2025-04-22 17:58:55,456 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,456 root INFO copying build/lib/django/contrib/sites/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,456 root INFO copying build/lib/django/contrib/sites/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,456 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/hi
2025-04-22 17:58:55,457 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,457 root INFO copying build/lib/django/contrib/sites/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,457 root INFO copying build/lib/django/contrib/sites/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,457 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/kab
2025-04-22 17:58:55,457 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,458 root INFO copying build/lib/django/contrib/sites/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,458 root INFO copying build/lib/django/contrib/sites/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,458 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/hsb
2025-04-22 17:58:55,458 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,458 root INFO copying build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,459 root INFO copying build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,459 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/sk
2025-04-22 17:58:55,459 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,459 root INFO copying build/lib/django/contrib/sites/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,459 root INFO copying build/lib/django/contrib/sites/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,460 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/lt
2025-04-22 17:58:55,460 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,460 root INFO copying build/lib/django/contrib/sites/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,460 root INFO copying build/lib/django/contrib/sites/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,461 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/de
2025-04-22 17:58:55,461 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/de/LC_MESSAGES
2025-04-22 17:58:55,461 root INFO copying build/lib/django/contrib/sites/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/de/LC_MESSAGES
2025-04-22 17:58:55,461 root INFO copying build/lib/django/contrib/sites/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/de/LC_MESSAGES
2025-04-22 17:58:55,461 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/it
2025-04-22 17:58:55,462 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/it/LC_MESSAGES
2025-04-22 17:58:55,462 root INFO copying build/lib/django/contrib/sites/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/it/LC_MESSAGES
2025-04-22 17:58:55,462 root INFO copying build/lib/django/contrib/sites/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/it/LC_MESSAGES
2025-04-22 17:58:55,462 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/my
2025-04-22 17:58:55,462 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/my/LC_MESSAGES
2025-04-22 17:58:55,463 root INFO copying build/lib/django/contrib/sites/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/my/LC_MESSAGES
2025-04-22 17:58:55,463 root INFO copying build/lib/django/contrib/sites/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/my/LC_MESSAGES
2025-04-22 17:58:55,463 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/sr
2025-04-22 17:58:55,463 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,463 root INFO copying build/lib/django/contrib/sites/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,464 root INFO copying build/lib/django/contrib/sites/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,464 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/bs
2025-04-22 17:58:55,464 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,464 root INFO copying build/lib/django/contrib/sites/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,464 root INFO copying build/lib/django/contrib/sites/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,465 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ro
2025-04-22 17:58:55,465 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,465 root INFO copying build/lib/django/contrib/sites/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,465 root INFO copying build/lib/django/contrib/sites/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,465 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ky
2025-04-22 17:58:55,466 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,466 root INFO copying build/lib/django/contrib/sites/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,466 root INFO copying build/lib/django/contrib/sites/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,466 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/fr
2025-04-22 17:58:55,466 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,467 root INFO copying build/lib/django/contrib/sites/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,467 root INFO copying build/lib/django/contrib/sites/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,467 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ar
2025-04-22 17:58:55,467 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,467 root INFO copying build/lib/django/contrib/sites/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,468 root INFO copying build/lib/django/contrib/sites/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,468 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/hy
2025-04-22 17:58:55,468 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,468 root INFO copying build/lib/django/contrib/sites/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,468 root INFO copying build/lib/django/contrib/sites/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,469 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/es_AR
2025-04-22 17:58:55,469 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,469 root INFO copying build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,469 root INFO copying build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,470 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/vi
2025-04-22 17:58:55,470 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,470 root INFO copying build/lib/django/contrib/sites/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,470 root INFO copying build/lib/django/contrib/sites/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,470 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ckb
2025-04-22 17:58:55,471 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,471 root INFO copying build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,471 root INFO copying build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,471 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/sv
2025-04-22 17:58:55,471 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,472 root INFO copying build/lib/django/contrib/sites/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,472 root INFO copying build/lib/django/contrib/sites/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,472 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/zh_Hant
2025-04-22 17:58:55,472 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,472 root INFO copying build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,473 root INFO copying build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,473 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/kk
2025-04-22 17:58:55,473 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,473 root INFO copying build/lib/django/contrib/sites/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,473 root INFO copying build/lib/django/contrib/sites/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,474 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/es_CO
2025-04-22 17:58:55,474 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,474 root INFO copying build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,474 root INFO copying build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,475 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/be
2025-04-22 17:58:55,475 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/be/LC_MESSAGES
2025-04-22 17:58:55,475 root INFO copying build/lib/django/contrib/sites/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/be/LC_MESSAGES
2025-04-22 17:58:55,475 root INFO copying build/lib/django/contrib/sites/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/be/LC_MESSAGES
2025-04-22 17:58:55,475 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/udm
2025-04-22 17:58:55,476 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,476 root INFO copying build/lib/django/contrib/sites/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,476 root INFO copying build/lib/django/contrib/sites/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,476 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ml
2025-04-22 17:58:55,477 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,477 root INFO copying build/lib/django/contrib/sites/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,477 root INFO copying build/lib/django/contrib/sites/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,477 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ar_DZ
2025-04-22 17:58:55,477 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,478 root INFO copying build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,478 root INFO copying build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,478 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ms
2025-04-22 17:58:55,478 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,478 root INFO copying build/lib/django/contrib/sites/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,479 root INFO copying build/lib/django/contrib/sites/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,479 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ast
2025-04-22 17:58:55,479 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,479 root INFO copying build/lib/django/contrib/sites/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,479 root INFO copying build/lib/django/contrib/sites/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,480 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/zh_Hans
2025-04-22 17:58:55,480 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,480 root INFO copying build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,480 root INFO copying build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,480 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ur
2025-04-22 17:58:55,481 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,481 root INFO copying build/lib/django/contrib/sites/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,481 root INFO copying build/lib/django/contrib/sites/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,481 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ia
2025-04-22 17:58:55,481 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,482 root INFO copying build/lib/django/contrib/sites/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,482 root INFO copying build/lib/django/contrib/sites/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,482 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/hu
2025-04-22 17:58:55,482 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,482 root INFO copying build/lib/django/contrib/sites/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,483 root INFO copying build/lib/django/contrib/sites/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,483 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ta
2025-04-22 17:58:55,483 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,483 root INFO copying build/lib/django/contrib/sites/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,483 root INFO copying build/lib/django/contrib/sites/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,484 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/eu
2025-04-22 17:58:55,484 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,484 root INFO copying build/lib/django/contrib/sites/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,484 root INFO copying build/lib/django/contrib/sites/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,485 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/es_MX
2025-04-22 17:58:55,485 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,485 root INFO copying build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,485 root INFO copying build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,485 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/tk
2025-04-22 17:58:55,486 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,486 root INFO copying build/lib/django/contrib/sites/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,486 root INFO copying build/lib/django/contrib/sites/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,486 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/th
2025-04-22 17:58:55,486 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/th/LC_MESSAGES
2025-04-22 17:58:55,487 root INFO copying build/lib/django/contrib/sites/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/th/LC_MESSAGES
2025-04-22 17:58:55,487 root INFO copying build/lib/django/contrib/sites/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/th/LC_MESSAGES
2025-04-22 17:58:55,487 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/nb
2025-04-22 17:58:55,487 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,487 root INFO copying build/lib/django/contrib/sites/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,488 root INFO copying build/lib/django/contrib/sites/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,488 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/mn
2025-04-22 17:58:55,488 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,488 root INFO copying build/lib/django/contrib/sites/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,488 root INFO copying build/lib/django/contrib/sites/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,489 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ka
2025-04-22 17:58:55,489 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,489 root INFO copying build/lib/django/contrib/sites/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,489 root INFO copying build/lib/django/contrib/sites/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,490 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/nl
2025-04-22 17:58:55,490 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,490 root INFO copying build/lib/django/contrib/sites/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,490 root INFO copying build/lib/django/contrib/sites/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,490 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/te
2025-04-22 17:58:55,491 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/te/LC_MESSAGES
2025-04-22 17:58:55,491 root INFO copying build/lib/django/contrib/sites/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/te/LC_MESSAGES
2025-04-22 17:58:55,491 root INFO copying build/lib/django/contrib/sites/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/te/LC_MESSAGES
2025-04-22 17:58:55,491 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/pt
2025-04-22 17:58:55,491 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,492 root INFO copying build/lib/django/contrib/sites/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,492 root INFO copying build/lib/django/contrib/sites/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,492 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/bn
2025-04-22 17:58:55,492 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,492 root INFO copying build/lib/django/contrib/sites/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,493 root INFO copying build/lib/django/contrib/sites/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,493 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/he
2025-04-22 17:58:55,493 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/he/LC_MESSAGES
2025-04-22 17:58:55,493 root INFO copying build/lib/django/contrib/sites/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/he/LC_MESSAGES
2025-04-22 17:58:55,493 root INFO copying build/lib/django/contrib/sites/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/he/LC_MESSAGES
2025-04-22 17:58:55,494 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/br
2025-04-22 17:58:55,494 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/br/LC_MESSAGES
2025-04-22 17:58:55,494 root INFO copying build/lib/django/contrib/sites/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/br/LC_MESSAGES
2025-04-22 17:58:55,494 root INFO copying build/lib/django/contrib/sites/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/br/LC_MESSAGES
2025-04-22 17:58:55,494 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/fa
2025-04-22 17:58:55,495 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,495 root INFO copying build/lib/django/contrib/sites/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,495 root INFO copying build/lib/django/contrib/sites/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,495 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/tg
2025-04-22 17:58:55,496 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,496 root INFO copying build/lib/django/contrib/sites/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,496 root INFO copying build/lib/django/contrib/sites/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,496 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/km
2025-04-22 17:58:55,496 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/km/LC_MESSAGES
2025-04-22 17:58:55,497 root INFO copying build/lib/django/contrib/sites/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/km/LC_MESSAGES
2025-04-22 17:58:55,497 root INFO copying build/lib/django/contrib/sites/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/km/LC_MESSAGES
2025-04-22 17:58:55,497 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/da
2025-04-22 17:58:55,497 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sites/locale/da/LC_MESSAGES
2025-04-22 17:58:55,497 root INFO copying build/lib/django/contrib/sites/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/da/LC_MESSAGES
2025-04-22 17:58:55,498 root INFO copying build/lib/django/contrib/sites/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sites/locale/da/LC_MESSAGES
2025-04-22 17:58:55,498 root INFO copying build/lib/django/contrib/sites/shortcuts.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sites
2025-04-22 17:58:55,498 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sitemaps
2025-04-22 17:58:55,498 root INFO copying build/lib/django/contrib/sitemaps/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sitemaps
2025-04-22 17:58:55,499 root INFO copying build/lib/django/contrib/sitemaps/views.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sitemaps
2025-04-22 17:58:55,499 root INFO copying build/lib/django/contrib/sitemaps/apps.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sitemaps
2025-04-22 17:58:55,499 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sitemaps/management
2025-04-22 17:58:55,499 root INFO copying build/lib/django/contrib/sitemaps/management/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sitemaps/management
2025-04-22 17:58:55,499 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sitemaps/management/commands
2025-04-22 17:58:55,500 root INFO copying build/lib/django/contrib/sitemaps/management/commands/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sitemaps/management/commands
2025-04-22 17:58:55,500 root INFO copying build/lib/django/contrib/sitemaps/management/commands/ping_google.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sitemaps/management/commands
2025-04-22 17:58:55,500 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sitemaps/templates
2025-04-22 17:58:55,500 root INFO copying build/lib/django/contrib/sitemaps/templates/sitemap.xml -> build/bdist.linux-armv8l/wheel/./django/contrib/sitemaps/templates
2025-04-22 17:58:55,500 root INFO copying build/lib/django/contrib/sitemaps/templates/sitemap_index.xml -> build/bdist.linux-armv8l/wheel/./django/contrib/sitemaps/templates
2025-04-22 17:58:55,501 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages
2025-04-22 17:58:55,501 root INFO copying build/lib/django/contrib/flatpages/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages
2025-04-22 17:58:55,501 root INFO copying build/lib/django/contrib/flatpages/middleware.py -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages
2025-04-22 17:58:55,501 root INFO copying build/lib/django/contrib/flatpages/views.py -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages
2025-04-22 17:58:55,501 root INFO copying build/lib/django/contrib/flatpages/forms.py -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages
2025-04-22 17:58:55,502 root INFO copying build/lib/django/contrib/flatpages/models.py -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages
2025-04-22 17:58:55,502 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/migrations
2025-04-22 17:58:55,502 root INFO copying build/lib/django/contrib/flatpages/migrations/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/migrations
2025-04-22 17:58:55,502 root INFO copying build/lib/django/contrib/flatpages/migrations/0001_initial.py -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/migrations
2025-04-22 17:58:55,502 root INFO copying build/lib/django/contrib/flatpages/apps.py -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages
2025-04-22 17:58:55,503 root INFO copying build/lib/django/contrib/flatpages/urls.py -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages
2025-04-22 17:58:55,503 root INFO copying build/lib/django/contrib/flatpages/admin.py -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages
2025-04-22 17:58:55,503 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/templatetags
2025-04-22 17:58:55,503 root INFO copying build/lib/django/contrib/flatpages/templatetags/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/templatetags
2025-04-22 17:58:55,504 root INFO copying build/lib/django/contrib/flatpages/templatetags/flatpages.py -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/templatetags
2025-04-22 17:58:55,504 root INFO copying build/lib/django/contrib/flatpages/sitemaps.py -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages
2025-04-22 17:58:55,504 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale
2025-04-22 17:58:55,504 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/lv
2025-04-22 17:58:55,504 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,505 root INFO copying build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,505 root INFO copying build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,505 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/sw
2025-04-22 17:58:55,505 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,505 root INFO copying build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,506 root INFO copying build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,506 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/en_AU
2025-04-22 17:58:55,506 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,506 root INFO copying build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,507 root INFO copying build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,507 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/mr
2025-04-22 17:58:55,507 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,507 root INFO copying build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,507 root INFO copying build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,508 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/lb
2025-04-22 17:58:55,508 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,508 root INFO copying build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,508 root INFO copying build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,509 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ca
2025-04-22 17:58:55,509 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,509 root INFO copying build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,509 root INFO copying build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,509 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/en_GB
2025-04-22 17:58:55,510 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,510 root INFO copying build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,510 root INFO copying build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,510 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/el
2025-04-22 17:58:55,511 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/el/LC_MESSAGES
2025-04-22 17:58:55,511 root INFO copying build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/el/LC_MESSAGES
2025-04-22 17:58:55,511 root INFO copying build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/el/LC_MESSAGES
2025-04-22 17:58:55,511 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/es_VE
2025-04-22 17:58:55,511 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,512 root INFO copying build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,512 root INFO copying build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,512 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/af
2025-04-22 17:58:55,512 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/af/LC_MESSAGES
2025-04-22 17:58:55,512 root INFO copying build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/af/LC_MESSAGES
2025-04-22 17:58:55,513 root INFO copying build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/af/LC_MESSAGES
2025-04-22 17:58:55,513 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/en
2025-04-22 17:58:55,513 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/en/LC_MESSAGES
2025-04-22 17:58:55,513 root INFO copying build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/en/LC_MESSAGES
2025-04-22 17:58:55,513 root INFO copying build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/en/LC_MESSAGES
2025-04-22 17:58:55,514 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/dsb
2025-04-22 17:58:55,514 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,514 root INFO copying build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,514 root INFO copying build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,515 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/et
2025-04-22 17:58:55,515 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/et/LC_MESSAGES
2025-04-22 17:58:55,515 root INFO copying build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/et/LC_MESSAGES
2025-04-22 17:58:55,515 root INFO copying build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/et/LC_MESSAGES
2025-04-22 17:58:55,515 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/nn
2025-04-22 17:58:55,516 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,516 root INFO copying build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,516 root INFO copying build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,516 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/cy
2025-04-22 17:58:55,516 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,517 root INFO copying build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,517 root INFO copying build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,517 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ko
2025-04-22 17:58:55,517 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,517 root INFO copying build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,518 root INFO copying build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,518 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/is
2025-04-22 17:58:55,518 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/is/LC_MESSAGES
2025-04-22 17:58:55,518 root INFO copying build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/is/LC_MESSAGES
2025-04-22 17:58:55,518 root INFO copying build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/is/LC_MESSAGES
2025-04-22 17:58:55,519 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/pa
2025-04-22 17:58:55,519 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,519 root INFO copying build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,520 root INFO copying build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,520 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/tt
2025-04-22 17:58:55,520 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,520 root INFO copying build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,520 root INFO copying build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,521 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ne
2025-04-22 17:58:55,521 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,521 root INFO copying build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,521 root INFO copying build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,522 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/sr_Latn
2025-04-22 17:58:55,522 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,522 root INFO copying build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,522 root INFO copying build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,522 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/fy
2025-04-22 17:58:55,523 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,523 root INFO copying build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,523 root INFO copying build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,523 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/bg
2025-04-22 17:58:55,523 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,524 root INFO copying build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,524 root INFO copying build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,524 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ga
2025-04-22 17:58:55,524 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,524 root INFO copying build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,525 root INFO copying build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,525 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/gl
2025-04-22 17:58:55,525 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,525 root INFO copying build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,525 root INFO copying build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,526 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/uk
2025-04-22 17:58:55,526 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,526 root INFO copying build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,526 root INFO copying build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,527 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/kn
2025-04-22 17:58:55,527 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,527 root INFO copying build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,527 root INFO copying build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,527 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ja
2025-04-22 17:58:55,528 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,528 root INFO copying build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,528 root INFO copying build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,528 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/cs
2025-04-22 17:58:55,529 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,529 root INFO copying build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,529 root INFO copying build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,529 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/os
2025-04-22 17:58:55,529 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/os/LC_MESSAGES
2025-04-22 17:58:55,530 root INFO copying build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/os/LC_MESSAGES
2025-04-22 17:58:55,530 root INFO copying build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/os/LC_MESSAGES
2025-04-22 17:58:55,530 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/tr
2025-04-22 17:58:55,530 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,530 root INFO copying build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,531 root INFO copying build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,531 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/io
2025-04-22 17:58:55,531 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/io/LC_MESSAGES
2025-04-22 17:58:55,531 root INFO copying build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/io/LC_MESSAGES
2025-04-22 17:58:55,531 root INFO copying build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/io/LC_MESSAGES
2025-04-22 17:58:55,532 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/sl
2025-04-22 17:58:55,532 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,532 root INFO copying build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,532 root INFO copying build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,532 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/sq
2025-04-22 17:58:55,533 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,533 root INFO copying build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,533 root INFO copying build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,533 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/az
2025-04-22 17:58:55,534 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/az/LC_MESSAGES
2025-04-22 17:58:55,534 root INFO copying build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/az/LC_MESSAGES
2025-04-22 17:58:55,534 root INFO copying build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/az/LC_MESSAGES
2025-04-22 17:58:55,534 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/eo
2025-04-22 17:58:55,534 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,535 root INFO copying build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,535 root INFO copying build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,535 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/pt_BR
2025-04-22 17:58:55,535 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,535 root INFO copying build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,536 root INFO copying build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,536 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/pl
2025-04-22 17:58:55,536 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,536 root INFO copying build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,536 root INFO copying build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,537 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/gd
2025-04-22 17:58:55,537 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,537 root INFO copying build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,537 root INFO copying build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,538 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/hr
2025-04-22 17:58:55,538 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,538 root INFO copying build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,538 root INFO copying build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,538 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ru
2025-04-22 17:58:55,539 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,539 root INFO copying build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,539 root INFO copying build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,539 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/es
2025-04-22 17:58:55,539 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/es/LC_MESSAGES
2025-04-22 17:58:55,540 root INFO copying build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/es/LC_MESSAGES
2025-04-22 17:58:55,540 root INFO copying build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/es/LC_MESSAGES
2025-04-22 17:58:55,540 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/id
2025-04-22 17:58:55,540 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/id/LC_MESSAGES
2025-04-22 17:58:55,540 root INFO copying build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/id/LC_MESSAGES
2025-04-22 17:58:55,541 root INFO copying build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/id/LC_MESSAGES
2025-04-22 17:58:55,541 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/fi
2025-04-22 17:58:55,541 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,541 root INFO copying build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,541 root INFO copying build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,542 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/mk
2025-04-22 17:58:55,542 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,542 root INFO copying build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,542 root INFO copying build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,543 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/hi
2025-04-22 17:58:55,543 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,543 root INFO copying build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,543 root INFO copying build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,544 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/hsb
2025-04-22 17:58:55,544 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,544 root INFO copying build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,544 root INFO copying build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,544 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/sk
2025-04-22 17:58:55,545 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,545 root INFO copying build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,545 root INFO copying build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,545 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/lt
2025-04-22 17:58:55,545 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,546 root INFO copying build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,546 root INFO copying build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,546 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/de
2025-04-22 17:58:55,546 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/de/LC_MESSAGES
2025-04-22 17:58:55,547 root INFO copying build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/de/LC_MESSAGES
2025-04-22 17:58:55,547 root INFO copying build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/de/LC_MESSAGES
2025-04-22 17:58:55,547 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/it
2025-04-22 17:58:55,547 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/it/LC_MESSAGES
2025-04-22 17:58:55,547 root INFO copying build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/it/LC_MESSAGES
2025-04-22 17:58:55,548 root INFO copying build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/it/LC_MESSAGES
2025-04-22 17:58:55,548 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/my
2025-04-22 17:58:55,548 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/my/LC_MESSAGES
2025-04-22 17:58:55,548 root INFO copying build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/my/LC_MESSAGES
2025-04-22 17:58:55,548 root INFO copying build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/my/LC_MESSAGES
2025-04-22 17:58:55,549 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/sr
2025-04-22 17:58:55,549 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,549 root INFO copying build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,549 root INFO copying build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,549 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/bs
2025-04-22 17:58:55,550 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,550 root INFO copying build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,550 root INFO copying build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,550 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ro
2025-04-22 17:58:55,550 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,551 root INFO copying build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,551 root INFO copying build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,551 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ky
2025-04-22 17:58:55,551 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,551 root INFO copying build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,552 root INFO copying build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,552 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/fr
2025-04-22 17:58:55,552 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,552 root INFO copying build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,553 root INFO copying build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,553 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ar
2025-04-22 17:58:55,553 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,553 root INFO copying build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,553 root INFO copying build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,554 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/hy
2025-04-22 17:58:55,554 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,554 root INFO copying build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,554 root INFO copying build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,554 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/es_AR
2025-04-22 17:58:55,555 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,555 root INFO copying build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,555 root INFO copying build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,555 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/vi
2025-04-22 17:58:55,555 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,556 root INFO copying build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,556 root INFO copying build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,556 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ckb
2025-04-22 17:58:55,556 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,556 root INFO copying build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,557 root INFO copying build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,557 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/sv
2025-04-22 17:58:55,557 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,557 root INFO copying build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,558 root INFO copying build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,558 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/zh_Hant
2025-04-22 17:58:55,558 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,558 root INFO copying build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,558 root INFO copying build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,559 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/kk
2025-04-22 17:58:55,559 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,559 root INFO copying build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,559 root INFO copying build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,559 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/es_CO
2025-04-22 17:58:55,560 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,560 root INFO copying build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,560 root INFO copying build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,560 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/be
2025-04-22 17:58:55,561 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/be/LC_MESSAGES
2025-04-22 17:58:55,561 root INFO copying build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/be/LC_MESSAGES
2025-04-22 17:58:55,561 root INFO copying build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/be/LC_MESSAGES
2025-04-22 17:58:55,561 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/udm
2025-04-22 17:58:55,561 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,562 root INFO copying build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,562 root INFO copying build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,562 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ml
2025-04-22 17:58:55,562 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,562 root INFO copying build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,563 root INFO copying build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,563 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ar_DZ
2025-04-22 17:58:55,563 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,563 root INFO copying build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,564 root INFO copying build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,564 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ms
2025-04-22 17:58:55,564 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,564 root INFO copying build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,564 root INFO copying build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,565 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ast
2025-04-22 17:58:55,565 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,565 root INFO copying build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,565 root INFO copying build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,566 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/zh_Hans
2025-04-22 17:58:55,566 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,566 root INFO copying build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,566 root INFO copying build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,566 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ur
2025-04-22 17:58:55,567 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,567 root INFO copying build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,567 root INFO copying build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,567 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ia
2025-04-22 17:58:55,568 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,568 root INFO copying build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,568 root INFO copying build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,568 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/hu
2025-04-22 17:58:55,568 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,569 root INFO copying build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,569 root INFO copying build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,569 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ta
2025-04-22 17:58:55,569 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,569 root INFO copying build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,570 root INFO copying build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,570 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/eu
2025-04-22 17:58:55,570 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,570 root INFO copying build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,570 root INFO copying build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,571 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/es_MX
2025-04-22 17:58:55,571 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,571 root INFO copying build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,571 root INFO copying build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,572 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/tk
2025-04-22 17:58:55,572 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,572 root INFO copying build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,572 root INFO copying build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,572 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/th
2025-04-22 17:58:55,573 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/th/LC_MESSAGES
2025-04-22 17:58:55,573 root INFO copying build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/th/LC_MESSAGES
2025-04-22 17:58:55,573 root INFO copying build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/th/LC_MESSAGES
2025-04-22 17:58:55,573 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/nb
2025-04-22 17:58:55,574 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,574 root INFO copying build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,574 root INFO copying build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,574 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/mn
2025-04-22 17:58:55,574 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,574 root INFO copying build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,575 root INFO copying build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,575 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ka
2025-04-22 17:58:55,575 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,575 root INFO copying build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,576 root INFO copying build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,576 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/nl
2025-04-22 17:58:55,576 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,576 root INFO copying build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,576 root INFO copying build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,577 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/te
2025-04-22 17:58:55,577 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/te/LC_MESSAGES
2025-04-22 17:58:55,577 root INFO copying build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/te/LC_MESSAGES
2025-04-22 17:58:55,577 root INFO copying build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/te/LC_MESSAGES
2025-04-22 17:58:55,577 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/pt
2025-04-22 17:58:55,578 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,578 root INFO copying build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,578 root INFO copying build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,578 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/bn
2025-04-22 17:58:55,579 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,579 root INFO copying build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,579 root INFO copying build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,579 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/he
2025-04-22 17:58:55,579 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/he/LC_MESSAGES
2025-04-22 17:58:55,580 root INFO copying build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/he/LC_MESSAGES
2025-04-22 17:58:55,580 root INFO copying build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/he/LC_MESSAGES
2025-04-22 17:58:55,580 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/br
2025-04-22 17:58:55,580 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/br/LC_MESSAGES
2025-04-22 17:58:55,580 root INFO copying build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/br/LC_MESSAGES
2025-04-22 17:58:55,581 root INFO copying build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/br/LC_MESSAGES
2025-04-22 17:58:55,581 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/fa
2025-04-22 17:58:55,581 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,581 root INFO copying build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,581 root INFO copying build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,582 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/tg
2025-04-22 17:58:55,582 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,582 root INFO copying build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,582 root INFO copying build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,582 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/km
2025-04-22 17:58:55,583 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/km/LC_MESSAGES
2025-04-22 17:58:55,583 root INFO copying build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/km/LC_MESSAGES
2025-04-22 17:58:55,583 root INFO copying build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/km/LC_MESSAGES
2025-04-22 17:58:55,583 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/da
2025-04-22 17:58:55,584 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/flatpages/locale/da/LC_MESSAGES
2025-04-22 17:58:55,584 root INFO copying build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/da/LC_MESSAGES
2025-04-22 17:58:55,584 root INFO copying build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/flatpages/locale/da/LC_MESSAGES
2025-04-22 17:58:55,584 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/staticfiles
2025-04-22 17:58:55,584 root INFO copying build/lib/django/contrib/staticfiles/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/staticfiles
2025-04-22 17:58:55,585 root INFO copying build/lib/django/contrib/staticfiles/handlers.py -> build/bdist.linux-armv8l/wheel/./django/contrib/staticfiles
2025-04-22 17:58:55,585 root INFO copying build/lib/django/contrib/staticfiles/views.py -> build/bdist.linux-armv8l/wheel/./django/contrib/staticfiles
2025-04-22 17:58:55,585 root INFO copying build/lib/django/contrib/staticfiles/testing.py -> build/bdist.linux-armv8l/wheel/./django/contrib/staticfiles
2025-04-22 17:58:55,585 root INFO copying build/lib/django/contrib/staticfiles/apps.py -> build/bdist.linux-armv8l/wheel/./django/contrib/staticfiles
2025-04-22 17:58:55,586 root INFO copying build/lib/django/contrib/staticfiles/urls.py -> build/bdist.linux-armv8l/wheel/./django/contrib/staticfiles
2025-04-22 17:58:55,586 root INFO copying build/lib/django/contrib/staticfiles/utils.py -> build/bdist.linux-armv8l/wheel/./django/contrib/staticfiles
2025-04-22 17:58:55,586 root INFO copying build/lib/django/contrib/staticfiles/checks.py -> build/bdist.linux-armv8l/wheel/./django/contrib/staticfiles
2025-04-22 17:58:55,586 root INFO copying build/lib/django/contrib/staticfiles/finders.py -> build/bdist.linux-armv8l/wheel/./django/contrib/staticfiles
2025-04-22 17:58:55,587 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/staticfiles/management
2025-04-22 17:58:55,587 root INFO copying build/lib/django/contrib/staticfiles/management/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/staticfiles/management
2025-04-22 17:58:55,587 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/staticfiles/management/commands
2025-04-22 17:58:55,587 root INFO copying build/lib/django/contrib/staticfiles/management/commands/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/staticfiles/management/commands
2025-04-22 17:58:55,588 root INFO copying build/lib/django/contrib/staticfiles/management/commands/collectstatic.py -> build/bdist.linux-armv8l/wheel/./django/contrib/staticfiles/management/commands
2025-04-22 17:58:55,588 root INFO copying build/lib/django/contrib/staticfiles/management/commands/findstatic.py -> build/bdist.linux-armv8l/wheel/./django/contrib/staticfiles/management/commands
2025-04-22 17:58:55,588 root INFO copying build/lib/django/contrib/staticfiles/management/commands/runserver.py -> build/bdist.linux-armv8l/wheel/./django/contrib/staticfiles/management/commands
2025-04-22 17:58:55,588 root INFO copying build/lib/django/contrib/staticfiles/storage.py -> build/bdist.linux-armv8l/wheel/./django/contrib/staticfiles
2025-04-22 17:58:55,589 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions
2025-04-22 17:58:55,589 root INFO copying build/lib/django/contrib/sessions/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions
2025-04-22 17:58:55,589 root INFO copying build/lib/django/contrib/sessions/middleware.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions
2025-04-22 17:58:55,589 root INFO copying build/lib/django/contrib/sessions/exceptions.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions
2025-04-22 17:58:55,589 root INFO copying build/lib/django/contrib/sessions/base_session.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions
2025-04-22 17:58:55,590 root INFO copying build/lib/django/contrib/sessions/models.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions
2025-04-22 17:58:55,590 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/migrations
2025-04-22 17:58:55,590 root INFO copying build/lib/django/contrib/sessions/migrations/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/migrations
2025-04-22 17:58:55,590 root INFO copying build/lib/django/contrib/sessions/migrations/0001_initial.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/migrations
2025-04-22 17:58:55,590 root INFO copying build/lib/django/contrib/sessions/apps.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions
2025-04-22 17:58:55,591 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/management
2025-04-22 17:58:55,591 root INFO copying build/lib/django/contrib/sessions/management/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/management
2025-04-22 17:58:55,591 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/management/commands
2025-04-22 17:58:55,591 root INFO copying build/lib/django/contrib/sessions/management/commands/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/management/commands
2025-04-22 17:58:55,592 root INFO copying build/lib/django/contrib/sessions/management/commands/clearsessions.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/management/commands
2025-04-22 17:58:55,592 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale
2025-04-22 17:58:55,592 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/lv
2025-04-22 17:58:55,592 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,593 root INFO copying build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,593 root INFO copying build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,593 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/sw
2025-04-22 17:58:55,593 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,594 root INFO copying build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,594 root INFO copying build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,594 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/en_AU
2025-04-22 17:58:55,594 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,594 root INFO copying build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,595 root INFO copying build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,595 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/mr
2025-04-22 17:58:55,595 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,595 root INFO copying build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,596 root INFO copying build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,596 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/lb
2025-04-22 17:58:55,596 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,596 root INFO copying build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,597 root INFO copying build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,597 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ca
2025-04-22 17:58:55,597 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,597 root INFO copying build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,597 root INFO copying build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,598 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/en_GB
2025-04-22 17:58:55,598 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,598 root INFO copying build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,598 root INFO copying build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,599 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/el
2025-04-22 17:58:55,599 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/el/LC_MESSAGES
2025-04-22 17:58:55,599 root INFO copying build/lib/django/contrib/sessions/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/el/LC_MESSAGES
2025-04-22 17:58:55,599 root INFO copying build/lib/django/contrib/sessions/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/el/LC_MESSAGES
2025-04-22 17:58:55,600 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/es_VE
2025-04-22 17:58:55,600 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,600 root INFO copying build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,600 root INFO copying build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,601 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/af
2025-04-22 17:58:55,601 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/af/LC_MESSAGES
2025-04-22 17:58:55,601 root INFO copying build/lib/django/contrib/sessions/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/af/LC_MESSAGES
2025-04-22 17:58:55,601 root INFO copying build/lib/django/contrib/sessions/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/af/LC_MESSAGES
2025-04-22 17:58:55,601 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/en
2025-04-22 17:58:55,602 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/en/LC_MESSAGES
2025-04-22 17:58:55,602 root INFO copying build/lib/django/contrib/sessions/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/en/LC_MESSAGES
2025-04-22 17:58:55,602 root INFO copying build/lib/django/contrib/sessions/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/en/LC_MESSAGES
2025-04-22 17:58:55,602 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/dsb
2025-04-22 17:58:55,603 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,603 root INFO copying build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,603 root INFO copying build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,603 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/et
2025-04-22 17:58:55,604 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/et/LC_MESSAGES
2025-04-22 17:58:55,604 root INFO copying build/lib/django/contrib/sessions/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/et/LC_MESSAGES
2025-04-22 17:58:55,604 root INFO copying build/lib/django/contrib/sessions/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/et/LC_MESSAGES
2025-04-22 17:58:55,604 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/nn
2025-04-22 17:58:55,604 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,605 root INFO copying build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,605 root INFO copying build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,605 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/cy
2025-04-22 17:58:55,605 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,606 root INFO copying build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,606 root INFO copying build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,606 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ko
2025-04-22 17:58:55,606 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,607 root INFO copying build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,607 root INFO copying build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,607 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/is
2025-04-22 17:58:55,607 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/is/LC_MESSAGES
2025-04-22 17:58:55,607 root INFO copying build/lib/django/contrib/sessions/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/is/LC_MESSAGES
2025-04-22 17:58:55,608 root INFO copying build/lib/django/contrib/sessions/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/is/LC_MESSAGES
2025-04-22 17:58:55,608 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/pa
2025-04-22 17:58:55,608 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,608 root INFO copying build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,608 root INFO copying build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,609 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/tt
2025-04-22 17:58:55,609 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,609 root INFO copying build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,609 root INFO copying build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,610 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ne
2025-04-22 17:58:55,610 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,610 root INFO copying build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,610 root INFO copying build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,610 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/sr_Latn
2025-04-22 17:58:55,611 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,611 root INFO copying build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,611 root INFO copying build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,611 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/fy
2025-04-22 17:58:55,611 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,612 root INFO copying build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,612 root INFO copying build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,612 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/bg
2025-04-22 17:58:55,612 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,612 root INFO copying build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,613 root INFO copying build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,613 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ga
2025-04-22 17:58:55,613 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,613 root INFO copying build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,613 root INFO copying build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,614 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/gl
2025-04-22 17:58:55,614 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,614 root INFO copying build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,614 root INFO copying build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,614 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/uk
2025-04-22 17:58:55,614 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,615 root INFO copying build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,615 root INFO copying build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,615 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/uz
2025-04-22 17:58:55,615 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,615 root INFO copying build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,616 root INFO copying build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,616 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/kn
2025-04-22 17:58:55,616 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,616 root INFO copying build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,616 root INFO copying build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,617 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ja
2025-04-22 17:58:55,617 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,617 root INFO copying build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,617 root INFO copying build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,617 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/cs
2025-04-22 17:58:55,618 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,618 root INFO copying build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,618 root INFO copying build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,618 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/os
2025-04-22 17:58:55,618 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/os/LC_MESSAGES
2025-04-22 17:58:55,618 root INFO copying build/lib/django/contrib/sessions/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/os/LC_MESSAGES
2025-04-22 17:58:55,619 root INFO copying build/lib/django/contrib/sessions/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/os/LC_MESSAGES
2025-04-22 17:58:55,619 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/tr
2025-04-22 17:58:55,619 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,619 root INFO copying build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,619 root INFO copying build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,620 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/io
2025-04-22 17:58:55,620 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/io/LC_MESSAGES
2025-04-22 17:58:55,620 root INFO copying build/lib/django/contrib/sessions/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/io/LC_MESSAGES
2025-04-22 17:58:55,620 root INFO copying build/lib/django/contrib/sessions/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/io/LC_MESSAGES
2025-04-22 17:58:55,620 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/sl
2025-04-22 17:58:55,621 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,621 root INFO copying build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,621 root INFO copying build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,621 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/sq
2025-04-22 17:58:55,621 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,621 root INFO copying build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,622 root INFO copying build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,622 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/az
2025-04-22 17:58:55,622 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/az/LC_MESSAGES
2025-04-22 17:58:55,622 root INFO copying build/lib/django/contrib/sessions/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/az/LC_MESSAGES
2025-04-22 17:58:55,622 root INFO copying build/lib/django/contrib/sessions/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/az/LC_MESSAGES
2025-04-22 17:58:55,623 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/eo
2025-04-22 17:58:55,623 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,623 root INFO copying build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,623 root INFO copying build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,623 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/pt_BR
2025-04-22 17:58:55,624 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,624 root INFO copying build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,624 root INFO copying build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,624 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/pl
2025-04-22 17:58:55,624 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,625 root INFO copying build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,625 root INFO copying build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,625 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/gd
2025-04-22 17:58:55,625 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,625 root INFO copying build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,625 root INFO copying build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,626 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/hr
2025-04-22 17:58:55,626 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,626 root INFO copying build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,626 root INFO copying build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,627 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ru
2025-04-22 17:58:55,627 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,627 root INFO copying build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,627 root INFO copying build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,627 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/es
2025-04-22 17:58:55,628 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/es/LC_MESSAGES
2025-04-22 17:58:55,628 root INFO copying build/lib/django/contrib/sessions/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/es/LC_MESSAGES
2025-04-22 17:58:55,628 root INFO copying build/lib/django/contrib/sessions/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/es/LC_MESSAGES
2025-04-22 17:58:55,628 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/id
2025-04-22 17:58:55,628 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/id/LC_MESSAGES
2025-04-22 17:58:55,629 root INFO copying build/lib/django/contrib/sessions/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/id/LC_MESSAGES
2025-04-22 17:58:55,629 root INFO copying build/lib/django/contrib/sessions/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/id/LC_MESSAGES
2025-04-22 17:58:55,629 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/fi
2025-04-22 17:58:55,629 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,629 root INFO copying build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,629 root INFO copying build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,630 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/mk
2025-04-22 17:58:55,630 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,630 root INFO copying build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,630 root INFO copying build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,630 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/hi
2025-04-22 17:58:55,631 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,631 root INFO copying build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,631 root INFO copying build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,631 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/kab
2025-04-22 17:58:55,631 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,632 root INFO copying build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,632 root INFO copying build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,632 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/hsb
2025-04-22 17:58:55,632 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,632 root INFO copying build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,633 root INFO copying build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,633 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/sk
2025-04-22 17:58:55,633 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,633 root INFO copying build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,633 root INFO copying build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,634 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/lt
2025-04-22 17:58:55,634 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,634 root INFO copying build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,634 root INFO copying build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,634 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/de
2025-04-22 17:58:55,635 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/de/LC_MESSAGES
2025-04-22 17:58:55,635 root INFO copying build/lib/django/contrib/sessions/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/de/LC_MESSAGES
2025-04-22 17:58:55,635 root INFO copying build/lib/django/contrib/sessions/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/de/LC_MESSAGES
2025-04-22 17:58:55,635 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/it
2025-04-22 17:58:55,635 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/it/LC_MESSAGES
2025-04-22 17:58:55,635 root INFO copying build/lib/django/contrib/sessions/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/it/LC_MESSAGES
2025-04-22 17:58:55,636 root INFO copying build/lib/django/contrib/sessions/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/it/LC_MESSAGES
2025-04-22 17:58:55,636 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/my
2025-04-22 17:58:55,636 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/my/LC_MESSAGES
2025-04-22 17:58:55,636 root INFO copying build/lib/django/contrib/sessions/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/my/LC_MESSAGES
2025-04-22 17:58:55,636 root INFO copying build/lib/django/contrib/sessions/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/my/LC_MESSAGES
2025-04-22 17:58:55,637 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/sr
2025-04-22 17:58:55,637 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,637 root INFO copying build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,637 root INFO copying build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,637 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/bs
2025-04-22 17:58:55,638 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,638 root INFO copying build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,638 root INFO copying build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,638 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ro
2025-04-22 17:58:55,638 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,639 root INFO copying build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,639 root INFO copying build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,639 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ky
2025-04-22 17:58:55,639 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,639 root INFO copying build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,640 root INFO copying build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,640 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/fr
2025-04-22 17:58:55,640 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,640 root INFO copying build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,640 root INFO copying build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,640 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ar
2025-04-22 17:58:55,641 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,641 root INFO copying build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,641 root INFO copying build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,641 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/hy
2025-04-22 17:58:55,641 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,642 root INFO copying build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,642 root INFO copying build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,642 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/es_AR
2025-04-22 17:58:55,642 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,642 root INFO copying build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,642 root INFO copying build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,643 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/vi
2025-04-22 17:58:55,643 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,643 root INFO copying build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,643 root INFO copying build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,643 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ckb
2025-04-22 17:58:55,644 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,644 root INFO copying build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,644 root INFO copying build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,644 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/sv
2025-04-22 17:58:55,644 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,645 root INFO copying build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,645 root INFO copying build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,645 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/zh_Hant
2025-04-22 17:58:55,645 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,645 root INFO copying build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,645 root INFO copying build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,646 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/kk
2025-04-22 17:58:55,646 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,646 root INFO copying build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,646 root INFO copying build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,647 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/es_CO
2025-04-22 17:58:55,647 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,647 root INFO copying build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,647 root INFO copying build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,647 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/be
2025-04-22 17:58:55,648 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/be/LC_MESSAGES
2025-04-22 17:58:55,648 root INFO copying build/lib/django/contrib/sessions/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/be/LC_MESSAGES
2025-04-22 17:58:55,648 root INFO copying build/lib/django/contrib/sessions/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/be/LC_MESSAGES
2025-04-22 17:58:55,648 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/udm
2025-04-22 17:58:55,648 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,648 root INFO copying build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,649 root INFO copying build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,649 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ml
2025-04-22 17:58:55,649 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,649 root INFO copying build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,649 root INFO copying build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,650 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ar_DZ
2025-04-22 17:58:55,650 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,650 root INFO copying build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,650 root INFO copying build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,650 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ms
2025-04-22 17:58:55,651 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,651 root INFO copying build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,651 root INFO copying build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,651 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ast
2025-04-22 17:58:55,651 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,651 root INFO copying build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,652 root INFO copying build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,652 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/zh_Hans
2025-04-22 17:58:55,652 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,652 root INFO copying build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,652 root INFO copying build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,653 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ur
2025-04-22 17:58:55,653 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,653 root INFO copying build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,653 root INFO copying build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,654 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ia
2025-04-22 17:58:55,654 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,654 root INFO copying build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,654 root INFO copying build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,654 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/hu
2025-04-22 17:58:55,655 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,655 root INFO copying build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,655 root INFO copying build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,655 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ta
2025-04-22 17:58:55,655 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,656 root INFO copying build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,656 root INFO copying build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,656 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/eu
2025-04-22 17:58:55,656 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,656 root INFO copying build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,656 root INFO copying build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,657 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/es_MX
2025-04-22 17:58:55,657 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,657 root INFO copying build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,657 root INFO copying build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,657 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/tk
2025-04-22 17:58:55,658 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,658 root INFO copying build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,658 root INFO copying build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,658 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/th
2025-04-22 17:58:55,658 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/th/LC_MESSAGES
2025-04-22 17:58:55,659 root INFO copying build/lib/django/contrib/sessions/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/th/LC_MESSAGES
2025-04-22 17:58:55,659 root INFO copying build/lib/django/contrib/sessions/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/th/LC_MESSAGES
2025-04-22 17:58:55,659 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/nb
2025-04-22 17:58:55,659 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,659 root INFO copying build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,660 root INFO copying build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,660 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/mn
2025-04-22 17:58:55,660 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,660 root INFO copying build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,660 root INFO copying build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,661 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ka
2025-04-22 17:58:55,661 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,661 root INFO copying build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,661 root INFO copying build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,661 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/nl
2025-04-22 17:58:55,661 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,662 root INFO copying build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,662 root INFO copying build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,662 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/te
2025-04-22 17:58:55,662 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/te/LC_MESSAGES
2025-04-22 17:58:55,662 root INFO copying build/lib/django/contrib/sessions/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/te/LC_MESSAGES
2025-04-22 17:58:55,663 root INFO copying build/lib/django/contrib/sessions/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/te/LC_MESSAGES
2025-04-22 17:58:55,663 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/pt
2025-04-22 17:58:55,663 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,663 root INFO copying build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,663 root INFO copying build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,664 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/bn
2025-04-22 17:58:55,664 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,664 root INFO copying build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,664 root INFO copying build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,664 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/he
2025-04-22 17:58:55,665 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/he/LC_MESSAGES
2025-04-22 17:58:55,665 root INFO copying build/lib/django/contrib/sessions/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/he/LC_MESSAGES
2025-04-22 17:58:55,665 root INFO copying build/lib/django/contrib/sessions/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/he/LC_MESSAGES
2025-04-22 17:58:55,665 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/br
2025-04-22 17:58:55,665 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/br/LC_MESSAGES
2025-04-22 17:58:55,666 root INFO copying build/lib/django/contrib/sessions/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/br/LC_MESSAGES
2025-04-22 17:58:55,666 root INFO copying build/lib/django/contrib/sessions/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/br/LC_MESSAGES
2025-04-22 17:58:55,666 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/fa
2025-04-22 17:58:55,666 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,666 root INFO copying build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,666 root INFO copying build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,667 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/tg
2025-04-22 17:58:55,667 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,667 root INFO copying build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,667 root INFO copying build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,667 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/km
2025-04-22 17:58:55,668 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/km/LC_MESSAGES
2025-04-22 17:58:55,668 root INFO copying build/lib/django/contrib/sessions/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/km/LC_MESSAGES
2025-04-22 17:58:55,668 root INFO copying build/lib/django/contrib/sessions/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/km/LC_MESSAGES
2025-04-22 17:58:55,668 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/da
2025-04-22 17:58:55,668 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/locale/da/LC_MESSAGES
2025-04-22 17:58:55,669 root INFO copying build/lib/django/contrib/sessions/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/da/LC_MESSAGES
2025-04-22 17:58:55,669 root INFO copying build/lib/django/contrib/sessions/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/locale/da/LC_MESSAGES
2025-04-22 17:58:55,669 root INFO copying build/lib/django/contrib/sessions/serializers.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions
2025-04-22 17:58:55,669 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/sessions/backends
2025-04-22 17:58:55,669 root INFO copying build/lib/django/contrib/sessions/backends/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/backends
2025-04-22 17:58:55,669 root INFO copying build/lib/django/contrib/sessions/backends/cache.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/backends
2025-04-22 17:58:55,670 root INFO copying build/lib/django/contrib/sessions/backends/db.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/backends
2025-04-22 17:58:55,670 root INFO copying build/lib/django/contrib/sessions/backends/cached_db.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/backends
2025-04-22 17:58:55,670 root INFO copying build/lib/django/contrib/sessions/backends/signed_cookies.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/backends
2025-04-22 17:58:55,670 root INFO copying build/lib/django/contrib/sessions/backends/base.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/backends
2025-04-22 17:58:55,670 root INFO copying build/lib/django/contrib/sessions/backends/file.py -> build/bdist.linux-armv8l/wheel/./django/contrib/sessions/backends
2025-04-22 17:58:55,671 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs
2025-04-22 17:58:55,671 root INFO copying build/lib/django/contrib/admindocs/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs
2025-04-22 17:58:55,671 root INFO copying build/lib/django/contrib/admindocs/middleware.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs
2025-04-22 17:58:55,671 root INFO copying build/lib/django/contrib/admindocs/views.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs
2025-04-22 17:58:55,671 root INFO copying build/lib/django/contrib/admindocs/apps.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs
2025-04-22 17:58:55,672 root INFO copying build/lib/django/contrib/admindocs/urls.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs
2025-04-22 17:58:55,672 root INFO copying build/lib/django/contrib/admindocs/utils.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs
2025-04-22 17:58:55,672 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale
2025-04-22 17:58:55,672 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/lv
2025-04-22 17:58:55,673 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,673 root INFO copying build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,673 root INFO copying build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,673 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/sw
2025-04-22 17:58:55,673 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,674 root INFO copying build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,674 root INFO copying build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,674 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/en_AU
2025-04-22 17:58:55,674 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,674 root INFO copying build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,675 root INFO copying build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,675 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/mr
2025-04-22 17:58:55,675 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,675 root INFO copying build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,675 root INFO copying build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,675 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/lb
2025-04-22 17:58:55,676 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,676 root INFO copying build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,676 root INFO copying build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,676 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ca
2025-04-22 17:58:55,677 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,677 root INFO copying build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,677 root INFO copying build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,677 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/en_GB
2025-04-22 17:58:55,677 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,678 root INFO copying build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,678 root INFO copying build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,678 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/el
2025-04-22 17:58:55,678 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/el/LC_MESSAGES
2025-04-22 17:58:55,678 root INFO copying build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/el/LC_MESSAGES
2025-04-22 17:58:55,679 root INFO copying build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/el/LC_MESSAGES
2025-04-22 17:58:55,679 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/es_VE
2025-04-22 17:58:55,679 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,679 root INFO copying build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,680 root INFO copying build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,680 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/af
2025-04-22 17:58:55,680 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/af/LC_MESSAGES
2025-04-22 17:58:55,680 root INFO copying build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/af/LC_MESSAGES
2025-04-22 17:58:55,680 root INFO copying build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/af/LC_MESSAGES
2025-04-22 17:58:55,681 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/en
2025-04-22 17:58:55,681 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/en/LC_MESSAGES
2025-04-22 17:58:55,681 root INFO copying build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/en/LC_MESSAGES
2025-04-22 17:58:55,681 root INFO copying build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/en/LC_MESSAGES
2025-04-22 17:58:55,682 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/dsb
2025-04-22 17:58:55,682 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,682 root INFO copying build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,682 root INFO copying build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,682 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/et
2025-04-22 17:58:55,683 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/et/LC_MESSAGES
2025-04-22 17:58:55,683 root INFO copying build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/et/LC_MESSAGES
2025-04-22 17:58:55,683 root INFO copying build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/et/LC_MESSAGES
2025-04-22 17:58:55,683 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/nn
2025-04-22 17:58:55,683 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,684 root INFO copying build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,684 root INFO copying build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,684 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/cy
2025-04-22 17:58:55,684 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,685 root INFO copying build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,685 root INFO copying build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,685 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ko
2025-04-22 17:58:55,685 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,685 root INFO copying build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,686 root INFO copying build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,686 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/is
2025-04-22 17:58:55,686 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/is/LC_MESSAGES
2025-04-22 17:58:55,686 root INFO copying build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/is/LC_MESSAGES
2025-04-22 17:58:55,687 root INFO copying build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/is/LC_MESSAGES
2025-04-22 17:58:55,687 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/pa
2025-04-22 17:58:55,687 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,687 root INFO copying build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,687 root INFO copying build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,688 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/tt
2025-04-22 17:58:55,688 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,688 root INFO copying build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,688 root INFO copying build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,688 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ne
2025-04-22 17:58:55,689 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,689 root INFO copying build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,689 root INFO copying build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,689 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/sr_Latn
2025-04-22 17:58:55,690 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,690 root INFO copying build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,690 root INFO copying build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,690 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/fy
2025-04-22 17:58:55,690 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,691 root INFO copying build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,691 root INFO copying build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,691 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/bg
2025-04-22 17:58:55,691 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,692 root INFO copying build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,692 root INFO copying build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,692 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ga
2025-04-22 17:58:55,692 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,692 root INFO copying build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,693 root INFO copying build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,693 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/gl
2025-04-22 17:58:55,693 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,693 root INFO copying build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,694 root INFO copying build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,694 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/uk
2025-04-22 17:58:55,694 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,694 root INFO copying build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,694 root INFO copying build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,695 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/kn
2025-04-22 17:58:55,695 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,695 root INFO copying build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,695 root INFO copying build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,695 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ja
2025-04-22 17:58:55,696 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,696 root INFO copying build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,696 root INFO copying build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,696 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/cs
2025-04-22 17:58:55,697 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,697 root INFO copying build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,697 root INFO copying build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,697 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/os
2025-04-22 17:58:55,698 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/os/LC_MESSAGES
2025-04-22 17:58:55,698 root INFO copying build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/os/LC_MESSAGES
2025-04-22 17:58:55,698 root INFO copying build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/os/LC_MESSAGES
2025-04-22 17:58:55,698 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/tr
2025-04-22 17:58:55,698 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,698 root INFO copying build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,699 root INFO copying build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,699 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/io
2025-04-22 17:58:55,699 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/io/LC_MESSAGES
2025-04-22 17:58:55,699 root INFO copying build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/io/LC_MESSAGES
2025-04-22 17:58:55,700 root INFO copying build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/io/LC_MESSAGES
2025-04-22 17:58:55,700 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/sl
2025-04-22 17:58:55,700 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,700 root INFO copying build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,700 root INFO copying build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,701 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/sq
2025-04-22 17:58:55,701 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,701 root INFO copying build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,701 root INFO copying build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,702 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/az
2025-04-22 17:58:55,702 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/az/LC_MESSAGES
2025-04-22 17:58:55,702 root INFO copying build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/az/LC_MESSAGES
2025-04-22 17:58:55,702 root INFO copying build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/az/LC_MESSAGES
2025-04-22 17:58:55,702 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/eo
2025-04-22 17:58:55,703 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,703 root INFO copying build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,703 root INFO copying build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,703 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/pt_BR
2025-04-22 17:58:55,704 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,704 root INFO copying build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,704 root INFO copying build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,705 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/pl
2025-04-22 17:58:55,705 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,705 root INFO copying build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,705 root INFO copying build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,705 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/gd
2025-04-22 17:58:55,706 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,706 root INFO copying build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,706 root INFO copying build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,706 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/hr
2025-04-22 17:58:55,707 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,707 root INFO copying build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,707 root INFO copying build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,707 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ru
2025-04-22 17:58:55,707 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,708 root INFO copying build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,708 root INFO copying build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,708 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/es
2025-04-22 17:58:55,708 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/es/LC_MESSAGES
2025-04-22 17:58:55,708 root INFO copying build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/es/LC_MESSAGES
2025-04-22 17:58:55,709 root INFO copying build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/es/LC_MESSAGES
2025-04-22 17:58:55,709 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/id
2025-04-22 17:58:55,709 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/id/LC_MESSAGES
2025-04-22 17:58:55,709 root INFO copying build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/id/LC_MESSAGES
2025-04-22 17:58:55,710 root INFO copying build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/id/LC_MESSAGES
2025-04-22 17:58:55,710 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/fi
2025-04-22 17:58:55,710 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,710 root INFO copying build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,710 root INFO copying build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,711 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/mk
2025-04-22 17:58:55,711 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,711 root INFO copying build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,711 root INFO copying build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,712 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/hi
2025-04-22 17:58:55,712 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,712 root INFO copying build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,712 root INFO copying build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,712 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/kab
2025-04-22 17:58:55,713 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,713 root INFO copying build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,713 root INFO copying build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/kab/LC_MESSAGES
2025-04-22 17:58:55,713 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/hsb
2025-04-22 17:58:55,714 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,714 root INFO copying build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,714 root INFO copying build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,714 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/sk
2025-04-22 17:58:55,714 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,715 root INFO copying build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,715 root INFO copying build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,715 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/lt
2025-04-22 17:58:55,715 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,716 root INFO copying build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,716 root INFO copying build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,716 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/de
2025-04-22 17:58:55,716 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/de/LC_MESSAGES
2025-04-22 17:58:55,716 root INFO copying build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/de/LC_MESSAGES
2025-04-22 17:58:55,717 root INFO copying build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/de/LC_MESSAGES
2025-04-22 17:58:55,717 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/it
2025-04-22 17:58:55,717 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/it/LC_MESSAGES
2025-04-22 17:58:55,717 root INFO copying build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/it/LC_MESSAGES
2025-04-22 17:58:55,718 root INFO copying build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/it/LC_MESSAGES
2025-04-22 17:58:55,718 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/my
2025-04-22 17:58:55,718 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/my/LC_MESSAGES
2025-04-22 17:58:55,718 root INFO copying build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/my/LC_MESSAGES
2025-04-22 17:58:55,718 root INFO copying build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/my/LC_MESSAGES
2025-04-22 17:58:55,719 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/sr
2025-04-22 17:58:55,719 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,719 root INFO copying build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,719 root INFO copying build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,720 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/bs
2025-04-22 17:58:55,720 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,720 root INFO copying build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,720 root INFO copying build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,721 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ro
2025-04-22 17:58:55,721 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,721 root INFO copying build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,721 root INFO copying build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,721 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ky
2025-04-22 17:58:55,722 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,722 root INFO copying build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,722 root INFO copying build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,722 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/fr
2025-04-22 17:58:55,722 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,723 root INFO copying build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,723 root INFO copying build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,723 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ar
2025-04-22 17:58:55,723 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,724 root INFO copying build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,724 root INFO copying build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,724 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/es_AR
2025-04-22 17:58:55,724 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,725 root INFO copying build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,725 root INFO copying build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,725 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/vi
2025-04-22 17:58:55,725 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,725 root INFO copying build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,726 root INFO copying build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,726 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ckb
2025-04-22 17:58:55,726 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,726 root INFO copying build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,727 root INFO copying build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,727 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/sv
2025-04-22 17:58:55,727 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,727 root INFO copying build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,727 root INFO copying build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,728 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/zh_Hant
2025-04-22 17:58:55,728 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,728 root INFO copying build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,728 root INFO copying build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,729 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/kk
2025-04-22 17:58:55,729 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,729 root INFO copying build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,729 root INFO copying build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,729 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/es_CO
2025-04-22 17:58:55,730 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,730 root INFO copying build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,730 root INFO copying build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,730 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/be
2025-04-22 17:58:55,731 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/be/LC_MESSAGES
2025-04-22 17:58:55,731 root INFO copying build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/be/LC_MESSAGES
2025-04-22 17:58:55,731 root INFO copying build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/be/LC_MESSAGES
2025-04-22 17:58:55,731 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/udm
2025-04-22 17:58:55,731 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,732 root INFO copying build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,732 root INFO copying build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,732 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ml
2025-04-22 17:58:55,732 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,732 root INFO copying build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,733 root INFO copying build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,733 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ar_DZ
2025-04-22 17:58:55,733 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,733 root INFO copying build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,734 root INFO copying build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,734 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ms
2025-04-22 17:58:55,734 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,734 root INFO copying build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,734 root INFO copying build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,735 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ast
2025-04-22 17:58:55,735 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,735 root INFO copying build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,735 root INFO copying build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,736 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/zh_Hans
2025-04-22 17:58:55,736 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,736 root INFO copying build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,736 root INFO copying build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,736 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ur
2025-04-22 17:58:55,737 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,737 root INFO copying build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,737 root INFO copying build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,737 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ia
2025-04-22 17:58:55,737 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,738 root INFO copying build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,738 root INFO copying build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,738 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/hu
2025-04-22 17:58:55,738 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,738 root INFO copying build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,739 root INFO copying build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,739 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ta
2025-04-22 17:58:55,739 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,739 root INFO copying build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,740 root INFO copying build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,740 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/eu
2025-04-22 17:58:55,740 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,740 root INFO copying build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,740 root INFO copying build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,741 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/es_MX
2025-04-22 17:58:55,741 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,741 root INFO copying build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,741 root INFO copying build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,742 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/th
2025-04-22 17:58:55,742 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/th/LC_MESSAGES
2025-04-22 17:58:55,742 root INFO copying build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/th/LC_MESSAGES
2025-04-22 17:58:55,742 root INFO copying build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/th/LC_MESSAGES
2025-04-22 17:58:55,742 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/nb
2025-04-22 17:58:55,743 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,743 root INFO copying build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,743 root INFO copying build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,743 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/mn
2025-04-22 17:58:55,744 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,744 root INFO copying build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,744 root INFO copying build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,744 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ka
2025-04-22 17:58:55,745 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,745 root INFO copying build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,745 root INFO copying build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,745 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/nl
2025-04-22 17:58:55,745 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,746 root INFO copying build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,746 root INFO copying build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,746 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/te
2025-04-22 17:58:55,746 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/te/LC_MESSAGES
2025-04-22 17:58:55,746 root INFO copying build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/te/LC_MESSAGES
2025-04-22 17:58:55,747 root INFO copying build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/te/LC_MESSAGES
2025-04-22 17:58:55,747 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/pt
2025-04-22 17:58:55,747 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,747 root INFO copying build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,747 root INFO copying build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,748 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/bn
2025-04-22 17:58:55,748 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,748 root INFO copying build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,748 root INFO copying build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,749 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/he
2025-04-22 17:58:55,749 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/he/LC_MESSAGES
2025-04-22 17:58:55,749 root INFO copying build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/he/LC_MESSAGES
2025-04-22 17:58:55,749 root INFO copying build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/he/LC_MESSAGES
2025-04-22 17:58:55,750 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/br
2025-04-22 17:58:55,750 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/br/LC_MESSAGES
2025-04-22 17:58:55,750 root INFO copying build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/br/LC_MESSAGES
2025-04-22 17:58:55,750 root INFO copying build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/br/LC_MESSAGES
2025-04-22 17:58:55,751 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/fa
2025-04-22 17:58:55,751 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,751 root INFO copying build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,751 root INFO copying build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,752 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/tg
2025-04-22 17:58:55,752 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,752 root INFO copying build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,752 root INFO copying build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,752 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/km
2025-04-22 17:58:55,753 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/km/LC_MESSAGES
2025-04-22 17:58:55,753 root INFO copying build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/km/LC_MESSAGES
2025-04-22 17:58:55,753 root INFO copying build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/km/LC_MESSAGES
2025-04-22 17:58:55,753 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/da
2025-04-22 17:58:55,754 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/locale/da/LC_MESSAGES
2025-04-22 17:58:55,754 root INFO copying build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/da/LC_MESSAGES
2025-04-22 17:58:55,754 root INFO copying build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/locale/da/LC_MESSAGES
2025-04-22 17:58:55,754 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/templates
2025-04-22 17:58:55,754 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:55,755 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/model_index.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:55,755 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/index.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:55,755 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/model_detail.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:55,755 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/view_index.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:55,755 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/view_detail.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:55,756 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/template_tag_index.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:55,756 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/missing_docutils.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:55,756 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/template_detail.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:55,756 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/bookmarklets.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:55,756 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/template_filter_index.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admindocs/templates/admin_doc
2025-04-22 17:58:55,757 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/syndication
2025-04-22 17:58:55,757 root INFO copying build/lib/django/contrib/syndication/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/syndication
2025-04-22 17:58:55,757 root INFO copying build/lib/django/contrib/syndication/views.py -> build/bdist.linux-armv8l/wheel/./django/contrib/syndication
2025-04-22 17:58:55,757 root INFO copying build/lib/django/contrib/syndication/apps.py -> build/bdist.linux-armv8l/wheel/./django/contrib/syndication
2025-04-22 17:58:55,758 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres
2025-04-22 17:58:55,758 root INFO copying build/lib/django/contrib/postgres/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres
2025-04-22 17:58:55,758 root INFO copying build/lib/django/contrib/postgres/functions.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres
2025-04-22 17:58:55,758 root INFO copying build/lib/django/contrib/postgres/signals.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres
2025-04-22 17:58:55,758 root INFO copying build/lib/django/contrib/postgres/lookups.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres
2025-04-22 17:58:55,758 root INFO copying build/lib/django/contrib/postgres/validators.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres
2025-04-22 17:58:55,759 root INFO copying build/lib/django/contrib/postgres/operations.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres
2025-04-22 17:58:55,759 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/jinja2
2025-04-22 17:58:55,759 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/jinja2/postgres
2025-04-22 17:58:55,759 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/jinja2/postgres/widgets
2025-04-22 17:58:55,760 root INFO copying build/lib/django/contrib/postgres/jinja2/postgres/widgets/split_array.html -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/jinja2/postgres/widgets
2025-04-22 17:58:55,760 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/aggregates
2025-04-22 17:58:55,760 root INFO copying build/lib/django/contrib/postgres/aggregates/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/aggregates
2025-04-22 17:58:55,760 root INFO copying build/lib/django/contrib/postgres/aggregates/statistics.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/aggregates
2025-04-22 17:58:55,760 root INFO copying build/lib/django/contrib/postgres/aggregates/general.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/aggregates
2025-04-22 17:58:55,761 root INFO copying build/lib/django/contrib/postgres/aggregates/mixins.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/aggregates
2025-04-22 17:58:55,761 root INFO copying build/lib/django/contrib/postgres/apps.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres
2025-04-22 17:58:55,761 root INFO copying build/lib/django/contrib/postgres/indexes.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres
2025-04-22 17:58:55,761 root INFO copying build/lib/django/contrib/postgres/utils.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres
2025-04-22 17:58:55,761 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/fields
2025-04-22 17:58:55,762 root INFO copying build/lib/django/contrib/postgres/fields/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/fields
2025-04-22 17:58:55,762 root INFO copying build/lib/django/contrib/postgres/fields/hstore.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/fields
2025-04-22 17:58:55,762 root INFO copying build/lib/django/contrib/postgres/fields/citext.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/fields
2025-04-22 17:58:55,762 root INFO copying build/lib/django/contrib/postgres/fields/jsonb.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/fields
2025-04-22 17:58:55,762 root INFO copying build/lib/django/contrib/postgres/fields/utils.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/fields
2025-04-22 17:58:55,763 root INFO copying build/lib/django/contrib/postgres/fields/ranges.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/fields
2025-04-22 17:58:55,763 root INFO copying build/lib/django/contrib/postgres/fields/array.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/fields
2025-04-22 17:58:55,763 root INFO copying build/lib/django/contrib/postgres/expressions.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres
2025-04-22 17:58:55,763 root INFO copying build/lib/django/contrib/postgres/search.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres
2025-04-22 17:58:55,763 root INFO copying build/lib/django/contrib/postgres/constraints.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres
2025-04-22 17:58:55,764 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale
2025-04-22 17:58:55,764 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/lv
2025-04-22 17:58:55,764 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,764 root INFO copying build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,765 root INFO copying build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,765 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/en_AU
2025-04-22 17:58:55,765 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,765 root INFO copying build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,765 root INFO copying build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,766 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ca
2025-04-22 17:58:55,766 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,766 root INFO copying build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,766 root INFO copying build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,767 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/el
2025-04-22 17:58:55,767 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/el/LC_MESSAGES
2025-04-22 17:58:55,767 root INFO copying build/lib/django/contrib/postgres/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/el/LC_MESSAGES
2025-04-22 17:58:55,767 root INFO copying build/lib/django/contrib/postgres/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/el/LC_MESSAGES
2025-04-22 17:58:55,767 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/af
2025-04-22 17:58:55,768 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/af/LC_MESSAGES
2025-04-22 17:58:55,768 root INFO copying build/lib/django/contrib/postgres/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/af/LC_MESSAGES
2025-04-22 17:58:55,768 root INFO copying build/lib/django/contrib/postgres/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/af/LC_MESSAGES
2025-04-22 17:58:55,768 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/en
2025-04-22 17:58:55,768 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/en/LC_MESSAGES
2025-04-22 17:58:55,769 root INFO copying build/lib/django/contrib/postgres/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/en/LC_MESSAGES
2025-04-22 17:58:55,769 root INFO copying build/lib/django/contrib/postgres/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/en/LC_MESSAGES
2025-04-22 17:58:55,769 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/dsb
2025-04-22 17:58:55,769 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,769 root INFO copying build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,770 root INFO copying build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,770 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/et
2025-04-22 17:58:55,770 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/et/LC_MESSAGES
2025-04-22 17:58:55,770 root INFO copying build/lib/django/contrib/postgres/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/et/LC_MESSAGES
2025-04-22 17:58:55,771 root INFO copying build/lib/django/contrib/postgres/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/et/LC_MESSAGES
2025-04-22 17:58:55,771 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/nn
2025-04-22 17:58:55,771 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,771 root INFO copying build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,771 root INFO copying build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,772 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ko
2025-04-22 17:58:55,772 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,772 root INFO copying build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,772 root INFO copying build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,773 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/is
2025-04-22 17:58:55,773 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/is/LC_MESSAGES
2025-04-22 17:58:55,773 root INFO copying build/lib/django/contrib/postgres/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/is/LC_MESSAGES
2025-04-22 17:58:55,773 root INFO copying build/lib/django/contrib/postgres/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/is/LC_MESSAGES
2025-04-22 17:58:55,773 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ne
2025-04-22 17:58:55,774 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,774 root INFO copying build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,774 root INFO copying build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,774 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/sr_Latn
2025-04-22 17:58:55,774 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,775 root INFO copying build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,775 root INFO copying build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,775 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/bg
2025-04-22 17:58:55,775 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,775 root INFO copying build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,776 root INFO copying build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,776 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/gl
2025-04-22 17:58:55,776 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,776 root INFO copying build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,777 root INFO copying build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,777 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/uk
2025-04-22 17:58:55,777 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,777 root INFO copying build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,777 root INFO copying build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,778 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/uz
2025-04-22 17:58:55,778 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,778 root INFO copying build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,778 root INFO copying build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/uz/LC_MESSAGES
2025-04-22 17:58:55,778 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ja
2025-04-22 17:58:55,779 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,779 root INFO copying build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,779 root INFO copying build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,779 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/cs
2025-04-22 17:58:55,780 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,780 root INFO copying build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,780 root INFO copying build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,780 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/tr
2025-04-22 17:58:55,780 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,781 root INFO copying build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,781 root INFO copying build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,781 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/sl
2025-04-22 17:58:55,781 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,781 root INFO copying build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,782 root INFO copying build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,782 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/sq
2025-04-22 17:58:55,782 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,782 root INFO copying build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,782 root INFO copying build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,783 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/az
2025-04-22 17:58:55,783 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/az/LC_MESSAGES
2025-04-22 17:58:55,783 root INFO copying build/lib/django/contrib/postgres/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/az/LC_MESSAGES
2025-04-22 17:58:55,783 root INFO copying build/lib/django/contrib/postgres/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/az/LC_MESSAGES
2025-04-22 17:58:55,784 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/eo
2025-04-22 17:58:55,784 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,784 root INFO copying build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,784 root INFO copying build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,785 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/pt_BR
2025-04-22 17:58:55,785 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,785 root INFO copying build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,785 root INFO copying build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,786 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/pl
2025-04-22 17:58:55,786 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,786 root INFO copying build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,786 root INFO copying build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,786 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/gd
2025-04-22 17:58:55,787 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,787 root INFO copying build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,787 root INFO copying build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,787 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/hr
2025-04-22 17:58:55,787 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,788 root INFO copying build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,788 root INFO copying build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,788 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ru
2025-04-22 17:58:55,788 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,788 root INFO copying build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,789 root INFO copying build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,789 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/es
2025-04-22 17:58:55,789 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/es/LC_MESSAGES
2025-04-22 17:58:55,789 root INFO copying build/lib/django/contrib/postgres/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/es/LC_MESSAGES
2025-04-22 17:58:55,789 root INFO copying build/lib/django/contrib/postgres/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/es/LC_MESSAGES
2025-04-22 17:58:55,790 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/id
2025-04-22 17:58:55,790 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/id/LC_MESSAGES
2025-04-22 17:58:55,790 root INFO copying build/lib/django/contrib/postgres/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/id/LC_MESSAGES
2025-04-22 17:58:55,790 root INFO copying build/lib/django/contrib/postgres/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/id/LC_MESSAGES
2025-04-22 17:58:55,791 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/fi
2025-04-22 17:58:55,791 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,791 root INFO copying build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,791 root INFO copying build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,791 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/mk
2025-04-22 17:58:55,792 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,792 root INFO copying build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,792 root INFO copying build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,792 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/hsb
2025-04-22 17:58:55,792 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,793 root INFO copying build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,793 root INFO copying build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,793 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/sk
2025-04-22 17:58:55,794 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,794 root INFO copying build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,794 root INFO copying build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,794 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/lt
2025-04-22 17:58:55,794 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,794 root INFO copying build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,795 root INFO copying build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,795 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/de
2025-04-22 17:58:55,795 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/de/LC_MESSAGES
2025-04-22 17:58:55,795 root INFO copying build/lib/django/contrib/postgres/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/de/LC_MESSAGES
2025-04-22 17:58:55,796 root INFO copying build/lib/django/contrib/postgres/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/de/LC_MESSAGES
2025-04-22 17:58:55,796 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/it
2025-04-22 17:58:55,796 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/it/LC_MESSAGES
2025-04-22 17:58:55,796 root INFO copying build/lib/django/contrib/postgres/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/it/LC_MESSAGES
2025-04-22 17:58:55,796 root INFO copying build/lib/django/contrib/postgres/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/it/LC_MESSAGES
2025-04-22 17:58:55,797 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/sr
2025-04-22 17:58:55,797 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,797 root INFO copying build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,797 root INFO copying build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,798 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ro
2025-04-22 17:58:55,798 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,798 root INFO copying build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,798 root INFO copying build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,798 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ky
2025-04-22 17:58:55,799 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,799 root INFO copying build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,799 root INFO copying build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,799 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/fr
2025-04-22 17:58:55,799 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,800 root INFO copying build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,800 root INFO copying build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,800 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ar
2025-04-22 17:58:55,800 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,800 root INFO copying build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,801 root INFO copying build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,801 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/hy
2025-04-22 17:58:55,801 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,801 root INFO copying build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,801 root INFO copying build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,802 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/es_AR
2025-04-22 17:58:55,802 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,802 root INFO copying build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,802 root INFO copying build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,803 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ckb
2025-04-22 17:58:55,803 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,803 root INFO copying build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,803 root INFO copying build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,803 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/sv
2025-04-22 17:58:55,804 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,804 root INFO copying build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,804 root INFO copying build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,804 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/zh_Hant
2025-04-22 17:58:55,804 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,805 root INFO copying build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,805 root INFO copying build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,805 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/kk
2025-04-22 17:58:55,805 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,805 root INFO copying build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,806 root INFO copying build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,806 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/es_CO
2025-04-22 17:58:55,806 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,806 root INFO copying build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,806 root INFO copying build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,807 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/be
2025-04-22 17:58:55,807 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/be/LC_MESSAGES
2025-04-22 17:58:55,807 root INFO copying build/lib/django/contrib/postgres/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/be/LC_MESSAGES
2025-04-22 17:58:55,807 root INFO copying build/lib/django/contrib/postgres/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/be/LC_MESSAGES
2025-04-22 17:58:55,808 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ml
2025-04-22 17:58:55,808 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,808 root INFO copying build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,808 root INFO copying build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,808 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ar_DZ
2025-04-22 17:58:55,809 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,809 root INFO copying build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,809 root INFO copying build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,810 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ms
2025-04-22 17:58:55,810 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,810 root INFO copying build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,810 root INFO copying build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,810 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/zh_Hans
2025-04-22 17:58:55,811 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,811 root INFO copying build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,811 root INFO copying build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,811 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ia
2025-04-22 17:58:55,811 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,812 root INFO copying build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,812 root INFO copying build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,812 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/hu
2025-04-22 17:58:55,812 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,812 root INFO copying build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,813 root INFO copying build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,813 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/eu
2025-04-22 17:58:55,813 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,813 root INFO copying build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,814 root INFO copying build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,814 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/es_MX
2025-04-22 17:58:55,814 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,814 root INFO copying build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,814 root INFO copying build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,815 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/tk
2025-04-22 17:58:55,815 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,815 root INFO copying build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,815 root INFO copying build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/tk/LC_MESSAGES
2025-04-22 17:58:55,815 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/nb
2025-04-22 17:58:55,816 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,816 root INFO copying build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,816 root INFO copying build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,816 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/mn
2025-04-22 17:58:55,817 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,817 root INFO copying build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,817 root INFO copying build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,817 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ka
2025-04-22 17:58:55,817 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,818 root INFO copying build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,818 root INFO copying build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,818 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/nl
2025-04-22 17:58:55,818 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,818 root INFO copying build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,819 root INFO copying build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,819 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/pt
2025-04-22 17:58:55,819 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,819 root INFO copying build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,820 root INFO copying build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,820 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/he
2025-04-22 17:58:55,820 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/he/LC_MESSAGES
2025-04-22 17:58:55,820 root INFO copying build/lib/django/contrib/postgres/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/he/LC_MESSAGES
2025-04-22 17:58:55,821 root INFO copying build/lib/django/contrib/postgres/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/he/LC_MESSAGES
2025-04-22 17:58:55,821 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/fa
2025-04-22 17:58:55,821 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,821 root INFO copying build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,821 root INFO copying build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,822 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/tg
2025-04-22 17:58:55,822 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,822 root INFO copying build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,822 root INFO copying build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,822 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/da
2025-04-22 17:58:55,823 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/locale/da/LC_MESSAGES
2025-04-22 17:58:55,823 root INFO copying build/lib/django/contrib/postgres/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/da/LC_MESSAGES
2025-04-22 17:58:55,823 root INFO copying build/lib/django/contrib/postgres/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/locale/da/LC_MESSAGES
2025-04-22 17:58:55,823 root INFO copying build/lib/django/contrib/postgres/serializers.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres
2025-04-22 17:58:55,824 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/templates
2025-04-22 17:58:55,824 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/templates/postgres
2025-04-22 17:58:55,824 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/templates/postgres/widgets
2025-04-22 17:58:55,824 root INFO copying build/lib/django/contrib/postgres/templates/postgres/widgets/split_array.html -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/templates/postgres/widgets
2025-04-22 17:58:55,824 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/postgres/forms
2025-04-22 17:58:55,825 root INFO copying build/lib/django/contrib/postgres/forms/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/forms
2025-04-22 17:58:55,825 root INFO copying build/lib/django/contrib/postgres/forms/hstore.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/forms
2025-04-22 17:58:55,825 root INFO copying build/lib/django/contrib/postgres/forms/ranges.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/forms
2025-04-22 17:58:55,825 root INFO copying build/lib/django/contrib/postgres/forms/array.py -> build/bdist.linux-armv8l/wheel/./django/contrib/postgres/forms
2025-04-22 17:58:55,826 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis
2025-04-22 17:58:55,826 root INFO copying build/lib/django/contrib/gis/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis
2025-04-22 17:58:55,826 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/db
2025-04-22 17:58:55,826 root INFO copying build/lib/django/contrib/gis/db/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db
2025-04-22 17:58:55,826 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/db/models
2025-04-22 17:58:55,827 root INFO copying build/lib/django/contrib/gis/db/models/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/models
2025-04-22 17:58:55,827 root INFO copying build/lib/django/contrib/gis/db/models/functions.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/models
2025-04-22 17:58:55,827 root INFO copying build/lib/django/contrib/gis/db/models/lookups.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/models
2025-04-22 17:58:55,827 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/db/models/sql
2025-04-22 17:58:55,827 root INFO copying build/lib/django/contrib/gis/db/models/sql/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/models/sql
2025-04-22 17:58:55,828 root INFO copying build/lib/django/contrib/gis/db/models/sql/conversion.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/models/sql
2025-04-22 17:58:55,828 root INFO copying build/lib/django/contrib/gis/db/models/fields.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/models
2025-04-22 17:58:55,828 root INFO copying build/lib/django/contrib/gis/db/models/aggregates.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/models
2025-04-22 17:58:55,828 root INFO copying build/lib/django/contrib/gis/db/models/proxy.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/models
2025-04-22 17:58:55,829 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/db/backends
2025-04-22 17:58:55,829 root INFO copying build/lib/django/contrib/gis/db/backends/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends
2025-04-22 17:58:55,829 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:55,829 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:55,829 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/schema.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:55,830 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/features.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:55,830 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/operations.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:55,830 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/models.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:55,830 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/introspection.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:55,830 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/base.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:55,831 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/client.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:55,831 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/adapter.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/spatialite
2025-04-22 17:58:55,831 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/db/backends/base
2025-04-22 17:58:55,831 root INFO copying build/lib/django/contrib/gis/db/backends/base/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/base
2025-04-22 17:58:55,831 root INFO copying build/lib/django/contrib/gis/db/backends/base/features.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/base
2025-04-22 17:58:55,832 root INFO copying build/lib/django/contrib/gis/db/backends/base/operations.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/base
2025-04-22 17:58:55,832 root INFO copying build/lib/django/contrib/gis/db/backends/base/models.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/base
2025-04-22 17:58:55,832 root INFO copying build/lib/django/contrib/gis/db/backends/base/adapter.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/base
2025-04-22 17:58:55,832 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/db/backends/postgis
2025-04-22 17:58:55,832 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/postgis
2025-04-22 17:58:55,833 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/schema.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/postgis
2025-04-22 17:58:55,833 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/features.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/postgis
2025-04-22 17:58:55,833 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/operations.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/postgis
2025-04-22 17:58:55,833 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/models.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/postgis
2025-04-22 17:58:55,833 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/introspection.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/postgis
2025-04-22 17:58:55,834 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/base.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/postgis
2025-04-22 17:58:55,834 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/const.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/postgis
2025-04-22 17:58:55,834 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/pgraster.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/postgis
2025-04-22 17:58:55,834 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/adapter.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/postgis
2025-04-22 17:58:55,834 root INFO copying build/lib/django/contrib/gis/db/backends/utils.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends
2025-04-22 17:58:55,835 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/db/backends/oracle
2025-04-22 17:58:55,835 root INFO copying build/lib/django/contrib/gis/db/backends/oracle/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/oracle
2025-04-22 17:58:55,835 root INFO copying build/lib/django/contrib/gis/db/backends/oracle/schema.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/oracle
2025-04-22 17:58:55,835 root INFO copying build/lib/django/contrib/gis/db/backends/oracle/features.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/oracle
2025-04-22 17:58:55,836 root INFO copying build/lib/django/contrib/gis/db/backends/oracle/operations.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/oracle
2025-04-22 17:58:55,836 root INFO copying build/lib/django/contrib/gis/db/backends/oracle/models.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/oracle
2025-04-22 17:58:55,836 root INFO copying build/lib/django/contrib/gis/db/backends/oracle/introspection.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/oracle
2025-04-22 17:58:55,836 root INFO copying build/lib/django/contrib/gis/db/backends/oracle/base.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/oracle
2025-04-22 17:58:55,836 root INFO copying build/lib/django/contrib/gis/db/backends/oracle/adapter.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/oracle
2025-04-22 17:58:55,837 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/db/backends/mysql
2025-04-22 17:58:55,837 root INFO copying build/lib/django/contrib/gis/db/backends/mysql/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/mysql
2025-04-22 17:58:55,837 root INFO copying build/lib/django/contrib/gis/db/backends/mysql/schema.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/mysql
2025-04-22 17:58:55,837 root INFO copying build/lib/django/contrib/gis/db/backends/mysql/features.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/mysql
2025-04-22 17:58:55,837 root INFO copying build/lib/django/contrib/gis/db/backends/mysql/operations.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/mysql
2025-04-22 17:58:55,838 root INFO copying build/lib/django/contrib/gis/db/backends/mysql/introspection.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/mysql
2025-04-22 17:58:55,838 root INFO copying build/lib/django/contrib/gis/db/backends/mysql/base.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/db/backends/mysql
2025-04-22 17:58:55,838 root INFO copying build/lib/django/contrib/gis/views.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis
2025-04-22 17:58:55,838 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/sitemaps
2025-04-22 17:58:55,838 root INFO copying build/lib/django/contrib/gis/sitemaps/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/sitemaps
2025-04-22 17:58:55,839 root INFO copying build/lib/django/contrib/gis/sitemaps/views.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/sitemaps
2025-04-22 17:58:55,839 root INFO copying build/lib/django/contrib/gis/sitemaps/kml.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/sitemaps
2025-04-22 17:58:55,839 root INFO copying build/lib/django/contrib/gis/apps.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis
2025-04-22 17:58:55,839 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/utils
2025-04-22 17:58:55,840 root INFO copying build/lib/django/contrib/gis/utils/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/utils
2025-04-22 17:58:55,840 root INFO copying build/lib/django/contrib/gis/utils/layermapping.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/utils
2025-04-22 17:58:55,840 root INFO copying build/lib/django/contrib/gis/utils/srs.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/utils
2025-04-22 17:58:55,840 root INFO copying build/lib/django/contrib/gis/utils/ogrinfo.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/utils
2025-04-22 17:58:55,840 root INFO copying build/lib/django/contrib/gis/utils/ogrinspect.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/utils
2025-04-22 17:58:55,841 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/geoip2
2025-04-22 17:58:55,841 root INFO copying build/lib/django/contrib/gis/geoip2/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geoip2
2025-04-22 17:58:55,841 root INFO copying build/lib/django/contrib/gis/geoip2/resources.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geoip2
2025-04-22 17:58:55,841 root INFO copying build/lib/django/contrib/gis/geoip2/base.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geoip2
2025-04-22 17:58:55,841 root INFO copying build/lib/django/contrib/gis/geometry.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis
2025-04-22 17:58:55,842 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/static
2025-04-22 17:58:55,842 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/static/gis
2025-04-22 17:58:55,842 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/static/gis/css
2025-04-22 17:58:55,842 root INFO copying build/lib/django/contrib/gis/static/gis/css/ol3.css -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/static/gis/css
2025-04-22 17:58:55,843 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/static/gis/img
2025-04-22 17:58:55,843 root INFO copying build/lib/django/contrib/gis/static/gis/img/draw_line_off.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/static/gis/img
2025-04-22 17:58:55,843 root INFO copying build/lib/django/contrib/gis/static/gis/img/draw_point_on.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/static/gis/img
2025-04-22 17:58:55,843 root INFO copying build/lib/django/contrib/gis/static/gis/img/draw_polygon_on.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/static/gis/img
2025-04-22 17:58:55,843 root INFO copying build/lib/django/contrib/gis/static/gis/img/draw_polygon_off.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/static/gis/img
2025-04-22 17:58:55,844 root INFO copying build/lib/django/contrib/gis/static/gis/img/draw_line_on.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/static/gis/img
2025-04-22 17:58:55,844 root INFO copying build/lib/django/contrib/gis/static/gis/img/draw_point_off.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/static/gis/img
2025-04-22 17:58:55,844 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/static/gis/js
2025-04-22 17:58:55,844 root INFO copying build/lib/django/contrib/gis/static/gis/js/OLMapWidget.js -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/static/gis/js
2025-04-22 17:58:55,845 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/management
2025-04-22 17:58:55,845 root INFO copying build/lib/django/contrib/gis/management/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/management
2025-04-22 17:58:55,845 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/management/commands
2025-04-22 17:58:55,845 root INFO copying build/lib/django/contrib/gis/management/commands/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/management/commands
2025-04-22 17:58:55,845 root INFO copying build/lib/django/contrib/gis/management/commands/inspectdb.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/management/commands
2025-04-22 17:58:55,845 root INFO copying build/lib/django/contrib/gis/management/commands/ogrinspect.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/management/commands
2025-04-22 17:58:55,846 root INFO copying build/lib/django/contrib/gis/feeds.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis
2025-04-22 17:58:55,846 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/serializers
2025-04-22 17:58:55,846 root INFO copying build/lib/django/contrib/gis/serializers/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/serializers
2025-04-22 17:58:55,846 root INFO copying build/lib/django/contrib/gis/serializers/geojson.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/serializers
2025-04-22 17:58:55,847 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/admin
2025-04-22 17:58:55,847 root INFO copying build/lib/django/contrib/gis/admin/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/admin
2025-04-22 17:58:55,847 root INFO copying build/lib/django/contrib/gis/admin/options.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/admin
2025-04-22 17:58:55,847 root INFO copying build/lib/django/contrib/gis/admin/widgets.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/admin
2025-04-22 17:58:55,848 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale
2025-04-22 17:58:55,848 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/lv
2025-04-22 17:58:55,848 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,848 root INFO copying build/lib/django/contrib/gis/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,848 root INFO copying build/lib/django/contrib/gis/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,849 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/sw
2025-04-22 17:58:55,849 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,849 root INFO copying build/lib/django/contrib/gis/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,849 root INFO copying build/lib/django/contrib/gis/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,850 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/en_AU
2025-04-22 17:58:55,850 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,850 root INFO copying build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,850 root INFO copying build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,850 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/mr
2025-04-22 17:58:55,851 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,851 root INFO copying build/lib/django/contrib/gis/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,851 root INFO copying build/lib/django/contrib/gis/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,851 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/lb
2025-04-22 17:58:55,851 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,852 root INFO copying build/lib/django/contrib/gis/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,852 root INFO copying build/lib/django/contrib/gis/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,852 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ca
2025-04-22 17:58:55,852 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,852 root INFO copying build/lib/django/contrib/gis/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,853 root INFO copying build/lib/django/contrib/gis/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,853 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/en_GB
2025-04-22 17:58:55,853 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,853 root INFO copying build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,853 root INFO copying build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,854 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/el
2025-04-22 17:58:55,854 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/el/LC_MESSAGES
2025-04-22 17:58:55,854 root INFO copying build/lib/django/contrib/gis/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/el/LC_MESSAGES
2025-04-22 17:58:55,854 root INFO copying build/lib/django/contrib/gis/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/el/LC_MESSAGES
2025-04-22 17:58:55,855 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/es_VE
2025-04-22 17:58:55,855 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,855 root INFO copying build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,855 root INFO copying build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,855 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/af
2025-04-22 17:58:55,856 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/af/LC_MESSAGES
2025-04-22 17:58:55,856 root INFO copying build/lib/django/contrib/gis/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/af/LC_MESSAGES
2025-04-22 17:58:55,856 root INFO copying build/lib/django/contrib/gis/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/af/LC_MESSAGES
2025-04-22 17:58:55,856 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/en
2025-04-22 17:58:55,856 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/en/LC_MESSAGES
2025-04-22 17:58:55,857 root INFO copying build/lib/django/contrib/gis/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/en/LC_MESSAGES
2025-04-22 17:58:55,857 root INFO copying build/lib/django/contrib/gis/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/en/LC_MESSAGES
2025-04-22 17:58:55,857 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/dsb
2025-04-22 17:58:55,857 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,857 root INFO copying build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,858 root INFO copying build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,858 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/et
2025-04-22 17:58:55,858 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/et/LC_MESSAGES
2025-04-22 17:58:55,858 root INFO copying build/lib/django/contrib/gis/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/et/LC_MESSAGES
2025-04-22 17:58:55,858 root INFO copying build/lib/django/contrib/gis/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/et/LC_MESSAGES
2025-04-22 17:58:55,859 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/nn
2025-04-22 17:58:55,859 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,859 root INFO copying build/lib/django/contrib/gis/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,859 root INFO copying build/lib/django/contrib/gis/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,860 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/cy
2025-04-22 17:58:55,860 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,860 root INFO copying build/lib/django/contrib/gis/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,860 root INFO copying build/lib/django/contrib/gis/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,860 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ko
2025-04-22 17:58:55,861 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,861 root INFO copying build/lib/django/contrib/gis/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,861 root INFO copying build/lib/django/contrib/gis/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ko/LC_MESSAGES
2025-04-22 17:58:55,861 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/is
2025-04-22 17:58:55,861 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/is/LC_MESSAGES
2025-04-22 17:58:55,862 root INFO copying build/lib/django/contrib/gis/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/is/LC_MESSAGES
2025-04-22 17:58:55,862 root INFO copying build/lib/django/contrib/gis/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/is/LC_MESSAGES
2025-04-22 17:58:55,862 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/pa
2025-04-22 17:58:55,862 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,862 root INFO copying build/lib/django/contrib/gis/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,863 root INFO copying build/lib/django/contrib/gis/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/pa/LC_MESSAGES
2025-04-22 17:58:55,863 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/tt
2025-04-22 17:58:55,863 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,863 root INFO copying build/lib/django/contrib/gis/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,864 root INFO copying build/lib/django/contrib/gis/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/tt/LC_MESSAGES
2025-04-22 17:58:55,864 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ne
2025-04-22 17:58:55,864 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,864 root INFO copying build/lib/django/contrib/gis/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,864 root INFO copying build/lib/django/contrib/gis/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ne/LC_MESSAGES
2025-04-22 17:58:55,865 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/sr_Latn
2025-04-22 17:58:55,865 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,865 root INFO copying build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,865 root INFO copying build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:55,866 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/fy
2025-04-22 17:58:55,866 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,866 root INFO copying build/lib/django/contrib/gis/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,866 root INFO copying build/lib/django/contrib/gis/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/fy/LC_MESSAGES
2025-04-22 17:58:55,867 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/bg
2025-04-22 17:58:55,867 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,867 root INFO copying build/lib/django/contrib/gis/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,867 root INFO copying build/lib/django/contrib/gis/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/bg/LC_MESSAGES
2025-04-22 17:58:55,867 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ga
2025-04-22 17:58:55,868 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,868 root INFO copying build/lib/django/contrib/gis/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,868 root INFO copying build/lib/django/contrib/gis/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ga/LC_MESSAGES
2025-04-22 17:58:55,868 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/gl
2025-04-22 17:58:55,868 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,869 root INFO copying build/lib/django/contrib/gis/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,869 root INFO copying build/lib/django/contrib/gis/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/gl/LC_MESSAGES
2025-04-22 17:58:55,869 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/uk
2025-04-22 17:58:55,869 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,869 root INFO copying build/lib/django/contrib/gis/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,870 root INFO copying build/lib/django/contrib/gis/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/uk/LC_MESSAGES
2025-04-22 17:58:55,870 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/kn
2025-04-22 17:58:55,870 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,870 root INFO copying build/lib/django/contrib/gis/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,870 root INFO copying build/lib/django/contrib/gis/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/kn/LC_MESSAGES
2025-04-22 17:58:55,871 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ja
2025-04-22 17:58:55,871 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,871 root INFO copying build/lib/django/contrib/gis/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,871 root INFO copying build/lib/django/contrib/gis/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ja/LC_MESSAGES
2025-04-22 17:58:55,872 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/cs
2025-04-22 17:58:55,872 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,872 root INFO copying build/lib/django/contrib/gis/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,872 root INFO copying build/lib/django/contrib/gis/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/cs/LC_MESSAGES
2025-04-22 17:58:55,872 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/os
2025-04-22 17:58:55,873 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/os/LC_MESSAGES
2025-04-22 17:58:55,873 root INFO copying build/lib/django/contrib/gis/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/os/LC_MESSAGES
2025-04-22 17:58:55,873 root INFO copying build/lib/django/contrib/gis/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/os/LC_MESSAGES
2025-04-22 17:58:55,873 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/tr
2025-04-22 17:58:55,874 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,874 root INFO copying build/lib/django/contrib/gis/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,874 root INFO copying build/lib/django/contrib/gis/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/tr/LC_MESSAGES
2025-04-22 17:58:55,874 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/io
2025-04-22 17:58:55,874 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/io/LC_MESSAGES
2025-04-22 17:58:55,875 root INFO copying build/lib/django/contrib/gis/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/io/LC_MESSAGES
2025-04-22 17:58:55,875 root INFO copying build/lib/django/contrib/gis/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/io/LC_MESSAGES
2025-04-22 17:58:55,875 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/sl
2025-04-22 17:58:55,875 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,875 root INFO copying build/lib/django/contrib/gis/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,876 root INFO copying build/lib/django/contrib/gis/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/sl/LC_MESSAGES
2025-04-22 17:58:55,876 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/sq
2025-04-22 17:58:55,876 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,876 root INFO copying build/lib/django/contrib/gis/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,876 root INFO copying build/lib/django/contrib/gis/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/sq/LC_MESSAGES
2025-04-22 17:58:55,877 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/az
2025-04-22 17:58:55,877 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/az/LC_MESSAGES
2025-04-22 17:58:55,877 root INFO copying build/lib/django/contrib/gis/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/az/LC_MESSAGES
2025-04-22 17:58:55,877 root INFO copying build/lib/django/contrib/gis/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/az/LC_MESSAGES
2025-04-22 17:58:55,877 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/eo
2025-04-22 17:58:55,878 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,878 root INFO copying build/lib/django/contrib/gis/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,878 root INFO copying build/lib/django/contrib/gis/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/eo/LC_MESSAGES
2025-04-22 17:58:55,878 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/pt_BR
2025-04-22 17:58:55,879 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,879 root INFO copying build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,879 root INFO copying build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:55,879 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/pl
2025-04-22 17:58:55,879 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,880 root INFO copying build/lib/django/contrib/gis/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,880 root INFO copying build/lib/django/contrib/gis/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/pl/LC_MESSAGES
2025-04-22 17:58:55,880 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/gd
2025-04-22 17:58:55,880 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,880 root INFO copying build/lib/django/contrib/gis/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,881 root INFO copying build/lib/django/contrib/gis/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/gd/LC_MESSAGES
2025-04-22 17:58:55,881 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/hr
2025-04-22 17:58:55,881 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,881 root INFO copying build/lib/django/contrib/gis/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,881 root INFO copying build/lib/django/contrib/gis/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/hr/LC_MESSAGES
2025-04-22 17:58:55,882 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ru
2025-04-22 17:58:55,882 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,882 root INFO copying build/lib/django/contrib/gis/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,882 root INFO copying build/lib/django/contrib/gis/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ru/LC_MESSAGES
2025-04-22 17:58:55,882 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/es
2025-04-22 17:58:55,883 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/es/LC_MESSAGES
2025-04-22 17:58:55,883 root INFO copying build/lib/django/contrib/gis/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/es/LC_MESSAGES
2025-04-22 17:58:55,883 root INFO copying build/lib/django/contrib/gis/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/es/LC_MESSAGES
2025-04-22 17:58:55,883 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/id
2025-04-22 17:58:55,883 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/id/LC_MESSAGES
2025-04-22 17:58:55,884 root INFO copying build/lib/django/contrib/gis/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/id/LC_MESSAGES
2025-04-22 17:58:55,884 root INFO copying build/lib/django/contrib/gis/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/id/LC_MESSAGES
2025-04-22 17:58:55,884 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/fi
2025-04-22 17:58:55,884 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,884 root INFO copying build/lib/django/contrib/gis/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,885 root INFO copying build/lib/django/contrib/gis/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/fi/LC_MESSAGES
2025-04-22 17:58:55,885 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/mk
2025-04-22 17:58:55,885 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,885 root INFO copying build/lib/django/contrib/gis/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,885 root INFO copying build/lib/django/contrib/gis/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/mk/LC_MESSAGES
2025-04-22 17:58:55,886 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/hi
2025-04-22 17:58:55,886 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,886 root INFO copying build/lib/django/contrib/gis/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,886 root INFO copying build/lib/django/contrib/gis/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/hi/LC_MESSAGES
2025-04-22 17:58:55,887 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/hsb
2025-04-22 17:58:55,887 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,887 root INFO copying build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,887 root INFO copying build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/hsb/LC_MESSAGES
2025-04-22 17:58:55,887 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/sk
2025-04-22 17:58:55,888 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,888 root INFO copying build/lib/django/contrib/gis/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,888 root INFO copying build/lib/django/contrib/gis/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/sk/LC_MESSAGES
2025-04-22 17:58:55,888 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/lt
2025-04-22 17:58:55,889 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,889 root INFO copying build/lib/django/contrib/gis/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,889 root INFO copying build/lib/django/contrib/gis/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/lt/LC_MESSAGES
2025-04-22 17:58:55,889 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/de
2025-04-22 17:58:55,889 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/de/LC_MESSAGES
2025-04-22 17:58:55,889 root INFO copying build/lib/django/contrib/gis/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/de/LC_MESSAGES
2025-04-22 17:58:55,890 root INFO copying build/lib/django/contrib/gis/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/de/LC_MESSAGES
2025-04-22 17:58:55,890 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/it
2025-04-22 17:58:55,890 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/it/LC_MESSAGES
2025-04-22 17:58:55,890 root INFO copying build/lib/django/contrib/gis/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/it/LC_MESSAGES
2025-04-22 17:58:55,890 root INFO copying build/lib/django/contrib/gis/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/it/LC_MESSAGES
2025-04-22 17:58:55,891 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/my
2025-04-22 17:58:55,891 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/my/LC_MESSAGES
2025-04-22 17:58:55,891 root INFO copying build/lib/django/contrib/gis/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/my/LC_MESSAGES
2025-04-22 17:58:55,891 root INFO copying build/lib/django/contrib/gis/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/my/LC_MESSAGES
2025-04-22 17:58:55,892 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/sr
2025-04-22 17:58:55,892 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,892 root INFO copying build/lib/django/contrib/gis/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,892 root INFO copying build/lib/django/contrib/gis/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/sr/LC_MESSAGES
2025-04-22 17:58:55,892 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/bs
2025-04-22 17:58:55,893 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,893 root INFO copying build/lib/django/contrib/gis/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,893 root INFO copying build/lib/django/contrib/gis/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/bs/LC_MESSAGES
2025-04-22 17:58:55,893 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ro
2025-04-22 17:58:55,893 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,894 root INFO copying build/lib/django/contrib/gis/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,894 root INFO copying build/lib/django/contrib/gis/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ro/LC_MESSAGES
2025-04-22 17:58:55,894 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ky
2025-04-22 17:58:55,894 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,894 root INFO copying build/lib/django/contrib/gis/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,895 root INFO copying build/lib/django/contrib/gis/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ky/LC_MESSAGES
2025-04-22 17:58:55,895 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/fr
2025-04-22 17:58:55,895 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,895 root INFO copying build/lib/django/contrib/gis/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,895 root INFO copying build/lib/django/contrib/gis/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/fr/LC_MESSAGES
2025-04-22 17:58:55,896 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ar
2025-04-22 17:58:55,896 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,896 root INFO copying build/lib/django/contrib/gis/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,896 root INFO copying build/lib/django/contrib/gis/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ar/LC_MESSAGES
2025-04-22 17:58:55,897 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/hy
2025-04-22 17:58:55,897 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,897 root INFO copying build/lib/django/contrib/gis/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,897 root INFO copying build/lib/django/contrib/gis/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/hy/LC_MESSAGES
2025-04-22 17:58:55,897 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/es_AR
2025-04-22 17:58:55,898 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,898 root INFO copying build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,898 root INFO copying build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:55,898 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/vi
2025-04-22 17:58:55,898 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,899 root INFO copying build/lib/django/contrib/gis/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,899 root INFO copying build/lib/django/contrib/gis/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/vi/LC_MESSAGES
2025-04-22 17:58:55,899 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ckb
2025-04-22 17:58:55,899 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,899 root INFO copying build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,900 root INFO copying build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ckb/LC_MESSAGES
2025-04-22 17:58:55,900 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/sv
2025-04-22 17:58:55,900 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,900 root INFO copying build/lib/django/contrib/gis/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,900 root INFO copying build/lib/django/contrib/gis/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/sv/LC_MESSAGES
2025-04-22 17:58:55,901 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/zh_Hant
2025-04-22 17:58:55,901 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,901 root INFO copying build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,901 root INFO copying build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:55,901 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/kk
2025-04-22 17:58:55,902 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,902 root INFO copying build/lib/django/contrib/gis/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,902 root INFO copying build/lib/django/contrib/gis/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/kk/LC_MESSAGES
2025-04-22 17:58:55,902 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/es_CO
2025-04-22 17:58:55,903 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,903 root INFO copying build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,903 root INFO copying build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:55,903 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/be
2025-04-22 17:58:55,903 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/be/LC_MESSAGES
2025-04-22 17:58:55,904 root INFO copying build/lib/django/contrib/gis/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/be/LC_MESSAGES
2025-04-22 17:58:55,904 root INFO copying build/lib/django/contrib/gis/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/be/LC_MESSAGES
2025-04-22 17:58:55,904 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/udm
2025-04-22 17:58:55,904 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,904 root INFO copying build/lib/django/contrib/gis/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,905 root INFO copying build/lib/django/contrib/gis/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/udm/LC_MESSAGES
2025-04-22 17:58:55,905 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ml
2025-04-22 17:58:55,905 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,905 root INFO copying build/lib/django/contrib/gis/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,905 root INFO copying build/lib/django/contrib/gis/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ml/LC_MESSAGES
2025-04-22 17:58:55,906 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ar_DZ
2025-04-22 17:58:55,906 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,906 root INFO copying build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,906 root INFO copying build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:55,907 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ms
2025-04-22 17:58:55,907 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,907 root INFO copying build/lib/django/contrib/gis/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,907 root INFO copying build/lib/django/contrib/gis/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ms/LC_MESSAGES
2025-04-22 17:58:55,908 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ast
2025-04-22 17:58:55,908 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,908 root INFO copying build/lib/django/contrib/gis/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,908 root INFO copying build/lib/django/contrib/gis/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ast/LC_MESSAGES
2025-04-22 17:58:55,908 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/zh_Hans
2025-04-22 17:58:55,909 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,909 root INFO copying build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,909 root INFO copying build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:55,909 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ur
2025-04-22 17:58:55,909 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,910 root INFO copying build/lib/django/contrib/gis/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,910 root INFO copying build/lib/django/contrib/gis/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ur/LC_MESSAGES
2025-04-22 17:58:55,910 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ia
2025-04-22 17:58:55,910 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,910 root INFO copying build/lib/django/contrib/gis/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,911 root INFO copying build/lib/django/contrib/gis/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ia/LC_MESSAGES
2025-04-22 17:58:55,911 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/hu
2025-04-22 17:58:55,911 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,911 root INFO copying build/lib/django/contrib/gis/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,912 root INFO copying build/lib/django/contrib/gis/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/hu/LC_MESSAGES
2025-04-22 17:58:55,912 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ta
2025-04-22 17:58:55,912 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,912 root INFO copying build/lib/django/contrib/gis/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,912 root INFO copying build/lib/django/contrib/gis/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ta/LC_MESSAGES
2025-04-22 17:58:55,913 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/eu
2025-04-22 17:58:55,913 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,913 root INFO copying build/lib/django/contrib/gis/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,913 root INFO copying build/lib/django/contrib/gis/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/eu/LC_MESSAGES
2025-04-22 17:58:55,914 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/es_MX
2025-04-22 17:58:55,914 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,914 root INFO copying build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,914 root INFO copying build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:55,914 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/th
2025-04-22 17:58:55,915 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/th/LC_MESSAGES
2025-04-22 17:58:55,915 root INFO copying build/lib/django/contrib/gis/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/th/LC_MESSAGES
2025-04-22 17:58:55,915 root INFO copying build/lib/django/contrib/gis/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/th/LC_MESSAGES
2025-04-22 17:58:55,915 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/nb
2025-04-22 17:58:55,915 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,916 root INFO copying build/lib/django/contrib/gis/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,916 root INFO copying build/lib/django/contrib/gis/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/nb/LC_MESSAGES
2025-04-22 17:58:55,916 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/mn
2025-04-22 17:58:55,916 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,916 root INFO copying build/lib/django/contrib/gis/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,917 root INFO copying build/lib/django/contrib/gis/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/mn/LC_MESSAGES
2025-04-22 17:58:55,917 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ka
2025-04-22 17:58:55,917 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,917 root INFO copying build/lib/django/contrib/gis/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,917 root INFO copying build/lib/django/contrib/gis/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/ka/LC_MESSAGES
2025-04-22 17:58:55,918 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/nl
2025-04-22 17:58:55,918 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,918 root INFO copying build/lib/django/contrib/gis/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,918 root INFO copying build/lib/django/contrib/gis/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/nl/LC_MESSAGES
2025-04-22 17:58:55,919 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/te
2025-04-22 17:58:55,919 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/te/LC_MESSAGES
2025-04-22 17:58:55,919 root INFO copying build/lib/django/contrib/gis/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/te/LC_MESSAGES
2025-04-22 17:58:55,919 root INFO copying build/lib/django/contrib/gis/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/te/LC_MESSAGES
2025-04-22 17:58:55,920 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/pt
2025-04-22 17:58:55,920 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,920 root INFO copying build/lib/django/contrib/gis/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,920 root INFO copying build/lib/django/contrib/gis/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/pt/LC_MESSAGES
2025-04-22 17:58:55,920 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/bn
2025-04-22 17:58:55,921 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,921 root INFO copying build/lib/django/contrib/gis/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,921 root INFO copying build/lib/django/contrib/gis/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/bn/LC_MESSAGES
2025-04-22 17:58:55,921 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/he
2025-04-22 17:58:55,921 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/he/LC_MESSAGES
2025-04-22 17:58:55,922 root INFO copying build/lib/django/contrib/gis/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/he/LC_MESSAGES
2025-04-22 17:58:55,922 root INFO copying build/lib/django/contrib/gis/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/he/LC_MESSAGES
2025-04-22 17:58:55,922 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/br
2025-04-22 17:58:55,922 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/br/LC_MESSAGES
2025-04-22 17:58:55,922 root INFO copying build/lib/django/contrib/gis/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/br/LC_MESSAGES
2025-04-22 17:58:55,923 root INFO copying build/lib/django/contrib/gis/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/br/LC_MESSAGES
2025-04-22 17:58:55,923 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/fa
2025-04-22 17:58:55,923 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,923 root INFO copying build/lib/django/contrib/gis/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,924 root INFO copying build/lib/django/contrib/gis/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/fa/LC_MESSAGES
2025-04-22 17:58:55,924 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/tg
2025-04-22 17:58:55,924 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,924 root INFO copying build/lib/django/contrib/gis/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,924 root INFO copying build/lib/django/contrib/gis/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/tg/LC_MESSAGES
2025-04-22 17:58:55,925 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/km
2025-04-22 17:58:55,925 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/km/LC_MESSAGES
2025-04-22 17:58:55,925 root INFO copying build/lib/django/contrib/gis/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/km/LC_MESSAGES
2025-04-22 17:58:55,925 root INFO copying build/lib/django/contrib/gis/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/km/LC_MESSAGES
2025-04-22 17:58:55,925 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/da
2025-04-22 17:58:55,926 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/locale/da/LC_MESSAGES
2025-04-22 17:58:55,926 root INFO copying build/lib/django/contrib/gis/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/da/LC_MESSAGES
2025-04-22 17:58:55,926 root INFO copying build/lib/django/contrib/gis/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/locale/da/LC_MESSAGES
2025-04-22 17:58:55,926 root INFO copying build/lib/django/contrib/gis/ptr.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis
2025-04-22 17:58:55,927 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/geos
2025-04-22 17:58:55,927 root INFO copying build/lib/django/contrib/gis/geos/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos
2025-04-22 17:58:55,927 root INFO copying build/lib/django/contrib/gis/geos/libgeos.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos
2025-04-22 17:58:55,927 root INFO copying build/lib/django/contrib/gis/geos/collections.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos
2025-04-22 17:58:55,927 root INFO copying build/lib/django/contrib/gis/geos/linestring.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos
2025-04-22 17:58:55,928 root INFO copying build/lib/django/contrib/gis/geos/LICENSE -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos
2025-04-22 17:58:55,928 root INFO copying build/lib/django/contrib/gis/geos/prepared.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos
2025-04-22 17:58:55,928 root INFO copying build/lib/django/contrib/gis/geos/io.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos
2025-04-22 17:58:55,928 root INFO copying build/lib/django/contrib/gis/geos/mutable_list.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos
2025-04-22 17:58:55,928 root INFO copying build/lib/django/contrib/gis/geos/point.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos
2025-04-22 17:58:55,929 root INFO copying build/lib/django/contrib/gis/geos/geometry.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos
2025-04-22 17:58:55,929 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/geos/prototypes
2025-04-22 17:58:55,929 root INFO copying build/lib/django/contrib/gis/geos/prototypes/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos/prototypes
2025-04-22 17:58:55,929 root INFO copying build/lib/django/contrib/gis/geos/prototypes/prepared.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos/prototypes
2025-04-22 17:58:55,930 root INFO copying build/lib/django/contrib/gis/geos/prototypes/io.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos/prototypes
2025-04-22 17:58:55,930 root INFO copying build/lib/django/contrib/gis/geos/prototypes/threadsafe.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos/prototypes
2025-04-22 17:58:55,930 root INFO copying build/lib/django/contrib/gis/geos/prototypes/errcheck.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos/prototypes
2025-04-22 17:58:55,930 root INFO copying build/lib/django/contrib/gis/geos/prototypes/misc.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos/prototypes
2025-04-22 17:58:55,930 root INFO copying build/lib/django/contrib/gis/geos/prototypes/predicates.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos/prototypes
2025-04-22 17:58:55,931 root INFO copying build/lib/django/contrib/gis/geos/prototypes/topology.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos/prototypes
2025-04-22 17:58:55,931 root INFO copying build/lib/django/contrib/gis/geos/prototypes/geom.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos/prototypes
2025-04-22 17:58:55,931 root INFO copying build/lib/django/contrib/gis/geos/prototypes/coordseq.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos/prototypes
2025-04-22 17:58:55,931 root INFO copying build/lib/django/contrib/gis/geos/polygon.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos
2025-04-22 17:58:55,931 root INFO copying build/lib/django/contrib/gis/geos/error.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos
2025-04-22 17:58:55,931 root INFO copying build/lib/django/contrib/gis/geos/factory.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos
2025-04-22 17:58:55,932 root INFO copying build/lib/django/contrib/gis/geos/base.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos
2025-04-22 17:58:55,932 root INFO copying build/lib/django/contrib/gis/geos/coordseq.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/geos
2025-04-22 17:58:55,932 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/templates
2025-04-22 17:58:55,932 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/templates/gis
2025-04-22 17:58:55,933 root INFO copying build/lib/django/contrib/gis/templates/gis/openlayers.html -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/templates/gis
2025-04-22 17:58:55,933 root INFO copying build/lib/django/contrib/gis/templates/gis/openlayers-osm.html -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/templates/gis
2025-04-22 17:58:55,933 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/templates/gis/admin
2025-04-22 17:58:55,933 root INFO copying build/lib/django/contrib/gis/templates/gis/admin/osm.html -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/templates/gis/admin
2025-04-22 17:58:55,934 root INFO copying build/lib/django/contrib/gis/templates/gis/admin/openlayers.html -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/templates/gis/admin
2025-04-22 17:58:55,934 root INFO copying build/lib/django/contrib/gis/templates/gis/admin/openlayers.js -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/templates/gis/admin
2025-04-22 17:58:55,934 root INFO copying build/lib/django/contrib/gis/templates/gis/admin/osm.js -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/templates/gis/admin
2025-04-22 17:58:55,934 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/templates/gis/kml
2025-04-22 17:58:55,934 root INFO copying build/lib/django/contrib/gis/templates/gis/kml/placemarks.kml -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/templates/gis/kml
2025-04-22 17:58:55,935 root INFO copying build/lib/django/contrib/gis/templates/gis/kml/base.kml -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/templates/gis/kml
2025-04-22 17:58:55,935 root INFO copying build/lib/django/contrib/gis/shortcuts.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis
2025-04-22 17:58:55,935 root INFO copying build/lib/django/contrib/gis/measure.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis
2025-04-22 17:58:55,935 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/gdal
2025-04-22 17:58:55,935 root INFO copying build/lib/django/contrib/gis/gdal/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal
2025-04-22 17:58:55,936 root INFO copying build/lib/django/contrib/gis/gdal/geomtype.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal
2025-04-22 17:58:55,936 root INFO copying build/lib/django/contrib/gis/gdal/field.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal
2025-04-22 17:58:55,936 root INFO copying build/lib/django/contrib/gis/gdal/LICENSE -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal
2025-04-22 17:58:55,936 root INFO copying build/lib/django/contrib/gis/gdal/geometries.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal
2025-04-22 17:58:55,937 root INFO copying build/lib/django/contrib/gis/gdal/feature.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal
2025-04-22 17:58:55,937 root INFO copying build/lib/django/contrib/gis/gdal/envelope.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal
2025-04-22 17:58:55,937 root INFO copying build/lib/django/contrib/gis/gdal/libgdal.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal
2025-04-22 17:58:55,937 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/gdal/raster
2025-04-22 17:58:55,937 root INFO copying build/lib/django/contrib/gis/gdal/raster/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal/raster
2025-04-22 17:58:55,938 root INFO copying build/lib/django/contrib/gis/gdal/raster/source.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal/raster
2025-04-22 17:58:55,938 root INFO copying build/lib/django/contrib/gis/gdal/raster/band.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal/raster
2025-04-22 17:58:55,938 root INFO copying build/lib/django/contrib/gis/gdal/raster/base.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal/raster
2025-04-22 17:58:55,938 root INFO copying build/lib/django/contrib/gis/gdal/raster/const.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal/raster
2025-04-22 17:58:55,939 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/gdal/prototypes
2025-04-22 17:58:55,939 root INFO copying build/lib/django/contrib/gis/gdal/prototypes/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal/prototypes
2025-04-22 17:58:55,939 root INFO copying build/lib/django/contrib/gis/gdal/prototypes/generation.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal/prototypes
2025-04-22 17:58:55,939 root INFO copying build/lib/django/contrib/gis/gdal/prototypes/ds.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal/prototypes
2025-04-22 17:58:55,939 root INFO copying build/lib/django/contrib/gis/gdal/prototypes/raster.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal/prototypes
2025-04-22 17:58:55,940 root INFO copying build/lib/django/contrib/gis/gdal/prototypes/srs.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal/prototypes
2025-04-22 17:58:55,940 root INFO copying build/lib/django/contrib/gis/gdal/prototypes/errcheck.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal/prototypes
2025-04-22 17:58:55,940 root INFO copying build/lib/django/contrib/gis/gdal/prototypes/geom.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal/prototypes
2025-04-22 17:58:55,940 root INFO copying build/lib/django/contrib/gis/gdal/srs.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal
2025-04-22 17:58:55,940 root INFO copying build/lib/django/contrib/gis/gdal/error.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal
2025-04-22 17:58:55,941 root INFO copying build/lib/django/contrib/gis/gdal/datasource.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal
2025-04-22 17:58:55,941 root INFO copying build/lib/django/contrib/gis/gdal/driver.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal
2025-04-22 17:58:55,941 root INFO copying build/lib/django/contrib/gis/gdal/layer.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal
2025-04-22 17:58:55,941 root INFO copying build/lib/django/contrib/gis/gdal/base.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/gdal
2025-04-22 17:58:55,941 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/gis/forms
2025-04-22 17:58:55,942 root INFO copying build/lib/django/contrib/gis/forms/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/forms
2025-04-22 17:58:55,942 root INFO copying build/lib/django/contrib/gis/forms/widgets.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/forms
2025-04-22 17:58:55,942 root INFO copying build/lib/django/contrib/gis/forms/fields.py -> build/bdist.linux-armv8l/wheel/./django/contrib/gis/forms
2025-04-22 17:58:55,942 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin
2025-04-22 17:58:55,942 root INFO copying build/lib/django/contrib/admin/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin
2025-04-22 17:58:55,943 root INFO copying build/lib/django/contrib/admin/options.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin
2025-04-22 17:58:55,943 root INFO copying build/lib/django/contrib/admin/widgets.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin
2025-04-22 17:58:55,943 root INFO copying build/lib/django/contrib/admin/forms.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin
2025-04-22 17:58:55,944 root INFO copying build/lib/django/contrib/admin/decorators.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin
2025-04-22 17:58:55,944 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/views
2025-04-22 17:58:55,944 root INFO copying build/lib/django/contrib/admin/views/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/views
2025-04-22 17:58:55,944 root INFO copying build/lib/django/contrib/admin/views/decorators.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/views
2025-04-22 17:58:55,944 root INFO copying build/lib/django/contrib/admin/views/autocomplete.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/views
2025-04-22 17:58:55,945 root INFO copying build/lib/django/contrib/admin/views/main.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/views
2025-04-22 17:58:55,945 root INFO copying build/lib/django/contrib/admin/filters.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin
2025-04-22 17:58:55,945 root INFO copying build/lib/django/contrib/admin/exceptions.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin
2025-04-22 17:58:55,945 root INFO copying build/lib/django/contrib/admin/models.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin
2025-04-22 17:58:55,946 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/migrations
2025-04-22 17:58:55,946 root INFO copying build/lib/django/contrib/admin/migrations/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/migrations
2025-04-22 17:58:55,946 root INFO copying build/lib/django/contrib/admin/migrations/0002_logentry_remove_auto_add.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/migrations
2025-04-22 17:58:55,946 root INFO copying build/lib/django/contrib/admin/migrations/0001_initial.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/migrations
2025-04-22 17:58:55,946 root INFO copying build/lib/django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/migrations
2025-04-22 17:58:55,947 root INFO copying build/lib/django/contrib/admin/apps.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin
2025-04-22 17:58:55,947 root INFO copying build/lib/django/contrib/admin/utils.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin
2025-04-22 17:58:55,947 root INFO copying build/lib/django/contrib/admin/checks.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin
2025-04-22 17:58:55,947 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/static
2025-04-22 17:58:55,948 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/static/admin
2025-04-22 17:58:55,948 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/static/admin/css
2025-04-22 17:58:55,948 root INFO copying build/lib/django/contrib/admin/static/admin/css/changelists.css -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/css
2025-04-22 17:58:55,948 root INFO copying build/lib/django/contrib/admin/static/admin/css/autocomplete.css -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/css
2025-04-22 17:58:55,948 root INFO copying build/lib/django/contrib/admin/static/admin/css/dashboard.css -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/css
2025-04-22 17:58:55,949 root INFO copying build/lib/django/contrib/admin/static/admin/css/responsive.css -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/css
2025-04-22 17:58:55,949 root INFO copying build/lib/django/contrib/admin/static/admin/css/dark_mode.css -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/css
2025-04-22 17:58:55,949 root INFO copying build/lib/django/contrib/admin/static/admin/css/responsive_rtl.css -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/css
2025-04-22 17:58:55,949 root INFO copying build/lib/django/contrib/admin/static/admin/css/rtl.css -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/css
2025-04-22 17:58:55,949 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/static/admin/css/vendor
2025-04-22 17:58:55,950 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/static/admin/css/vendor/select2
2025-04-22 17:58:55,950 root INFO copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/css/vendor/select2
2025-04-22 17:58:55,950 root INFO copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/select2.min.css -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/css/vendor/select2
2025-04-22 17:58:55,950 root INFO copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/select2.css -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/css/vendor/select2
2025-04-22 17:58:55,951 root INFO copying build/lib/django/contrib/admin/static/admin/css/nav_sidebar.css -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/css
2025-04-22 17:58:55,951 root INFO copying build/lib/django/contrib/admin/static/admin/css/widgets.css -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/css
2025-04-22 17:58:55,951 root INFO copying build/lib/django/contrib/admin/static/admin/css/forms.css -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/css
2025-04-22 17:58:55,951 root INFO copying build/lib/django/contrib/admin/static/admin/css/base.css -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/css
2025-04-22 17:58:55,951 root INFO copying build/lib/django/contrib/admin/static/admin/css/login.css -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/css
2025-04-22 17:58:55,952 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/static/admin/img
2025-04-22 17:58:55,952 root INFO copying build/lib/django/contrib/admin/static/admin/img/search.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,952 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-clock.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,952 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-viewlink.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,952 root INFO copying build/lib/django/contrib/admin/static/admin/img/LICENSE -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,953 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-changelink.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,953 root INFO copying build/lib/django/contrib/admin/static/admin/img/inline-delete.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,953 root INFO copying build/lib/django/contrib/admin/static/admin/img/sorting-icons.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,953 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-no.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,953 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-yes.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,954 root INFO copying build/lib/django/contrib/admin/static/admin/img/tooltag-add.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,954 root INFO copying build/lib/django/contrib/admin/static/admin/img/selector-icons.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,954 root INFO copying build/lib/django/contrib/admin/static/admin/img/tooltag-arrowright.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,954 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/static/admin/img/gis
2025-04-22 17:58:55,954 root INFO copying build/lib/django/contrib/admin/static/admin/img/gis/move_vertex_on.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img/gis
2025-04-22 17:58:55,955 root INFO copying build/lib/django/contrib/admin/static/admin/img/gis/move_vertex_off.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img/gis
2025-04-22 17:58:55,955 root INFO copying build/lib/django/contrib/admin/static/admin/img/README.txt -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,955 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-unknown-alt.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,955 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-alert.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,955 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-addlink.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,956 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-unknown.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,956 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-calendar.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,956 root INFO copying build/lib/django/contrib/admin/static/admin/img/calendar-icons.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,956 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-deletelink.svg -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/img
2025-04-22 17:58:55,956 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/static/admin/js
2025-04-22 17:58:55,957 root INFO copying build/lib/django/contrib/admin/static/admin/js/urlify.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,957 root INFO copying build/lib/django/contrib/admin/static/admin/js/jquery.init.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,957 root INFO copying build/lib/django/contrib/admin/static/admin/js/filters.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,957 root INFO copying build/lib/django/contrib/admin/static/admin/js/SelectBox.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,958 root INFO copying build/lib/django/contrib/admin/static/admin/js/autocomplete.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,958 root INFO copying build/lib/django/contrib/admin/static/admin/js/SelectFilter2.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,958 root INFO copying build/lib/django/contrib/admin/static/admin/js/nav_sidebar.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,958 root INFO copying build/lib/django/contrib/admin/static/admin/js/inlines.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,958 root INFO copying build/lib/django/contrib/admin/static/admin/js/change_form.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,959 root INFO copying build/lib/django/contrib/admin/static/admin/js/core.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,959 root INFO copying build/lib/django/contrib/admin/static/admin/js/theme.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,959 root INFO copying build/lib/django/contrib/admin/static/admin/js/popup_response.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,959 root INFO copying build/lib/django/contrib/admin/static/admin/js/collapse.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,959 root INFO copying build/lib/django/contrib/admin/static/admin/js/prepopulate_init.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,960 root INFO copying build/lib/django/contrib/admin/static/admin/js/calendar.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,960 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/static/admin/js/admin
2025-04-22 17:58:55,960 root INFO copying build/lib/django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/admin
2025-04-22 17:58:55,960 root INFO copying build/lib/django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/admin
2025-04-22 17:58:55,961 root INFO copying build/lib/django/contrib/admin/static/admin/js/cancel.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,961 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/static/admin/js/vendor
2025-04-22 17:58:55,961 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/static/admin/js/vendor/xregexp
2025-04-22 17:58:55,961 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/xregexp
2025-04-22 17:58:55,962 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/xregexp
2025-04-22 17:58:55,962 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/xregexp
2025-04-22 17:58:55,963 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/static/admin/js/vendor/jquery
2025-04-22 17:58:55,963 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/jquery
2025-04-22 17:58:55,963 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/jquery.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/jquery
2025-04-22 17:58:55,964 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/jquery
2025-04-22 17:58:55,964 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/static/admin/js/vendor/select2
2025-04-22 17:58:55,964 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2
2025-04-22 17:58:55,965 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/select2.full.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2
2025-04-22 17:58:55,965 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2
2025-04-22 17:58:55,965 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,966 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,966 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,966 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,966 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,966 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,967 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,967 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,967 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,967 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,967 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,968 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,968 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,968 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,968 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,968 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,968 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,969 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,969 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,969 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,969 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,969 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,970 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,970 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,970 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,970 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,970 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,971 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,971 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,971 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,971 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,971 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,972 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,972 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,972 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,972 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,972 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,973 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,973 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,973 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,973 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,973 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,974 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,974 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,974 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,974 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,974 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,974 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,975 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,975 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,975 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,975 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,975 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,976 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,976 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,976 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,976 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,977 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,977 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,977 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 17:58:55,977 root INFO copying build/lib/django/contrib/admin/static/admin/js/prepopulate.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,977 root INFO copying build/lib/django/contrib/admin/static/admin/js/actions.js -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/static/admin/js
2025-04-22 17:58:55,978 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/templatetags
2025-04-22 17:58:55,978 root INFO copying build/lib/django/contrib/admin/templatetags/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templatetags
2025-04-22 17:58:55,978 root INFO copying build/lib/django/contrib/admin/templatetags/log.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templatetags
2025-04-22 17:58:55,978 root INFO copying build/lib/django/contrib/admin/templatetags/admin_urls.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templatetags
2025-04-22 17:58:55,979 root INFO copying build/lib/django/contrib/admin/templatetags/admin_modify.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templatetags
2025-04-22 17:58:55,979 root INFO copying build/lib/django/contrib/admin/templatetags/admin_list.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templatetags
2025-04-22 17:58:55,979 root INFO copying build/lib/django/contrib/admin/templatetags/base.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templatetags
2025-04-22 17:58:55,979 root INFO copying build/lib/django/contrib/admin/tests.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin
2025-04-22 17:58:55,980 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale
2025-04-22 17:58:55,980 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/lv
2025-04-22 17:58:55,980 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,980 root INFO copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,980 root INFO copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,981 root INFO copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,981 root INFO copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 17:58:55,981 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/sw
2025-04-22 17:58:55,981 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,982 root INFO copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,982 root INFO copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,982 root INFO copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,982 root INFO copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 17:58:55,982 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/en_AU
2025-04-22 17:58:55,983 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,983 root INFO copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,983 root INFO copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,983 root INFO copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,984 root INFO copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:55,984 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/mr
2025-04-22 17:58:55,984 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,984 root INFO copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,984 root INFO copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,985 root INFO copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,985 root INFO copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 17:58:55,985 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/lb
2025-04-22 17:58:55,985 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,985 root INFO copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,986 root INFO copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,986 root INFO copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,986 root INFO copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 17:58:55,986 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ca
2025-04-22 17:58:55,987 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,987 root INFO copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,987 root INFO copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,987 root INFO copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,987 root INFO copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 17:58:55,988 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/en_GB
2025-04-22 17:58:55,988 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,988 root INFO copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,988 root INFO copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,989 root INFO copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,989 root INFO copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:55,989 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/el
2025-04-22 17:58:55,989 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 17:58:55,989 root INFO copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 17:58:55,990 root INFO copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 17:58:55,990 root INFO copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 17:58:55,990 root INFO copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 17:58:55,990 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/es_VE
2025-04-22 17:58:55,991 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,991 root INFO copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,991 root INFO copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,991 root INFO copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,991 root INFO copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:55,992 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/af
2025-04-22 17:58:55,992 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 17:58:55,992 root INFO copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 17:58:55,992 root INFO copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 17:58:55,993 root INFO copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 17:58:55,993 root INFO copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 17:58:55,993 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/en
2025-04-22 17:58:55,993 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 17:58:55,993 root INFO copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 17:58:55,994 root INFO copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 17:58:55,994 root INFO copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 17:58:55,994 root INFO copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 17:58:55,994 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/dsb
2025-04-22 17:58:55,995 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,995 root INFO copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,995 root INFO copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,995 root INFO copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,995 root INFO copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 17:58:55,996 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/et
2025-04-22 17:58:55,996 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 17:58:55,996 root INFO copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 17:58:55,996 root INFO copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 17:58:55,997 root INFO copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 17:58:55,997 root INFO copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 17:58:55,997 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/nn
2025-04-22 17:58:55,997 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,997 root INFO copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,998 root INFO copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,998 root INFO copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,998 root INFO copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 17:58:55,998 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/cy
2025-04-22 17:58:55,999 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,999 root INFO copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,999 root INFO copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 17:58:55,999 root INFO copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 17:58:56,000 root INFO copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 17:58:56,000 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ko
2025-04-22 17:58:56,000 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 17:58:56,000 root INFO copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 17:58:56,000 root INFO copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 17:58:56,001 root INFO copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 17:58:56,001 root INFO copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 17:58:56,001 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/is
2025-04-22 17:58:56,001 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 17:58:56,002 root INFO copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 17:58:56,002 root INFO copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 17:58:56,002 root INFO copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 17:58:56,002 root INFO copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 17:58:56,002 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/pa
2025-04-22 17:58:56,003 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 17:58:56,003 root INFO copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 17:58:56,003 root INFO copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 17:58:56,003 root INFO copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 17:58:56,003 root INFO copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 17:58:56,004 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/tt
2025-04-22 17:58:56,004 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 17:58:56,004 root INFO copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 17:58:56,004 root INFO copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 17:58:56,005 root INFO copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 17:58:56,005 root INFO copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 17:58:56,005 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ne
2025-04-22 17:58:56,005 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 17:58:56,005 root INFO copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 17:58:56,006 root INFO copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 17:58:56,006 root INFO copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 17:58:56,006 root INFO copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 17:58:56,006 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/sr_Latn
2025-04-22 17:58:56,007 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:56,007 root INFO copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:56,007 root INFO copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:56,007 root INFO copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:56,007 root INFO copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:56,008 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/fy
2025-04-22 17:58:56,008 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 17:58:56,008 root INFO copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 17:58:56,008 root INFO copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 17:58:56,009 root INFO copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 17:58:56,009 root INFO copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 17:58:56,009 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/bg
2025-04-22 17:58:56,009 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 17:58:56,009 root INFO copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 17:58:56,010 root INFO copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 17:58:56,010 root INFO copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 17:58:56,010 root INFO copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 17:58:56,010 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ga
2025-04-22 17:58:56,011 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 17:58:56,011 root INFO copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 17:58:56,011 root INFO copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 17:58:56,011 root INFO copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 17:58:56,011 root INFO copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 17:58:56,012 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/gl
2025-04-22 17:58:56,012 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 17:58:56,012 root INFO copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 17:58:56,012 root INFO copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 17:58:56,012 root INFO copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 17:58:56,013 root INFO copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 17:58:56,013 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/uk
2025-04-22 17:58:56,013 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 17:58:56,013 root INFO copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 17:58:56,014 root INFO copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 17:58:56,014 root INFO copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 17:58:56,014 root INFO copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 17:58:56,014 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/uz
2025-04-22 17:58:56,015 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 17:58:56,015 root INFO copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 17:58:56,015 root INFO copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 17:58:56,015 root INFO copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 17:58:56,015 root INFO copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 17:58:56,016 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/kn
2025-04-22 17:58:56,016 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 17:58:56,016 root INFO copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 17:58:56,016 root INFO copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 17:58:56,016 root INFO copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 17:58:56,017 root INFO copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 17:58:56,017 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ja
2025-04-22 17:58:56,017 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 17:58:56,017 root INFO copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 17:58:56,018 root INFO copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 17:58:56,018 root INFO copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 17:58:56,018 root INFO copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 17:58:56,018 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/cs
2025-04-22 17:58:56,018 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 17:58:56,019 root INFO copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 17:58:56,019 root INFO copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 17:58:56,019 root INFO copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 17:58:56,019 root INFO copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 17:58:56,020 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/os
2025-04-22 17:58:56,020 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 17:58:56,020 root INFO copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 17:58:56,020 root INFO copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 17:58:56,020 root INFO copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 17:58:56,021 root INFO copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 17:58:56,021 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/tr
2025-04-22 17:58:56,021 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 17:58:56,021 root INFO copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 17:58:56,022 root INFO copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 17:58:56,022 root INFO copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 17:58:56,022 root INFO copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 17:58:56,022 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/io
2025-04-22 17:58:56,023 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 17:58:56,023 root INFO copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 17:58:56,023 root INFO copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 17:58:56,023 root INFO copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 17:58:56,023 root INFO copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 17:58:56,024 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/sl
2025-04-22 17:58:56,024 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 17:58:56,024 root INFO copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 17:58:56,024 root INFO copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 17:58:56,024 root INFO copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 17:58:56,025 root INFO copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 17:58:56,025 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/sq
2025-04-22 17:58:56,025 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 17:58:56,025 root INFO copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 17:58:56,025 root INFO copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 17:58:56,026 root INFO copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 17:58:56,026 root INFO copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 17:58:56,026 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/az
2025-04-22 17:58:56,027 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 17:58:56,027 root INFO copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 17:58:56,027 root INFO copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 17:58:56,027 root INFO copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 17:58:56,027 root INFO copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 17:58:56,028 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/eo
2025-04-22 17:58:56,028 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 17:58:56,028 root INFO copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 17:58:56,028 root INFO copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 17:58:56,028 root INFO copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 17:58:56,029 root INFO copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 17:58:56,029 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/pt_BR
2025-04-22 17:58:56,029 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:56,029 root INFO copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:56,030 root INFO copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:56,030 root INFO copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:56,030 root INFO copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:56,030 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/pl
2025-04-22 17:58:56,031 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 17:58:56,031 root INFO copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 17:58:56,031 root INFO copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 17:58:56,031 root INFO copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 17:58:56,031 root INFO copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 17:58:56,032 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/gd
2025-04-22 17:58:56,032 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 17:58:56,032 root INFO copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 17:58:56,032 root INFO copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 17:58:56,033 root INFO copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 17:58:56,033 root INFO copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 17:58:56,033 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/hr
2025-04-22 17:58:56,033 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 17:58:56,033 root INFO copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 17:58:56,034 root INFO copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 17:58:56,034 root INFO copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 17:58:56,034 root INFO copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 17:58:56,034 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ru
2025-04-22 17:58:56,035 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 17:58:56,035 root INFO copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 17:58:56,035 root INFO copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 17:58:56,035 root INFO copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 17:58:56,035 root INFO copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 17:58:56,036 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/es
2025-04-22 17:58:56,036 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 17:58:56,036 root INFO copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 17:58:56,036 root INFO copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 17:58:56,037 root INFO copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 17:58:56,037 root INFO copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 17:58:56,037 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/id
2025-04-22 17:58:56,037 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 17:58:56,037 root INFO copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 17:58:56,038 root INFO copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 17:58:56,038 root INFO copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 17:58:56,038 root INFO copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 17:58:56,038 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/fi
2025-04-22 17:58:56,039 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 17:58:56,039 root INFO copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 17:58:56,039 root INFO copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 17:58:56,039 root INFO copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 17:58:56,039 root INFO copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 17:58:56,040 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/mk
2025-04-22 17:58:56,040 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 17:58:56,040 root INFO copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 17:58:56,040 root INFO copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 17:58:56,040 root INFO copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 17:58:56,041 root INFO copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 17:58:56,041 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/hi
2025-04-22 17:58:56,041 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 17:58:56,041 root INFO copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 17:58:56,042 root INFO copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 17:58:56,042 root INFO copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 17:58:56,042 root INFO copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 17:58:56,042 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/kab
2025-04-22 17:58:56,043 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 17:58:56,043 root INFO copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 17:58:56,043 root INFO copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 17:58:56,043 root INFO copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 17:58:56,044 root INFO copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 17:58:56,044 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/hsb
2025-04-22 17:58:56,044 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 17:58:56,044 root INFO copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 17:58:56,044 root INFO copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 17:58:56,045 root INFO copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 17:58:56,045 root INFO copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 17:58:56,045 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/sk
2025-04-22 17:58:56,045 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 17:58:56,045 root INFO copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 17:58:56,046 root INFO copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 17:58:56,046 root INFO copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 17:58:56,046 root INFO copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 17:58:56,046 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/lt
2025-04-22 17:58:56,047 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 17:58:56,047 root INFO copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 17:58:56,047 root INFO copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 17:58:56,047 root INFO copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 17:58:56,047 root INFO copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 17:58:56,048 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/de
2025-04-22 17:58:56,048 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 17:58:56,048 root INFO copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 17:58:56,048 root INFO copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 17:58:56,048 root INFO copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 17:58:56,049 root INFO copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 17:58:56,049 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/it
2025-04-22 17:58:56,049 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 17:58:56,049 root INFO copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 17:58:56,050 root INFO copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 17:58:56,050 root INFO copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 17:58:56,050 root INFO copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 17:58:56,050 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/my
2025-04-22 17:58:56,051 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 17:58:56,051 root INFO copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 17:58:56,051 root INFO copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 17:58:56,051 root INFO copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 17:58:56,051 root INFO copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 17:58:56,052 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/sr
2025-04-22 17:58:56,052 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 17:58:56,052 root INFO copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 17:58:56,052 root INFO copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 17:58:56,052 root INFO copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 17:58:56,053 root INFO copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 17:58:56,053 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/bs
2025-04-22 17:58:56,053 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 17:58:56,053 root INFO copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 17:58:56,053 root INFO copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 17:58:56,054 root INFO copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 17:58:56,054 root INFO copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 17:58:56,054 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ro
2025-04-22 17:58:56,054 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 17:58:56,054 root INFO copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 17:58:56,055 root INFO copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 17:58:56,055 root INFO copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 17:58:56,055 root INFO copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 17:58:56,055 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ky
2025-04-22 17:58:56,056 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 17:58:56,056 root INFO copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 17:58:56,056 root INFO copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 17:58:56,056 root INFO copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 17:58:56,056 root INFO copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 17:58:56,057 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/fr
2025-04-22 17:58:56,057 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 17:58:56,057 root INFO copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 17:58:56,057 root INFO copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 17:58:56,058 root INFO copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 17:58:56,058 root INFO copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 17:58:56,058 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/am
2025-04-22 17:58:56,058 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/am/LC_MESSAGES
2025-04-22 17:58:56,059 root INFO copying build/lib/django/contrib/admin/locale/am/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/am/LC_MESSAGES
2025-04-22 17:58:56,059 root INFO copying build/lib/django/contrib/admin/locale/am/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/am/LC_MESSAGES
2025-04-22 17:58:56,059 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ar
2025-04-22 17:58:56,059 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 17:58:56,059 root INFO copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 17:58:56,060 root INFO copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 17:58:56,060 root INFO copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 17:58:56,060 root INFO copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 17:58:56,060 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/hy
2025-04-22 17:58:56,061 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 17:58:56,061 root INFO copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 17:58:56,061 root INFO copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 17:58:56,061 root INFO copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 17:58:56,062 root INFO copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 17:58:56,062 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/es_AR
2025-04-22 17:58:56,062 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:56,062 root INFO copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:56,063 root INFO copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:56,063 root INFO copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:56,063 root INFO copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:56,063 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/vi
2025-04-22 17:58:56,064 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 17:58:56,064 root INFO copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 17:58:56,064 root INFO copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 17:58:56,064 root INFO copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 17:58:56,065 root INFO copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 17:58:56,065 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ckb
2025-04-22 17:58:56,065 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 17:58:56,065 root INFO copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 17:58:56,066 root INFO copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 17:58:56,066 root INFO copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 17:58:56,066 root INFO copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 17:58:56,067 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/sv
2025-04-22 17:58:56,067 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 17:58:56,067 root INFO copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 17:58:56,067 root INFO copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 17:58:56,067 root INFO copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 17:58:56,068 root INFO copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 17:58:56,068 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/zh_Hant
2025-04-22 17:58:56,068 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:56,068 root INFO copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:56,069 root INFO copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:56,069 root INFO copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:56,069 root INFO copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:56,069 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/kk
2025-04-22 17:58:56,070 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 17:58:56,070 root INFO copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 17:58:56,070 root INFO copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 17:58:56,070 root INFO copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 17:58:56,070 root INFO copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 17:58:56,071 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/es_CO
2025-04-22 17:58:56,071 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:56,071 root INFO copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:56,071 root INFO copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:56,072 root INFO copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:56,072 root INFO copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:56,072 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/be
2025-04-22 17:58:56,072 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 17:58:56,072 root INFO copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 17:58:56,073 root INFO copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 17:58:56,073 root INFO copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 17:58:56,073 root INFO copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 17:58:56,073 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/udm
2025-04-22 17:58:56,074 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 17:58:56,074 root INFO copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 17:58:56,074 root INFO copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 17:58:56,074 root INFO copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 17:58:56,074 root INFO copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 17:58:56,075 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ml
2025-04-22 17:58:56,075 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 17:58:56,075 root INFO copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 17:58:56,075 root INFO copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 17:58:56,075 root INFO copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 17:58:56,076 root INFO copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 17:58:56,076 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ar_DZ
2025-04-22 17:58:56,076 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:56,076 root INFO copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:56,077 root INFO copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:56,077 root INFO copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:56,077 root INFO copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:56,077 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ms
2025-04-22 17:58:56,078 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 17:58:56,078 root INFO copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 17:58:56,078 root INFO copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 17:58:56,078 root INFO copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 17:58:56,078 root INFO copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 17:58:56,079 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ast
2025-04-22 17:58:56,079 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 17:58:56,079 root INFO copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 17:58:56,079 root INFO copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 17:58:56,080 root INFO copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 17:58:56,080 root INFO copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 17:58:56,080 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/zh_Hans
2025-04-22 17:58:56,080 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:56,080 root INFO copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:56,081 root INFO copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:56,081 root INFO copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:56,081 root INFO copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:56,081 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ur
2025-04-22 17:58:56,081 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 17:58:56,082 root INFO copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 17:58:56,082 root INFO copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 17:58:56,082 root INFO copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 17:58:56,082 root INFO copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 17:58:56,083 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ia
2025-04-22 17:58:56,083 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 17:58:56,083 root INFO copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 17:58:56,083 root INFO copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 17:58:56,083 root INFO copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 17:58:56,084 root INFO copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 17:58:56,084 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/hu
2025-04-22 17:58:56,084 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 17:58:56,084 root INFO copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 17:58:56,085 root INFO copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 17:58:56,085 root INFO copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 17:58:56,085 root INFO copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 17:58:56,085 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ta
2025-04-22 17:58:56,086 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 17:58:56,086 root INFO copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 17:58:56,086 root INFO copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 17:58:56,086 root INFO copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 17:58:56,086 root INFO copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 17:58:56,087 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/eu
2025-04-22 17:58:56,087 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 17:58:56,087 root INFO copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 17:58:56,087 root INFO copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 17:58:56,087 root INFO copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 17:58:56,088 root INFO copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 17:58:56,088 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/es_MX
2025-04-22 17:58:56,088 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:56,088 root INFO copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:56,088 root INFO copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:56,089 root INFO copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:56,089 root INFO copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:56,089 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/tk
2025-04-22 17:58:56,089 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/tk/LC_MESSAGES
2025-04-22 17:58:56,089 root INFO copying build/lib/django/contrib/admin/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/tk/LC_MESSAGES
2025-04-22 17:58:56,090 root INFO copying build/lib/django/contrib/admin/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/tk/LC_MESSAGES
2025-04-22 17:58:56,090 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/th
2025-04-22 17:58:56,090 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 17:58:56,090 root INFO copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 17:58:56,091 root INFO copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 17:58:56,091 root INFO copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 17:58:56,091 root INFO copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 17:58:56,091 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/nb
2025-04-22 17:58:56,091 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 17:58:56,092 root INFO copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 17:58:56,092 root INFO copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 17:58:56,092 root INFO copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 17:58:56,092 root INFO copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 17:58:56,093 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/mn
2025-04-22 17:58:56,093 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 17:58:56,093 root INFO copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 17:58:56,093 root INFO copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 17:58:56,093 root INFO copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 17:58:56,094 root INFO copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 17:58:56,094 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ka
2025-04-22 17:58:56,094 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 17:58:56,094 root INFO copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 17:58:56,094 root INFO copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 17:58:56,095 root INFO copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 17:58:56,095 root INFO copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 17:58:56,095 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/nl
2025-04-22 17:58:56,095 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 17:58:56,096 root INFO copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 17:58:56,096 root INFO copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 17:58:56,096 root INFO copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 17:58:56,096 root INFO copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 17:58:56,097 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/te
2025-04-22 17:58:56,097 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 17:58:56,097 root INFO copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 17:58:56,097 root INFO copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 17:58:56,098 root INFO copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 17:58:56,098 root INFO copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 17:58:56,098 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/pt
2025-04-22 17:58:56,098 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 17:58:56,098 root INFO copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 17:58:56,099 root INFO copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 17:58:56,099 root INFO copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 17:58:56,099 root INFO copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 17:58:56,099 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/bn
2025-04-22 17:58:56,100 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 17:58:56,100 root INFO copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 17:58:56,100 root INFO copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 17:58:56,100 root INFO copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 17:58:56,101 root INFO copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 17:58:56,101 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/he
2025-04-22 17:58:56,101 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 17:58:56,101 root INFO copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 17:58:56,101 root INFO copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 17:58:56,102 root INFO copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 17:58:56,102 root INFO copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 17:58:56,102 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/br
2025-04-22 17:58:56,102 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 17:58:56,103 root INFO copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 17:58:56,103 root INFO copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 17:58:56,103 root INFO copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 17:58:56,103 root INFO copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 17:58:56,104 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/fa
2025-04-22 17:58:56,104 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 17:58:56,104 root INFO copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 17:58:56,104 root INFO copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 17:58:56,104 root INFO copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 17:58:56,105 root INFO copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 17:58:56,105 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/tg
2025-04-22 17:58:56,105 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 17:58:56,105 root INFO copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 17:58:56,105 root INFO copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 17:58:56,106 root INFO copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 17:58:56,106 root INFO copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 17:58:56,106 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/km
2025-04-22 17:58:56,106 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 17:58:56,107 root INFO copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 17:58:56,107 root INFO copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 17:58:56,107 root INFO copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 17:58:56,107 root INFO copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 17:58:56,108 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/da
2025-04-22 17:58:56,108 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 17:58:56,108 root INFO copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 17:58:56,108 root INFO copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 17:58:56,108 root INFO copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 17:58:56,109 root INFO copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 17:58:56,109 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/templates
2025-04-22 17:58:56,109 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/templates/admin
2025-04-22 17:58:56,109 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/templates/admin/auth
2025-04-22 17:58:56,110 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/templates/admin/auth/user
2025-04-22 17:58:56,110 root INFO copying build/lib/django/contrib/admin/templates/admin/auth/user/add_form.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin/auth/user
2025-04-22 17:58:56,110 root INFO copying build/lib/django/contrib/admin/templates/admin/auth/user/change_password.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin/auth/user
2025-04-22 17:58:56,110 root INFO copying build/lib/django/contrib/admin/templates/admin/change_list_object_tools.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,110 root INFO copying build/lib/django/contrib/admin/templates/admin/change_form.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,111 root INFO copying build/lib/django/contrib/admin/templates/admin/change_list.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,111 root INFO copying build/lib/django/contrib/admin/templates/admin/login.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,111 root INFO copying build/lib/django/contrib/admin/templates/admin/index.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,111 root INFO copying build/lib/django/contrib/admin/templates/admin/prepopulated_fields_js.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,111 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/templates/admin/includes
2025-04-22 17:58:56,112 root INFO copying build/lib/django/contrib/admin/templates/admin/includes/fieldset.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin/includes
2025-04-22 17:58:56,112 root INFO copying build/lib/django/contrib/admin/templates/admin/includes/object_delete_summary.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin/includes
2025-04-22 17:58:56,112 root INFO copying build/lib/django/contrib/admin/templates/admin/500.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,112 root INFO copying build/lib/django/contrib/admin/templates/admin/filter.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,112 root INFO copying build/lib/django/contrib/admin/templates/admin/delete_selected_confirmation.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,113 root INFO copying build/lib/django/contrib/admin/templates/admin/base.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,113 root INFO copying build/lib/django/contrib/admin/templates/admin/nav_sidebar.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,113 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/templates/admin/edit_inline
2025-04-22 17:58:56,113 root INFO copying build/lib/django/contrib/admin/templates/admin/edit_inline/stacked.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin/edit_inline
2025-04-22 17:58:56,113 root INFO copying build/lib/django/contrib/admin/templates/admin/edit_inline/tabular.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin/edit_inline
2025-04-22 17:58:56,114 root INFO copying build/lib/django/contrib/admin/templates/admin/change_form_object_tools.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,114 root INFO copying build/lib/django/contrib/admin/templates/admin/search_form.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,114 root INFO copying build/lib/django/contrib/admin/templates/admin/popup_response.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,114 root INFO copying build/lib/django/contrib/admin/templates/admin/pagination.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,114 root INFO copying build/lib/django/contrib/admin/templates/admin/invalid_setup.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,115 root INFO copying build/lib/django/contrib/admin/templates/admin/404.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,115 root INFO copying build/lib/django/contrib/admin/templates/admin/date_hierarchy.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,115 root INFO copying build/lib/django/contrib/admin/templates/admin/color_theme_toggle.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,115 root INFO copying build/lib/django/contrib/admin/templates/admin/delete_confirmation.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,115 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:56,116 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/radio.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:56,116 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/time.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:56,116 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/url.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:56,116 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/split_datetime.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:56,116 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:56,117 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/clearable_file_input.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:56,117 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:56,117 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/date.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:56,117 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin/widgets
2025-04-22 17:58:56,117 root INFO copying build/lib/django/contrib/admin/templates/admin/base_site.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,118 root INFO copying build/lib/django/contrib/admin/templates/admin/app_index.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,118 root INFO copying build/lib/django/contrib/admin/templates/admin/change_list_results.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,118 root INFO copying build/lib/django/contrib/admin/templates/admin/object_history.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,118 root INFO copying build/lib/django/contrib/admin/templates/admin/actions.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,118 root INFO copying build/lib/django/contrib/admin/templates/admin/submit_line.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,118 root INFO copying build/lib/django/contrib/admin/templates/admin/app_list.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/admin
2025-04-22 17:58:56,119 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/admin/templates/registration
2025-04-22 17:58:56,119 root INFO copying build/lib/django/contrib/admin/templates/registration/password_change_done.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/registration
2025-04-22 17:58:56,119 root INFO copying build/lib/django/contrib/admin/templates/registration/password_reset_confirm.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/registration
2025-04-22 17:58:56,119 root INFO copying build/lib/django/contrib/admin/templates/registration/password_reset_complete.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/registration
2025-04-22 17:58:56,120 root INFO copying build/lib/django/contrib/admin/templates/registration/logged_out.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/registration
2025-04-22 17:58:56,120 root INFO copying build/lib/django/contrib/admin/templates/registration/password_reset_form.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/registration
2025-04-22 17:58:56,120 root INFO copying build/lib/django/contrib/admin/templates/registration/password_reset_done.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/registration
2025-04-22 17:58:56,120 root INFO copying build/lib/django/contrib/admin/templates/registration/password_change_form.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/registration
2025-04-22 17:58:56,120 root INFO copying build/lib/django/contrib/admin/templates/registration/password_reset_email.html -> build/bdist.linux-armv8l/wheel/./django/contrib/admin/templates/registration
2025-04-22 17:58:56,121 root INFO copying build/lib/django/contrib/admin/helpers.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin
2025-04-22 17:58:56,121 root INFO copying build/lib/django/contrib/admin/sites.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin
2025-04-22 17:58:56,121 root INFO copying build/lib/django/contrib/admin/actions.py -> build/bdist.linux-armv8l/wheel/./django/contrib/admin
2025-04-22 17:58:56,121 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize
2025-04-22 17:58:56,122 root INFO copying build/lib/django/contrib/humanize/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize
2025-04-22 17:58:56,122 root INFO copying build/lib/django/contrib/humanize/apps.py -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize
2025-04-22 17:58:56,122 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/templatetags
2025-04-22 17:58:56,122 root INFO copying build/lib/django/contrib/humanize/templatetags/__init__.py -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/templatetags
2025-04-22 17:58:56,122 root INFO copying build/lib/django/contrib/humanize/templatetags/humanize.py -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/templatetags
2025-04-22 17:58:56,123 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale
2025-04-22 17:58:56,123 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/lv
2025-04-22 17:58:56,123 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/lv/LC_MESSAGES
2025-04-22 17:58:56,123 root INFO copying build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/lv/LC_MESSAGES
2025-04-22 17:58:56,124 root INFO copying build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/lv/LC_MESSAGES
2025-04-22 17:58:56,124 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/sw
2025-04-22 17:58:56,124 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/sw/LC_MESSAGES
2025-04-22 17:58:56,124 root INFO copying build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/sw/LC_MESSAGES
2025-04-22 17:58:56,124 root INFO copying build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/sw/LC_MESSAGES
2025-04-22 17:58:56,125 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/en_AU
2025-04-22 17:58:56,125 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:56,125 root INFO copying build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:56,125 root INFO copying build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/en_AU/LC_MESSAGES
2025-04-22 17:58:56,126 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/mr
2025-04-22 17:58:56,126 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/mr/LC_MESSAGES
2025-04-22 17:58:56,126 root INFO copying build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/mr/LC_MESSAGES
2025-04-22 17:58:56,126 root INFO copying build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/mr/LC_MESSAGES
2025-04-22 17:58:56,127 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/lb
2025-04-22 17:58:56,127 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/lb/LC_MESSAGES
2025-04-22 17:58:56,127 root INFO copying build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/lb/LC_MESSAGES
2025-04-22 17:58:56,127 root INFO copying build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/lb/LC_MESSAGES
2025-04-22 17:58:56,127 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ca
2025-04-22 17:58:56,128 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ca/LC_MESSAGES
2025-04-22 17:58:56,128 root INFO copying build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ca/LC_MESSAGES
2025-04-22 17:58:56,128 root INFO copying build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ca/LC_MESSAGES
2025-04-22 17:58:56,128 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/en_GB
2025-04-22 17:58:56,129 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:56,129 root INFO copying build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:56,129 root INFO copying build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/en_GB/LC_MESSAGES
2025-04-22 17:58:56,129 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/el
2025-04-22 17:58:56,129 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/el/LC_MESSAGES
2025-04-22 17:58:56,130 root INFO copying build/lib/django/contrib/humanize/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/el/LC_MESSAGES
2025-04-22 17:58:56,130 root INFO copying build/lib/django/contrib/humanize/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/el/LC_MESSAGES
2025-04-22 17:58:56,130 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/es_VE
2025-04-22 17:58:56,130 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:56,130 root INFO copying build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:56,131 root INFO copying build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/es_VE/LC_MESSAGES
2025-04-22 17:58:56,131 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/af
2025-04-22 17:58:56,131 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/af/LC_MESSAGES
2025-04-22 17:58:56,131 root INFO copying build/lib/django/contrib/humanize/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/af/LC_MESSAGES
2025-04-22 17:58:56,131 root INFO copying build/lib/django/contrib/humanize/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/af/LC_MESSAGES
2025-04-22 17:58:56,132 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/en
2025-04-22 17:58:56,132 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/en/LC_MESSAGES
2025-04-22 17:58:56,132 root INFO copying build/lib/django/contrib/humanize/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/en/LC_MESSAGES
2025-04-22 17:58:56,132 root INFO copying build/lib/django/contrib/humanize/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/en/LC_MESSAGES
2025-04-22 17:58:56,133 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/dsb
2025-04-22 17:58:56,133 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/dsb/LC_MESSAGES
2025-04-22 17:58:56,133 root INFO copying build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/dsb/LC_MESSAGES
2025-04-22 17:58:56,133 root INFO copying build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/dsb/LC_MESSAGES
2025-04-22 17:58:56,134 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/et
2025-04-22 17:58:56,134 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/et/LC_MESSAGES
2025-04-22 17:58:56,134 root INFO copying build/lib/django/contrib/humanize/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/et/LC_MESSAGES
2025-04-22 17:58:56,134 root INFO copying build/lib/django/contrib/humanize/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/et/LC_MESSAGES
2025-04-22 17:58:56,134 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/nn
2025-04-22 17:58:56,135 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/nn/LC_MESSAGES
2025-04-22 17:58:56,135 root INFO copying build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/nn/LC_MESSAGES
2025-04-22 17:58:56,135 root INFO copying build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/nn/LC_MESSAGES
2025-04-22 17:58:56,135 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/cy
2025-04-22 17:58:56,135 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/cy/LC_MESSAGES
2025-04-22 17:58:56,136 root INFO copying build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/cy/LC_MESSAGES
2025-04-22 17:58:56,136 root INFO copying build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/cy/LC_MESSAGES
2025-04-22 17:58:56,136 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ko
2025-04-22 17:58:56,137 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ko/LC_MESSAGES
2025-04-22 17:58:56,137 root INFO copying build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ko/LC_MESSAGES
2025-04-22 17:58:56,137 root INFO copying build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ko/LC_MESSAGES
2025-04-22 17:58:56,137 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/is
2025-04-22 17:58:56,137 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/is/LC_MESSAGES
2025-04-22 17:58:56,138 root INFO copying build/lib/django/contrib/humanize/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/is/LC_MESSAGES
2025-04-22 17:58:56,138 root INFO copying build/lib/django/contrib/humanize/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/is/LC_MESSAGES
2025-04-22 17:58:56,138 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/pa
2025-04-22 17:58:56,138 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/pa/LC_MESSAGES
2025-04-22 17:58:56,138 root INFO copying build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/pa/LC_MESSAGES
2025-04-22 17:58:56,139 root INFO copying build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/pa/LC_MESSAGES
2025-04-22 17:58:56,139 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/tt
2025-04-22 17:58:56,139 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/tt/LC_MESSAGES
2025-04-22 17:58:56,139 root INFO copying build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/tt/LC_MESSAGES
2025-04-22 17:58:56,140 root INFO copying build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/tt/LC_MESSAGES
2025-04-22 17:58:56,140 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ne
2025-04-22 17:58:56,140 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ne/LC_MESSAGES
2025-04-22 17:58:56,140 root INFO copying build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ne/LC_MESSAGES
2025-04-22 17:58:56,140 root INFO copying build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ne/LC_MESSAGES
2025-04-22 17:58:56,141 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/sr_Latn
2025-04-22 17:58:56,141 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:56,141 root INFO copying build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:56,141 root INFO copying build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
2025-04-22 17:58:56,141 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/fy
2025-04-22 17:58:56,142 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/fy/LC_MESSAGES
2025-04-22 17:58:56,142 root INFO copying build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/fy/LC_MESSAGES
2025-04-22 17:58:56,142 root INFO copying build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/fy/LC_MESSAGES
2025-04-22 17:58:56,142 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/bg
2025-04-22 17:58:56,143 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/bg/LC_MESSAGES
2025-04-22 17:58:56,143 root INFO copying build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/bg/LC_MESSAGES
2025-04-22 17:58:56,143 root INFO copying build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/bg/LC_MESSAGES
2025-04-22 17:58:56,143 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ga
2025-04-22 17:58:56,143 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ga/LC_MESSAGES
2025-04-22 17:58:56,144 root INFO copying build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ga/LC_MESSAGES
2025-04-22 17:58:56,144 root INFO copying build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ga/LC_MESSAGES
2025-04-22 17:58:56,144 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/gl
2025-04-22 17:58:56,144 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/gl/LC_MESSAGES
2025-04-22 17:58:56,144 root INFO copying build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/gl/LC_MESSAGES
2025-04-22 17:58:56,145 root INFO copying build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/gl/LC_MESSAGES
2025-04-22 17:58:56,145 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/uk
2025-04-22 17:58:56,145 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/uk/LC_MESSAGES
2025-04-22 17:58:56,145 root INFO copying build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/uk/LC_MESSAGES
2025-04-22 17:58:56,145 root INFO copying build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/uk/LC_MESSAGES
2025-04-22 17:58:56,146 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/uz
2025-04-22 17:58:56,146 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/uz/LC_MESSAGES
2025-04-22 17:58:56,146 root INFO copying build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/uz/LC_MESSAGES
2025-04-22 17:58:56,146 root INFO copying build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/uz/LC_MESSAGES
2025-04-22 17:58:56,147 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/kn
2025-04-22 17:58:56,147 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/kn/LC_MESSAGES
2025-04-22 17:58:56,147 root INFO copying build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/kn/LC_MESSAGES
2025-04-22 17:58:56,147 root INFO copying build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/kn/LC_MESSAGES
2025-04-22 17:58:56,148 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ja
2025-04-22 17:58:56,148 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ja/LC_MESSAGES
2025-04-22 17:58:56,148 root INFO copying build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ja/LC_MESSAGES
2025-04-22 17:58:56,148 root INFO copying build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ja/LC_MESSAGES
2025-04-22 17:58:56,148 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/cs
2025-04-22 17:58:56,149 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/cs/LC_MESSAGES
2025-04-22 17:58:56,149 root INFO copying build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/cs/LC_MESSAGES
2025-04-22 17:58:56,149 root INFO copying build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/cs/LC_MESSAGES
2025-04-22 17:58:56,149 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/os
2025-04-22 17:58:56,149 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/os/LC_MESSAGES
2025-04-22 17:58:56,150 root INFO copying build/lib/django/contrib/humanize/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/os/LC_MESSAGES
2025-04-22 17:58:56,150 root INFO copying build/lib/django/contrib/humanize/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/os/LC_MESSAGES
2025-04-22 17:58:56,150 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/tr
2025-04-22 17:58:56,150 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/tr/LC_MESSAGES
2025-04-22 17:58:56,150 root INFO copying build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/tr/LC_MESSAGES
2025-04-22 17:58:56,151 root INFO copying build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/tr/LC_MESSAGES
2025-04-22 17:58:56,151 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/io
2025-04-22 17:58:56,151 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/io/LC_MESSAGES
2025-04-22 17:58:56,151 root INFO copying build/lib/django/contrib/humanize/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/io/LC_MESSAGES
2025-04-22 17:58:56,152 root INFO copying build/lib/django/contrib/humanize/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/io/LC_MESSAGES
2025-04-22 17:58:56,152 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/sl
2025-04-22 17:58:56,152 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/sl/LC_MESSAGES
2025-04-22 17:58:56,152 root INFO copying build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/sl/LC_MESSAGES
2025-04-22 17:58:56,152 root INFO copying build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/sl/LC_MESSAGES
2025-04-22 17:58:56,153 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/sq
2025-04-22 17:58:56,153 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/sq/LC_MESSAGES
2025-04-22 17:58:56,153 root INFO copying build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/sq/LC_MESSAGES
2025-04-22 17:58:56,153 root INFO copying build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/sq/LC_MESSAGES
2025-04-22 17:58:56,153 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/az
2025-04-22 17:58:56,154 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/az/LC_MESSAGES
2025-04-22 17:58:56,154 root INFO copying build/lib/django/contrib/humanize/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/az/LC_MESSAGES
2025-04-22 17:58:56,154 root INFO copying build/lib/django/contrib/humanize/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/az/LC_MESSAGES
2025-04-22 17:58:56,154 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/eo
2025-04-22 17:58:56,155 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/eo/LC_MESSAGES
2025-04-22 17:58:56,155 root INFO copying build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/eo/LC_MESSAGES
2025-04-22 17:58:56,155 root INFO copying build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/eo/LC_MESSAGES
2025-04-22 17:58:56,155 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/pt_BR
2025-04-22 17:58:56,155 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:56,156 root INFO copying build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:56,156 root INFO copying build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/pt_BR/LC_MESSAGES
2025-04-22 17:58:56,156 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/pl
2025-04-22 17:58:56,156 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/pl/LC_MESSAGES
2025-04-22 17:58:56,156 root INFO copying build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/pl/LC_MESSAGES
2025-04-22 17:58:56,157 root INFO copying build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/pl/LC_MESSAGES
2025-04-22 17:58:56,157 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/gd
2025-04-22 17:58:56,157 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/gd/LC_MESSAGES
2025-04-22 17:58:56,157 root INFO copying build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/gd/LC_MESSAGES
2025-04-22 17:58:56,157 root INFO copying build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/gd/LC_MESSAGES
2025-04-22 17:58:56,158 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/hr
2025-04-22 17:58:56,158 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/hr/LC_MESSAGES
2025-04-22 17:58:56,158 root INFO copying build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/hr/LC_MESSAGES
2025-04-22 17:58:56,158 root INFO copying build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/hr/LC_MESSAGES
2025-04-22 17:58:56,159 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ru
2025-04-22 17:58:56,159 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ru/LC_MESSAGES
2025-04-22 17:58:56,159 root INFO copying build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ru/LC_MESSAGES
2025-04-22 17:58:56,159 root INFO copying build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ru/LC_MESSAGES
2025-04-22 17:58:56,160 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/es
2025-04-22 17:58:56,160 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/es/LC_MESSAGES
2025-04-22 17:58:56,160 root INFO copying build/lib/django/contrib/humanize/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/es/LC_MESSAGES
2025-04-22 17:58:56,160 root INFO copying build/lib/django/contrib/humanize/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/es/LC_MESSAGES
2025-04-22 17:58:56,161 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/id
2025-04-22 17:58:56,161 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/id/LC_MESSAGES
2025-04-22 17:58:56,161 root INFO copying build/lib/django/contrib/humanize/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/id/LC_MESSAGES
2025-04-22 17:58:56,161 root INFO copying build/lib/django/contrib/humanize/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/id/LC_MESSAGES
2025-04-22 17:58:56,161 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/fi
2025-04-22 17:58:56,162 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/fi/LC_MESSAGES
2025-04-22 17:58:56,162 root INFO copying build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/fi/LC_MESSAGES
2025-04-22 17:58:56,162 root INFO copying build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/fi/LC_MESSAGES
2025-04-22 17:58:56,162 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/mk
2025-04-22 17:58:56,162 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/mk/LC_MESSAGES
2025-04-22 17:58:56,163 root INFO copying build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/mk/LC_MESSAGES
2025-04-22 17:58:56,163 root INFO copying build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/mk/LC_MESSAGES
2025-04-22 17:58:56,163 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/hi
2025-04-22 17:58:56,163 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/hi/LC_MESSAGES
2025-04-22 17:58:56,163 root INFO copying build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/hi/LC_MESSAGES
2025-04-22 17:58:56,164 root INFO copying build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/hi/LC_MESSAGES
2025-04-22 17:58:56,164 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/hsb
2025-04-22 17:58:56,164 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/hsb/LC_MESSAGES
2025-04-22 17:58:56,164 root INFO copying build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/hsb/LC_MESSAGES
2025-04-22 17:58:56,164 root INFO copying build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/hsb/LC_MESSAGES
2025-04-22 17:58:56,165 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/sk
2025-04-22 17:58:56,165 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/sk/LC_MESSAGES
2025-04-22 17:58:56,165 root INFO copying build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/sk/LC_MESSAGES
2025-04-22 17:58:56,165 root INFO copying build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/sk/LC_MESSAGES
2025-04-22 17:58:56,166 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/lt
2025-04-22 17:58:56,166 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/lt/LC_MESSAGES
2025-04-22 17:58:56,166 root INFO copying build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/lt/LC_MESSAGES
2025-04-22 17:58:56,166 root INFO copying build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/lt/LC_MESSAGES
2025-04-22 17:58:56,167 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/de
2025-04-22 17:58:56,167 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/de/LC_MESSAGES
2025-04-22 17:58:56,167 root INFO copying build/lib/django/contrib/humanize/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/de/LC_MESSAGES
2025-04-22 17:58:56,167 root INFO copying build/lib/django/contrib/humanize/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/de/LC_MESSAGES
2025-04-22 17:58:56,167 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/it
2025-04-22 17:58:56,168 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/it/LC_MESSAGES
2025-04-22 17:58:56,168 root INFO copying build/lib/django/contrib/humanize/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/it/LC_MESSAGES
2025-04-22 17:58:56,168 root INFO copying build/lib/django/contrib/humanize/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/it/LC_MESSAGES
2025-04-22 17:58:56,168 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/my
2025-04-22 17:58:56,168 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/my/LC_MESSAGES
2025-04-22 17:58:56,169 root INFO copying build/lib/django/contrib/humanize/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/my/LC_MESSAGES
2025-04-22 17:58:56,169 root INFO copying build/lib/django/contrib/humanize/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/my/LC_MESSAGES
2025-04-22 17:58:56,169 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/sr
2025-04-22 17:58:56,169 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/sr/LC_MESSAGES
2025-04-22 17:58:56,169 root INFO copying build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/sr/LC_MESSAGES
2025-04-22 17:58:56,170 root INFO copying build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/sr/LC_MESSAGES
2025-04-22 17:58:56,170 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/bs
2025-04-22 17:58:56,170 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/bs/LC_MESSAGES
2025-04-22 17:58:56,170 root INFO copying build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/bs/LC_MESSAGES
2025-04-22 17:58:56,171 root INFO copying build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/bs/LC_MESSAGES
2025-04-22 17:58:56,171 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ro
2025-04-22 17:58:56,171 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ro/LC_MESSAGES
2025-04-22 17:58:56,171 root INFO copying build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ro/LC_MESSAGES
2025-04-22 17:58:56,171 root INFO copying build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ro/LC_MESSAGES
2025-04-22 17:58:56,172 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ky
2025-04-22 17:58:56,172 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ky/LC_MESSAGES
2025-04-22 17:58:56,172 root INFO copying build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ky/LC_MESSAGES
2025-04-22 17:58:56,172 root INFO copying build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ky/LC_MESSAGES
2025-04-22 17:58:56,172 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/fr
2025-04-22 17:58:56,173 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/fr/LC_MESSAGES
2025-04-22 17:58:56,173 root INFO copying build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/fr/LC_MESSAGES
2025-04-22 17:58:56,173 root INFO copying build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/fr/LC_MESSAGES
2025-04-22 17:58:56,173 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ar
2025-04-22 17:58:56,174 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ar/LC_MESSAGES
2025-04-22 17:58:56,174 root INFO copying build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ar/LC_MESSAGES
2025-04-22 17:58:56,174 root INFO copying build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ar/LC_MESSAGES
2025-04-22 17:58:56,174 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/hy
2025-04-22 17:58:56,174 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/hy/LC_MESSAGES
2025-04-22 17:58:56,175 root INFO copying build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/hy/LC_MESSAGES
2025-04-22 17:58:56,175 root INFO copying build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/hy/LC_MESSAGES
2025-04-22 17:58:56,175 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/es_AR
2025-04-22 17:58:56,175 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:56,175 root INFO copying build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:56,176 root INFO copying build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/es_AR/LC_MESSAGES
2025-04-22 17:58:56,176 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/vi
2025-04-22 17:58:56,176 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/vi/LC_MESSAGES
2025-04-22 17:58:56,176 root INFO copying build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/vi/LC_MESSAGES
2025-04-22 17:58:56,176 root INFO copying build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/vi/LC_MESSAGES
2025-04-22 17:58:56,177 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ckb
2025-04-22 17:58:56,177 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ckb/LC_MESSAGES
2025-04-22 17:58:56,177 root INFO copying build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ckb/LC_MESSAGES
2025-04-22 17:58:56,177 root INFO copying build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ckb/LC_MESSAGES
2025-04-22 17:58:56,178 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/sv
2025-04-22 17:58:56,178 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/sv/LC_MESSAGES
2025-04-22 17:58:56,178 root INFO copying build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/sv/LC_MESSAGES
2025-04-22 17:58:56,178 root INFO copying build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/sv/LC_MESSAGES
2025-04-22 17:58:56,178 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/zh_Hant
2025-04-22 17:58:56,179 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:56,179 root INFO copying build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:56,179 root INFO copying build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
2025-04-22 17:58:56,179 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/kk
2025-04-22 17:58:56,180 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/kk/LC_MESSAGES
2025-04-22 17:58:56,180 root INFO copying build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/kk/LC_MESSAGES
2025-04-22 17:58:56,180 root INFO copying build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/kk/LC_MESSAGES
2025-04-22 17:58:56,180 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/es_CO
2025-04-22 17:58:56,180 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:56,181 root INFO copying build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:56,181 root INFO copying build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/es_CO/LC_MESSAGES
2025-04-22 17:58:56,181 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/be
2025-04-22 17:58:56,181 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/be/LC_MESSAGES
2025-04-22 17:58:56,181 root INFO copying build/lib/django/contrib/humanize/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/be/LC_MESSAGES
2025-04-22 17:58:56,182 root INFO copying build/lib/django/contrib/humanize/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/be/LC_MESSAGES
2025-04-22 17:58:56,182 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/udm
2025-04-22 17:58:56,182 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/udm/LC_MESSAGES
2025-04-22 17:58:56,182 root INFO copying build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/udm/LC_MESSAGES
2025-04-22 17:58:56,183 root INFO copying build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/udm/LC_MESSAGES
2025-04-22 17:58:56,183 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ml
2025-04-22 17:58:56,183 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ml/LC_MESSAGES
2025-04-22 17:58:56,183 root INFO copying build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ml/LC_MESSAGES
2025-04-22 17:58:56,183 root INFO copying build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ml/LC_MESSAGES
2025-04-22 17:58:56,184 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ar_DZ
2025-04-22 17:58:56,184 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:56,184 root INFO copying build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:56,184 root INFO copying build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
2025-04-22 17:58:56,185 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ms
2025-04-22 17:58:56,185 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ms/LC_MESSAGES
2025-04-22 17:58:56,185 root INFO copying build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ms/LC_MESSAGES
2025-04-22 17:58:56,185 root INFO copying build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ms/LC_MESSAGES
2025-04-22 17:58:56,185 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ast
2025-04-22 17:58:56,186 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ast/LC_MESSAGES
2025-04-22 17:58:56,186 root INFO copying build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ast/LC_MESSAGES
2025-04-22 17:58:56,186 root INFO copying build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ast/LC_MESSAGES
2025-04-22 17:58:56,186 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/zh_Hans
2025-04-22 17:58:56,187 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:56,187 root INFO copying build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:56,187 root INFO copying build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
2025-04-22 17:58:56,187 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ur
2025-04-22 17:58:56,187 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ur/LC_MESSAGES
2025-04-22 17:58:56,188 root INFO copying build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ur/LC_MESSAGES
2025-04-22 17:58:56,188 root INFO copying build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ur/LC_MESSAGES
2025-04-22 17:58:56,188 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ia
2025-04-22 17:58:56,188 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ia/LC_MESSAGES
2025-04-22 17:58:56,188 root INFO copying build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ia/LC_MESSAGES
2025-04-22 17:58:56,189 root INFO copying build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ia/LC_MESSAGES
2025-04-22 17:58:56,189 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/hu
2025-04-22 17:58:56,189 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/hu/LC_MESSAGES
2025-04-22 17:58:56,189 root INFO copying build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/hu/LC_MESSAGES
2025-04-22 17:58:56,189 root INFO copying build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/hu/LC_MESSAGES
2025-04-22 17:58:56,190 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ta
2025-04-22 17:58:56,190 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ta/LC_MESSAGES
2025-04-22 17:58:56,190 root INFO copying build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ta/LC_MESSAGES
2025-04-22 17:58:56,190 root INFO copying build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ta/LC_MESSAGES
2025-04-22 17:58:56,191 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/eu
2025-04-22 17:58:56,191 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/eu/LC_MESSAGES
2025-04-22 17:58:56,191 root INFO copying build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/eu/LC_MESSAGES
2025-04-22 17:58:56,191 root INFO copying build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/eu/LC_MESSAGES
2025-04-22 17:58:56,191 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/es_MX
2025-04-22 17:58:56,192 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:56,192 root INFO copying build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:56,192 root INFO copying build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/es_MX/LC_MESSAGES
2025-04-22 17:58:56,192 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/tk
2025-04-22 17:58:56,192 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/tk/LC_MESSAGES
2025-04-22 17:58:56,193 root INFO copying build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/tk/LC_MESSAGES
2025-04-22 17:58:56,193 root INFO copying build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/tk/LC_MESSAGES
2025-04-22 17:58:56,193 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/th
2025-04-22 17:58:56,193 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/th/LC_MESSAGES
2025-04-22 17:58:56,194 root INFO copying build/lib/django/contrib/humanize/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/th/LC_MESSAGES
2025-04-22 17:58:56,194 root INFO copying build/lib/django/contrib/humanize/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/th/LC_MESSAGES
2025-04-22 17:58:56,194 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/nb
2025-04-22 17:58:56,194 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/nb/LC_MESSAGES
2025-04-22 17:58:56,194 root INFO copying build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/nb/LC_MESSAGES
2025-04-22 17:58:56,195 root INFO copying build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/nb/LC_MESSAGES
2025-04-22 17:58:56,195 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/mn
2025-04-22 17:58:56,195 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/mn/LC_MESSAGES
2025-04-22 17:58:56,195 root INFO copying build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/mn/LC_MESSAGES
2025-04-22 17:58:56,195 root INFO copying build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/mn/LC_MESSAGES
2025-04-22 17:58:56,196 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ka
2025-04-22 17:58:56,196 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/ka/LC_MESSAGES
2025-04-22 17:58:56,196 root INFO copying build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ka/LC_MESSAGES
2025-04-22 17:58:56,196 root INFO copying build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/ka/LC_MESSAGES
2025-04-22 17:58:56,197 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/nl
2025-04-22 17:58:56,197 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/nl/LC_MESSAGES
2025-04-22 17:58:56,197 root INFO copying build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/nl/LC_MESSAGES
2025-04-22 17:58:56,197 root INFO copying build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/nl/LC_MESSAGES
2025-04-22 17:58:56,197 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/te
2025-04-22 17:58:56,198 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/te/LC_MESSAGES
2025-04-22 17:58:56,198 root INFO copying build/lib/django/contrib/humanize/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/te/LC_MESSAGES
2025-04-22 17:58:56,198 root INFO copying build/lib/django/contrib/humanize/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/te/LC_MESSAGES
2025-04-22 17:58:56,198 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/pt
2025-04-22 17:58:56,198 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/pt/LC_MESSAGES
2025-04-22 17:58:56,199 root INFO copying build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/pt/LC_MESSAGES
2025-04-22 17:58:56,199 root INFO copying build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/pt/LC_MESSAGES
2025-04-22 17:58:56,199 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/bn
2025-04-22 17:58:56,199 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/bn/LC_MESSAGES
2025-04-22 17:58:56,199 root INFO copying build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/bn/LC_MESSAGES
2025-04-22 17:58:56,200 root INFO copying build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/bn/LC_MESSAGES
2025-04-22 17:58:56,200 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/he
2025-04-22 17:58:56,200 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/he/LC_MESSAGES
2025-04-22 17:58:56,200 root INFO copying build/lib/django/contrib/humanize/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/he/LC_MESSAGES
2025-04-22 17:58:56,201 root INFO copying build/lib/django/contrib/humanize/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/he/LC_MESSAGES
2025-04-22 17:58:56,201 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/br
2025-04-22 17:58:56,201 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/br/LC_MESSAGES
2025-04-22 17:58:56,201 root INFO copying build/lib/django/contrib/humanize/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/br/LC_MESSAGES
2025-04-22 17:58:56,201 root INFO copying build/lib/django/contrib/humanize/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/br/LC_MESSAGES
2025-04-22 17:58:56,202 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/fa
2025-04-22 17:58:56,202 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/fa/LC_MESSAGES
2025-04-22 17:58:56,202 root INFO copying build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/fa/LC_MESSAGES
2025-04-22 17:58:56,202 root INFO copying build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/fa/LC_MESSAGES
2025-04-22 17:58:56,203 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/tg
2025-04-22 17:58:56,203 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/tg/LC_MESSAGES
2025-04-22 17:58:56,203 root INFO copying build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/tg/LC_MESSAGES
2025-04-22 17:58:56,203 root INFO copying build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/tg/LC_MESSAGES
2025-04-22 17:58:56,203 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/km
2025-04-22 17:58:56,204 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/km/LC_MESSAGES
2025-04-22 17:58:56,204 root INFO copying build/lib/django/contrib/humanize/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/km/LC_MESSAGES
2025-04-22 17:58:56,204 root INFO copying build/lib/django/contrib/humanize/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/km/LC_MESSAGES
2025-04-22 17:58:56,204 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/da
2025-04-22 17:58:56,204 root INFO creating build/bdist.linux-armv8l/wheel/django/contrib/humanize/locale/da/LC_MESSAGES
2025-04-22 17:58:56,205 root INFO copying build/lib/django/contrib/humanize/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/da/LC_MESSAGES
2025-04-22 17:58:56,205 root INFO copying build/lib/django/contrib/humanize/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-armv8l/wheel/./django/contrib/humanize/locale/da/LC_MESSAGES
2025-04-22 17:58:56,205 root INFO creating build/bdist.linux-armv8l/wheel/django/forms
2025-04-22 17:58:56,206 root INFO copying build/lib/django/forms/__init__.py -> build/bdist.linux-armv8l/wheel/./django/forms
2025-04-22 17:58:56,206 root INFO copying build/lib/django/forms/widgets.py -> build/bdist.linux-armv8l/wheel/./django/forms
2025-04-22 17:58:56,206 root INFO copying build/lib/django/forms/forms.py -> build/bdist.linux-armv8l/wheel/./django/forms
2025-04-22 17:58:56,207 root INFO creating build/bdist.linux-armv8l/wheel/django/forms/jinja2
2025-04-22 17:58:56,207 root INFO creating build/bdist.linux-armv8l/wheel/django/forms/jinja2/django
2025-04-22 17:58:56,207 root INFO creating build/bdist.linux-armv8l/wheel/django/forms/jinja2/django/forms
2025-04-22 17:58:56,207 root INFO copying build/lib/django/forms/jinja2/django/forms/table.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms
2025-04-22 17:58:56,207 root INFO copying build/lib/django/forms/jinja2/django/forms/label.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms
2025-04-22 17:58:56,208 root INFO copying build/lib/django/forms/jinja2/django/forms/default.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms
2025-04-22 17:58:56,208 root INFO creating build/bdist.linux-armv8l/wheel/django/forms/jinja2/django/forms/errors
2025-04-22 17:58:56,208 root INFO creating build/bdist.linux-armv8l/wheel/django/forms/jinja2/django/forms/errors/dict
2025-04-22 17:58:56,208 root INFO copying build/lib/django/forms/jinja2/django/forms/errors/dict/default.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/errors/dict
2025-04-22 17:58:56,208 root INFO copying build/lib/django/forms/jinja2/django/forms/errors/dict/text.txt -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/errors/dict
2025-04-22 17:58:56,209 root INFO copying build/lib/django/forms/jinja2/django/forms/errors/dict/ul.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/errors/dict
2025-04-22 17:58:56,209 root INFO creating build/bdist.linux-armv8l/wheel/django/forms/jinja2/django/forms/errors/list
2025-04-22 17:58:56,209 root INFO copying build/lib/django/forms/jinja2/django/forms/errors/list/default.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/errors/list
2025-04-22 17:58:56,209 root INFO copying build/lib/django/forms/jinja2/django/forms/errors/list/text.txt -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/errors/list
2025-04-22 17:58:56,209 root INFO copying build/lib/django/forms/jinja2/django/forms/errors/list/ul.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/errors/list
2025-04-22 17:58:56,210 root INFO creating build/bdist.linux-armv8l/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,210 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/radio.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,210 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/multiwidget.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,210 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/radio_option.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,210 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/input.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,211 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/time.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,211 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/email.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,211 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/splitdatetime.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,211 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/password.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,211 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/url.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,211 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/multiple_input.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,212 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/select_date.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,212 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/select_option.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,212 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,212 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/select.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,212 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/multiple_hidden.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,212 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/hidden.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,213 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/clearable_file_input.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,213 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/file.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,213 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/datetime.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,213 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/date.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,213 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/textarea.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,214 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/number.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,214 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/text.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,214 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/input_option.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,214 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/splithiddendatetime.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,214 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/attrs.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,214 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox_select.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,215 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox_option.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/widgets
2025-04-22 17:58:56,215 root INFO copying build/lib/django/forms/jinja2/django/forms/div.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms
2025-04-22 17:58:56,215 root INFO copying build/lib/django/forms/jinja2/django/forms/p.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms
2025-04-22 17:58:56,215 root INFO creating build/bdist.linux-armv8l/wheel/django/forms/jinja2/django/forms/formsets
2025-04-22 17:58:56,216 root INFO copying build/lib/django/forms/jinja2/django/forms/formsets/table.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/formsets
2025-04-22 17:58:56,216 root INFO copying build/lib/django/forms/jinja2/django/forms/formsets/default.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/formsets
2025-04-22 17:58:56,216 root INFO copying build/lib/django/forms/jinja2/django/forms/formsets/div.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/formsets
2025-04-22 17:58:56,216 root INFO copying build/lib/django/forms/jinja2/django/forms/formsets/p.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/formsets
2025-04-22 17:58:56,216 root INFO copying build/lib/django/forms/jinja2/django/forms/formsets/ul.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms/formsets
2025-04-22 17:58:56,216 root INFO copying build/lib/django/forms/jinja2/django/forms/attrs.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms
2025-04-22 17:58:56,217 root INFO copying build/lib/django/forms/jinja2/django/forms/ul.html -> build/bdist.linux-armv8l/wheel/./django/forms/jinja2/django/forms
2025-04-22 17:58:56,217 root INFO copying build/lib/django/forms/models.py -> build/bdist.linux-armv8l/wheel/./django/forms
2025-04-22 17:58:56,217 root INFO copying build/lib/django/forms/utils.py -> build/bdist.linux-armv8l/wheel/./django/forms
2025-04-22 17:58:56,217 root INFO copying build/lib/django/forms/renderers.py -> build/bdist.linux-armv8l/wheel/./django/forms
2025-04-22 17:58:56,218 root INFO copying build/lib/django/forms/fields.py -> build/bdist.linux-armv8l/wheel/./django/forms
2025-04-22 17:58:56,218 root INFO creating build/bdist.linux-armv8l/wheel/django/forms/templates
2025-04-22 17:58:56,218 root INFO creating build/bdist.linux-armv8l/wheel/django/forms/templates/django
2025-04-22 17:58:56,218 root INFO creating build/bdist.linux-armv8l/wheel/django/forms/templates/django/forms
2025-04-22 17:58:56,219 root INFO copying build/lib/django/forms/templates/django/forms/table.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms
2025-04-22 17:58:56,219 root INFO copying build/lib/django/forms/templates/django/forms/label.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms
2025-04-22 17:58:56,219 root INFO copying build/lib/django/forms/templates/django/forms/default.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms
2025-04-22 17:58:56,219 root INFO creating build/bdist.linux-armv8l/wheel/django/forms/templates/django/forms/errors
2025-04-22 17:58:56,220 root INFO creating build/bdist.linux-armv8l/wheel/django/forms/templates/django/forms/errors/dict
2025-04-22 17:58:56,220 root INFO copying build/lib/django/forms/templates/django/forms/errors/dict/default.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/errors/dict
2025-04-22 17:58:56,220 root INFO copying build/lib/django/forms/templates/django/forms/errors/dict/text.txt -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/errors/dict
2025-04-22 17:58:56,220 root INFO copying build/lib/django/forms/templates/django/forms/errors/dict/ul.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/errors/dict
2025-04-22 17:58:56,220 root INFO creating build/bdist.linux-armv8l/wheel/django/forms/templates/django/forms/errors/list
2025-04-22 17:58:56,221 root INFO copying build/lib/django/forms/templates/django/forms/errors/list/default.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/errors/list
2025-04-22 17:58:56,221 root INFO copying build/lib/django/forms/templates/django/forms/errors/list/text.txt -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/errors/list
2025-04-22 17:58:56,221 root INFO copying build/lib/django/forms/templates/django/forms/errors/list/ul.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/errors/list
2025-04-22 17:58:56,221 root INFO creating build/bdist.linux-armv8l/wheel/django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,221 root INFO copying build/lib/django/forms/templates/django/forms/widgets/radio.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,222 root INFO copying build/lib/django/forms/templates/django/forms/widgets/multiwidget.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,222 root INFO copying build/lib/django/forms/templates/django/forms/widgets/radio_option.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,222 root INFO copying build/lib/django/forms/templates/django/forms/widgets/input.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,222 root INFO copying build/lib/django/forms/templates/django/forms/widgets/time.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,222 root INFO copying build/lib/django/forms/templates/django/forms/widgets/email.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,222 root INFO copying build/lib/django/forms/templates/django/forms/widgets/splitdatetime.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,223 root INFO copying build/lib/django/forms/templates/django/forms/widgets/password.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,223 root INFO copying build/lib/django/forms/templates/django/forms/widgets/url.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,223 root INFO copying build/lib/django/forms/templates/django/forms/widgets/multiple_input.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,223 root INFO copying build/lib/django/forms/templates/django/forms/widgets/select_date.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,223 root INFO copying build/lib/django/forms/templates/django/forms/widgets/select_option.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,224 root INFO copying build/lib/django/forms/templates/django/forms/widgets/checkbox.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,224 root INFO copying build/lib/django/forms/templates/django/forms/widgets/select.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,224 root INFO copying build/lib/django/forms/templates/django/forms/widgets/multiple_hidden.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,224 root INFO copying build/lib/django/forms/templates/django/forms/widgets/hidden.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,224 root INFO copying build/lib/django/forms/templates/django/forms/widgets/clearable_file_input.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,225 root INFO copying build/lib/django/forms/templates/django/forms/widgets/file.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,225 root INFO copying build/lib/django/forms/templates/django/forms/widgets/datetime.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,225 root INFO copying build/lib/django/forms/templates/django/forms/widgets/date.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,225 root INFO copying build/lib/django/forms/templates/django/forms/widgets/textarea.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,225 root INFO copying build/lib/django/forms/templates/django/forms/widgets/number.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,225 root INFO copying build/lib/django/forms/templates/django/forms/widgets/text.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,226 root INFO copying build/lib/django/forms/templates/django/forms/widgets/input_option.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,226 root INFO copying build/lib/django/forms/templates/django/forms/widgets/splithiddendatetime.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,226 root INFO copying build/lib/django/forms/templates/django/forms/widgets/attrs.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,226 root INFO copying build/lib/django/forms/templates/django/forms/widgets/checkbox_select.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,226 root INFO copying build/lib/django/forms/templates/django/forms/widgets/checkbox_option.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/widgets
2025-04-22 17:58:56,227 root INFO copying build/lib/django/forms/templates/django/forms/div.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms
2025-04-22 17:58:56,227 root INFO copying build/lib/django/forms/templates/django/forms/p.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms
2025-04-22 17:58:56,227 root INFO creating build/bdist.linux-armv8l/wheel/django/forms/templates/django/forms/formsets
2025-04-22 17:58:56,227 root INFO copying build/lib/django/forms/templates/django/forms/formsets/table.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/formsets
2025-04-22 17:58:56,227 root INFO copying build/lib/django/forms/templates/django/forms/formsets/default.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/formsets
2025-04-22 17:58:56,228 root INFO copying build/lib/django/forms/templates/django/forms/formsets/div.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/formsets
2025-04-22 17:58:56,228 root INFO copying build/lib/django/forms/templates/django/forms/formsets/p.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/formsets
2025-04-22 17:58:56,228 root INFO copying build/lib/django/forms/templates/django/forms/formsets/ul.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms/formsets
2025-04-22 17:58:56,228 root INFO copying build/lib/django/forms/templates/django/forms/attrs.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms
2025-04-22 17:58:56,228 root INFO copying build/lib/django/forms/templates/django/forms/ul.html -> build/bdist.linux-armv8l/wheel/./django/forms/templates/django/forms
2025-04-22 17:58:56,229 root INFO copying build/lib/django/forms/boundfield.py -> build/bdist.linux-armv8l/wheel/./django/forms
2025-04-22 17:58:56,229 root INFO copying build/lib/django/forms/formsets.py -> build/bdist.linux-armv8l/wheel/./django/forms
2025-04-22 17:58:56,229 root INFO creating build/bdist.linux-armv8l/wheel/django/apps
2025-04-22 17:58:56,229 root INFO copying build/lib/django/apps/__init__.py -> build/bdist.linux-armv8l/wheel/./django/apps
2025-04-22 17:58:56,230 root INFO copying build/lib/django/apps/registry.py -> build/bdist.linux-armv8l/wheel/./django/apps
2025-04-22 17:58:56,230 root INFO copying build/lib/django/apps/config.py -> build/bdist.linux-armv8l/wheel/./django/apps
2025-04-22 17:58:56,231 root INFO running install_egg_info
2025-04-22 17:58:56,235 root INFO Copying Django.egg-info to build/bdist.linux-armv8l/wheel/./Django-4.2.20-py3.12.egg-info
2025-04-22 17:58:56,236 root INFO running install_scripts
2025-04-22 17:58:56,238 root INFO creating build/bdist.linux-armv8l/wheel/django-4.2.20.dist-info/WHEEL
2025-04-22 17:58:56,239 wheel INFO creating '/home/buildozer/aports/community/py3-django/src/Django-4.2.20/.dist/.tmp-ejsvlfkv/django-4.2.20-py3-none-any.whl' and adding 'build/bdist.linux-armv8l/wheel' to it
2025-04-22 17:58:56,239 wheel INFO adding 'django/__init__.py'
2025-04-22 17:58:56,240 wheel INFO adding 'django/__main__.py'
2025-04-22 17:58:56,240 wheel INFO adding 'django/shortcuts.py'
2025-04-22 17:58:56,240 wheel INFO adding 'django/apps/__init__.py'
2025-04-22 17:58:56,240 wheel INFO adding 'django/apps/config.py'
2025-04-22 17:58:56,241 wheel INFO adding 'django/apps/registry.py'
2025-04-22 17:58:56,241 wheel INFO adding 'django/conf/__init__.py'
2025-04-22 17:58:56,241 wheel INFO adding 'django/conf/global_settings.py'
2025-04-22 17:58:56,242 wheel INFO adding 'django/conf/app_template/__init__.py-tpl'
2025-04-22 17:58:56,242 wheel INFO adding 'django/conf/app_template/admin.py-tpl'
2025-04-22 17:58:56,242 wheel INFO adding 'django/conf/app_template/apps.py-tpl'
2025-04-22 17:58:56,242 wheel INFO adding 'django/conf/app_template/models.py-tpl'
2025-04-22 17:58:56,242 wheel INFO adding 'django/conf/app_template/tests.py-tpl'
2025-04-22 17:58:56,243 wheel INFO adding 'django/conf/app_template/views.py-tpl'
2025-04-22 17:58:56,243 wheel INFO adding 'django/conf/app_template/migrations/__init__.py-tpl'
2025-04-22 17:58:56,243 wheel INFO adding 'django/conf/locale/__init__.py'
2025-04-22 17:58:56,244 wheel INFO adding 'django/conf/locale/af/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,245 wheel INFO adding 'django/conf/locale/af/LC_MESSAGES/django.po'
2025-04-22 17:58:56,245 wheel INFO adding 'django/conf/locale/ar/__init__.py'
2025-04-22 17:58:56,245 wheel INFO adding 'django/conf/locale/ar/formats.py'
2025-04-22 17:58:56,245 wheel INFO adding 'django/conf/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,246 wheel INFO adding 'django/conf/locale/ar/LC_MESSAGES/django.po'
2025-04-22 17:58:56,246 wheel INFO adding 'django/conf/locale/ar_DZ/__init__.py'
2025-04-22 17:58:56,246 wheel INFO adding 'django/conf/locale/ar_DZ/formats.py'
2025-04-22 17:58:56,247 wheel INFO adding 'django/conf/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,247 wheel INFO adding 'django/conf/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 17:58:56,248 wheel INFO adding 'django/conf/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,248 wheel INFO adding 'django/conf/locale/ast/LC_MESSAGES/django.po'
2025-04-22 17:58:56,248 wheel INFO adding 'django/conf/locale/az/__init__.py'
2025-04-22 17:58:56,248 wheel INFO adding 'django/conf/locale/az/formats.py'
2025-04-22 17:58:56,249 wheel INFO adding 'django/conf/locale/az/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,249 wheel INFO adding 'django/conf/locale/az/LC_MESSAGES/django.po'
2025-04-22 17:58:56,249 wheel INFO adding 'django/conf/locale/be/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,250 wheel INFO adding 'django/conf/locale/be/LC_MESSAGES/django.po'
2025-04-22 17:58:56,250 wheel INFO adding 'django/conf/locale/bg/__init__.py'
2025-04-22 17:58:56,250 wheel INFO adding 'django/conf/locale/bg/formats.py'
2025-04-22 17:58:56,251 wheel INFO adding 'django/conf/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,251 wheel INFO adding 'django/conf/locale/bg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,251 wheel INFO adding 'django/conf/locale/bn/__init__.py'
2025-04-22 17:58:56,251 wheel INFO adding 'django/conf/locale/bn/formats.py'
2025-04-22 17:58:56,252 wheel INFO adding 'django/conf/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,252 wheel INFO adding 'django/conf/locale/bn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,252 wheel INFO adding 'django/conf/locale/br/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,253 wheel INFO adding 'django/conf/locale/br/LC_MESSAGES/django.po'
2025-04-22 17:58:56,253 wheel INFO adding 'django/conf/locale/bs/__init__.py'
2025-04-22 17:58:56,253 wheel INFO adding 'django/conf/locale/bs/formats.py'
2025-04-22 17:58:56,253 wheel INFO adding 'django/conf/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,254 wheel INFO adding 'django/conf/locale/bs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,254 wheel INFO adding 'django/conf/locale/ca/__init__.py'
2025-04-22 17:58:56,254 wheel INFO adding 'django/conf/locale/ca/formats.py'
2025-04-22 17:58:56,254 wheel INFO adding 'django/conf/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,255 wheel INFO adding 'django/conf/locale/ca/LC_MESSAGES/django.po'
2025-04-22 17:58:56,255 wheel INFO adding 'django/conf/locale/ckb/__init__.py'
2025-04-22 17:58:56,255 wheel INFO adding 'django/conf/locale/ckb/formats.py'
2025-04-22 17:58:56,255 wheel INFO adding 'django/conf/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,256 wheel INFO adding 'django/conf/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,256 wheel INFO adding 'django/conf/locale/cs/__init__.py'
2025-04-22 17:58:56,256 wheel INFO adding 'django/conf/locale/cs/formats.py'
2025-04-22 17:58:56,257 wheel INFO adding 'django/conf/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,257 wheel INFO adding 'django/conf/locale/cs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,257 wheel INFO adding 'django/conf/locale/cy/__init__.py'
2025-04-22 17:58:56,257 wheel INFO adding 'django/conf/locale/cy/formats.py'
2025-04-22 17:58:56,257 wheel INFO adding 'django/conf/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,258 wheel INFO adding 'django/conf/locale/cy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,258 wheel INFO adding 'django/conf/locale/da/__init__.py'
2025-04-22 17:58:56,258 wheel INFO adding 'django/conf/locale/da/formats.py'
2025-04-22 17:58:56,258 wheel INFO adding 'django/conf/locale/da/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,259 wheel INFO adding 'django/conf/locale/da/LC_MESSAGES/django.po'
2025-04-22 17:58:56,259 wheel INFO adding 'django/conf/locale/de/__init__.py'
2025-04-22 17:58:56,259 wheel INFO adding 'django/conf/locale/de/formats.py'
2025-04-22 17:58:56,259 wheel INFO adding 'django/conf/locale/de/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,260 wheel INFO adding 'django/conf/locale/de/LC_MESSAGES/django.po'
2025-04-22 17:58:56,260 wheel INFO adding 'django/conf/locale/de_CH/__init__.py'
2025-04-22 17:58:56,260 wheel INFO adding 'django/conf/locale/de_CH/formats.py'
2025-04-22 17:58:56,260 wheel INFO adding 'django/conf/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,261 wheel INFO adding 'django/conf/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,261 wheel INFO adding 'django/conf/locale/el/__init__.py'
2025-04-22 17:58:56,261 wheel INFO adding 'django/conf/locale/el/formats.py'
2025-04-22 17:58:56,261 wheel INFO adding 'django/conf/locale/el/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,262 wheel INFO adding 'django/conf/locale/el/LC_MESSAGES/django.po'
2025-04-22 17:58:56,262 wheel INFO adding 'django/conf/locale/en/__init__.py'
2025-04-22 17:58:56,262 wheel INFO adding 'django/conf/locale/en/formats.py'
2025-04-22 17:58:56,262 wheel INFO adding 'django/conf/locale/en/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,263 wheel INFO adding 'django/conf/locale/en/LC_MESSAGES/django.po'
2025-04-22 17:58:56,263 wheel INFO adding 'django/conf/locale/en_AU/__init__.py'
2025-04-22 17:58:56,263 wheel INFO adding 'django/conf/locale/en_AU/formats.py'
2025-04-22 17:58:56,263 wheel INFO adding 'django/conf/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,264 wheel INFO adding 'django/conf/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 17:58:56,264 wheel INFO adding 'django/conf/locale/en_GB/__init__.py'
2025-04-22 17:58:56,264 wheel INFO adding 'django/conf/locale/en_GB/formats.py'
2025-04-22 17:58:56,264 wheel INFO adding 'django/conf/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,264 wheel INFO adding 'django/conf/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 17:58:56,265 wheel INFO adding 'django/conf/locale/eo/__init__.py'
2025-04-22 17:58:56,265 wheel INFO adding 'django/conf/locale/eo/formats.py'
2025-04-22 17:58:56,265 wheel INFO adding 'django/conf/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,265 wheel INFO adding 'django/conf/locale/eo/LC_MESSAGES/django.po'
2025-04-22 17:58:56,266 wheel INFO adding 'django/conf/locale/es/__init__.py'
2025-04-22 17:58:56,266 wheel INFO adding 'django/conf/locale/es/formats.py'
2025-04-22 17:58:56,266 wheel INFO adding 'django/conf/locale/es/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,266 wheel INFO adding 'django/conf/locale/es/LC_MESSAGES/django.po'
2025-04-22 17:58:56,267 wheel INFO adding 'django/conf/locale/es_AR/__init__.py'
2025-04-22 17:58:56,267 wheel INFO adding 'django/conf/locale/es_AR/formats.py'
2025-04-22 17:58:56,267 wheel INFO adding 'django/conf/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,267 wheel INFO adding 'django/conf/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,268 wheel INFO adding 'django/conf/locale/es_CO/__init__.py'
2025-04-22 17:58:56,268 wheel INFO adding 'django/conf/locale/es_CO/formats.py'
2025-04-22 17:58:56,268 wheel INFO adding 'django/conf/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,268 wheel INFO adding 'django/conf/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 17:58:56,269 wheel INFO adding 'django/conf/locale/es_MX/__init__.py'
2025-04-22 17:58:56,269 wheel INFO adding 'django/conf/locale/es_MX/formats.py'
2025-04-22 17:58:56,269 wheel INFO adding 'django/conf/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,269 wheel INFO adding 'django/conf/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 17:58:56,269 wheel INFO adding 'django/conf/locale/es_NI/__init__.py'
2025-04-22 17:58:56,270 wheel INFO adding 'django/conf/locale/es_NI/formats.py'
2025-04-22 17:58:56,270 wheel INFO adding 'django/conf/locale/es_PR/__init__.py'
2025-04-22 17:58:56,270 wheel INFO adding 'django/conf/locale/es_PR/formats.py'
2025-04-22 17:58:56,270 wheel INFO adding 'django/conf/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,271 wheel INFO adding 'django/conf/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 17:58:56,271 wheel INFO adding 'django/conf/locale/et/__init__.py'
2025-04-22 17:58:56,271 wheel INFO adding 'django/conf/locale/et/formats.py'
2025-04-22 17:58:56,271 wheel INFO adding 'django/conf/locale/et/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,272 wheel INFO adding 'django/conf/locale/et/LC_MESSAGES/django.po'
2025-04-22 17:58:56,272 wheel INFO adding 'django/conf/locale/eu/__init__.py'
2025-04-22 17:58:56,272 wheel INFO adding 'django/conf/locale/eu/formats.py'
2025-04-22 17:58:56,272 wheel INFO adding 'django/conf/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,272 wheel INFO adding 'django/conf/locale/eu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,273 wheel INFO adding 'django/conf/locale/fa/__init__.py'
2025-04-22 17:58:56,273 wheel INFO adding 'django/conf/locale/fa/formats.py'
2025-04-22 17:58:56,273 wheel INFO adding 'django/conf/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,274 wheel INFO adding 'django/conf/locale/fa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,274 wheel INFO adding 'django/conf/locale/fi/__init__.py'
2025-04-22 17:58:56,274 wheel INFO adding 'django/conf/locale/fi/formats.py'
2025-04-22 17:58:56,274 wheel INFO adding 'django/conf/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,275 wheel INFO adding 'django/conf/locale/fi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,275 wheel INFO adding 'django/conf/locale/fr/__init__.py'
2025-04-22 17:58:56,275 wheel INFO adding 'django/conf/locale/fr/formats.py'
2025-04-22 17:58:56,275 wheel INFO adding 'django/conf/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,276 wheel INFO adding 'django/conf/locale/fr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,276 wheel INFO adding 'django/conf/locale/fy/__init__.py'
2025-04-22 17:58:56,276 wheel INFO adding 'django/conf/locale/fy/formats.py'
2025-04-22 17:58:56,276 wheel INFO adding 'django/conf/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,277 wheel INFO adding 'django/conf/locale/fy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,277 wheel INFO adding 'django/conf/locale/ga/__init__.py'
2025-04-22 17:58:56,277 wheel INFO adding 'django/conf/locale/ga/formats.py'
2025-04-22 17:58:56,277 wheel INFO adding 'django/conf/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,277 wheel INFO adding 'django/conf/locale/ga/LC_MESSAGES/django.po'
2025-04-22 17:58:56,278 wheel INFO adding 'django/conf/locale/gd/__init__.py'
2025-04-22 17:58:56,278 wheel INFO adding 'django/conf/locale/gd/formats.py'
2025-04-22 17:58:56,278 wheel INFO adding 'django/conf/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,278 wheel INFO adding 'django/conf/locale/gd/LC_MESSAGES/django.po'
2025-04-22 17:58:56,279 wheel INFO adding 'django/conf/locale/gl/__init__.py'
2025-04-22 17:58:56,279 wheel INFO adding 'django/conf/locale/gl/formats.py'
2025-04-22 17:58:56,279 wheel INFO adding 'django/conf/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,279 wheel INFO adding 'django/conf/locale/gl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,280 wheel INFO adding 'django/conf/locale/he/__init__.py'
2025-04-22 17:58:56,280 wheel INFO adding 'django/conf/locale/he/formats.py'
2025-04-22 17:58:56,280 wheel INFO adding 'django/conf/locale/he/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,280 wheel INFO adding 'django/conf/locale/he/LC_MESSAGES/django.po'
2025-04-22 17:58:56,281 wheel INFO adding 'django/conf/locale/hi/__init__.py'
2025-04-22 17:58:56,281 wheel INFO adding 'django/conf/locale/hi/formats.py'
2025-04-22 17:58:56,281 wheel INFO adding 'django/conf/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,281 wheel INFO adding 'django/conf/locale/hi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,282 wheel INFO adding 'django/conf/locale/hr/__init__.py'
2025-04-22 17:58:56,282 wheel INFO adding 'django/conf/locale/hr/formats.py'
2025-04-22 17:58:56,282 wheel INFO adding 'django/conf/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,282 wheel INFO adding 'django/conf/locale/hr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,283 wheel INFO adding 'django/conf/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,283 wheel INFO adding 'django/conf/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,283 wheel INFO adding 'django/conf/locale/hu/__init__.py'
2025-04-22 17:58:56,283 wheel INFO adding 'django/conf/locale/hu/formats.py'
2025-04-22 17:58:56,284 wheel INFO adding 'django/conf/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,284 wheel INFO adding 'django/conf/locale/hu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,284 wheel INFO adding 'django/conf/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,285 wheel INFO adding 'django/conf/locale/hy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,285 wheel INFO adding 'django/conf/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,285 wheel INFO adding 'django/conf/locale/ia/LC_MESSAGES/django.po'
2025-04-22 17:58:56,285 wheel INFO adding 'django/conf/locale/id/__init__.py'
2025-04-22 17:58:56,286 wheel INFO adding 'django/conf/locale/id/formats.py'
2025-04-22 17:58:56,286 wheel INFO adding 'django/conf/locale/id/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,286 wheel INFO adding 'django/conf/locale/id/LC_MESSAGES/django.po'
2025-04-22 17:58:56,286 wheel INFO adding 'django/conf/locale/ig/__init__.py'
2025-04-22 17:58:56,287 wheel INFO adding 'django/conf/locale/ig/formats.py'
2025-04-22 17:58:56,287 wheel INFO adding 'django/conf/locale/ig/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,287 wheel INFO adding 'django/conf/locale/ig/LC_MESSAGES/django.po'
2025-04-22 17:58:56,287 wheel INFO adding 'django/conf/locale/io/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,288 wheel INFO adding 'django/conf/locale/io/LC_MESSAGES/django.po'
2025-04-22 17:58:56,288 wheel INFO adding 'django/conf/locale/is/__init__.py'
2025-04-22 17:58:56,288 wheel INFO adding 'django/conf/locale/is/formats.py'
2025-04-22 17:58:56,288 wheel INFO adding 'django/conf/locale/is/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,289 wheel INFO adding 'django/conf/locale/is/LC_MESSAGES/django.po'
2025-04-22 17:58:56,289 wheel INFO adding 'django/conf/locale/it/__init__.py'
2025-04-22 17:58:56,289 wheel INFO adding 'django/conf/locale/it/formats.py'
2025-04-22 17:58:56,289 wheel INFO adding 'django/conf/locale/it/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,290 wheel INFO adding 'django/conf/locale/it/LC_MESSAGES/django.po'
2025-04-22 17:58:56,290 wheel INFO adding 'django/conf/locale/ja/__init__.py'
2025-04-22 17:58:56,290 wheel INFO adding 'django/conf/locale/ja/formats.py'
2025-04-22 17:58:56,290 wheel INFO adding 'django/conf/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,291 wheel INFO adding 'django/conf/locale/ja/LC_MESSAGES/django.po'
2025-04-22 17:58:56,291 wheel INFO adding 'django/conf/locale/ka/__init__.py'
2025-04-22 17:58:56,291 wheel INFO adding 'django/conf/locale/ka/formats.py'
2025-04-22 17:58:56,291 wheel INFO adding 'django/conf/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,292 wheel INFO adding 'django/conf/locale/ka/LC_MESSAGES/django.po'
2025-04-22 17:58:56,292 wheel INFO adding 'django/conf/locale/kab/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,292 wheel INFO adding 'django/conf/locale/kab/LC_MESSAGES/django.po'
2025-04-22 17:58:56,292 wheel INFO adding 'django/conf/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,293 wheel INFO adding 'django/conf/locale/kk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,293 wheel INFO adding 'django/conf/locale/km/__init__.py'
2025-04-22 17:58:56,293 wheel INFO adding 'django/conf/locale/km/formats.py'
2025-04-22 17:58:56,294 wheel INFO adding 'django/conf/locale/km/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,294 wheel INFO adding 'django/conf/locale/km/LC_MESSAGES/django.po'
2025-04-22 17:58:56,294 wheel INFO adding 'django/conf/locale/kn/__init__.py'
2025-04-22 17:58:56,294 wheel INFO adding 'django/conf/locale/kn/formats.py'
2025-04-22 17:58:56,294 wheel INFO adding 'django/conf/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,295 wheel INFO adding 'django/conf/locale/kn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,295 wheel INFO adding 'django/conf/locale/ko/__init__.py'
2025-04-22 17:58:56,295 wheel INFO adding 'django/conf/locale/ko/formats.py'
2025-04-22 17:58:56,295 wheel INFO adding 'django/conf/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,296 wheel INFO adding 'django/conf/locale/ko/LC_MESSAGES/django.po'
2025-04-22 17:58:56,296 wheel INFO adding 'django/conf/locale/ky/__init__.py'
2025-04-22 17:58:56,296 wheel INFO adding 'django/conf/locale/ky/formats.py'
2025-04-22 17:58:56,296 wheel INFO adding 'django/conf/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,297 wheel INFO adding 'django/conf/locale/ky/LC_MESSAGES/django.po'
2025-04-22 17:58:56,297 wheel INFO adding 'django/conf/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,297 wheel INFO adding 'django/conf/locale/lb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,298 wheel INFO adding 'django/conf/locale/lt/__init__.py'
2025-04-22 17:58:56,298 wheel INFO adding 'django/conf/locale/lt/formats.py'
2025-04-22 17:58:56,298 wheel INFO adding 'django/conf/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,298 wheel INFO adding 'django/conf/locale/lt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,299 wheel INFO adding 'django/conf/locale/lv/__init__.py'
2025-04-22 17:58:56,299 wheel INFO adding 'django/conf/locale/lv/formats.py'
2025-04-22 17:58:56,299 wheel INFO adding 'django/conf/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,299 wheel INFO adding 'django/conf/locale/lv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,300 wheel INFO adding 'django/conf/locale/mk/__init__.py'
2025-04-22 17:58:56,300 wheel INFO adding 'django/conf/locale/mk/formats.py'
2025-04-22 17:58:56,300 wheel INFO adding 'django/conf/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,300 wheel INFO adding 'django/conf/locale/mk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,301 wheel INFO adding 'django/conf/locale/ml/__init__.py'
2025-04-22 17:58:56,301 wheel INFO adding 'django/conf/locale/ml/formats.py'
2025-04-22 17:58:56,301 wheel INFO adding 'django/conf/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,301 wheel INFO adding 'django/conf/locale/ml/LC_MESSAGES/django.po'
2025-04-22 17:58:56,302 wheel INFO adding 'django/conf/locale/mn/__init__.py'
2025-04-22 17:58:56,302 wheel INFO adding 'django/conf/locale/mn/formats.py'
2025-04-22 17:58:56,302 wheel INFO adding 'django/conf/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,303 wheel INFO adding 'django/conf/locale/mn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,303 wheel INFO adding 'django/conf/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,303 wheel INFO adding 'django/conf/locale/mr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,303 wheel INFO adding 'django/conf/locale/ms/__init__.py'
2025-04-22 17:58:56,304 wheel INFO adding 'django/conf/locale/ms/formats.py'
2025-04-22 17:58:56,304 wheel INFO adding 'django/conf/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,304 wheel INFO adding 'django/conf/locale/ms/LC_MESSAGES/django.po'
2025-04-22 17:58:56,305 wheel INFO adding 'django/conf/locale/my/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,305 wheel INFO adding 'django/conf/locale/my/LC_MESSAGES/django.po'
2025-04-22 17:58:56,305 wheel INFO adding 'django/conf/locale/nb/__init__.py'
2025-04-22 17:58:56,305 wheel INFO adding 'django/conf/locale/nb/formats.py'
2025-04-22 17:58:56,306 wheel INFO adding 'django/conf/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,306 wheel INFO adding 'django/conf/locale/nb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,306 wheel INFO adding 'django/conf/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,307 wheel INFO adding 'django/conf/locale/ne/LC_MESSAGES/django.po'
2025-04-22 17:58:56,307 wheel INFO adding 'django/conf/locale/nl/__init__.py'
2025-04-22 17:58:56,307 wheel INFO adding 'django/conf/locale/nl/formats.py'
2025-04-22 17:58:56,307 wheel INFO adding 'django/conf/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,308 wheel INFO adding 'django/conf/locale/nl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,308 wheel INFO adding 'django/conf/locale/nn/__init__.py'
2025-04-22 17:58:56,308 wheel INFO adding 'django/conf/locale/nn/formats.py'
2025-04-22 17:58:56,309 wheel INFO adding 'django/conf/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,309 wheel INFO adding 'django/conf/locale/nn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,309 wheel INFO adding 'django/conf/locale/os/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,309 wheel INFO adding 'django/conf/locale/os/LC_MESSAGES/django.po'
2025-04-22 17:58:56,310 wheel INFO adding 'django/conf/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,310 wheel INFO adding 'django/conf/locale/pa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,310 wheel INFO adding 'django/conf/locale/pl/__init__.py'
2025-04-22 17:58:56,310 wheel INFO adding 'django/conf/locale/pl/formats.py'
2025-04-22 17:58:56,311 wheel INFO adding 'django/conf/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,311 wheel INFO adding 'django/conf/locale/pl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,311 wheel INFO adding 'django/conf/locale/pt/__init__.py'
2025-04-22 17:58:56,311 wheel INFO adding 'django/conf/locale/pt/formats.py'
2025-04-22 17:58:56,312 wheel INFO adding 'django/conf/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,312 wheel INFO adding 'django/conf/locale/pt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,312 wheel INFO adding 'django/conf/locale/pt_BR/__init__.py'
2025-04-22 17:58:56,312 wheel INFO adding 'django/conf/locale/pt_BR/formats.py'
2025-04-22 17:58:56,313 wheel INFO adding 'django/conf/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,313 wheel INFO adding 'django/conf/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,313 wheel INFO adding 'django/conf/locale/ro/__init__.py'
2025-04-22 17:58:56,313 wheel INFO adding 'django/conf/locale/ro/formats.py'
2025-04-22 17:58:56,314 wheel INFO adding 'django/conf/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,314 wheel INFO adding 'django/conf/locale/ro/LC_MESSAGES/django.po'
2025-04-22 17:58:56,315 wheel INFO adding 'django/conf/locale/ru/__init__.py'
2025-04-22 17:58:56,315 wheel INFO adding 'django/conf/locale/ru/formats.py'
2025-04-22 17:58:56,315 wheel INFO adding 'django/conf/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,315 wheel INFO adding 'django/conf/locale/ru/LC_MESSAGES/django.po'
2025-04-22 17:58:56,316 wheel INFO adding 'django/conf/locale/sk/__init__.py'
2025-04-22 17:58:56,316 wheel INFO adding 'django/conf/locale/sk/formats.py'
2025-04-22 17:58:56,316 wheel INFO adding 'django/conf/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,316 wheel INFO adding 'django/conf/locale/sk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,317 wheel INFO adding 'django/conf/locale/sl/__init__.py'
2025-04-22 17:58:56,317 wheel INFO adding 'django/conf/locale/sl/formats.py'
2025-04-22 17:58:56,317 wheel INFO adding 'django/conf/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,317 wheel INFO adding 'django/conf/locale/sl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,318 wheel INFO adding 'django/conf/locale/sq/__init__.py'
2025-04-22 17:58:56,318 wheel INFO adding 'django/conf/locale/sq/formats.py'
2025-04-22 17:58:56,318 wheel INFO adding 'django/conf/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,318 wheel INFO adding 'django/conf/locale/sq/LC_MESSAGES/django.po'
2025-04-22 17:58:56,318 wheel INFO adding 'django/conf/locale/sr/__init__.py'
2025-04-22 17:58:56,319 wheel INFO adding 'django/conf/locale/sr/formats.py'
2025-04-22 17:58:56,319 wheel INFO adding 'django/conf/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,319 wheel INFO adding 'django/conf/locale/sr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,320 wheel INFO adding 'django/conf/locale/sr_Latn/__init__.py'
2025-04-22 17:58:56,320 wheel INFO adding 'django/conf/locale/sr_Latn/formats.py'
2025-04-22 17:58:56,320 wheel INFO adding 'django/conf/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,320 wheel INFO adding 'django/conf/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,321 wheel INFO adding 'django/conf/locale/sv/__init__.py'
2025-04-22 17:58:56,321 wheel INFO adding 'django/conf/locale/sv/formats.py'
2025-04-22 17:58:56,321 wheel INFO adding 'django/conf/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,321 wheel INFO adding 'django/conf/locale/sv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,322 wheel INFO adding 'django/conf/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,322 wheel INFO adding 'django/conf/locale/sw/LC_MESSAGES/django.po'
2025-04-22 17:58:56,322 wheel INFO adding 'django/conf/locale/ta/__init__.py'
2025-04-22 17:58:56,322 wheel INFO adding 'django/conf/locale/ta/formats.py'
2025-04-22 17:58:56,322 wheel INFO adding 'django/conf/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,323 wheel INFO adding 'django/conf/locale/ta/LC_MESSAGES/django.po'
2025-04-22 17:58:56,323 wheel INFO adding 'django/conf/locale/te/__init__.py'
2025-04-22 17:58:56,323 wheel INFO adding 'django/conf/locale/te/formats.py'
2025-04-22 17:58:56,323 wheel INFO adding 'django/conf/locale/te/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,324 wheel INFO adding 'django/conf/locale/te/LC_MESSAGES/django.po'
2025-04-22 17:58:56,324 wheel INFO adding 'django/conf/locale/tg/__init__.py'
2025-04-22 17:58:56,324 wheel INFO adding 'django/conf/locale/tg/formats.py'
2025-04-22 17:58:56,324 wheel INFO adding 'django/conf/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,325 wheel INFO adding 'django/conf/locale/tg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,325 wheel INFO adding 'django/conf/locale/th/__init__.py'
2025-04-22 17:58:56,325 wheel INFO adding 'django/conf/locale/th/formats.py'
2025-04-22 17:58:56,325 wheel INFO adding 'django/conf/locale/th/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,326 wheel INFO adding 'django/conf/locale/th/LC_MESSAGES/django.po'
2025-04-22 17:58:56,326 wheel INFO adding 'django/conf/locale/tk/__init__.py'
2025-04-22 17:58:56,326 wheel INFO adding 'django/conf/locale/tk/formats.py'
2025-04-22 17:58:56,326 wheel INFO adding 'django/conf/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,327 wheel INFO adding 'django/conf/locale/tk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,327 wheel INFO adding 'django/conf/locale/tr/__init__.py'
2025-04-22 17:58:56,327 wheel INFO adding 'django/conf/locale/tr/formats.py'
2025-04-22 17:58:56,327 wheel INFO adding 'django/conf/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,328 wheel INFO adding 'django/conf/locale/tr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,328 wheel INFO adding 'django/conf/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,328 wheel INFO adding 'django/conf/locale/tt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,328 wheel INFO adding 'django/conf/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,329 wheel INFO adding 'django/conf/locale/udm/LC_MESSAGES/django.po'
2025-04-22 17:58:56,329 wheel INFO adding 'django/conf/locale/uk/__init__.py'
2025-04-22 17:58:56,329 wheel INFO adding 'django/conf/locale/uk/formats.py'
2025-04-22 17:58:56,330 wheel INFO adding 'django/conf/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,330 wheel INFO adding 'django/conf/locale/uk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,330 wheel INFO adding 'django/conf/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,330 wheel INFO adding 'django/conf/locale/ur/LC_MESSAGES/django.po'
2025-04-22 17:58:56,331 wheel INFO adding 'django/conf/locale/uz/__init__.py'
2025-04-22 17:58:56,331 wheel INFO adding 'django/conf/locale/uz/formats.py'
2025-04-22 17:58:56,331 wheel INFO adding 'django/conf/locale/uz/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,331 wheel INFO adding 'django/conf/locale/uz/LC_MESSAGES/django.po'
2025-04-22 17:58:56,332 wheel INFO adding 'django/conf/locale/vi/__init__.py'
2025-04-22 17:58:56,332 wheel INFO adding 'django/conf/locale/vi/formats.py'
2025-04-22 17:58:56,332 wheel INFO adding 'django/conf/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,332 wheel INFO adding 'django/conf/locale/vi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,333 wheel INFO adding 'django/conf/locale/zh_Hans/__init__.py'
2025-04-22 17:58:56,333 wheel INFO adding 'django/conf/locale/zh_Hans/formats.py'
2025-04-22 17:58:56,333 wheel INFO adding 'django/conf/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,333 wheel INFO adding 'django/conf/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 17:58:56,334 wheel INFO adding 'django/conf/locale/zh_Hant/__init__.py'
2025-04-22 17:58:56,334 wheel INFO adding 'django/conf/locale/zh_Hant/formats.py'
2025-04-22 17:58:56,334 wheel INFO adding 'django/conf/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,334 wheel INFO adding 'django/conf/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 17:58:56,335 wheel INFO adding 'django/conf/project_template/manage.py-tpl'
2025-04-22 17:58:56,335 wheel INFO adding 'django/conf/project_template/project_name/__init__.py-tpl'
2025-04-22 17:58:56,335 wheel INFO adding 'django/conf/project_template/project_name/asgi.py-tpl'
2025-04-22 17:58:56,335 wheel INFO adding 'django/conf/project_template/project_name/settings.py-tpl'
2025-04-22 17:58:56,335 wheel INFO adding 'django/conf/project_template/project_name/urls.py-tpl'
2025-04-22 17:58:56,335 wheel INFO adding 'django/conf/project_template/project_name/wsgi.py-tpl'
2025-04-22 17:58:56,336 wheel INFO adding 'django/conf/urls/__init__.py'
2025-04-22 17:58:56,336 wheel INFO adding 'django/conf/urls/i18n.py'
2025-04-22 17:58:56,336 wheel INFO adding 'django/conf/urls/static.py'
2025-04-22 17:58:56,336 wheel INFO adding 'django/contrib/__init__.py'
2025-04-22 17:58:56,337 wheel INFO adding 'django/contrib/admin/__init__.py'
2025-04-22 17:58:56,337 wheel INFO adding 'django/contrib/admin/actions.py'
2025-04-22 17:58:56,337 wheel INFO adding 'django/contrib/admin/apps.py'
2025-04-22 17:58:56,337 wheel INFO adding 'django/contrib/admin/checks.py'
2025-04-22 17:58:56,337 wheel INFO adding 'django/contrib/admin/decorators.py'
2025-04-22 17:58:56,338 wheel INFO adding 'django/contrib/admin/exceptions.py'
2025-04-22 17:58:56,338 wheel INFO adding 'django/contrib/admin/filters.py'
2025-04-22 17:58:56,338 wheel INFO adding 'django/contrib/admin/forms.py'
2025-04-22 17:58:56,338 wheel INFO adding 'django/contrib/admin/helpers.py'
2025-04-22 17:58:56,338 wheel INFO adding 'django/contrib/admin/models.py'
2025-04-22 17:58:56,339 wheel INFO adding 'django/contrib/admin/options.py'
2025-04-22 17:58:56,339 wheel INFO adding 'django/contrib/admin/sites.py'
2025-04-22 17:58:56,339 wheel INFO adding 'django/contrib/admin/tests.py'
2025-04-22 17:58:56,340 wheel INFO adding 'django/contrib/admin/utils.py'
2025-04-22 17:58:56,340 wheel INFO adding 'django/contrib/admin/widgets.py'
2025-04-22 17:58:56,341 wheel INFO adding 'django/contrib/admin/locale/af/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,341 wheel INFO adding 'django/contrib/admin/locale/af/LC_MESSAGES/django.po'
2025-04-22 17:58:56,341 wheel INFO adding 'django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,342 wheel INFO adding 'django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,342 wheel INFO adding 'django/contrib/admin/locale/am/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,342 wheel INFO adding 'django/contrib/admin/locale/am/LC_MESSAGES/django.po'
2025-04-22 17:58:56,342 wheel INFO adding 'django/contrib/admin/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,343 wheel INFO adding 'django/contrib/admin/locale/ar/LC_MESSAGES/django.po'
2025-04-22 17:58:56,343 wheel INFO adding 'django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,343 wheel INFO adding 'django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,344 wheel INFO adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,344 wheel INFO adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 17:58:56,344 wheel INFO adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,344 wheel INFO adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,345 wheel INFO adding 'django/contrib/admin/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,345 wheel INFO adding 'django/contrib/admin/locale/ast/LC_MESSAGES/django.po'
2025-04-22 17:58:56,345 wheel INFO adding 'django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,345 wheel INFO adding 'django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,345 wheel INFO adding 'django/contrib/admin/locale/az/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,346 wheel INFO adding 'django/contrib/admin/locale/az/LC_MESSAGES/django.po'
2025-04-22 17:58:56,346 wheel INFO adding 'django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,346 wheel INFO adding 'django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,346 wheel INFO adding 'django/contrib/admin/locale/be/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,347 wheel INFO adding 'django/contrib/admin/locale/be/LC_MESSAGES/django.po'
2025-04-22 17:58:56,347 wheel INFO adding 'django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,347 wheel INFO adding 'django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,347 wheel INFO adding 'django/contrib/admin/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,348 wheel INFO adding 'django/contrib/admin/locale/bg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,348 wheel INFO adding 'django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,348 wheel INFO adding 'django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,348 wheel INFO adding 'django/contrib/admin/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,349 wheel INFO adding 'django/contrib/admin/locale/bn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,349 wheel INFO adding 'django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,349 wheel INFO adding 'django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,349 wheel INFO adding 'django/contrib/admin/locale/br/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,350 wheel INFO adding 'django/contrib/admin/locale/br/LC_MESSAGES/django.po'
2025-04-22 17:58:56,350 wheel INFO adding 'django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,350 wheel INFO adding 'django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,350 wheel INFO adding 'django/contrib/admin/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,351 wheel INFO adding 'django/contrib/admin/locale/bs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,351 wheel INFO adding 'django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,351 wheel INFO adding 'django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,351 wheel INFO adding 'django/contrib/admin/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,351 wheel INFO adding 'django/contrib/admin/locale/ca/LC_MESSAGES/django.po'
2025-04-22 17:58:56,352 wheel INFO adding 'django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,352 wheel INFO adding 'django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,352 wheel INFO adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,353 wheel INFO adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,353 wheel INFO adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,353 wheel INFO adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,353 wheel INFO adding 'django/contrib/admin/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,354 wheel INFO adding 'django/contrib/admin/locale/cs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,354 wheel INFO adding 'django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,354 wheel INFO adding 'django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,354 wheel INFO adding 'django/contrib/admin/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,355 wheel INFO adding 'django/contrib/admin/locale/cy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,355 wheel INFO adding 'django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,355 wheel INFO adding 'django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,355 wheel INFO adding 'django/contrib/admin/locale/da/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,355 wheel INFO adding 'django/contrib/admin/locale/da/LC_MESSAGES/django.po'
2025-04-22 17:58:56,356 wheel INFO adding 'django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,356 wheel INFO adding 'django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,356 wheel INFO adding 'django/contrib/admin/locale/de/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,356 wheel INFO adding 'django/contrib/admin/locale/de/LC_MESSAGES/django.po'
2025-04-22 17:58:56,357 wheel INFO adding 'django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,357 wheel INFO adding 'django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,357 wheel INFO adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,357 wheel INFO adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,358 wheel INFO adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,358 wheel INFO adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,358 wheel INFO adding 'django/contrib/admin/locale/el/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,359 wheel INFO adding 'django/contrib/admin/locale/el/LC_MESSAGES/django.po'
2025-04-22 17:58:56,359 wheel INFO adding 'django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,359 wheel INFO adding 'django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,359 wheel INFO adding 'django/contrib/admin/locale/en/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,360 wheel INFO adding 'django/contrib/admin/locale/en/LC_MESSAGES/django.po'
2025-04-22 17:58:56,360 wheel INFO adding 'django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,360 wheel INFO adding 'django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,360 wheel INFO adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,361 wheel INFO adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 17:58:56,361 wheel INFO adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,361 wheel INFO adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,361 wheel INFO adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,361 wheel INFO adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 17:58:56,362 wheel INFO adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,362 wheel INFO adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,362 wheel INFO adding 'django/contrib/admin/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,362 wheel INFO adding 'django/contrib/admin/locale/eo/LC_MESSAGES/django.po'
2025-04-22 17:58:56,363 wheel INFO adding 'django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,363 wheel INFO adding 'django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,363 wheel INFO adding 'django/contrib/admin/locale/es/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,363 wheel INFO adding 'django/contrib/admin/locale/es/LC_MESSAGES/django.po'
2025-04-22 17:58:56,364 wheel INFO adding 'django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,364 wheel INFO adding 'django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,364 wheel INFO adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,364 wheel INFO adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,365 wheel INFO adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,365 wheel INFO adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,365 wheel INFO adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,365 wheel INFO adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 17:58:56,366 wheel INFO adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,366 wheel INFO adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,366 wheel INFO adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,366 wheel INFO adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 17:58:56,366 wheel INFO adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,367 wheel INFO adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,367 wheel INFO adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,367 wheel INFO adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 17:58:56,367 wheel INFO adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,368 wheel INFO adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,368 wheel INFO adding 'django/contrib/admin/locale/et/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,368 wheel INFO adding 'django/contrib/admin/locale/et/LC_MESSAGES/django.po'
2025-04-22 17:58:56,368 wheel INFO adding 'django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,368 wheel INFO adding 'django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,369 wheel INFO adding 'django/contrib/admin/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,369 wheel INFO adding 'django/contrib/admin/locale/eu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,369 wheel INFO adding 'django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,369 wheel INFO adding 'django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,370 wheel INFO adding 'django/contrib/admin/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,370 wheel INFO adding 'django/contrib/admin/locale/fa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,370 wheel INFO adding 'django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,370 wheel INFO adding 'django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,371 wheel INFO adding 'django/contrib/admin/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,371 wheel INFO adding 'django/contrib/admin/locale/fi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,371 wheel INFO adding 'django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,371 wheel INFO adding 'django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,372 wheel INFO adding 'django/contrib/admin/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,372 wheel INFO adding 'django/contrib/admin/locale/fr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,372 wheel INFO adding 'django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,372 wheel INFO adding 'django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,373 wheel INFO adding 'django/contrib/admin/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,373 wheel INFO adding 'django/contrib/admin/locale/fy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,373 wheel INFO adding 'django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,373 wheel INFO adding 'django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,374 wheel INFO adding 'django/contrib/admin/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,374 wheel INFO adding 'django/contrib/admin/locale/ga/LC_MESSAGES/django.po'
2025-04-22 17:58:56,374 wheel INFO adding 'django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,374 wheel INFO adding 'django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,375 wheel INFO adding 'django/contrib/admin/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,375 wheel INFO adding 'django/contrib/admin/locale/gd/LC_MESSAGES/django.po'
2025-04-22 17:58:56,375 wheel INFO adding 'django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,375 wheel INFO adding 'django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,376 wheel INFO adding 'django/contrib/admin/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,376 wheel INFO adding 'django/contrib/admin/locale/gl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,376 wheel INFO adding 'django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,376 wheel INFO adding 'django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,377 wheel INFO adding 'django/contrib/admin/locale/he/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,377 wheel INFO adding 'django/contrib/admin/locale/he/LC_MESSAGES/django.po'
2025-04-22 17:58:56,377 wheel INFO adding 'django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,377 wheel INFO adding 'django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,378 wheel INFO adding 'django/contrib/admin/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,378 wheel INFO adding 'django/contrib/admin/locale/hi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,378 wheel INFO adding 'django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,378 wheel INFO adding 'django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,379 wheel INFO adding 'django/contrib/admin/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,379 wheel INFO adding 'django/contrib/admin/locale/hr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,379 wheel INFO adding 'django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,379 wheel INFO adding 'django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,380 wheel INFO adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,380 wheel INFO adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,380 wheel INFO adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,380 wheel INFO adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,381 wheel INFO adding 'django/contrib/admin/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,381 wheel INFO adding 'django/contrib/admin/locale/hu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,381 wheel INFO adding 'django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,381 wheel INFO adding 'django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,381 wheel INFO adding 'django/contrib/admin/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,382 wheel INFO adding 'django/contrib/admin/locale/hy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,382 wheel INFO adding 'django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,382 wheel INFO adding 'django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,382 wheel INFO adding 'django/contrib/admin/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,383 wheel INFO adding 'django/contrib/admin/locale/ia/LC_MESSAGES/django.po'
2025-04-22 17:58:56,383 wheel INFO adding 'django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,383 wheel INFO adding 'django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,383 wheel INFO adding 'django/contrib/admin/locale/id/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,384 wheel INFO adding 'django/contrib/admin/locale/id/LC_MESSAGES/django.po'
2025-04-22 17:58:56,384 wheel INFO adding 'django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,384 wheel INFO adding 'django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,384 wheel INFO adding 'django/contrib/admin/locale/io/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,385 wheel INFO adding 'django/contrib/admin/locale/io/LC_MESSAGES/django.po'
2025-04-22 17:58:56,385 wheel INFO adding 'django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,385 wheel INFO adding 'django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,385 wheel INFO adding 'django/contrib/admin/locale/is/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,385 wheel INFO adding 'django/contrib/admin/locale/is/LC_MESSAGES/django.po'
2025-04-22 17:58:56,386 wheel INFO adding 'django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,386 wheel INFO adding 'django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,386 wheel INFO adding 'django/contrib/admin/locale/it/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,386 wheel INFO adding 'django/contrib/admin/locale/it/LC_MESSAGES/django.po'
2025-04-22 17:58:56,387 wheel INFO adding 'django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,387 wheel INFO adding 'django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,387 wheel INFO adding 'django/contrib/admin/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,387 wheel INFO adding 'django/contrib/admin/locale/ja/LC_MESSAGES/django.po'
2025-04-22 17:58:56,388 wheel INFO adding 'django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,388 wheel INFO adding 'django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,388 wheel INFO adding 'django/contrib/admin/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,388 wheel INFO adding 'django/contrib/admin/locale/ka/LC_MESSAGES/django.po'
2025-04-22 17:58:56,389 wheel INFO adding 'django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,389 wheel INFO adding 'django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,389 wheel INFO adding 'django/contrib/admin/locale/kab/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,390 wheel INFO adding 'django/contrib/admin/locale/kab/LC_MESSAGES/django.po'
2025-04-22 17:58:56,390 wheel INFO adding 'django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,390 wheel INFO adding 'django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,390 wheel INFO adding 'django/contrib/admin/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,390 wheel INFO adding 'django/contrib/admin/locale/kk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,391 wheel INFO adding 'django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,391 wheel INFO adding 'django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,391 wheel INFO adding 'django/contrib/admin/locale/km/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,391 wheel INFO adding 'django/contrib/admin/locale/km/LC_MESSAGES/django.po'
2025-04-22 17:58:56,392 wheel INFO adding 'django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,392 wheel INFO adding 'django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,392 wheel INFO adding 'django/contrib/admin/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,392 wheel INFO adding 'django/contrib/admin/locale/kn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,392 wheel INFO adding 'django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,393 wheel INFO adding 'django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,393 wheel INFO adding 'django/contrib/admin/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,393 wheel INFO adding 'django/contrib/admin/locale/ko/LC_MESSAGES/django.po'
2025-04-22 17:58:56,393 wheel INFO adding 'django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,394 wheel INFO adding 'django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,394 wheel INFO adding 'django/contrib/admin/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,394 wheel INFO adding 'django/contrib/admin/locale/ky/LC_MESSAGES/django.po'
2025-04-22 17:58:56,394 wheel INFO adding 'django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,395 wheel INFO adding 'django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,395 wheel INFO adding 'django/contrib/admin/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,395 wheel INFO adding 'django/contrib/admin/locale/lb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,395 wheel INFO adding 'django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,395 wheel INFO adding 'django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,396 wheel INFO adding 'django/contrib/admin/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,396 wheel INFO adding 'django/contrib/admin/locale/lt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,396 wheel INFO adding 'django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,396 wheel INFO adding 'django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,397 wheel INFO adding 'django/contrib/admin/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,397 wheel INFO adding 'django/contrib/admin/locale/lv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,397 wheel INFO adding 'django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,397 wheel INFO adding 'django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,398 wheel INFO adding 'django/contrib/admin/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,398 wheel INFO adding 'django/contrib/admin/locale/mk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,398 wheel INFO adding 'django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,398 wheel INFO adding 'django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,399 wheel INFO adding 'django/contrib/admin/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,399 wheel INFO adding 'django/contrib/admin/locale/ml/LC_MESSAGES/django.po'
2025-04-22 17:58:56,399 wheel INFO adding 'django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,399 wheel INFO adding 'django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,400 wheel INFO adding 'django/contrib/admin/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,400 wheel INFO adding 'django/contrib/admin/locale/mn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,400 wheel INFO adding 'django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,400 wheel INFO adding 'django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,401 wheel INFO adding 'django/contrib/admin/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,401 wheel INFO adding 'django/contrib/admin/locale/mr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,401 wheel INFO adding 'django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,401 wheel INFO adding 'django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,402 wheel INFO adding 'django/contrib/admin/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,402 wheel INFO adding 'django/contrib/admin/locale/ms/LC_MESSAGES/django.po'
2025-04-22 17:58:56,402 wheel INFO adding 'django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,402 wheel INFO adding 'django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,402 wheel INFO adding 'django/contrib/admin/locale/my/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,403 wheel INFO adding 'django/contrib/admin/locale/my/LC_MESSAGES/django.po'
2025-04-22 17:58:56,403 wheel INFO adding 'django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,403 wheel INFO adding 'django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,403 wheel INFO adding 'django/contrib/admin/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,404 wheel INFO adding 'django/contrib/admin/locale/nb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,404 wheel INFO adding 'django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,404 wheel INFO adding 'django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,404 wheel INFO adding 'django/contrib/admin/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,405 wheel INFO adding 'django/contrib/admin/locale/ne/LC_MESSAGES/django.po'
2025-04-22 17:58:56,405 wheel INFO adding 'django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,405 wheel INFO adding 'django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,405 wheel INFO adding 'django/contrib/admin/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,406 wheel INFO adding 'django/contrib/admin/locale/nl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,406 wheel INFO adding 'django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,406 wheel INFO adding 'django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,406 wheel INFO adding 'django/contrib/admin/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,406 wheel INFO adding 'django/contrib/admin/locale/nn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,407 wheel INFO adding 'django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,407 wheel INFO adding 'django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,407 wheel INFO adding 'django/contrib/admin/locale/os/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,407 wheel INFO adding 'django/contrib/admin/locale/os/LC_MESSAGES/django.po'
2025-04-22 17:58:56,408 wheel INFO adding 'django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,408 wheel INFO adding 'django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,408 wheel INFO adding 'django/contrib/admin/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,408 wheel INFO adding 'django/contrib/admin/locale/pa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,408 wheel INFO adding 'django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,409 wheel INFO adding 'django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,409 wheel INFO adding 'django/contrib/admin/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,409 wheel INFO adding 'django/contrib/admin/locale/pl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,410 wheel INFO adding 'django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,410 wheel INFO adding 'django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,410 wheel INFO adding 'django/contrib/admin/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,410 wheel INFO adding 'django/contrib/admin/locale/pt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,410 wheel INFO adding 'django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,411 wheel INFO adding 'django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,411 wheel INFO adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,411 wheel INFO adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,411 wheel INFO adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,412 wheel INFO adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,412 wheel INFO adding 'django/contrib/admin/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,412 wheel INFO adding 'django/contrib/admin/locale/ro/LC_MESSAGES/django.po'
2025-04-22 17:58:56,412 wheel INFO adding 'django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,413 wheel INFO adding 'django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,413 wheel INFO adding 'django/contrib/admin/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,413 wheel INFO adding 'django/contrib/admin/locale/ru/LC_MESSAGES/django.po'
2025-04-22 17:58:56,413 wheel INFO adding 'django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,414 wheel INFO adding 'django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,414 wheel INFO adding 'django/contrib/admin/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,414 wheel INFO adding 'django/contrib/admin/locale/sk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,414 wheel INFO adding 'django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,415 wheel INFO adding 'django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,415 wheel INFO adding 'django/contrib/admin/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,415 wheel INFO adding 'django/contrib/admin/locale/sl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,415 wheel INFO adding 'django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,415 wheel INFO adding 'django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,416 wheel INFO adding 'django/contrib/admin/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,416 wheel INFO adding 'django/contrib/admin/locale/sq/LC_MESSAGES/django.po'
2025-04-22 17:58:56,416 wheel INFO adding 'django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,416 wheel INFO adding 'django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,417 wheel INFO adding 'django/contrib/admin/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,417 wheel INFO adding 'django/contrib/admin/locale/sr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,417 wheel INFO adding 'django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,417 wheel INFO adding 'django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,418 wheel INFO adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,418 wheel INFO adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,418 wheel INFO adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,418 wheel INFO adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,419 wheel INFO adding 'django/contrib/admin/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,419 wheel INFO adding 'django/contrib/admin/locale/sv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,419 wheel INFO adding 'django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,419 wheel INFO adding 'django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,420 wheel INFO adding 'django/contrib/admin/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,420 wheel INFO adding 'django/contrib/admin/locale/sw/LC_MESSAGES/django.po'
2025-04-22 17:58:56,420 wheel INFO adding 'django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,420 wheel INFO adding 'django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,420 wheel INFO adding 'django/contrib/admin/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,421 wheel INFO adding 'django/contrib/admin/locale/ta/LC_MESSAGES/django.po'
2025-04-22 17:58:56,421 wheel INFO adding 'django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,421 wheel INFO adding 'django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,421 wheel INFO adding 'django/contrib/admin/locale/te/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,421 wheel INFO adding 'django/contrib/admin/locale/te/LC_MESSAGES/django.po'
2025-04-22 17:58:56,422 wheel INFO adding 'django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,422 wheel INFO adding 'django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,422 wheel INFO adding 'django/contrib/admin/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,422 wheel INFO adding 'django/contrib/admin/locale/tg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,423 wheel INFO adding 'django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,423 wheel INFO adding 'django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,423 wheel INFO adding 'django/contrib/admin/locale/th/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,423 wheel INFO adding 'django/contrib/admin/locale/th/LC_MESSAGES/django.po'
2025-04-22 17:58:56,424 wheel INFO adding 'django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,424 wheel INFO adding 'django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,424 wheel INFO adding 'django/contrib/admin/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,424 wheel INFO adding 'django/contrib/admin/locale/tk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,424 wheel INFO adding 'django/contrib/admin/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,425 wheel INFO adding 'django/contrib/admin/locale/tr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,425 wheel INFO adding 'django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,425 wheel INFO adding 'django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,425 wheel INFO adding 'django/contrib/admin/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,426 wheel INFO adding 'django/contrib/admin/locale/tt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,426 wheel INFO adding 'django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,426 wheel INFO adding 'django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,426 wheel INFO adding 'django/contrib/admin/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,426 wheel INFO adding 'django/contrib/admin/locale/udm/LC_MESSAGES/django.po'
2025-04-22 17:58:56,427 wheel INFO adding 'django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,427 wheel INFO adding 'django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,427 wheel INFO adding 'django/contrib/admin/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,427 wheel INFO adding 'django/contrib/admin/locale/uk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,428 wheel INFO adding 'django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,428 wheel INFO adding 'django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,428 wheel INFO adding 'django/contrib/admin/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,428 wheel INFO adding 'django/contrib/admin/locale/ur/LC_MESSAGES/django.po'
2025-04-22 17:58:56,428 wheel INFO adding 'django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,429 wheel INFO adding 'django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,429 wheel INFO adding 'django/contrib/admin/locale/uz/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,429 wheel INFO adding 'django/contrib/admin/locale/uz/LC_MESSAGES/django.po'
2025-04-22 17:58:56,429 wheel INFO adding 'django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,429 wheel INFO adding 'django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,430 wheel INFO adding 'django/contrib/admin/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,430 wheel INFO adding 'django/contrib/admin/locale/vi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,430 wheel INFO adding 'django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,430 wheel INFO adding 'django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,431 wheel INFO adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,431 wheel INFO adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 17:58:56,431 wheel INFO adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,431 wheel INFO adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,432 wheel INFO adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,432 wheel INFO adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 17:58:56,432 wheel INFO adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo'
2025-04-22 17:58:56,432 wheel INFO adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po'
2025-04-22 17:58:56,432 wheel INFO adding 'django/contrib/admin/migrations/0001_initial.py'
2025-04-22 17:58:56,433 wheel INFO adding 'django/contrib/admin/migrations/0002_logentry_remove_auto_add.py'
2025-04-22 17:58:56,433 wheel INFO adding 'django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py'
2025-04-22 17:58:56,433 wheel INFO adding 'django/contrib/admin/migrations/__init__.py'
2025-04-22 17:58:56,433 wheel INFO adding 'django/contrib/admin/static/admin/css/autocomplete.css'
2025-04-22 17:58:56,433 wheel INFO adding 'django/contrib/admin/static/admin/css/base.css'
2025-04-22 17:58:56,434 wheel INFO adding 'django/contrib/admin/static/admin/css/changelists.css'
2025-04-22 17:58:56,434 wheel INFO adding 'django/contrib/admin/static/admin/css/dark_mode.css'
2025-04-22 17:58:56,434 wheel INFO adding 'django/contrib/admin/static/admin/css/dashboard.css'
2025-04-22 17:58:56,434 wheel INFO adding 'django/contrib/admin/static/admin/css/forms.css'
2025-04-22 17:58:56,434 wheel INFO adding 'django/contrib/admin/static/admin/css/login.css'
2025-04-22 17:58:56,435 wheel INFO adding 'django/contrib/admin/static/admin/css/nav_sidebar.css'
2025-04-22 17:58:56,435 wheel INFO adding 'django/contrib/admin/static/admin/css/responsive.css'
2025-04-22 17:58:56,435 wheel INFO adding 'django/contrib/admin/static/admin/css/responsive_rtl.css'
2025-04-22 17:58:56,435 wheel INFO adding 'django/contrib/admin/static/admin/css/rtl.css'
2025-04-22 17:58:56,435 wheel INFO adding 'django/contrib/admin/static/admin/css/widgets.css'
2025-04-22 17:58:56,436 wheel INFO adding 'django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md'
2025-04-22 17:58:56,436 wheel INFO adding 'django/contrib/admin/static/admin/css/vendor/select2/select2.css'
2025-04-22 17:58:56,436 wheel INFO adding 'django/contrib/admin/static/admin/css/vendor/select2/select2.min.css'
2025-04-22 17:58:56,436 wheel INFO adding 'django/contrib/admin/static/admin/img/LICENSE'
2025-04-22 17:58:56,436 wheel INFO adding 'django/contrib/admin/static/admin/img/README.txt'
2025-04-22 17:58:56,437 wheel INFO adding 'django/contrib/admin/static/admin/img/calendar-icons.svg'
2025-04-22 17:58:56,437 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-addlink.svg'
2025-04-22 17:58:56,437 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-alert.svg'
2025-04-22 17:58:56,437 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-calendar.svg'
2025-04-22 17:58:56,437 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-changelink.svg'
2025-04-22 17:58:56,437 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-clock.svg'
2025-04-22 17:58:56,438 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-deletelink.svg'
2025-04-22 17:58:56,438 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-no.svg'
2025-04-22 17:58:56,438 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-unknown-alt.svg'
2025-04-22 17:58:56,438 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-unknown.svg'
2025-04-22 17:58:56,438 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-viewlink.svg'
2025-04-22 17:58:56,438 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-yes.svg'
2025-04-22 17:58:56,438 wheel INFO adding 'django/contrib/admin/static/admin/img/inline-delete.svg'
2025-04-22 17:58:56,439 wheel INFO adding 'django/contrib/admin/static/admin/img/search.svg'
2025-04-22 17:58:56,439 wheel INFO adding 'django/contrib/admin/static/admin/img/selector-icons.svg'
2025-04-22 17:58:56,439 wheel INFO adding 'django/contrib/admin/static/admin/img/sorting-icons.svg'
2025-04-22 17:58:56,439 wheel INFO adding 'django/contrib/admin/static/admin/img/tooltag-add.svg'
2025-04-22 17:58:56,439 wheel INFO adding 'django/contrib/admin/static/admin/img/tooltag-arrowright.svg'
2025-04-22 17:58:56,440 wheel INFO adding 'django/contrib/admin/static/admin/img/gis/move_vertex_off.svg'
2025-04-22 17:58:56,440 wheel INFO adding 'django/contrib/admin/static/admin/img/gis/move_vertex_on.svg'
2025-04-22 17:58:56,440 wheel INFO adding 'django/contrib/admin/static/admin/js/SelectBox.js'
2025-04-22 17:58:56,440 wheel INFO adding 'django/contrib/admin/static/admin/js/SelectFilter2.js'
2025-04-22 17:58:56,441 wheel INFO adding 'django/contrib/admin/static/admin/js/actions.js'
2025-04-22 17:58:56,441 wheel INFO adding 'django/contrib/admin/static/admin/js/autocomplete.js'
2025-04-22 17:58:56,441 wheel INFO adding 'django/contrib/admin/static/admin/js/calendar.js'
2025-04-22 17:58:56,441 wheel INFO adding 'django/contrib/admin/static/admin/js/cancel.js'
2025-04-22 17:58:56,441 wheel INFO adding 'django/contrib/admin/static/admin/js/change_form.js'
2025-04-22 17:58:56,441 wheel INFO adding 'django/contrib/admin/static/admin/js/collapse.js'
2025-04-22 17:58:56,442 wheel INFO adding 'django/contrib/admin/static/admin/js/core.js'
2025-04-22 17:58:56,442 wheel INFO adding 'django/contrib/admin/static/admin/js/filters.js'
2025-04-22 17:58:56,442 wheel INFO adding 'django/contrib/admin/static/admin/js/inlines.js'
2025-04-22 17:58:56,442 wheel INFO adding 'django/contrib/admin/static/admin/js/jquery.init.js'
2025-04-22 17:58:56,442 wheel INFO adding 'django/contrib/admin/static/admin/js/nav_sidebar.js'
2025-04-22 17:58:56,443 wheel INFO adding 'django/contrib/admin/static/admin/js/popup_response.js'
2025-04-22 17:58:56,443 wheel INFO adding 'django/contrib/admin/static/admin/js/prepopulate.js'
2025-04-22 17:58:56,443 wheel INFO adding 'django/contrib/admin/static/admin/js/prepopulate_init.js'
2025-04-22 17:58:56,443 wheel INFO adding 'django/contrib/admin/static/admin/js/theme.js'
2025-04-22 17:58:56,443 wheel INFO adding 'django/contrib/admin/static/admin/js/urlify.js'
2025-04-22 17:58:56,444 wheel INFO adding 'django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js'
2025-04-22 17:58:56,444 wheel INFO adding 'django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js'
2025-04-22 17:58:56,444 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt'
2025-04-22 17:58:56,445 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/jquery/jquery.js'
2025-04-22 17:58:56,445 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js'
2025-04-22 17:58:56,446 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md'
2025-04-22 17:58:56,446 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/select2.full.js'
2025-04-22 17:58:56,447 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js'
2025-04-22 17:58:56,447 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js'
2025-04-22 17:58:56,447 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js'
2025-04-22 17:58:56,448 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js'
2025-04-22 17:58:56,448 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js'
2025-04-22 17:58:56,448 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js'
2025-04-22 17:58:56,448 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js'
2025-04-22 17:58:56,448 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js'
2025-04-22 17:58:56,448 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js'
2025-04-22 17:58:56,449 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js'
2025-04-22 17:58:56,449 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js'
2025-04-22 17:58:56,449 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js'
2025-04-22 17:58:56,449 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js'
2025-04-22 17:58:56,449 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js'
2025-04-22 17:58:56,449 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js'
2025-04-22 17:58:56,450 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js'
2025-04-22 17:58:56,450 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js'
2025-04-22 17:58:56,450 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js'
2025-04-22 17:58:56,450 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js'
2025-04-22 17:58:56,450 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js'
2025-04-22 17:58:56,450 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js'
2025-04-22 17:58:56,451 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js'
2025-04-22 17:58:56,451 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js'
2025-04-22 17:58:56,451 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js'
2025-04-22 17:58:56,451 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js'
2025-04-22 17:58:56,451 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js'
2025-04-22 17:58:56,451 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js'
2025-04-22 17:58:56,452 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js'
2025-04-22 17:58:56,452 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js'
2025-04-22 17:58:56,452 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js'
2025-04-22 17:58:56,452 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js'
2025-04-22 17:58:56,452 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js'
2025-04-22 17:58:56,452 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js'
2025-04-22 17:58:56,453 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js'
2025-04-22 17:58:56,453 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js'
2025-04-22 17:58:56,453 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js'
2025-04-22 17:58:56,453 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js'
2025-04-22 17:58:56,453 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js'
2025-04-22 17:58:56,453 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js'
2025-04-22 17:58:56,454 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js'
2025-04-22 17:58:56,454 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js'
2025-04-22 17:58:56,454 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js'
2025-04-22 17:58:56,454 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js'
2025-04-22 17:58:56,454 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js'
2025-04-22 17:58:56,454 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js'
2025-04-22 17:58:56,454 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js'
2025-04-22 17:58:56,455 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js'
2025-04-22 17:58:56,455 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js'
2025-04-22 17:58:56,455 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js'
2025-04-22 17:58:56,455 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js'
2025-04-22 17:58:56,455 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js'
2025-04-22 17:58:56,455 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js'
2025-04-22 17:58:56,456 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js'
2025-04-22 17:58:56,456 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js'
2025-04-22 17:58:56,456 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js'
2025-04-22 17:58:56,456 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js'
2025-04-22 17:58:56,456 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js'
2025-04-22 17:58:56,456 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js'
2025-04-22 17:58:56,457 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js'
2025-04-22 17:58:56,457 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js'
2025-04-22 17:58:56,457 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt'
2025-04-22 17:58:56,458 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js'
2025-04-22 17:58:56,458 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js'
2025-04-22 17:58:56,459 wheel INFO adding 'django/contrib/admin/templates/admin/404.html'
2025-04-22 17:58:56,459 wheel INFO adding 'django/contrib/admin/templates/admin/500.html'
2025-04-22 17:58:56,459 wheel INFO adding 'django/contrib/admin/templates/admin/actions.html'
2025-04-22 17:58:56,459 wheel INFO adding 'django/contrib/admin/templates/admin/app_index.html'
2025-04-22 17:58:56,460 wheel INFO adding 'django/contrib/admin/templates/admin/app_list.html'
2025-04-22 17:58:56,460 wheel INFO adding 'django/contrib/admin/templates/admin/base.html'
2025-04-22 17:58:56,460 wheel INFO adding 'django/contrib/admin/templates/admin/base_site.html'
2025-04-22 17:58:56,460 wheel INFO adding 'django/contrib/admin/templates/admin/change_form.html'
2025-04-22 17:58:56,460 wheel INFO adding 'django/contrib/admin/templates/admin/change_form_object_tools.html'
2025-04-22 17:58:56,460 wheel INFO adding 'django/contrib/admin/templates/admin/change_list.html'
2025-04-22 17:58:56,461 wheel INFO adding 'django/contrib/admin/templates/admin/change_list_object_tools.html'
2025-04-22 17:58:56,461 wheel INFO adding 'django/contrib/admin/templates/admin/change_list_results.html'
2025-04-22 17:58:56,461 wheel INFO adding 'django/contrib/admin/templates/admin/color_theme_toggle.html'
2025-04-22 17:58:56,461 wheel INFO adding 'django/contrib/admin/templates/admin/date_hierarchy.html'
2025-04-22 17:58:56,461 wheel INFO adding 'django/contrib/admin/templates/admin/delete_confirmation.html'
2025-04-22 17:58:56,461 wheel INFO adding 'django/contrib/admin/templates/admin/delete_selected_confirmation.html'
2025-04-22 17:58:56,462 wheel INFO adding 'django/contrib/admin/templates/admin/filter.html'
2025-04-22 17:58:56,462 wheel INFO adding 'django/contrib/admin/templates/admin/index.html'
2025-04-22 17:58:56,462 wheel INFO adding 'django/contrib/admin/templates/admin/invalid_setup.html'
2025-04-22 17:58:56,462 wheel INFO adding 'django/contrib/admin/templates/admin/login.html'
2025-04-22 17:58:56,462 wheel INFO adding 'django/contrib/admin/templates/admin/nav_sidebar.html'
2025-04-22 17:58:56,462 wheel INFO adding 'django/contrib/admin/templates/admin/object_history.html'
2025-04-22 17:58:56,463 wheel INFO adding 'django/contrib/admin/templates/admin/pagination.html'
2025-04-22 17:58:56,463 wheel INFO adding 'django/contrib/admin/templates/admin/popup_response.html'
2025-04-22 17:58:56,463 wheel INFO adding 'django/contrib/admin/templates/admin/prepopulated_fields_js.html'
2025-04-22 17:58:56,463 wheel INFO adding 'django/contrib/admin/templates/admin/search_form.html'
2025-04-22 17:58:56,463 wheel INFO adding 'django/contrib/admin/templates/admin/submit_line.html'
2025-04-22 17:58:56,463 wheel INFO adding 'django/contrib/admin/templates/admin/auth/user/add_form.html'
2025-04-22 17:58:56,464 wheel INFO adding 'django/contrib/admin/templates/admin/auth/user/change_password.html'
2025-04-22 17:58:56,464 wheel INFO adding 'django/contrib/admin/templates/admin/edit_inline/stacked.html'
2025-04-22 17:58:56,464 wheel INFO adding 'django/contrib/admin/templates/admin/edit_inline/tabular.html'
2025-04-22 17:58:56,464 wheel INFO adding 'django/contrib/admin/templates/admin/includes/fieldset.html'
2025-04-22 17:58:56,464 wheel INFO adding 'django/contrib/admin/templates/admin/includes/object_delete_summary.html'
2025-04-22 17:58:56,465 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/clearable_file_input.html'
2025-04-22 17:58:56,465 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/date.html'
2025-04-22 17:58:56,465 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html'
2025-04-22 17:58:56,465 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html'
2025-04-22 17:58:56,465 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/radio.html'
2025-04-22 17:58:56,465 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html'
2025-04-22 17:58:56,465 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/split_datetime.html'
2025-04-22 17:58:56,466 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/time.html'
2025-04-22 17:58:56,466 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/url.html'
2025-04-22 17:58:56,466 wheel INFO adding 'django/contrib/admin/templates/registration/logged_out.html'
2025-04-22 17:58:56,466 wheel INFO adding 'django/contrib/admin/templates/registration/password_change_done.html'
2025-04-22 17:58:56,466 wheel INFO adding 'django/contrib/admin/templates/registration/password_change_form.html'
2025-04-22 17:58:56,467 wheel INFO adding 'django/contrib/admin/templates/registration/password_reset_complete.html'
2025-04-22 17:58:56,467 wheel INFO adding 'django/contrib/admin/templates/registration/password_reset_confirm.html'
2025-04-22 17:58:56,467 wheel INFO adding 'django/contrib/admin/templates/registration/password_reset_done.html'
2025-04-22 17:58:56,467 wheel INFO adding 'django/contrib/admin/templates/registration/password_reset_email.html'
2025-04-22 17:58:56,467 wheel INFO adding 'django/contrib/admin/templates/registration/password_reset_form.html'
2025-04-22 17:58:56,467 wheel INFO adding 'django/contrib/admin/templatetags/__init__.py'
2025-04-22 17:58:56,468 wheel INFO adding 'django/contrib/admin/templatetags/admin_list.py'
2025-04-22 17:58:56,468 wheel INFO adding 'django/contrib/admin/templatetags/admin_modify.py'
2025-04-22 17:58:56,468 wheel INFO adding 'django/contrib/admin/templatetags/admin_urls.py'
2025-04-22 17:58:56,468 wheel INFO adding 'django/contrib/admin/templatetags/base.py'
2025-04-22 17:58:56,468 wheel INFO adding 'django/contrib/admin/templatetags/log.py'
2025-04-22 17:58:56,468 wheel INFO adding 'django/contrib/admin/views/__init__.py'
2025-04-22 17:58:56,469 wheel INFO adding 'django/contrib/admin/views/autocomplete.py'
2025-04-22 17:58:56,469 wheel INFO adding 'django/contrib/admin/views/decorators.py'
2025-04-22 17:58:56,469 wheel INFO adding 'django/contrib/admin/views/main.py'
2025-04-22 17:58:56,469 wheel INFO adding 'django/contrib/admindocs/__init__.py'
2025-04-22 17:58:56,469 wheel INFO adding 'django/contrib/admindocs/apps.py'
2025-04-22 17:58:56,470 wheel INFO adding 'django/contrib/admindocs/middleware.py'
2025-04-22 17:58:56,470 wheel INFO adding 'django/contrib/admindocs/urls.py'
2025-04-22 17:58:56,470 wheel INFO adding 'django/contrib/admindocs/utils.py'
2025-04-22 17:58:56,470 wheel INFO adding 'django/contrib/admindocs/views.py'
2025-04-22 17:58:56,471 wheel INFO adding 'django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,471 wheel INFO adding 'django/contrib/admindocs/locale/af/LC_MESSAGES/django.po'
2025-04-22 17:58:56,472 wheel INFO adding 'django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,473 wheel INFO adding 'django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po'
2025-04-22 17:58:56,474 wheel INFO adding 'django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,474 wheel INFO adding 'django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 17:58:56,474 wheel INFO adding 'django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,474 wheel INFO adding 'django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po'
2025-04-22 17:58:56,475 wheel INFO adding 'django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,475 wheel INFO adding 'django/contrib/admindocs/locale/az/LC_MESSAGES/django.po'
2025-04-22 17:58:56,475 wheel INFO adding 'django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,475 wheel INFO adding 'django/contrib/admindocs/locale/be/LC_MESSAGES/django.po'
2025-04-22 17:58:56,476 wheel INFO adding 'django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,476 wheel INFO adding 'django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,476 wheel INFO adding 'django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,476 wheel INFO adding 'django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,476 wheel INFO adding 'django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,477 wheel INFO adding 'django/contrib/admindocs/locale/br/LC_MESSAGES/django.po'
2025-04-22 17:58:56,477 wheel INFO adding 'django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,477 wheel INFO adding 'django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,477 wheel INFO adding 'django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,477 wheel INFO adding 'django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po'
2025-04-22 17:58:56,478 wheel INFO adding 'django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,478 wheel INFO adding 'django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,478 wheel INFO adding 'django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,478 wheel INFO adding 'django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,479 wheel INFO adding 'django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,479 wheel INFO adding 'django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,479 wheel INFO adding 'django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,479 wheel INFO adding 'django/contrib/admindocs/locale/da/LC_MESSAGES/django.po'
2025-04-22 17:58:56,479 wheel INFO adding 'django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,480 wheel INFO adding 'django/contrib/admindocs/locale/de/LC_MESSAGES/django.po'
2025-04-22 17:58:56,480 wheel INFO adding 'django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,480 wheel INFO adding 'django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,480 wheel INFO adding 'django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,480 wheel INFO adding 'django/contrib/admindocs/locale/el/LC_MESSAGES/django.po'
2025-04-22 17:58:56,481 wheel INFO adding 'django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,481 wheel INFO adding 'django/contrib/admindocs/locale/en/LC_MESSAGES/django.po'
2025-04-22 17:58:56,481 wheel INFO adding 'django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,481 wheel INFO adding 'django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 17:58:56,482 wheel INFO adding 'django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,482 wheel INFO adding 'django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 17:58:56,482 wheel INFO adding 'django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,482 wheel INFO adding 'django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po'
2025-04-22 17:58:56,482 wheel INFO adding 'django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,483 wheel INFO adding 'django/contrib/admindocs/locale/es/LC_MESSAGES/django.po'
2025-04-22 17:58:56,483 wheel INFO adding 'django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,483 wheel INFO adding 'django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,483 wheel INFO adding 'django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,483 wheel INFO adding 'django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 17:58:56,484 wheel INFO adding 'django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,484 wheel INFO adding 'django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 17:58:56,484 wheel INFO adding 'django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,484 wheel INFO adding 'django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 17:58:56,485 wheel INFO adding 'django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,485 wheel INFO adding 'django/contrib/admindocs/locale/et/LC_MESSAGES/django.po'
2025-04-22 17:58:56,485 wheel INFO adding 'django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,485 wheel INFO adding 'django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,485 wheel INFO adding 'django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,486 wheel INFO adding 'django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,486 wheel INFO adding 'django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,486 wheel INFO adding 'django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,486 wheel INFO adding 'django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,487 wheel INFO adding 'django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,487 wheel INFO adding 'django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,487 wheel INFO adding 'django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,487 wheel INFO adding 'django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,487 wheel INFO adding 'django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po'
2025-04-22 17:58:56,488 wheel INFO adding 'django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,488 wheel INFO adding 'django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po'
2025-04-22 17:58:56,488 wheel INFO adding 'django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,488 wheel INFO adding 'django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,489 wheel INFO adding 'django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,489 wheel INFO adding 'django/contrib/admindocs/locale/he/LC_MESSAGES/django.po'
2025-04-22 17:58:56,489 wheel INFO adding 'django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,489 wheel INFO adding 'django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,489 wheel INFO adding 'django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,490 wheel INFO adding 'django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,490 wheel INFO adding 'django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,490 wheel INFO adding 'django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,490 wheel INFO adding 'django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,490 wheel INFO adding 'django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,491 wheel INFO adding 'django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,491 wheel INFO adding 'django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po'
2025-04-22 17:58:56,491 wheel INFO adding 'django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,491 wheel INFO adding 'django/contrib/admindocs/locale/id/LC_MESSAGES/django.po'
2025-04-22 17:58:56,491 wheel INFO adding 'django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,492 wheel INFO adding 'django/contrib/admindocs/locale/io/LC_MESSAGES/django.po'
2025-04-22 17:58:56,492 wheel INFO adding 'django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,492 wheel INFO adding 'django/contrib/admindocs/locale/is/LC_MESSAGES/django.po'
2025-04-22 17:58:56,492 wheel INFO adding 'django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,492 wheel INFO adding 'django/contrib/admindocs/locale/it/LC_MESSAGES/django.po'
2025-04-22 17:58:56,493 wheel INFO adding 'django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,493 wheel INFO adding 'django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po'
2025-04-22 17:58:56,493 wheel INFO adding 'django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,493 wheel INFO adding 'django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po'
2025-04-22 17:58:56,494 wheel INFO adding 'django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,494 wheel INFO adding 'django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po'
2025-04-22 17:58:56,494 wheel INFO adding 'django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,494 wheel INFO adding 'django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,494 wheel INFO adding 'django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,495 wheel INFO adding 'django/contrib/admindocs/locale/km/LC_MESSAGES/django.po'
2025-04-22 17:58:56,495 wheel INFO adding 'django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,495 wheel INFO adding 'django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,495 wheel INFO adding 'django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,495 wheel INFO adding 'django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po'
2025-04-22 17:58:56,496 wheel INFO adding 'django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,496 wheel INFO adding 'django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po'
2025-04-22 17:58:56,496 wheel INFO adding 'django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,496 wheel INFO adding 'django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,497 wheel INFO adding 'django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,497 wheel INFO adding 'django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,497 wheel INFO adding 'django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,497 wheel INFO adding 'django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,497 wheel INFO adding 'django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,498 wheel INFO adding 'django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,498 wheel INFO adding 'django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,498 wheel INFO adding 'django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po'
2025-04-22 17:58:56,498 wheel INFO adding 'django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,498 wheel INFO adding 'django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,499 wheel INFO adding 'django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,499 wheel INFO adding 'django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,499 wheel INFO adding 'django/contrib/admindocs/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,499 wheel INFO adding 'django/contrib/admindocs/locale/ms/LC_MESSAGES/django.po'
2025-04-22 17:58:56,500 wheel INFO adding 'django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,500 wheel INFO adding 'django/contrib/admindocs/locale/my/LC_MESSAGES/django.po'
2025-04-22 17:58:56,500 wheel INFO adding 'django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,500 wheel INFO adding 'django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,500 wheel INFO adding 'django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,501 wheel INFO adding 'django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po'
2025-04-22 17:58:56,501 wheel INFO adding 'django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,501 wheel INFO adding 'django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,501 wheel INFO adding 'django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,502 wheel INFO adding 'django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,502 wheel INFO adding 'django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,502 wheel INFO adding 'django/contrib/admindocs/locale/os/LC_MESSAGES/django.po'
2025-04-22 17:58:56,502 wheel INFO adding 'django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,503 wheel INFO adding 'django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,503 wheel INFO adding 'django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,503 wheel INFO adding 'django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,503 wheel INFO adding 'django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,504 wheel INFO adding 'django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,504 wheel INFO adding 'django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,504 wheel INFO adding 'django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,505 wheel INFO adding 'django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,505 wheel INFO adding 'django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po'
2025-04-22 17:58:56,505 wheel INFO adding 'django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,505 wheel INFO adding 'django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po'
2025-04-22 17:58:56,506 wheel INFO adding 'django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,506 wheel INFO adding 'django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,506 wheel INFO adding 'django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,507 wheel INFO adding 'django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,507 wheel INFO adding 'django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,507 wheel INFO adding 'django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po'
2025-04-22 17:58:56,507 wheel INFO adding 'django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,508 wheel INFO adding 'django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,508 wheel INFO adding 'django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,508 wheel INFO adding 'django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,508 wheel INFO adding 'django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,509 wheel INFO adding 'django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,509 wheel INFO adding 'django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,509 wheel INFO adding 'django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po'
2025-04-22 17:58:56,509 wheel INFO adding 'django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,510 wheel INFO adding 'django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po'
2025-04-22 17:58:56,510 wheel INFO adding 'django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,510 wheel INFO adding 'django/contrib/admindocs/locale/te/LC_MESSAGES/django.po'
2025-04-22 17:58:56,510 wheel INFO adding 'django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,511 wheel INFO adding 'django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,511 wheel INFO adding 'django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,511 wheel INFO adding 'django/contrib/admindocs/locale/th/LC_MESSAGES/django.po'
2025-04-22 17:58:56,512 wheel INFO adding 'django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,512 wheel INFO adding 'django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,512 wheel INFO adding 'django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,512 wheel INFO adding 'django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,513 wheel INFO adding 'django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,513 wheel INFO adding 'django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po'
2025-04-22 17:58:56,513 wheel INFO adding 'django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,513 wheel INFO adding 'django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,514 wheel INFO adding 'django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,514 wheel INFO adding 'django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po'
2025-04-22 17:58:56,514 wheel INFO adding 'django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,514 wheel INFO adding 'django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,515 wheel INFO adding 'django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,515 wheel INFO adding 'django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 17:58:56,515 wheel INFO adding 'django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,515 wheel INFO adding 'django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 17:58:56,515 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/bookmarklets.html'
2025-04-22 17:58:56,516 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/index.html'
2025-04-22 17:58:56,516 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/missing_docutils.html'
2025-04-22 17:58:56,516 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/model_detail.html'
2025-04-22 17:58:56,516 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/model_index.html'
2025-04-22 17:58:56,516 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/template_detail.html'
2025-04-22 17:58:56,516 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/template_filter_index.html'
2025-04-22 17:58:56,517 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/template_tag_index.html'
2025-04-22 17:58:56,517 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/view_detail.html'
2025-04-22 17:58:56,517 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/view_index.html'
2025-04-22 17:58:56,517 wheel INFO adding 'django/contrib/auth/__init__.py'
2025-04-22 17:58:56,517 wheel INFO adding 'django/contrib/auth/admin.py'
2025-04-22 17:58:56,518 wheel INFO adding 'django/contrib/auth/apps.py'
2025-04-22 17:58:56,518 wheel INFO adding 'django/contrib/auth/backends.py'
2025-04-22 17:58:56,518 wheel INFO adding 'django/contrib/auth/base_user.py'
2025-04-22 17:58:56,518 wheel INFO adding 'django/contrib/auth/checks.py'
2025-04-22 17:58:56,518 wheel INFO adding 'django/contrib/auth/common-passwords.txt.gz'
2025-04-22 17:58:56,519 wheel INFO adding 'django/contrib/auth/context_processors.py'
2025-04-22 17:58:56,519 wheel INFO adding 'django/contrib/auth/decorators.py'
2025-04-22 17:58:56,519 wheel INFO adding 'django/contrib/auth/forms.py'
2025-04-22 17:58:56,519 wheel INFO adding 'django/contrib/auth/hashers.py'
2025-04-22 17:58:56,520 wheel INFO adding 'django/contrib/auth/middleware.py'
2025-04-22 17:58:56,520 wheel INFO adding 'django/contrib/auth/mixins.py'
2025-04-22 17:58:56,520 wheel INFO adding 'django/contrib/auth/models.py'
2025-04-22 17:58:56,520 wheel INFO adding 'django/contrib/auth/password_validation.py'
2025-04-22 17:58:56,520 wheel INFO adding 'django/contrib/auth/signals.py'
2025-04-22 17:58:56,521 wheel INFO adding 'django/contrib/auth/tokens.py'
2025-04-22 17:58:56,521 wheel INFO adding 'django/contrib/auth/urls.py'
2025-04-22 17:58:56,521 wheel INFO adding 'django/contrib/auth/validators.py'
2025-04-22 17:58:56,521 wheel INFO adding 'django/contrib/auth/views.py'
2025-04-22 17:58:56,521 wheel INFO adding 'django/contrib/auth/handlers/__init__.py'
2025-04-22 17:58:56,522 wheel INFO adding 'django/contrib/auth/handlers/modwsgi.py'
2025-04-22 17:58:56,522 wheel INFO adding 'django/contrib/auth/locale/af/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,523 wheel INFO adding 'django/contrib/auth/locale/af/LC_MESSAGES/django.po'
2025-04-22 17:58:56,523 wheel INFO adding 'django/contrib/auth/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,523 wheel INFO adding 'django/contrib/auth/locale/ar/LC_MESSAGES/django.po'
2025-04-22 17:58:56,523 wheel INFO adding 'django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,524 wheel INFO adding 'django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 17:58:56,524 wheel INFO adding 'django/contrib/auth/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,524 wheel INFO adding 'django/contrib/auth/locale/ast/LC_MESSAGES/django.po'
2025-04-22 17:58:56,524 wheel INFO adding 'django/contrib/auth/locale/az/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,524 wheel INFO adding 'django/contrib/auth/locale/az/LC_MESSAGES/django.po'
2025-04-22 17:58:56,525 wheel INFO adding 'django/contrib/auth/locale/be/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,525 wheel INFO adding 'django/contrib/auth/locale/be/LC_MESSAGES/django.po'
2025-04-22 17:58:56,525 wheel INFO adding 'django/contrib/auth/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,525 wheel INFO adding 'django/contrib/auth/locale/bg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,526 wheel INFO adding 'django/contrib/auth/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,526 wheel INFO adding 'django/contrib/auth/locale/bn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,526 wheel INFO adding 'django/contrib/auth/locale/br/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,526 wheel INFO adding 'django/contrib/auth/locale/br/LC_MESSAGES/django.po'
2025-04-22 17:58:56,527 wheel INFO adding 'django/contrib/auth/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,527 wheel INFO adding 'django/contrib/auth/locale/bs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,527 wheel INFO adding 'django/contrib/auth/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,527 wheel INFO adding 'django/contrib/auth/locale/ca/LC_MESSAGES/django.po'
2025-04-22 17:58:56,527 wheel INFO adding 'django/contrib/auth/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,528 wheel INFO adding 'django/contrib/auth/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,528 wheel INFO adding 'django/contrib/auth/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,528 wheel INFO adding 'django/contrib/auth/locale/cs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,528 wheel INFO adding 'django/contrib/auth/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,528 wheel INFO adding 'django/contrib/auth/locale/cy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,529 wheel INFO adding 'django/contrib/auth/locale/da/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,529 wheel INFO adding 'django/contrib/auth/locale/da/LC_MESSAGES/django.po'
2025-04-22 17:58:56,529 wheel INFO adding 'django/contrib/auth/locale/de/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,529 wheel INFO adding 'django/contrib/auth/locale/de/LC_MESSAGES/django.po'
2025-04-22 17:58:56,530 wheel INFO adding 'django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,530 wheel INFO adding 'django/contrib/auth/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,530 wheel INFO adding 'django/contrib/auth/locale/el/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,530 wheel INFO adding 'django/contrib/auth/locale/el/LC_MESSAGES/django.po'
2025-04-22 17:58:56,531 wheel INFO adding 'django/contrib/auth/locale/en/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,531 wheel INFO adding 'django/contrib/auth/locale/en/LC_MESSAGES/django.po'
2025-04-22 17:58:56,531 wheel INFO adding 'django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,531 wheel INFO adding 'django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 17:58:56,531 wheel INFO adding 'django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,532 wheel INFO adding 'django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 17:58:56,532 wheel INFO adding 'django/contrib/auth/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,532 wheel INFO adding 'django/contrib/auth/locale/eo/LC_MESSAGES/django.po'
2025-04-22 17:58:56,532 wheel INFO adding 'django/contrib/auth/locale/es/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,532 wheel INFO adding 'django/contrib/auth/locale/es/LC_MESSAGES/django.po'
2025-04-22 17:58:56,533 wheel INFO adding 'django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,533 wheel INFO adding 'django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,533 wheel INFO adding 'django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,533 wheel INFO adding 'django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 17:58:56,534 wheel INFO adding 'django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,534 wheel INFO adding 'django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 17:58:56,534 wheel INFO adding 'django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,534 wheel INFO adding 'django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 17:58:56,534 wheel INFO adding 'django/contrib/auth/locale/et/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,535 wheel INFO adding 'django/contrib/auth/locale/et/LC_MESSAGES/django.po'
2025-04-22 17:58:56,535 wheel INFO adding 'django/contrib/auth/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,535 wheel INFO adding 'django/contrib/auth/locale/eu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,535 wheel INFO adding 'django/contrib/auth/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,536 wheel INFO adding 'django/contrib/auth/locale/fa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,536 wheel INFO adding 'django/contrib/auth/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,536 wheel INFO adding 'django/contrib/auth/locale/fi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,536 wheel INFO adding 'django/contrib/auth/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,536 wheel INFO adding 'django/contrib/auth/locale/fr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,537 wheel INFO adding 'django/contrib/auth/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,537 wheel INFO adding 'django/contrib/auth/locale/fy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,537 wheel INFO adding 'django/contrib/auth/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,537 wheel INFO adding 'django/contrib/auth/locale/ga/LC_MESSAGES/django.po'
2025-04-22 17:58:56,538 wheel INFO adding 'django/contrib/auth/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,538 wheel INFO adding 'django/contrib/auth/locale/gd/LC_MESSAGES/django.po'
2025-04-22 17:58:56,538 wheel INFO adding 'django/contrib/auth/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,538 wheel INFO adding 'django/contrib/auth/locale/gl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,538 wheel INFO adding 'django/contrib/auth/locale/he/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,539 wheel INFO adding 'django/contrib/auth/locale/he/LC_MESSAGES/django.po'
2025-04-22 17:58:56,539 wheel INFO adding 'django/contrib/auth/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,539 wheel INFO adding 'django/contrib/auth/locale/hi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,539 wheel INFO adding 'django/contrib/auth/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,539 wheel INFO adding 'django/contrib/auth/locale/hr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,540 wheel INFO adding 'django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,540 wheel INFO adding 'django/contrib/auth/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,540 wheel INFO adding 'django/contrib/auth/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,540 wheel INFO adding 'django/contrib/auth/locale/hu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,541 wheel INFO adding 'django/contrib/auth/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,541 wheel INFO adding 'django/contrib/auth/locale/hy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,541 wheel INFO adding 'django/contrib/auth/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,541 wheel INFO adding 'django/contrib/auth/locale/ia/LC_MESSAGES/django.po'
2025-04-22 17:58:56,541 wheel INFO adding 'django/contrib/auth/locale/id/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,542 wheel INFO adding 'django/contrib/auth/locale/id/LC_MESSAGES/django.po'
2025-04-22 17:58:56,542 wheel INFO adding 'django/contrib/auth/locale/io/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,542 wheel INFO adding 'django/contrib/auth/locale/io/LC_MESSAGES/django.po'
2025-04-22 17:58:56,542 wheel INFO adding 'django/contrib/auth/locale/is/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,542 wheel INFO adding 'django/contrib/auth/locale/is/LC_MESSAGES/django.po'
2025-04-22 17:58:56,543 wheel INFO adding 'django/contrib/auth/locale/it/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,543 wheel INFO adding 'django/contrib/auth/locale/it/LC_MESSAGES/django.po'
2025-04-22 17:58:56,543 wheel INFO adding 'django/contrib/auth/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,543 wheel INFO adding 'django/contrib/auth/locale/ja/LC_MESSAGES/django.po'
2025-04-22 17:58:56,544 wheel INFO adding 'django/contrib/auth/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,544 wheel INFO adding 'django/contrib/auth/locale/ka/LC_MESSAGES/django.po'
2025-04-22 17:58:56,544 wheel INFO adding 'django/contrib/auth/locale/kab/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,544 wheel INFO adding 'django/contrib/auth/locale/kab/LC_MESSAGES/django.po'
2025-04-22 17:58:56,544 wheel INFO adding 'django/contrib/auth/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,545 wheel INFO adding 'django/contrib/auth/locale/kk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,545 wheel INFO adding 'django/contrib/auth/locale/km/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,545 wheel INFO adding 'django/contrib/auth/locale/km/LC_MESSAGES/django.po'
2025-04-22 17:58:56,545 wheel INFO adding 'django/contrib/auth/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,546 wheel INFO adding 'django/contrib/auth/locale/kn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,546 wheel INFO adding 'django/contrib/auth/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,546 wheel INFO adding 'django/contrib/auth/locale/ko/LC_MESSAGES/django.po'
2025-04-22 17:58:56,546 wheel INFO adding 'django/contrib/auth/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,546 wheel INFO adding 'django/contrib/auth/locale/ky/LC_MESSAGES/django.po'
2025-04-22 17:58:56,547 wheel INFO adding 'django/contrib/auth/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,547 wheel INFO adding 'django/contrib/auth/locale/lb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,547 wheel INFO adding 'django/contrib/auth/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,547 wheel INFO adding 'django/contrib/auth/locale/lt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,548 wheel INFO adding 'django/contrib/auth/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,548 wheel INFO adding 'django/contrib/auth/locale/lv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,548 wheel INFO adding 'django/contrib/auth/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,548 wheel INFO adding 'django/contrib/auth/locale/mk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,548 wheel INFO adding 'django/contrib/auth/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,549 wheel INFO adding 'django/contrib/auth/locale/ml/LC_MESSAGES/django.po'
2025-04-22 17:58:56,549 wheel INFO adding 'django/contrib/auth/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,549 wheel INFO adding 'django/contrib/auth/locale/mn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,550 wheel INFO adding 'django/contrib/auth/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,550 wheel INFO adding 'django/contrib/auth/locale/mr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,550 wheel INFO adding 'django/contrib/auth/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,550 wheel INFO adding 'django/contrib/auth/locale/ms/LC_MESSAGES/django.po'
2025-04-22 17:58:56,550 wheel INFO adding 'django/contrib/auth/locale/my/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,551 wheel INFO adding 'django/contrib/auth/locale/my/LC_MESSAGES/django.po'
2025-04-22 17:58:56,551 wheel INFO adding 'django/contrib/auth/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,551 wheel INFO adding 'django/contrib/auth/locale/nb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,551 wheel INFO adding 'django/contrib/auth/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,552 wheel INFO adding 'django/contrib/auth/locale/ne/LC_MESSAGES/django.po'
2025-04-22 17:58:56,552 wheel INFO adding 'django/contrib/auth/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,552 wheel INFO adding 'django/contrib/auth/locale/nl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,552 wheel INFO adding 'django/contrib/auth/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,553 wheel INFO adding 'django/contrib/auth/locale/nn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,553 wheel INFO adding 'django/contrib/auth/locale/os/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,553 wheel INFO adding 'django/contrib/auth/locale/os/LC_MESSAGES/django.po'
2025-04-22 17:58:56,553 wheel INFO adding 'django/contrib/auth/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,553 wheel INFO adding 'django/contrib/auth/locale/pa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,554 wheel INFO adding 'django/contrib/auth/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,554 wheel INFO adding 'django/contrib/auth/locale/pl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,554 wheel INFO adding 'django/contrib/auth/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,554 wheel INFO adding 'django/contrib/auth/locale/pt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,555 wheel INFO adding 'django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,555 wheel INFO adding 'django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,555 wheel INFO adding 'django/contrib/auth/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,555 wheel INFO adding 'django/contrib/auth/locale/ro/LC_MESSAGES/django.po'
2025-04-22 17:58:56,555 wheel INFO adding 'django/contrib/auth/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,556 wheel INFO adding 'django/contrib/auth/locale/ru/LC_MESSAGES/django.po'
2025-04-22 17:58:56,556 wheel INFO adding 'django/contrib/auth/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,556 wheel INFO adding 'django/contrib/auth/locale/sk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,556 wheel INFO adding 'django/contrib/auth/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,557 wheel INFO adding 'django/contrib/auth/locale/sl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,557 wheel INFO adding 'django/contrib/auth/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,557 wheel INFO adding 'django/contrib/auth/locale/sq/LC_MESSAGES/django.po'
2025-04-22 17:58:56,557 wheel INFO adding 'django/contrib/auth/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,557 wheel INFO adding 'django/contrib/auth/locale/sr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,558 wheel INFO adding 'django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,558 wheel INFO adding 'django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,558 wheel INFO adding 'django/contrib/auth/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,558 wheel INFO adding 'django/contrib/auth/locale/sv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,558 wheel INFO adding 'django/contrib/auth/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,559 wheel INFO adding 'django/contrib/auth/locale/sw/LC_MESSAGES/django.po'
2025-04-22 17:58:56,559 wheel INFO adding 'django/contrib/auth/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,559 wheel INFO adding 'django/contrib/auth/locale/ta/LC_MESSAGES/django.po'
2025-04-22 17:58:56,559 wheel INFO adding 'django/contrib/auth/locale/te/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,560 wheel INFO adding 'django/contrib/auth/locale/te/LC_MESSAGES/django.po'
2025-04-22 17:58:56,560 wheel INFO adding 'django/contrib/auth/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,560 wheel INFO adding 'django/contrib/auth/locale/tg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,560 wheel INFO adding 'django/contrib/auth/locale/th/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,560 wheel INFO adding 'django/contrib/auth/locale/th/LC_MESSAGES/django.po'
2025-04-22 17:58:56,561 wheel INFO adding 'django/contrib/auth/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,561 wheel INFO adding 'django/contrib/auth/locale/tk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,561 wheel INFO adding 'django/contrib/auth/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,561 wheel INFO adding 'django/contrib/auth/locale/tr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,561 wheel INFO adding 'django/contrib/auth/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,562 wheel INFO adding 'django/contrib/auth/locale/tt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,562 wheel INFO adding 'django/contrib/auth/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,562 wheel INFO adding 'django/contrib/auth/locale/udm/LC_MESSAGES/django.po'
2025-04-22 17:58:56,563 wheel INFO adding 'django/contrib/auth/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,563 wheel INFO adding 'django/contrib/auth/locale/uk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,563 wheel INFO adding 'django/contrib/auth/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,563 wheel INFO adding 'django/contrib/auth/locale/ur/LC_MESSAGES/django.po'
2025-04-22 17:58:56,563 wheel INFO adding 'django/contrib/auth/locale/uz/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,564 wheel INFO adding 'django/contrib/auth/locale/uz/LC_MESSAGES/django.po'
2025-04-22 17:58:56,564 wheel INFO adding 'django/contrib/auth/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,564 wheel INFO adding 'django/contrib/auth/locale/vi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,564 wheel INFO adding 'django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,564 wheel INFO adding 'django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 17:58:56,565 wheel INFO adding 'django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,565 wheel INFO adding 'django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 17:58:56,565 wheel INFO adding 'django/contrib/auth/management/__init__.py'
2025-04-22 17:58:56,565 wheel INFO adding 'django/contrib/auth/management/commands/__init__.py'
2025-04-22 17:58:56,565 wheel INFO adding 'django/contrib/auth/management/commands/changepassword.py'
2025-04-22 17:58:56,566 wheel INFO adding 'django/contrib/auth/management/commands/createsuperuser.py'
2025-04-22 17:58:56,566 wheel INFO adding 'django/contrib/auth/migrations/0001_initial.py'
2025-04-22 17:58:56,566 wheel INFO adding 'django/contrib/auth/migrations/0002_alter_permission_name_max_length.py'
2025-04-22 17:58:56,566 wheel INFO adding 'django/contrib/auth/migrations/0003_alter_user_email_max_length.py'
2025-04-22 17:58:56,566 wheel INFO adding 'django/contrib/auth/migrations/0004_alter_user_username_opts.py'
2025-04-22 17:58:56,567 wheel INFO adding 'django/contrib/auth/migrations/0005_alter_user_last_login_null.py'
2025-04-22 17:58:56,567 wheel INFO adding 'django/contrib/auth/migrations/0006_require_contenttypes_0002.py'
2025-04-22 17:58:56,567 wheel INFO adding 'django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py'
2025-04-22 17:58:56,567 wheel INFO adding 'django/contrib/auth/migrations/0008_alter_user_username_max_length.py'
2025-04-22 17:58:56,567 wheel INFO adding 'django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py'
2025-04-22 17:58:56,567 wheel INFO adding 'django/contrib/auth/migrations/0010_alter_group_name_max_length.py'
2025-04-22 17:58:56,568 wheel INFO adding 'django/contrib/auth/migrations/0011_update_proxy_permissions.py'
2025-04-22 17:58:56,568 wheel INFO adding 'django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py'
2025-04-22 17:58:56,568 wheel INFO adding 'django/contrib/auth/migrations/__init__.py'
2025-04-22 17:58:56,568 wheel INFO adding 'django/contrib/auth/templates/auth/widgets/read_only_password_hash.html'
2025-04-22 17:58:56,568 wheel INFO adding 'django/contrib/auth/templates/registration/password_reset_subject.txt'
2025-04-22 17:58:56,569 wheel INFO adding 'django/contrib/contenttypes/__init__.py'
2025-04-22 17:58:56,569 wheel INFO adding 'django/contrib/contenttypes/admin.py'
2025-04-22 17:58:56,569 wheel INFO adding 'django/contrib/contenttypes/apps.py'
2025-04-22 17:58:56,569 wheel INFO adding 'django/contrib/contenttypes/checks.py'
2025-04-22 17:58:56,569 wheel INFO adding 'django/contrib/contenttypes/fields.py'
2025-04-22 17:58:56,570 wheel INFO adding 'django/contrib/contenttypes/forms.py'
2025-04-22 17:58:56,570 wheel INFO adding 'django/contrib/contenttypes/models.py'
2025-04-22 17:58:56,570 wheel INFO adding 'django/contrib/contenttypes/views.py'
2025-04-22 17:58:56,571 wheel INFO adding 'django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,571 wheel INFO adding 'django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po'
2025-04-22 17:58:56,571 wheel INFO adding 'django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,571 wheel INFO adding 'django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po'
2025-04-22 17:58:56,572 wheel INFO adding 'django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,572 wheel INFO adding 'django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 17:58:56,572 wheel INFO adding 'django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,572 wheel INFO adding 'django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po'
2025-04-22 17:58:56,572 wheel INFO adding 'django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,573 wheel INFO adding 'django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po'
2025-04-22 17:58:56,573 wheel INFO adding 'django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,573 wheel INFO adding 'django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po'
2025-04-22 17:58:56,573 wheel INFO adding 'django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,573 wheel INFO adding 'django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,574 wheel INFO adding 'django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,574 wheel INFO adding 'django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,574 wheel INFO adding 'django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,574 wheel INFO adding 'django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po'
2025-04-22 17:58:56,575 wheel INFO adding 'django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,575 wheel INFO adding 'django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,575 wheel INFO adding 'django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,575 wheel INFO adding 'django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po'
2025-04-22 17:58:56,575 wheel INFO adding 'django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,575 wheel INFO adding 'django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,576 wheel INFO adding 'django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,576 wheel INFO adding 'django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,576 wheel INFO adding 'django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,576 wheel INFO adding 'django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,576 wheel INFO adding 'django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,577 wheel INFO adding 'django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po'
2025-04-22 17:58:56,577 wheel INFO adding 'django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,577 wheel INFO adding 'django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po'
2025-04-22 17:58:56,577 wheel INFO adding 'django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,577 wheel INFO adding 'django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,578 wheel INFO adding 'django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,578 wheel INFO adding 'django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po'
2025-04-22 17:58:56,578 wheel INFO adding 'django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,578 wheel INFO adding 'django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po'
2025-04-22 17:58:56,578 wheel INFO adding 'django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,579 wheel INFO adding 'django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 17:58:56,579 wheel INFO adding 'django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,579 wheel INFO adding 'django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 17:58:56,579 wheel INFO adding 'django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,579 wheel INFO adding 'django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po'
2025-04-22 17:58:56,580 wheel INFO adding 'django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,580 wheel INFO adding 'django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po'
2025-04-22 17:58:56,580 wheel INFO adding 'django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,580 wheel INFO adding 'django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,580 wheel INFO adding 'django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,581 wheel INFO adding 'django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 17:58:56,581 wheel INFO adding 'django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,581 wheel INFO adding 'django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 17:58:56,581 wheel INFO adding 'django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,581 wheel INFO adding 'django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 17:58:56,581 wheel INFO adding 'django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,582 wheel INFO adding 'django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po'
2025-04-22 17:58:56,582 wheel INFO adding 'django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,582 wheel INFO adding 'django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,582 wheel INFO adding 'django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,582 wheel INFO adding 'django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,583 wheel INFO adding 'django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,583 wheel INFO adding 'django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,583 wheel INFO adding 'django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,583 wheel INFO adding 'django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,583 wheel INFO adding 'django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,584 wheel INFO adding 'django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,584 wheel INFO adding 'django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,584 wheel INFO adding 'django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po'
2025-04-22 17:58:56,584 wheel INFO adding 'django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,584 wheel INFO adding 'django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po'
2025-04-22 17:58:56,585 wheel INFO adding 'django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,585 wheel INFO adding 'django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,585 wheel INFO adding 'django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,585 wheel INFO adding 'django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po'
2025-04-22 17:58:56,585 wheel INFO adding 'django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,586 wheel INFO adding 'django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,586 wheel INFO adding 'django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,586 wheel INFO adding 'django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,586 wheel INFO adding 'django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,586 wheel INFO adding 'django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,587 wheel INFO adding 'django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,587 wheel INFO adding 'django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,587 wheel INFO adding 'django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,587 wheel INFO adding 'django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,587 wheel INFO adding 'django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,587 wheel INFO adding 'django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po'
2025-04-22 17:58:56,588 wheel INFO adding 'django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,588 wheel INFO adding 'django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po'
2025-04-22 17:58:56,588 wheel INFO adding 'django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,588 wheel INFO adding 'django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po'
2025-04-22 17:58:56,588 wheel INFO adding 'django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,589 wheel INFO adding 'django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po'
2025-04-22 17:58:56,589 wheel INFO adding 'django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,589 wheel INFO adding 'django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po'
2025-04-22 17:58:56,589 wheel INFO adding 'django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,589 wheel INFO adding 'django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po'
2025-04-22 17:58:56,590 wheel INFO adding 'django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,590 wheel INFO adding 'django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po'
2025-04-22 17:58:56,590 wheel INFO adding 'django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,590 wheel INFO adding 'django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,590 wheel INFO adding 'django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,591 wheel INFO adding 'django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po'
2025-04-22 17:58:56,591 wheel INFO adding 'django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,591 wheel INFO adding 'django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,591 wheel INFO adding 'django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,591 wheel INFO adding 'django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po'
2025-04-22 17:58:56,592 wheel INFO adding 'django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,592 wheel INFO adding 'django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po'
2025-04-22 17:58:56,592 wheel INFO adding 'django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,592 wheel INFO adding 'django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,592 wheel INFO adding 'django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,592 wheel INFO adding 'django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,593 wheel INFO adding 'django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,593 wheel INFO adding 'django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,593 wheel INFO adding 'django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,593 wheel INFO adding 'django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,593 wheel INFO adding 'django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,594 wheel INFO adding 'django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po'
2025-04-22 17:58:56,594 wheel INFO adding 'django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,594 wheel INFO adding 'django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,594 wheel INFO adding 'django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,594 wheel INFO adding 'django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,595 wheel INFO adding 'django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,595 wheel INFO adding 'django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.po'
2025-04-22 17:58:56,595 wheel INFO adding 'django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,595 wheel INFO adding 'django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po'
2025-04-22 17:58:56,595 wheel INFO adding 'django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,596 wheel INFO adding 'django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,596 wheel INFO adding 'django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,596 wheel INFO adding 'django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po'
2025-04-22 17:58:56,596 wheel INFO adding 'django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,596 wheel INFO adding 'django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,597 wheel INFO adding 'django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,597 wheel INFO adding 'django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,597 wheel INFO adding 'django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,597 wheel INFO adding 'django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po'
2025-04-22 17:58:56,597 wheel INFO adding 'django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,598 wheel INFO adding 'django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,598 wheel INFO adding 'django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,598 wheel INFO adding 'django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,598 wheel INFO adding 'django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,598 wheel INFO adding 'django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,599 wheel INFO adding 'django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,599 wheel INFO adding 'django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,599 wheel INFO adding 'django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,599 wheel INFO adding 'django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po'
2025-04-22 17:58:56,599 wheel INFO adding 'django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,600 wheel INFO adding 'django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po'
2025-04-22 17:58:56,600 wheel INFO adding 'django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,600 wheel INFO adding 'django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,600 wheel INFO adding 'django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,600 wheel INFO adding 'django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,601 wheel INFO adding 'django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,601 wheel INFO adding 'django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po'
2025-04-22 17:58:56,601 wheel INFO adding 'django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,601 wheel INFO adding 'django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,601 wheel INFO adding 'django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,602 wheel INFO adding 'django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,602 wheel INFO adding 'django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,602 wheel INFO adding 'django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,602 wheel INFO adding 'django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,602 wheel INFO adding 'django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po'
2025-04-22 17:58:56,603 wheel INFO adding 'django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,603 wheel INFO adding 'django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po'
2025-04-22 17:58:56,603 wheel INFO adding 'django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,603 wheel INFO adding 'django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po'
2025-04-22 17:58:56,603 wheel INFO adding 'django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,604 wheel INFO adding 'django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,604 wheel INFO adding 'django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,604 wheel INFO adding 'django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po'
2025-04-22 17:58:56,604 wheel INFO adding 'django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,604 wheel INFO adding 'django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,605 wheel INFO adding 'django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,605 wheel INFO adding 'django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,605 wheel INFO adding 'django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,605 wheel INFO adding 'django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,605 wheel INFO adding 'django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,605 wheel INFO adding 'django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po'
2025-04-22 17:58:56,606 wheel INFO adding 'django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,606 wheel INFO adding 'django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,606 wheel INFO adding 'django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,606 wheel INFO adding 'django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po'
2025-04-22 17:58:56,607 wheel INFO adding 'django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,607 wheel INFO adding 'django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,607 wheel INFO adding 'django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,607 wheel INFO adding 'django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 17:58:56,607 wheel INFO adding 'django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,607 wheel INFO adding 'django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 17:58:56,608 wheel INFO adding 'django/contrib/contenttypes/management/__init__.py'
2025-04-22 17:58:56,608 wheel INFO adding 'django/contrib/contenttypes/management/commands/__init__.py'
2025-04-22 17:58:56,608 wheel INFO adding 'django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py'
2025-04-22 17:58:56,608 wheel INFO adding 'django/contrib/contenttypes/migrations/0001_initial.py'
2025-04-22 17:58:56,608 wheel INFO adding 'django/contrib/contenttypes/migrations/0002_remove_content_type_name.py'
2025-04-22 17:58:56,609 wheel INFO adding 'django/contrib/contenttypes/migrations/__init__.py'
2025-04-22 17:58:56,609 wheel INFO adding 'django/contrib/flatpages/__init__.py'
2025-04-22 17:58:56,609 wheel INFO adding 'django/contrib/flatpages/admin.py'
2025-04-22 17:58:56,609 wheel INFO adding 'django/contrib/flatpages/apps.py'
2025-04-22 17:58:56,609 wheel INFO adding 'django/contrib/flatpages/forms.py'
2025-04-22 17:58:56,609 wheel INFO adding 'django/contrib/flatpages/middleware.py'
2025-04-22 17:58:56,610 wheel INFO adding 'django/contrib/flatpages/models.py'
2025-04-22 17:58:56,610 wheel INFO adding 'django/contrib/flatpages/sitemaps.py'
2025-04-22 17:58:56,610 wheel INFO adding 'django/contrib/flatpages/urls.py'
2025-04-22 17:58:56,610 wheel INFO adding 'django/contrib/flatpages/views.py'
2025-04-22 17:58:56,611 wheel INFO adding 'django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,611 wheel INFO adding 'django/contrib/flatpages/locale/af/LC_MESSAGES/django.po'
2025-04-22 17:58:56,611 wheel INFO adding 'django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,612 wheel INFO adding 'django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po'
2025-04-22 17:58:56,612 wheel INFO adding 'django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,612 wheel INFO adding 'django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 17:58:56,612 wheel INFO adding 'django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,612 wheel INFO adding 'django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po'
2025-04-22 17:58:56,613 wheel INFO adding 'django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,613 wheel INFO adding 'django/contrib/flatpages/locale/az/LC_MESSAGES/django.po'
2025-04-22 17:58:56,613 wheel INFO adding 'django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,613 wheel INFO adding 'django/contrib/flatpages/locale/be/LC_MESSAGES/django.po'
2025-04-22 17:58:56,613 wheel INFO adding 'django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,614 wheel INFO adding 'django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,614 wheel INFO adding 'django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,614 wheel INFO adding 'django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,614 wheel INFO adding 'django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,614 wheel INFO adding 'django/contrib/flatpages/locale/br/LC_MESSAGES/django.po'
2025-04-22 17:58:56,615 wheel INFO adding 'django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,615 wheel INFO adding 'django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,615 wheel INFO adding 'django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,615 wheel INFO adding 'django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po'
2025-04-22 17:58:56,615 wheel INFO adding 'django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,616 wheel INFO adding 'django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,616 wheel INFO adding 'django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,616 wheel INFO adding 'django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,616 wheel INFO adding 'django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,617 wheel INFO adding 'django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,617 wheel INFO adding 'django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,617 wheel INFO adding 'django/contrib/flatpages/locale/da/LC_MESSAGES/django.po'
2025-04-22 17:58:56,617 wheel INFO adding 'django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,617 wheel INFO adding 'django/contrib/flatpages/locale/de/LC_MESSAGES/django.po'
2025-04-22 17:58:56,618 wheel INFO adding 'django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,618 wheel INFO adding 'django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,618 wheel INFO adding 'django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,618 wheel INFO adding 'django/contrib/flatpages/locale/el/LC_MESSAGES/django.po'
2025-04-22 17:58:56,618 wheel INFO adding 'django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,619 wheel INFO adding 'django/contrib/flatpages/locale/en/LC_MESSAGES/django.po'
2025-04-22 17:58:56,619 wheel INFO adding 'django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,619 wheel INFO adding 'django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 17:58:56,619 wheel INFO adding 'django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,619 wheel INFO adding 'django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 17:58:56,620 wheel INFO adding 'django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,620 wheel INFO adding 'django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po'
2025-04-22 17:58:56,620 wheel INFO adding 'django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,620 wheel INFO adding 'django/contrib/flatpages/locale/es/LC_MESSAGES/django.po'
2025-04-22 17:58:56,620 wheel INFO adding 'django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,620 wheel INFO adding 'django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,621 wheel INFO adding 'django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,621 wheel INFO adding 'django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 17:58:56,621 wheel INFO adding 'django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,621 wheel INFO adding 'django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 17:58:56,622 wheel INFO adding 'django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,622 wheel INFO adding 'django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 17:58:56,622 wheel INFO adding 'django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,622 wheel INFO adding 'django/contrib/flatpages/locale/et/LC_MESSAGES/django.po'
2025-04-22 17:58:56,622 wheel INFO adding 'django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,623 wheel INFO adding 'django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,623 wheel INFO adding 'django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,623 wheel INFO adding 'django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,623 wheel INFO adding 'django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,623 wheel INFO adding 'django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,624 wheel INFO adding 'django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,624 wheel INFO adding 'django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,624 wheel INFO adding 'django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,624 wheel INFO adding 'django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,625 wheel INFO adding 'django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,625 wheel INFO adding 'django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po'
2025-04-22 17:58:56,625 wheel INFO adding 'django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,625 wheel INFO adding 'django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po'
2025-04-22 17:58:56,625 wheel INFO adding 'django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,625 wheel INFO adding 'django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,626 wheel INFO adding 'django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,626 wheel INFO adding 'django/contrib/flatpages/locale/he/LC_MESSAGES/django.po'
2025-04-22 17:58:56,626 wheel INFO adding 'django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,626 wheel INFO adding 'django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,627 wheel INFO adding 'django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,627 wheel INFO adding 'django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,627 wheel INFO adding 'django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,627 wheel INFO adding 'django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,627 wheel INFO adding 'django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,628 wheel INFO adding 'django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,628 wheel INFO adding 'django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,628 wheel INFO adding 'django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,628 wheel INFO adding 'django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,628 wheel INFO adding 'django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po'
2025-04-22 17:58:56,629 wheel INFO adding 'django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,629 wheel INFO adding 'django/contrib/flatpages/locale/id/LC_MESSAGES/django.po'
2025-04-22 17:58:56,629 wheel INFO adding 'django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,629 wheel INFO adding 'django/contrib/flatpages/locale/io/LC_MESSAGES/django.po'
2025-04-22 17:58:56,629 wheel INFO adding 'django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,630 wheel INFO adding 'django/contrib/flatpages/locale/is/LC_MESSAGES/django.po'
2025-04-22 17:58:56,630 wheel INFO adding 'django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,630 wheel INFO adding 'django/contrib/flatpages/locale/it/LC_MESSAGES/django.po'
2025-04-22 17:58:56,630 wheel INFO adding 'django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,630 wheel INFO adding 'django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po'
2025-04-22 17:58:56,631 wheel INFO adding 'django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,631 wheel INFO adding 'django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po'
2025-04-22 17:58:56,631 wheel INFO adding 'django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,631 wheel INFO adding 'django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,631 wheel INFO adding 'django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,631 wheel INFO adding 'django/contrib/flatpages/locale/km/LC_MESSAGES/django.po'
2025-04-22 17:58:56,632 wheel INFO adding 'django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,632 wheel INFO adding 'django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,632 wheel INFO adding 'django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,632 wheel INFO adding 'django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po'
2025-04-22 17:58:56,633 wheel INFO adding 'django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,633 wheel INFO adding 'django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po'
2025-04-22 17:58:56,633 wheel INFO adding 'django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,633 wheel INFO adding 'django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,633 wheel INFO adding 'django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,634 wheel INFO adding 'django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,634 wheel INFO adding 'django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,634 wheel INFO adding 'django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,634 wheel INFO adding 'django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,634 wheel INFO adding 'django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,635 wheel INFO adding 'django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,635 wheel INFO adding 'django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po'
2025-04-22 17:58:56,635 wheel INFO adding 'django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,635 wheel INFO adding 'django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,635 wheel INFO adding 'django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,636 wheel INFO adding 'django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,636 wheel INFO adding 'django/contrib/flatpages/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,636 wheel INFO adding 'django/contrib/flatpages/locale/ms/LC_MESSAGES/django.po'
2025-04-22 17:58:56,636 wheel INFO adding 'django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,636 wheel INFO adding 'django/contrib/flatpages/locale/my/LC_MESSAGES/django.po'
2025-04-22 17:58:56,637 wheel INFO adding 'django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,637 wheel INFO adding 'django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,637 wheel INFO adding 'django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,637 wheel INFO adding 'django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po'
2025-04-22 17:58:56,637 wheel INFO adding 'django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,638 wheel INFO adding 'django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,638 wheel INFO adding 'django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,638 wheel INFO adding 'django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,638 wheel INFO adding 'django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,638 wheel INFO adding 'django/contrib/flatpages/locale/os/LC_MESSAGES/django.po'
2025-04-22 17:58:56,639 wheel INFO adding 'django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,639 wheel INFO adding 'django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,639 wheel INFO adding 'django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,639 wheel INFO adding 'django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,640 wheel INFO adding 'django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,640 wheel INFO adding 'django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,640 wheel INFO adding 'django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,640 wheel INFO adding 'django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,640 wheel INFO adding 'django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,641 wheel INFO adding 'django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po'
2025-04-22 17:58:56,641 wheel INFO adding 'django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,641 wheel INFO adding 'django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po'
2025-04-22 17:58:56,641 wheel INFO adding 'django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,641 wheel INFO adding 'django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,642 wheel INFO adding 'django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,642 wheel INFO adding 'django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,642 wheel INFO adding 'django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,642 wheel INFO adding 'django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po'
2025-04-22 17:58:56,642 wheel INFO adding 'django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,643 wheel INFO adding 'django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,643 wheel INFO adding 'django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,643 wheel INFO adding 'django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,643 wheel INFO adding 'django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,643 wheel INFO adding 'django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,644 wheel INFO adding 'django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,644 wheel INFO adding 'django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po'
2025-04-22 17:58:56,644 wheel INFO adding 'django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,644 wheel INFO adding 'django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po'
2025-04-22 17:58:56,644 wheel INFO adding 'django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,645 wheel INFO adding 'django/contrib/flatpages/locale/te/LC_MESSAGES/django.po'
2025-04-22 17:58:56,645 wheel INFO adding 'django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,645 wheel INFO adding 'django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,645 wheel INFO adding 'django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,645 wheel INFO adding 'django/contrib/flatpages/locale/th/LC_MESSAGES/django.po'
2025-04-22 17:58:56,646 wheel INFO adding 'django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,646 wheel INFO adding 'django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,646 wheel INFO adding 'django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,646 wheel INFO adding 'django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,646 wheel INFO adding 'django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,647 wheel INFO adding 'django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,647 wheel INFO adding 'django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,647 wheel INFO adding 'django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po'
2025-04-22 17:58:56,647 wheel INFO adding 'django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,647 wheel INFO adding 'django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,648 wheel INFO adding 'django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,648 wheel INFO adding 'django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po'
2025-04-22 17:58:56,648 wheel INFO adding 'django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,648 wheel INFO adding 'django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,648 wheel INFO adding 'django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,649 wheel INFO adding 'django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 17:58:56,649 wheel INFO adding 'django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,649 wheel INFO adding 'django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 17:58:56,649 wheel INFO adding 'django/contrib/flatpages/migrations/0001_initial.py'
2025-04-22 17:58:56,649 wheel INFO adding 'django/contrib/flatpages/migrations/__init__.py'
2025-04-22 17:58:56,650 wheel INFO adding 'django/contrib/flatpages/templatetags/__init__.py'
2025-04-22 17:58:56,650 wheel INFO adding 'django/contrib/flatpages/templatetags/flatpages.py'
2025-04-22 17:58:56,650 wheel INFO adding 'django/contrib/gis/__init__.py'
2025-04-22 17:58:56,650 wheel INFO adding 'django/contrib/gis/apps.py'
2025-04-22 17:58:56,650 wheel INFO adding 'django/contrib/gis/feeds.py'
2025-04-22 17:58:56,650 wheel INFO adding 'django/contrib/gis/geometry.py'
2025-04-22 17:58:56,651 wheel INFO adding 'django/contrib/gis/measure.py'
2025-04-22 17:58:56,651 wheel INFO adding 'django/contrib/gis/ptr.py'
2025-04-22 17:58:56,651 wheel INFO adding 'django/contrib/gis/shortcuts.py'
2025-04-22 17:58:56,651 wheel INFO adding 'django/contrib/gis/views.py'
2025-04-22 17:58:56,651 wheel INFO adding 'django/contrib/gis/admin/__init__.py'
2025-04-22 17:58:56,652 wheel INFO adding 'django/contrib/gis/admin/options.py'
2025-04-22 17:58:56,652 wheel INFO adding 'django/contrib/gis/admin/widgets.py'
2025-04-22 17:58:56,652 wheel INFO adding 'django/contrib/gis/db/__init__.py'
2025-04-22 17:58:56,652 wheel INFO adding 'django/contrib/gis/db/backends/__init__.py'
2025-04-22 17:58:56,652 wheel INFO adding 'django/contrib/gis/db/backends/utils.py'
2025-04-22 17:58:56,653 wheel INFO adding 'django/contrib/gis/db/backends/base/__init__.py'
2025-04-22 17:58:56,653 wheel INFO adding 'django/contrib/gis/db/backends/base/adapter.py'
2025-04-22 17:58:56,653 wheel INFO adding 'django/contrib/gis/db/backends/base/features.py'
2025-04-22 17:58:56,653 wheel INFO adding 'django/contrib/gis/db/backends/base/models.py'
2025-04-22 17:58:56,653 wheel INFO adding 'django/contrib/gis/db/backends/base/operations.py'
2025-04-22 17:58:56,654 wheel INFO adding 'django/contrib/gis/db/backends/mysql/__init__.py'
2025-04-22 17:58:56,654 wheel INFO adding 'django/contrib/gis/db/backends/mysql/base.py'
2025-04-22 17:58:56,654 wheel INFO adding 'django/contrib/gis/db/backends/mysql/features.py'
2025-04-22 17:58:56,654 wheel INFO adding 'django/contrib/gis/db/backends/mysql/introspection.py'
2025-04-22 17:58:56,654 wheel INFO adding 'django/contrib/gis/db/backends/mysql/operations.py'
2025-04-22 17:58:56,654 wheel INFO adding 'django/contrib/gis/db/backends/mysql/schema.py'
2025-04-22 17:58:56,655 wheel INFO adding 'django/contrib/gis/db/backends/oracle/__init__.py'
2025-04-22 17:58:56,655 wheel INFO adding 'django/contrib/gis/db/backends/oracle/adapter.py'
2025-04-22 17:58:56,655 wheel INFO adding 'django/contrib/gis/db/backends/oracle/base.py'
2025-04-22 17:58:56,655 wheel INFO adding 'django/contrib/gis/db/backends/oracle/features.py'
2025-04-22 17:58:56,655 wheel INFO adding 'django/contrib/gis/db/backends/oracle/introspection.py'
2025-04-22 17:58:56,655 wheel INFO adding 'django/contrib/gis/db/backends/oracle/models.py'
2025-04-22 17:58:56,656 wheel INFO adding 'django/contrib/gis/db/backends/oracle/operations.py'
2025-04-22 17:58:56,656 wheel INFO adding 'django/contrib/gis/db/backends/oracle/schema.py'
2025-04-22 17:58:56,656 wheel INFO adding 'django/contrib/gis/db/backends/postgis/__init__.py'
2025-04-22 17:58:56,656 wheel INFO adding 'django/contrib/gis/db/backends/postgis/adapter.py'
2025-04-22 17:58:56,656 wheel INFO adding 'django/contrib/gis/db/backends/postgis/base.py'
2025-04-22 17:58:56,657 wheel INFO adding 'django/contrib/gis/db/backends/postgis/const.py'
2025-04-22 17:58:56,657 wheel INFO adding 'django/contrib/gis/db/backends/postgis/features.py'
2025-04-22 17:58:56,657 wheel INFO adding 'django/contrib/gis/db/backends/postgis/introspection.py'
2025-04-22 17:58:56,657 wheel INFO adding 'django/contrib/gis/db/backends/postgis/models.py'
2025-04-22 17:58:56,657 wheel INFO adding 'django/contrib/gis/db/backends/postgis/operations.py'
2025-04-22 17:58:56,657 wheel INFO adding 'django/contrib/gis/db/backends/postgis/pgraster.py'
2025-04-22 17:58:56,658 wheel INFO adding 'django/contrib/gis/db/backends/postgis/schema.py'
2025-04-22 17:58:56,658 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/__init__.py'
2025-04-22 17:58:56,658 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/adapter.py'
2025-04-22 17:58:56,658 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/base.py'
2025-04-22 17:58:56,658 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/client.py'
2025-04-22 17:58:56,658 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/features.py'
2025-04-22 17:58:56,659 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/introspection.py'
2025-04-22 17:58:56,659 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/models.py'
2025-04-22 17:58:56,659 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/operations.py'
2025-04-22 17:58:56,659 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/schema.py'
2025-04-22 17:58:56,659 wheel INFO adding 'django/contrib/gis/db/models/__init__.py'
2025-04-22 17:58:56,660 wheel INFO adding 'django/contrib/gis/db/models/aggregates.py'
2025-04-22 17:58:56,660 wheel INFO adding 'django/contrib/gis/db/models/fields.py'
2025-04-22 17:58:56,660 wheel INFO adding 'django/contrib/gis/db/models/functions.py'
2025-04-22 17:58:56,660 wheel INFO adding 'django/contrib/gis/db/models/lookups.py'
2025-04-22 17:58:56,660 wheel INFO adding 'django/contrib/gis/db/models/proxy.py'
2025-04-22 17:58:56,661 wheel INFO adding 'django/contrib/gis/db/models/sql/__init__.py'
2025-04-22 17:58:56,661 wheel INFO adding 'django/contrib/gis/db/models/sql/conversion.py'
2025-04-22 17:58:56,661 wheel INFO adding 'django/contrib/gis/forms/__init__.py'
2025-04-22 17:58:56,661 wheel INFO adding 'django/contrib/gis/forms/fields.py'
2025-04-22 17:58:56,661 wheel INFO adding 'django/contrib/gis/forms/widgets.py'
2025-04-22 17:58:56,662 wheel INFO adding 'django/contrib/gis/gdal/LICENSE'
2025-04-22 17:58:56,662 wheel INFO adding 'django/contrib/gis/gdal/__init__.py'
2025-04-22 17:58:56,662 wheel INFO adding 'django/contrib/gis/gdal/base.py'
2025-04-22 17:58:56,662 wheel INFO adding 'django/contrib/gis/gdal/datasource.py'
2025-04-22 17:58:56,662 wheel INFO adding 'django/contrib/gis/gdal/driver.py'
2025-04-22 17:58:56,662 wheel INFO adding 'django/contrib/gis/gdal/envelope.py'
2025-04-22 17:58:56,663 wheel INFO adding 'django/contrib/gis/gdal/error.py'
2025-04-22 17:58:56,663 wheel INFO adding 'django/contrib/gis/gdal/feature.py'
2025-04-22 17:58:56,663 wheel INFO adding 'django/contrib/gis/gdal/field.py'
2025-04-22 17:58:56,663 wheel INFO adding 'django/contrib/gis/gdal/geometries.py'
2025-04-22 17:58:56,663 wheel INFO adding 'django/contrib/gis/gdal/geomtype.py'
2025-04-22 17:58:56,664 wheel INFO adding 'django/contrib/gis/gdal/layer.py'
2025-04-22 17:58:56,664 wheel INFO adding 'django/contrib/gis/gdal/libgdal.py'
2025-04-22 17:58:56,664 wheel INFO adding 'django/contrib/gis/gdal/srs.py'
2025-04-22 17:58:56,664 wheel INFO adding 'django/contrib/gis/gdal/prototypes/__init__.py'
2025-04-22 17:58:56,664 wheel INFO adding 'django/contrib/gis/gdal/prototypes/ds.py'
2025-04-22 17:58:56,665 wheel INFO adding 'django/contrib/gis/gdal/prototypes/errcheck.py'
2025-04-22 17:58:56,665 wheel INFO adding 'django/contrib/gis/gdal/prototypes/generation.py'
2025-04-22 17:58:56,665 wheel INFO adding 'django/contrib/gis/gdal/prototypes/geom.py'
2025-04-22 17:58:56,665 wheel INFO adding 'django/contrib/gis/gdal/prototypes/raster.py'
2025-04-22 17:58:56,665 wheel INFO adding 'django/contrib/gis/gdal/prototypes/srs.py'
2025-04-22 17:58:56,666 wheel INFO adding 'django/contrib/gis/gdal/raster/__init__.py'
2025-04-22 17:58:56,666 wheel INFO adding 'django/contrib/gis/gdal/raster/band.py'
2025-04-22 17:58:56,666 wheel INFO adding 'django/contrib/gis/gdal/raster/base.py'
2025-04-22 17:58:56,666 wheel INFO adding 'django/contrib/gis/gdal/raster/const.py'
2025-04-22 17:58:56,666 wheel INFO adding 'django/contrib/gis/gdal/raster/source.py'
2025-04-22 17:58:56,667 wheel INFO adding 'django/contrib/gis/geoip2/__init__.py'
2025-04-22 17:58:56,667 wheel INFO adding 'django/contrib/gis/geoip2/base.py'
2025-04-22 17:58:56,667 wheel INFO adding 'django/contrib/gis/geoip2/resources.py'
2025-04-22 17:58:56,667 wheel INFO adding 'django/contrib/gis/geos/LICENSE'
2025-04-22 17:58:56,667 wheel INFO adding 'django/contrib/gis/geos/__init__.py'
2025-04-22 17:58:56,668 wheel INFO adding 'django/contrib/gis/geos/base.py'
2025-04-22 17:58:56,668 wheel INFO adding 'django/contrib/gis/geos/collections.py'
2025-04-22 17:58:56,668 wheel INFO adding 'django/contrib/gis/geos/coordseq.py'
2025-04-22 17:58:56,668 wheel INFO adding 'django/contrib/gis/geos/error.py'
2025-04-22 17:58:56,668 wheel INFO adding 'django/contrib/gis/geos/factory.py'
2025-04-22 17:58:56,669 wheel INFO adding 'django/contrib/gis/geos/geometry.py'
2025-04-22 17:58:56,669 wheel INFO adding 'django/contrib/gis/geos/io.py'
2025-04-22 17:58:56,669 wheel INFO adding 'django/contrib/gis/geos/libgeos.py'
2025-04-22 17:58:56,669 wheel INFO adding 'django/contrib/gis/geos/linestring.py'
2025-04-22 17:58:56,669 wheel INFO adding 'django/contrib/gis/geos/mutable_list.py'
2025-04-22 17:58:56,670 wheel INFO adding 'django/contrib/gis/geos/point.py'
2025-04-22 17:58:56,670 wheel INFO adding 'django/contrib/gis/geos/polygon.py'
2025-04-22 17:58:56,670 wheel INFO adding 'django/contrib/gis/geos/prepared.py'
2025-04-22 17:58:56,670 wheel INFO adding 'django/contrib/gis/geos/prototypes/__init__.py'
2025-04-22 17:58:56,670 wheel INFO adding 'django/contrib/gis/geos/prototypes/coordseq.py'
2025-04-22 17:58:56,670 wheel INFO adding 'django/contrib/gis/geos/prototypes/errcheck.py'
2025-04-22 17:58:56,671 wheel INFO adding 'django/contrib/gis/geos/prototypes/geom.py'
2025-04-22 17:58:56,671 wheel INFO adding 'django/contrib/gis/geos/prototypes/io.py'
2025-04-22 17:58:56,671 wheel INFO adding 'django/contrib/gis/geos/prototypes/misc.py'
2025-04-22 17:58:56,671 wheel INFO adding 'django/contrib/gis/geos/prototypes/predicates.py'
2025-04-22 17:58:56,671 wheel INFO adding 'django/contrib/gis/geos/prototypes/prepared.py'
2025-04-22 17:58:56,671 wheel INFO adding 'django/contrib/gis/geos/prototypes/threadsafe.py'
2025-04-22 17:58:56,672 wheel INFO adding 'django/contrib/gis/geos/prototypes/topology.py'
2025-04-22 17:58:56,673 wheel INFO adding 'django/contrib/gis/locale/af/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,673 wheel INFO adding 'django/contrib/gis/locale/af/LC_MESSAGES/django.po'
2025-04-22 17:58:56,673 wheel INFO adding 'django/contrib/gis/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,673 wheel INFO adding 'django/contrib/gis/locale/ar/LC_MESSAGES/django.po'
2025-04-22 17:58:56,673 wheel INFO adding 'django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,674 wheel INFO adding 'django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 17:58:56,674 wheel INFO adding 'django/contrib/gis/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,674 wheel INFO adding 'django/contrib/gis/locale/ast/LC_MESSAGES/django.po'
2025-04-22 17:58:56,674 wheel INFO adding 'django/contrib/gis/locale/az/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,674 wheel INFO adding 'django/contrib/gis/locale/az/LC_MESSAGES/django.po'
2025-04-22 17:58:56,675 wheel INFO adding 'django/contrib/gis/locale/be/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,675 wheel INFO adding 'django/contrib/gis/locale/be/LC_MESSAGES/django.po'
2025-04-22 17:58:56,675 wheel INFO adding 'django/contrib/gis/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,675 wheel INFO adding 'django/contrib/gis/locale/bg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,675 wheel INFO adding 'django/contrib/gis/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,676 wheel INFO adding 'django/contrib/gis/locale/bn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,676 wheel INFO adding 'django/contrib/gis/locale/br/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,676 wheel INFO adding 'django/contrib/gis/locale/br/LC_MESSAGES/django.po'
2025-04-22 17:58:56,676 wheel INFO adding 'django/contrib/gis/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,676 wheel INFO adding 'django/contrib/gis/locale/bs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,677 wheel INFO adding 'django/contrib/gis/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,677 wheel INFO adding 'django/contrib/gis/locale/ca/LC_MESSAGES/django.po'
2025-04-22 17:58:56,677 wheel INFO adding 'django/contrib/gis/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,677 wheel INFO adding 'django/contrib/gis/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,677 wheel INFO adding 'django/contrib/gis/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,678 wheel INFO adding 'django/contrib/gis/locale/cs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,678 wheel INFO adding 'django/contrib/gis/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,678 wheel INFO adding 'django/contrib/gis/locale/cy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,678 wheel INFO adding 'django/contrib/gis/locale/da/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,678 wheel INFO adding 'django/contrib/gis/locale/da/LC_MESSAGES/django.po'
2025-04-22 17:58:56,679 wheel INFO adding 'django/contrib/gis/locale/de/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,679 wheel INFO adding 'django/contrib/gis/locale/de/LC_MESSAGES/django.po'
2025-04-22 17:58:56,679 wheel INFO adding 'django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,679 wheel INFO adding 'django/contrib/gis/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,679 wheel INFO adding 'django/contrib/gis/locale/el/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,680 wheel INFO adding 'django/contrib/gis/locale/el/LC_MESSAGES/django.po'
2025-04-22 17:58:56,680 wheel INFO adding 'django/contrib/gis/locale/en/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,680 wheel INFO adding 'django/contrib/gis/locale/en/LC_MESSAGES/django.po'
2025-04-22 17:58:56,680 wheel INFO adding 'django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,680 wheel INFO adding 'django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 17:58:56,681 wheel INFO adding 'django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,681 wheel INFO adding 'django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 17:58:56,681 wheel INFO adding 'django/contrib/gis/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,681 wheel INFO adding 'django/contrib/gis/locale/eo/LC_MESSAGES/django.po'
2025-04-22 17:58:56,681 wheel INFO adding 'django/contrib/gis/locale/es/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,682 wheel INFO adding 'django/contrib/gis/locale/es/LC_MESSAGES/django.po'
2025-04-22 17:58:56,682 wheel INFO adding 'django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,682 wheel INFO adding 'django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,682 wheel INFO adding 'django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,682 wheel INFO adding 'django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 17:58:56,683 wheel INFO adding 'django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,683 wheel INFO adding 'django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 17:58:56,683 wheel INFO adding 'django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,683 wheel INFO adding 'django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 17:58:56,683 wheel INFO adding 'django/contrib/gis/locale/et/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,683 wheel INFO adding 'django/contrib/gis/locale/et/LC_MESSAGES/django.po'
2025-04-22 17:58:56,684 wheel INFO adding 'django/contrib/gis/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,684 wheel INFO adding 'django/contrib/gis/locale/eu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,684 wheel INFO adding 'django/contrib/gis/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,684 wheel INFO adding 'django/contrib/gis/locale/fa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,685 wheel INFO adding 'django/contrib/gis/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,685 wheel INFO adding 'django/contrib/gis/locale/fi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,685 wheel INFO adding 'django/contrib/gis/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,685 wheel INFO adding 'django/contrib/gis/locale/fr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,685 wheel INFO adding 'django/contrib/gis/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,686 wheel INFO adding 'django/contrib/gis/locale/fy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,686 wheel INFO adding 'django/contrib/gis/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,686 wheel INFO adding 'django/contrib/gis/locale/ga/LC_MESSAGES/django.po'
2025-04-22 17:58:56,686 wheel INFO adding 'django/contrib/gis/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,686 wheel INFO adding 'django/contrib/gis/locale/gd/LC_MESSAGES/django.po'
2025-04-22 17:58:56,687 wheel INFO adding 'django/contrib/gis/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,687 wheel INFO adding 'django/contrib/gis/locale/gl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,687 wheel INFO adding 'django/contrib/gis/locale/he/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,687 wheel INFO adding 'django/contrib/gis/locale/he/LC_MESSAGES/django.po'
2025-04-22 17:58:56,687 wheel INFO adding 'django/contrib/gis/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,687 wheel INFO adding 'django/contrib/gis/locale/hi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,688 wheel INFO adding 'django/contrib/gis/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,688 wheel INFO adding 'django/contrib/gis/locale/hr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,688 wheel INFO adding 'django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,688 wheel INFO adding 'django/contrib/gis/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,689 wheel INFO adding 'django/contrib/gis/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,689 wheel INFO adding 'django/contrib/gis/locale/hu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,689 wheel INFO adding 'django/contrib/gis/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,689 wheel INFO adding 'django/contrib/gis/locale/hy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,690 wheel INFO adding 'django/contrib/gis/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,690 wheel INFO adding 'django/contrib/gis/locale/ia/LC_MESSAGES/django.po'
2025-04-22 17:58:56,690 wheel INFO adding 'django/contrib/gis/locale/id/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,690 wheel INFO adding 'django/contrib/gis/locale/id/LC_MESSAGES/django.po'
2025-04-22 17:58:56,690 wheel INFO adding 'django/contrib/gis/locale/io/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,691 wheel INFO adding 'django/contrib/gis/locale/io/LC_MESSAGES/django.po'
2025-04-22 17:58:56,691 wheel INFO adding 'django/contrib/gis/locale/is/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,691 wheel INFO adding 'django/contrib/gis/locale/is/LC_MESSAGES/django.po'
2025-04-22 17:58:56,691 wheel INFO adding 'django/contrib/gis/locale/it/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,691 wheel INFO adding 'django/contrib/gis/locale/it/LC_MESSAGES/django.po'
2025-04-22 17:58:56,692 wheel INFO adding 'django/contrib/gis/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,692 wheel INFO adding 'django/contrib/gis/locale/ja/LC_MESSAGES/django.po'
2025-04-22 17:58:56,692 wheel INFO adding 'django/contrib/gis/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,692 wheel INFO adding 'django/contrib/gis/locale/ka/LC_MESSAGES/django.po'
2025-04-22 17:58:56,692 wheel INFO adding 'django/contrib/gis/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,693 wheel INFO adding 'django/contrib/gis/locale/kk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,693 wheel INFO adding 'django/contrib/gis/locale/km/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,693 wheel INFO adding 'django/contrib/gis/locale/km/LC_MESSAGES/django.po'
2025-04-22 17:58:56,693 wheel INFO adding 'django/contrib/gis/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,693 wheel INFO adding 'django/contrib/gis/locale/kn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,694 wheel INFO adding 'django/contrib/gis/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,694 wheel INFO adding 'django/contrib/gis/locale/ko/LC_MESSAGES/django.po'
2025-04-22 17:58:56,694 wheel INFO adding 'django/contrib/gis/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,694 wheel INFO adding 'django/contrib/gis/locale/ky/LC_MESSAGES/django.po'
2025-04-22 17:58:56,694 wheel INFO adding 'django/contrib/gis/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,695 wheel INFO adding 'django/contrib/gis/locale/lb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,695 wheel INFO adding 'django/contrib/gis/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,695 wheel INFO adding 'django/contrib/gis/locale/lt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,695 wheel INFO adding 'django/contrib/gis/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,695 wheel INFO adding 'django/contrib/gis/locale/lv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,696 wheel INFO adding 'django/contrib/gis/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,696 wheel INFO adding 'django/contrib/gis/locale/mk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,696 wheel INFO adding 'django/contrib/gis/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,696 wheel INFO adding 'django/contrib/gis/locale/ml/LC_MESSAGES/django.po'
2025-04-22 17:58:56,696 wheel INFO adding 'django/contrib/gis/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,697 wheel INFO adding 'django/contrib/gis/locale/mn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,697 wheel INFO adding 'django/contrib/gis/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,697 wheel INFO adding 'django/contrib/gis/locale/mr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,697 wheel INFO adding 'django/contrib/gis/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,697 wheel INFO adding 'django/contrib/gis/locale/ms/LC_MESSAGES/django.po'
2025-04-22 17:58:56,698 wheel INFO adding 'django/contrib/gis/locale/my/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,698 wheel INFO adding 'django/contrib/gis/locale/my/LC_MESSAGES/django.po'
2025-04-22 17:58:56,698 wheel INFO adding 'django/contrib/gis/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,698 wheel INFO adding 'django/contrib/gis/locale/nb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,698 wheel INFO adding 'django/contrib/gis/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,699 wheel INFO adding 'django/contrib/gis/locale/ne/LC_MESSAGES/django.po'
2025-04-22 17:58:56,699 wheel INFO adding 'django/contrib/gis/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,699 wheel INFO adding 'django/contrib/gis/locale/nl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,699 wheel INFO adding 'django/contrib/gis/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,699 wheel INFO adding 'django/contrib/gis/locale/nn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,700 wheel INFO adding 'django/contrib/gis/locale/os/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,700 wheel INFO adding 'django/contrib/gis/locale/os/LC_MESSAGES/django.po'
2025-04-22 17:58:56,700 wheel INFO adding 'django/contrib/gis/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,700 wheel INFO adding 'django/contrib/gis/locale/pa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,700 wheel INFO adding 'django/contrib/gis/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,701 wheel INFO adding 'django/contrib/gis/locale/pl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,701 wheel INFO adding 'django/contrib/gis/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,701 wheel INFO adding 'django/contrib/gis/locale/pt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,701 wheel INFO adding 'django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,701 wheel INFO adding 'django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,702 wheel INFO adding 'django/contrib/gis/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,702 wheel INFO adding 'django/contrib/gis/locale/ro/LC_MESSAGES/django.po'
2025-04-22 17:58:56,702 wheel INFO adding 'django/contrib/gis/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,702 wheel INFO adding 'django/contrib/gis/locale/ru/LC_MESSAGES/django.po'
2025-04-22 17:58:56,702 wheel INFO adding 'django/contrib/gis/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,703 wheel INFO adding 'django/contrib/gis/locale/sk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,703 wheel INFO adding 'django/contrib/gis/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,703 wheel INFO adding 'django/contrib/gis/locale/sl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,703 wheel INFO adding 'django/contrib/gis/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,703 wheel INFO adding 'django/contrib/gis/locale/sq/LC_MESSAGES/django.po'
2025-04-22 17:58:56,704 wheel INFO adding 'django/contrib/gis/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,704 wheel INFO adding 'django/contrib/gis/locale/sr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,704 wheel INFO adding 'django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,704 wheel INFO adding 'django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,704 wheel INFO adding 'django/contrib/gis/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,705 wheel INFO adding 'django/contrib/gis/locale/sv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,705 wheel INFO adding 'django/contrib/gis/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,705 wheel INFO adding 'django/contrib/gis/locale/sw/LC_MESSAGES/django.po'
2025-04-22 17:58:56,705 wheel INFO adding 'django/contrib/gis/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,705 wheel INFO adding 'django/contrib/gis/locale/ta/LC_MESSAGES/django.po'
2025-04-22 17:58:56,706 wheel INFO adding 'django/contrib/gis/locale/te/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,706 wheel INFO adding 'django/contrib/gis/locale/te/LC_MESSAGES/django.po'
2025-04-22 17:58:56,706 wheel INFO adding 'django/contrib/gis/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,706 wheel INFO adding 'django/contrib/gis/locale/tg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,706 wheel INFO adding 'django/contrib/gis/locale/th/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,707 wheel INFO adding 'django/contrib/gis/locale/th/LC_MESSAGES/django.po'
2025-04-22 17:58:56,707 wheel INFO adding 'django/contrib/gis/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,707 wheel INFO adding 'django/contrib/gis/locale/tr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,707 wheel INFO adding 'django/contrib/gis/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,707 wheel INFO adding 'django/contrib/gis/locale/tt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,708 wheel INFO adding 'django/contrib/gis/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,708 wheel INFO adding 'django/contrib/gis/locale/udm/LC_MESSAGES/django.po'
2025-04-22 17:58:56,708 wheel INFO adding 'django/contrib/gis/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,708 wheel INFO adding 'django/contrib/gis/locale/uk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,708 wheel INFO adding 'django/contrib/gis/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,709 wheel INFO adding 'django/contrib/gis/locale/ur/LC_MESSAGES/django.po'
2025-04-22 17:58:56,709 wheel INFO adding 'django/contrib/gis/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,709 wheel INFO adding 'django/contrib/gis/locale/vi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,709 wheel INFO adding 'django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,709 wheel INFO adding 'django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 17:58:56,710 wheel INFO adding 'django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,710 wheel INFO adding 'django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 17:58:56,710 wheel INFO adding 'django/contrib/gis/management/__init__.py'
2025-04-22 17:58:56,710 wheel INFO adding 'django/contrib/gis/management/commands/__init__.py'
2025-04-22 17:58:56,710 wheel INFO adding 'django/contrib/gis/management/commands/inspectdb.py'
2025-04-22 17:58:56,711 wheel INFO adding 'django/contrib/gis/management/commands/ogrinspect.py'
2025-04-22 17:58:56,711 wheel INFO adding 'django/contrib/gis/serializers/__init__.py'
2025-04-22 17:58:56,711 wheel INFO adding 'django/contrib/gis/serializers/geojson.py'
2025-04-22 17:58:56,711 wheel INFO adding 'django/contrib/gis/sitemaps/__init__.py'
2025-04-22 17:58:56,711 wheel INFO adding 'django/contrib/gis/sitemaps/kml.py'
2025-04-22 17:58:56,712 wheel INFO adding 'django/contrib/gis/sitemaps/views.py'
2025-04-22 17:58:56,712 wheel INFO adding 'django/contrib/gis/static/gis/css/ol3.css'
2025-04-22 17:58:56,712 wheel INFO adding 'django/contrib/gis/static/gis/img/draw_line_off.svg'
2025-04-22 17:58:56,712 wheel INFO adding 'django/contrib/gis/static/gis/img/draw_line_on.svg'
2025-04-22 17:58:56,712 wheel INFO adding 'django/contrib/gis/static/gis/img/draw_point_off.svg'
2025-04-22 17:58:56,712 wheel INFO adding 'django/contrib/gis/static/gis/img/draw_point_on.svg'
2025-04-22 17:58:56,713 wheel INFO adding 'django/contrib/gis/static/gis/img/draw_polygon_off.svg'
2025-04-22 17:58:56,713 wheel INFO adding 'django/contrib/gis/static/gis/img/draw_polygon_on.svg'
2025-04-22 17:58:56,713 wheel INFO adding 'django/contrib/gis/static/gis/js/OLMapWidget.js'
2025-04-22 17:58:56,713 wheel INFO adding 'django/contrib/gis/templates/gis/openlayers-osm.html'
2025-04-22 17:58:56,713 wheel INFO adding 'django/contrib/gis/templates/gis/openlayers.html'
2025-04-22 17:58:56,714 wheel INFO adding 'django/contrib/gis/templates/gis/admin/openlayers.html'
2025-04-22 17:58:56,714 wheel INFO adding 'django/contrib/gis/templates/gis/admin/openlayers.js'
2025-04-22 17:58:56,714 wheel INFO adding 'django/contrib/gis/templates/gis/admin/osm.html'
2025-04-22 17:58:56,714 wheel INFO adding 'django/contrib/gis/templates/gis/admin/osm.js'
2025-04-22 17:58:56,714 wheel INFO adding 'django/contrib/gis/templates/gis/kml/base.kml'
2025-04-22 17:58:56,715 wheel INFO adding 'django/contrib/gis/templates/gis/kml/placemarks.kml'
2025-04-22 17:58:56,715 wheel INFO adding 'django/contrib/gis/utils/__init__.py'
2025-04-22 17:58:56,715 wheel INFO adding 'django/contrib/gis/utils/layermapping.py'
2025-04-22 17:58:56,715 wheel INFO adding 'django/contrib/gis/utils/ogrinfo.py'
2025-04-22 17:58:56,715 wheel INFO adding 'django/contrib/gis/utils/ogrinspect.py'
2025-04-22 17:58:56,716 wheel INFO adding 'django/contrib/gis/utils/srs.py'
2025-04-22 17:58:56,716 wheel INFO adding 'django/contrib/humanize/__init__.py'
2025-04-22 17:58:56,716 wheel INFO adding 'django/contrib/humanize/apps.py'
2025-04-22 17:58:56,717 wheel INFO adding 'django/contrib/humanize/locale/af/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,717 wheel INFO adding 'django/contrib/humanize/locale/af/LC_MESSAGES/django.po'
2025-04-22 17:58:56,717 wheel INFO adding 'django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,718 wheel INFO adding 'django/contrib/humanize/locale/ar/LC_MESSAGES/django.po'
2025-04-22 17:58:56,718 wheel INFO adding 'django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,718 wheel INFO adding 'django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 17:58:56,718 wheel INFO adding 'django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,719 wheel INFO adding 'django/contrib/humanize/locale/ast/LC_MESSAGES/django.po'
2025-04-22 17:58:56,719 wheel INFO adding 'django/contrib/humanize/locale/az/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,719 wheel INFO adding 'django/contrib/humanize/locale/az/LC_MESSAGES/django.po'
2025-04-22 17:58:56,719 wheel INFO adding 'django/contrib/humanize/locale/be/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,719 wheel INFO adding 'django/contrib/humanize/locale/be/LC_MESSAGES/django.po'
2025-04-22 17:58:56,720 wheel INFO adding 'django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,720 wheel INFO adding 'django/contrib/humanize/locale/bg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,720 wheel INFO adding 'django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,720 wheel INFO adding 'django/contrib/humanize/locale/bn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,721 wheel INFO adding 'django/contrib/humanize/locale/br/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,721 wheel INFO adding 'django/contrib/humanize/locale/br/LC_MESSAGES/django.po'
2025-04-22 17:58:56,721 wheel INFO adding 'django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,721 wheel INFO adding 'django/contrib/humanize/locale/bs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,721 wheel INFO adding 'django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,722 wheel INFO adding 'django/contrib/humanize/locale/ca/LC_MESSAGES/django.po'
2025-04-22 17:58:56,722 wheel INFO adding 'django/contrib/humanize/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,722 wheel INFO adding 'django/contrib/humanize/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,722 wheel INFO adding 'django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,722 wheel INFO adding 'django/contrib/humanize/locale/cs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,723 wheel INFO adding 'django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,723 wheel INFO adding 'django/contrib/humanize/locale/cy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,723 wheel INFO adding 'django/contrib/humanize/locale/da/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,723 wheel INFO adding 'django/contrib/humanize/locale/da/LC_MESSAGES/django.po'
2025-04-22 17:58:56,724 wheel INFO adding 'django/contrib/humanize/locale/de/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,724 wheel INFO adding 'django/contrib/humanize/locale/de/LC_MESSAGES/django.po'
2025-04-22 17:58:56,724 wheel INFO adding 'django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,724 wheel INFO adding 'django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,724 wheel INFO adding 'django/contrib/humanize/locale/el/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,725 wheel INFO adding 'django/contrib/humanize/locale/el/LC_MESSAGES/django.po'
2025-04-22 17:58:56,725 wheel INFO adding 'django/contrib/humanize/locale/en/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,725 wheel INFO adding 'django/contrib/humanize/locale/en/LC_MESSAGES/django.po'
2025-04-22 17:58:56,725 wheel INFO adding 'django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,725 wheel INFO adding 'django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 17:58:56,726 wheel INFO adding 'django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,726 wheel INFO adding 'django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 17:58:56,726 wheel INFO adding 'django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,726 wheel INFO adding 'django/contrib/humanize/locale/eo/LC_MESSAGES/django.po'
2025-04-22 17:58:56,727 wheel INFO adding 'django/contrib/humanize/locale/es/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,727 wheel INFO adding 'django/contrib/humanize/locale/es/LC_MESSAGES/django.po'
2025-04-22 17:58:56,727 wheel INFO adding 'django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,727 wheel INFO adding 'django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,727 wheel INFO adding 'django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,728 wheel INFO adding 'django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 17:58:56,728 wheel INFO adding 'django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,728 wheel INFO adding 'django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 17:58:56,728 wheel INFO adding 'django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,728 wheel INFO adding 'django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 17:58:56,729 wheel INFO adding 'django/contrib/humanize/locale/et/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,729 wheel INFO adding 'django/contrib/humanize/locale/et/LC_MESSAGES/django.po'
2025-04-22 17:58:56,729 wheel INFO adding 'django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,729 wheel INFO adding 'django/contrib/humanize/locale/eu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,730 wheel INFO adding 'django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,730 wheel INFO adding 'django/contrib/humanize/locale/fa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,730 wheel INFO adding 'django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,730 wheel INFO adding 'django/contrib/humanize/locale/fi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,730 wheel INFO adding 'django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,731 wheel INFO adding 'django/contrib/humanize/locale/fr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,731 wheel INFO adding 'django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,731 wheel INFO adding 'django/contrib/humanize/locale/fy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,731 wheel INFO adding 'django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,731 wheel INFO adding 'django/contrib/humanize/locale/ga/LC_MESSAGES/django.po'
2025-04-22 17:58:56,732 wheel INFO adding 'django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,732 wheel INFO adding 'django/contrib/humanize/locale/gd/LC_MESSAGES/django.po'
2025-04-22 17:58:56,732 wheel INFO adding 'django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,732 wheel INFO adding 'django/contrib/humanize/locale/gl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,733 wheel INFO adding 'django/contrib/humanize/locale/he/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,733 wheel INFO adding 'django/contrib/humanize/locale/he/LC_MESSAGES/django.po'
2025-04-22 17:58:56,733 wheel INFO adding 'django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,733 wheel INFO adding 'django/contrib/humanize/locale/hi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,734 wheel INFO adding 'django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,734 wheel INFO adding 'django/contrib/humanize/locale/hr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,734 wheel INFO adding 'django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,734 wheel INFO adding 'django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,734 wheel INFO adding 'django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,735 wheel INFO adding 'django/contrib/humanize/locale/hu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,735 wheel INFO adding 'django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,735 wheel INFO adding 'django/contrib/humanize/locale/hy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,735 wheel INFO adding 'django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,735 wheel INFO adding 'django/contrib/humanize/locale/ia/LC_MESSAGES/django.po'
2025-04-22 17:58:56,736 wheel INFO adding 'django/contrib/humanize/locale/id/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,736 wheel INFO adding 'django/contrib/humanize/locale/id/LC_MESSAGES/django.po'
2025-04-22 17:58:56,736 wheel INFO adding 'django/contrib/humanize/locale/io/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,736 wheel INFO adding 'django/contrib/humanize/locale/io/LC_MESSAGES/django.po'
2025-04-22 17:58:56,737 wheel INFO adding 'django/contrib/humanize/locale/is/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,737 wheel INFO adding 'django/contrib/humanize/locale/is/LC_MESSAGES/django.po'
2025-04-22 17:58:56,737 wheel INFO adding 'django/contrib/humanize/locale/it/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,737 wheel INFO adding 'django/contrib/humanize/locale/it/LC_MESSAGES/django.po'
2025-04-22 17:58:56,738 wheel INFO adding 'django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,738 wheel INFO adding 'django/contrib/humanize/locale/ja/LC_MESSAGES/django.po'
2025-04-22 17:58:56,738 wheel INFO adding 'django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,738 wheel INFO adding 'django/contrib/humanize/locale/ka/LC_MESSAGES/django.po'
2025-04-22 17:58:56,738 wheel INFO adding 'django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,739 wheel INFO adding 'django/contrib/humanize/locale/kk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,739 wheel INFO adding 'django/contrib/humanize/locale/km/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,739 wheel INFO adding 'django/contrib/humanize/locale/km/LC_MESSAGES/django.po'
2025-04-22 17:58:56,739 wheel INFO adding 'django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,739 wheel INFO adding 'django/contrib/humanize/locale/kn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,740 wheel INFO adding 'django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,740 wheel INFO adding 'django/contrib/humanize/locale/ko/LC_MESSAGES/django.po'
2025-04-22 17:58:56,740 wheel INFO adding 'django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,740 wheel INFO adding 'django/contrib/humanize/locale/ky/LC_MESSAGES/django.po'
2025-04-22 17:58:56,740 wheel INFO adding 'django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,741 wheel INFO adding 'django/contrib/humanize/locale/lb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,741 wheel INFO adding 'django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,741 wheel INFO adding 'django/contrib/humanize/locale/lt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,741 wheel INFO adding 'django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,741 wheel INFO adding 'django/contrib/humanize/locale/lv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,742 wheel INFO adding 'django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,742 wheel INFO adding 'django/contrib/humanize/locale/mk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,742 wheel INFO adding 'django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,742 wheel INFO adding 'django/contrib/humanize/locale/ml/LC_MESSAGES/django.po'
2025-04-22 17:58:56,743 wheel INFO adding 'django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,743 wheel INFO adding 'django/contrib/humanize/locale/mn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,743 wheel INFO adding 'django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,743 wheel INFO adding 'django/contrib/humanize/locale/mr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,743 wheel INFO adding 'django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,744 wheel INFO adding 'django/contrib/humanize/locale/ms/LC_MESSAGES/django.po'
2025-04-22 17:58:56,744 wheel INFO adding 'django/contrib/humanize/locale/my/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,744 wheel INFO adding 'django/contrib/humanize/locale/my/LC_MESSAGES/django.po'
2025-04-22 17:58:56,744 wheel INFO adding 'django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,745 wheel INFO adding 'django/contrib/humanize/locale/nb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,745 wheel INFO adding 'django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,745 wheel INFO adding 'django/contrib/humanize/locale/ne/LC_MESSAGES/django.po'
2025-04-22 17:58:56,745 wheel INFO adding 'django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,745 wheel INFO adding 'django/contrib/humanize/locale/nl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,746 wheel INFO adding 'django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,746 wheel INFO adding 'django/contrib/humanize/locale/nn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,746 wheel INFO adding 'django/contrib/humanize/locale/os/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,746 wheel INFO adding 'django/contrib/humanize/locale/os/LC_MESSAGES/django.po'
2025-04-22 17:58:56,746 wheel INFO adding 'django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,747 wheel INFO adding 'django/contrib/humanize/locale/pa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,747 wheel INFO adding 'django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,747 wheel INFO adding 'django/contrib/humanize/locale/pl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,747 wheel INFO adding 'django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,748 wheel INFO adding 'django/contrib/humanize/locale/pt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,748 wheel INFO adding 'django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,748 wheel INFO adding 'django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,748 wheel INFO adding 'django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,748 wheel INFO adding 'django/contrib/humanize/locale/ro/LC_MESSAGES/django.po'
2025-04-22 17:58:56,749 wheel INFO adding 'django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,749 wheel INFO adding 'django/contrib/humanize/locale/ru/LC_MESSAGES/django.po'
2025-04-22 17:58:56,749 wheel INFO adding 'django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,749 wheel INFO adding 'django/contrib/humanize/locale/sk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,750 wheel INFO adding 'django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,750 wheel INFO adding 'django/contrib/humanize/locale/sl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,750 wheel INFO adding 'django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,750 wheel INFO adding 'django/contrib/humanize/locale/sq/LC_MESSAGES/django.po'
2025-04-22 17:58:56,750 wheel INFO adding 'django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,751 wheel INFO adding 'django/contrib/humanize/locale/sr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,751 wheel INFO adding 'django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,751 wheel INFO adding 'django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,751 wheel INFO adding 'django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,752 wheel INFO adding 'django/contrib/humanize/locale/sv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,752 wheel INFO adding 'django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,752 wheel INFO adding 'django/contrib/humanize/locale/sw/LC_MESSAGES/django.po'
2025-04-22 17:58:56,752 wheel INFO adding 'django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,752 wheel INFO adding 'django/contrib/humanize/locale/ta/LC_MESSAGES/django.po'
2025-04-22 17:58:56,753 wheel INFO adding 'django/contrib/humanize/locale/te/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,753 wheel INFO adding 'django/contrib/humanize/locale/te/LC_MESSAGES/django.po'
2025-04-22 17:58:56,753 wheel INFO adding 'django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,753 wheel INFO adding 'django/contrib/humanize/locale/tg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,753 wheel INFO adding 'django/contrib/humanize/locale/th/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,754 wheel INFO adding 'django/contrib/humanize/locale/th/LC_MESSAGES/django.po'
2025-04-22 17:58:56,754 wheel INFO adding 'django/contrib/humanize/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,754 wheel INFO adding 'django/contrib/humanize/locale/tk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,754 wheel INFO adding 'django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,754 wheel INFO adding 'django/contrib/humanize/locale/tr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,755 wheel INFO adding 'django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,755 wheel INFO adding 'django/contrib/humanize/locale/tt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,755 wheel INFO adding 'django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,755 wheel INFO adding 'django/contrib/humanize/locale/udm/LC_MESSAGES/django.po'
2025-04-22 17:58:56,755 wheel INFO adding 'django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,756 wheel INFO adding 'django/contrib/humanize/locale/uk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,756 wheel INFO adding 'django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,756 wheel INFO adding 'django/contrib/humanize/locale/ur/LC_MESSAGES/django.po'
2025-04-22 17:58:56,756 wheel INFO adding 'django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,757 wheel INFO adding 'django/contrib/humanize/locale/uz/LC_MESSAGES/django.po'
2025-04-22 17:58:56,757 wheel INFO adding 'django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,757 wheel INFO adding 'django/contrib/humanize/locale/vi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,757 wheel INFO adding 'django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,757 wheel INFO adding 'django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 17:58:56,758 wheel INFO adding 'django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,758 wheel INFO adding 'django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 17:58:56,758 wheel INFO adding 'django/contrib/humanize/templatetags/__init__.py'
2025-04-22 17:58:56,758 wheel INFO adding 'django/contrib/humanize/templatetags/humanize.py'
2025-04-22 17:58:56,758 wheel INFO adding 'django/contrib/messages/__init__.py'
2025-04-22 17:58:56,759 wheel INFO adding 'django/contrib/messages/api.py'
2025-04-22 17:58:56,759 wheel INFO adding 'django/contrib/messages/apps.py'
2025-04-22 17:58:56,759 wheel INFO adding 'django/contrib/messages/constants.py'
2025-04-22 17:58:56,759 wheel INFO adding 'django/contrib/messages/context_processors.py'
2025-04-22 17:58:56,759 wheel INFO adding 'django/contrib/messages/middleware.py'
2025-04-22 17:58:56,759 wheel INFO adding 'django/contrib/messages/utils.py'
2025-04-22 17:58:56,760 wheel INFO adding 'django/contrib/messages/views.py'
2025-04-22 17:58:56,760 wheel INFO adding 'django/contrib/messages/storage/__init__.py'
2025-04-22 17:58:56,760 wheel INFO adding 'django/contrib/messages/storage/base.py'
2025-04-22 17:58:56,760 wheel INFO adding 'django/contrib/messages/storage/cookie.py'
2025-04-22 17:58:56,760 wheel INFO adding 'django/contrib/messages/storage/fallback.py'
2025-04-22 17:58:56,761 wheel INFO adding 'django/contrib/messages/storage/session.py'
2025-04-22 17:58:56,761 wheel INFO adding 'django/contrib/postgres/__init__.py'
2025-04-22 17:58:56,761 wheel INFO adding 'django/contrib/postgres/apps.py'
2025-04-22 17:58:56,761 wheel INFO adding 'django/contrib/postgres/constraints.py'
2025-04-22 17:58:56,761 wheel INFO adding 'django/contrib/postgres/expressions.py'
2025-04-22 17:58:56,761 wheel INFO adding 'django/contrib/postgres/functions.py'
2025-04-22 17:58:56,762 wheel INFO adding 'django/contrib/postgres/indexes.py'
2025-04-22 17:58:56,762 wheel INFO adding 'django/contrib/postgres/lookups.py'
2025-04-22 17:58:56,762 wheel INFO adding 'django/contrib/postgres/operations.py'
2025-04-22 17:58:56,762 wheel INFO adding 'django/contrib/postgres/search.py'
2025-04-22 17:58:56,762 wheel INFO adding 'django/contrib/postgres/serializers.py'
2025-04-22 17:58:56,762 wheel INFO adding 'django/contrib/postgres/signals.py'
2025-04-22 17:58:56,763 wheel INFO adding 'django/contrib/postgres/utils.py'
2025-04-22 17:58:56,763 wheel INFO adding 'django/contrib/postgres/validators.py'
2025-04-22 17:58:56,763 wheel INFO adding 'django/contrib/postgres/aggregates/__init__.py'
2025-04-22 17:58:56,763 wheel INFO adding 'django/contrib/postgres/aggregates/general.py'
2025-04-22 17:58:56,763 wheel INFO adding 'django/contrib/postgres/aggregates/mixins.py'
2025-04-22 17:58:56,764 wheel INFO adding 'django/contrib/postgres/aggregates/statistics.py'
2025-04-22 17:58:56,764 wheel INFO adding 'django/contrib/postgres/fields/__init__.py'
2025-04-22 17:58:56,764 wheel INFO adding 'django/contrib/postgres/fields/array.py'
2025-04-22 17:58:56,764 wheel INFO adding 'django/contrib/postgres/fields/citext.py'
2025-04-22 17:58:56,764 wheel INFO adding 'django/contrib/postgres/fields/hstore.py'
2025-04-22 17:58:56,764 wheel INFO adding 'django/contrib/postgres/fields/jsonb.py'
2025-04-22 17:58:56,765 wheel INFO adding 'django/contrib/postgres/fields/ranges.py'
2025-04-22 17:58:56,765 wheel INFO adding 'django/contrib/postgres/fields/utils.py'
2025-04-22 17:58:56,765 wheel INFO adding 'django/contrib/postgres/forms/__init__.py'
2025-04-22 17:58:56,765 wheel INFO adding 'django/contrib/postgres/forms/array.py'
2025-04-22 17:58:56,765 wheel INFO adding 'django/contrib/postgres/forms/hstore.py'
2025-04-22 17:58:56,766 wheel INFO adding 'django/contrib/postgres/forms/ranges.py'
2025-04-22 17:58:56,766 wheel INFO adding 'django/contrib/postgres/jinja2/postgres/widgets/split_array.html'
2025-04-22 17:58:56,767 wheel INFO adding 'django/contrib/postgres/locale/af/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,767 wheel INFO adding 'django/contrib/postgres/locale/af/LC_MESSAGES/django.po'
2025-04-22 17:58:56,767 wheel INFO adding 'django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,767 wheel INFO adding 'django/contrib/postgres/locale/ar/LC_MESSAGES/django.po'
2025-04-22 17:58:56,767 wheel INFO adding 'django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,768 wheel INFO adding 'django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 17:58:56,768 wheel INFO adding 'django/contrib/postgres/locale/az/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,768 wheel INFO adding 'django/contrib/postgres/locale/az/LC_MESSAGES/django.po'
2025-04-22 17:58:56,768 wheel INFO adding 'django/contrib/postgres/locale/be/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,769 wheel INFO adding 'django/contrib/postgres/locale/be/LC_MESSAGES/django.po'
2025-04-22 17:58:56,769 wheel INFO adding 'django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,769 wheel INFO adding 'django/contrib/postgres/locale/bg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,769 wheel INFO adding 'django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,769 wheel INFO adding 'django/contrib/postgres/locale/ca/LC_MESSAGES/django.po'
2025-04-22 17:58:56,770 wheel INFO adding 'django/contrib/postgres/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,770 wheel INFO adding 'django/contrib/postgres/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,770 wheel INFO adding 'django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,770 wheel INFO adding 'django/contrib/postgres/locale/cs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,770 wheel INFO adding 'django/contrib/postgres/locale/da/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,771 wheel INFO adding 'django/contrib/postgres/locale/da/LC_MESSAGES/django.po'
2025-04-22 17:58:56,771 wheel INFO adding 'django/contrib/postgres/locale/de/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,771 wheel INFO adding 'django/contrib/postgres/locale/de/LC_MESSAGES/django.po'
2025-04-22 17:58:56,771 wheel INFO adding 'django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,771 wheel INFO adding 'django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,772 wheel INFO adding 'django/contrib/postgres/locale/el/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,772 wheel INFO adding 'django/contrib/postgres/locale/el/LC_MESSAGES/django.po'
2025-04-22 17:58:56,772 wheel INFO adding 'django/contrib/postgres/locale/en/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,772 wheel INFO adding 'django/contrib/postgres/locale/en/LC_MESSAGES/django.po'
2025-04-22 17:58:56,772 wheel INFO adding 'django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,773 wheel INFO adding 'django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 17:58:56,773 wheel INFO adding 'django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,773 wheel INFO adding 'django/contrib/postgres/locale/eo/LC_MESSAGES/django.po'
2025-04-22 17:58:56,773 wheel INFO adding 'django/contrib/postgres/locale/es/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,773 wheel INFO adding 'django/contrib/postgres/locale/es/LC_MESSAGES/django.po'
2025-04-22 17:58:56,774 wheel INFO adding 'django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,774 wheel INFO adding 'django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,774 wheel INFO adding 'django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,774 wheel INFO adding 'django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 17:58:56,774 wheel INFO adding 'django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,775 wheel INFO adding 'django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 17:58:56,775 wheel INFO adding 'django/contrib/postgres/locale/et/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,775 wheel INFO adding 'django/contrib/postgres/locale/et/LC_MESSAGES/django.po'
2025-04-22 17:58:56,775 wheel INFO adding 'django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,775 wheel INFO adding 'django/contrib/postgres/locale/eu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,776 wheel INFO adding 'django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,776 wheel INFO adding 'django/contrib/postgres/locale/fa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,776 wheel INFO adding 'django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,776 wheel INFO adding 'django/contrib/postgres/locale/fi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,777 wheel INFO adding 'django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,777 wheel INFO adding 'django/contrib/postgres/locale/fr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,777 wheel INFO adding 'django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,777 wheel INFO adding 'django/contrib/postgres/locale/gd/LC_MESSAGES/django.po'
2025-04-22 17:58:56,777 wheel INFO adding 'django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,778 wheel INFO adding 'django/contrib/postgres/locale/gl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,778 wheel INFO adding 'django/contrib/postgres/locale/he/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,778 wheel INFO adding 'django/contrib/postgres/locale/he/LC_MESSAGES/django.po'
2025-04-22 17:58:56,778 wheel INFO adding 'django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,778 wheel INFO adding 'django/contrib/postgres/locale/hr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,779 wheel INFO adding 'django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,779 wheel INFO adding 'django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,779 wheel INFO adding 'django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,779 wheel INFO adding 'django/contrib/postgres/locale/hu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,780 wheel INFO adding 'django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,780 wheel INFO adding 'django/contrib/postgres/locale/hy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,780 wheel INFO adding 'django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,780 wheel INFO adding 'django/contrib/postgres/locale/ia/LC_MESSAGES/django.po'
2025-04-22 17:58:56,780 wheel INFO adding 'django/contrib/postgres/locale/id/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,780 wheel INFO adding 'django/contrib/postgres/locale/id/LC_MESSAGES/django.po'
2025-04-22 17:58:56,781 wheel INFO adding 'django/contrib/postgres/locale/is/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,781 wheel INFO adding 'django/contrib/postgres/locale/is/LC_MESSAGES/django.po'
2025-04-22 17:58:56,781 wheel INFO adding 'django/contrib/postgres/locale/it/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,781 wheel INFO adding 'django/contrib/postgres/locale/it/LC_MESSAGES/django.po'
2025-04-22 17:58:56,781 wheel INFO adding 'django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,782 wheel INFO adding 'django/contrib/postgres/locale/ja/LC_MESSAGES/django.po'
2025-04-22 17:58:56,782 wheel INFO adding 'django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,782 wheel INFO adding 'django/contrib/postgres/locale/ka/LC_MESSAGES/django.po'
2025-04-22 17:58:56,782 wheel INFO adding 'django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,782 wheel INFO adding 'django/contrib/postgres/locale/kk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,783 wheel INFO adding 'django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,783 wheel INFO adding 'django/contrib/postgres/locale/ko/LC_MESSAGES/django.po'
2025-04-22 17:58:56,783 wheel INFO adding 'django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,783 wheel INFO adding 'django/contrib/postgres/locale/ky/LC_MESSAGES/django.po'
2025-04-22 17:58:56,784 wheel INFO adding 'django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,784 wheel INFO adding 'django/contrib/postgres/locale/lt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,784 wheel INFO adding 'django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,784 wheel INFO adding 'django/contrib/postgres/locale/lv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,784 wheel INFO adding 'django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,785 wheel INFO adding 'django/contrib/postgres/locale/mk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,785 wheel INFO adding 'django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,785 wheel INFO adding 'django/contrib/postgres/locale/ml/LC_MESSAGES/django.po'
2025-04-22 17:58:56,785 wheel INFO adding 'django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,785 wheel INFO adding 'django/contrib/postgres/locale/mn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,786 wheel INFO adding 'django/contrib/postgres/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,786 wheel INFO adding 'django/contrib/postgres/locale/ms/LC_MESSAGES/django.po'
2025-04-22 17:58:56,786 wheel INFO adding 'django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,786 wheel INFO adding 'django/contrib/postgres/locale/nb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,787 wheel INFO adding 'django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,787 wheel INFO adding 'django/contrib/postgres/locale/ne/LC_MESSAGES/django.po'
2025-04-22 17:58:56,787 wheel INFO adding 'django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,787 wheel INFO adding 'django/contrib/postgres/locale/nl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,787 wheel INFO adding 'django/contrib/postgres/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,787 wheel INFO adding 'django/contrib/postgres/locale/nn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,788 wheel INFO adding 'django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,788 wheel INFO adding 'django/contrib/postgres/locale/pl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,788 wheel INFO adding 'django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,788 wheel INFO adding 'django/contrib/postgres/locale/pt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,789 wheel INFO adding 'django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,789 wheel INFO adding 'django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,789 wheel INFO adding 'django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,789 wheel INFO adding 'django/contrib/postgres/locale/ro/LC_MESSAGES/django.po'
2025-04-22 17:58:56,789 wheel INFO adding 'django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,790 wheel INFO adding 'django/contrib/postgres/locale/ru/LC_MESSAGES/django.po'
2025-04-22 17:58:56,790 wheel INFO adding 'django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,790 wheel INFO adding 'django/contrib/postgres/locale/sk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,790 wheel INFO adding 'django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,790 wheel INFO adding 'django/contrib/postgres/locale/sl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,791 wheel INFO adding 'django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,791 wheel INFO adding 'django/contrib/postgres/locale/sq/LC_MESSAGES/django.po'
2025-04-22 17:58:56,791 wheel INFO adding 'django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,791 wheel INFO adding 'django/contrib/postgres/locale/sr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,791 wheel INFO adding 'django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,792 wheel INFO adding 'django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,792 wheel INFO adding 'django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,792 wheel INFO adding 'django/contrib/postgres/locale/sv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,792 wheel INFO adding 'django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,792 wheel INFO adding 'django/contrib/postgres/locale/tg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,793 wheel INFO adding 'django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,793 wheel INFO adding 'django/contrib/postgres/locale/tk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,793 wheel INFO adding 'django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,793 wheel INFO adding 'django/contrib/postgres/locale/tr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,794 wheel INFO adding 'django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,794 wheel INFO adding 'django/contrib/postgres/locale/uk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,794 wheel INFO adding 'django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,794 wheel INFO adding 'django/contrib/postgres/locale/uz/LC_MESSAGES/django.po'
2025-04-22 17:58:56,794 wheel INFO adding 'django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,794 wheel INFO adding 'django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 17:58:56,795 wheel INFO adding 'django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,795 wheel INFO adding 'django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 17:58:56,795 wheel INFO adding 'django/contrib/postgres/templates/postgres/widgets/split_array.html'
2025-04-22 17:58:56,795 wheel INFO adding 'django/contrib/redirects/__init__.py'
2025-04-22 17:58:56,795 wheel INFO adding 'django/contrib/redirects/admin.py'
2025-04-22 17:58:56,796 wheel INFO adding 'django/contrib/redirects/apps.py'
2025-04-22 17:58:56,796 wheel INFO adding 'django/contrib/redirects/middleware.py'
2025-04-22 17:58:56,796 wheel INFO adding 'django/contrib/redirects/models.py'
2025-04-22 17:58:56,797 wheel INFO adding 'django/contrib/redirects/locale/af/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,797 wheel INFO adding 'django/contrib/redirects/locale/af/LC_MESSAGES/django.po'
2025-04-22 17:58:56,797 wheel INFO adding 'django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,797 wheel INFO adding 'django/contrib/redirects/locale/ar/LC_MESSAGES/django.po'
2025-04-22 17:58:56,798 wheel INFO adding 'django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,798 wheel INFO adding 'django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 17:58:56,798 wheel INFO adding 'django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,798 wheel INFO adding 'django/contrib/redirects/locale/ast/LC_MESSAGES/django.po'
2025-04-22 17:58:56,798 wheel INFO adding 'django/contrib/redirects/locale/az/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,799 wheel INFO adding 'django/contrib/redirects/locale/az/LC_MESSAGES/django.po'
2025-04-22 17:58:56,799 wheel INFO adding 'django/contrib/redirects/locale/be/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,799 wheel INFO adding 'django/contrib/redirects/locale/be/LC_MESSAGES/django.po'
2025-04-22 17:58:56,799 wheel INFO adding 'django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,799 wheel INFO adding 'django/contrib/redirects/locale/bg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,800 wheel INFO adding 'django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,800 wheel INFO adding 'django/contrib/redirects/locale/bn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,800 wheel INFO adding 'django/contrib/redirects/locale/br/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,800 wheel INFO adding 'django/contrib/redirects/locale/br/LC_MESSAGES/django.po'
2025-04-22 17:58:56,800 wheel INFO adding 'django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,801 wheel INFO adding 'django/contrib/redirects/locale/bs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,801 wheel INFO adding 'django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,801 wheel INFO adding 'django/contrib/redirects/locale/ca/LC_MESSAGES/django.po'
2025-04-22 17:58:56,801 wheel INFO adding 'django/contrib/redirects/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,801 wheel INFO adding 'django/contrib/redirects/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,802 wheel INFO adding 'django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,802 wheel INFO adding 'django/contrib/redirects/locale/cs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,802 wheel INFO adding 'django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,802 wheel INFO adding 'django/contrib/redirects/locale/cy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,802 wheel INFO adding 'django/contrib/redirects/locale/da/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,803 wheel INFO adding 'django/contrib/redirects/locale/da/LC_MESSAGES/django.po'
2025-04-22 17:58:56,803 wheel INFO adding 'django/contrib/redirects/locale/de/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,803 wheel INFO adding 'django/contrib/redirects/locale/de/LC_MESSAGES/django.po'
2025-04-22 17:58:56,803 wheel INFO adding 'django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,804 wheel INFO adding 'django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,804 wheel INFO adding 'django/contrib/redirects/locale/el/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,804 wheel INFO adding 'django/contrib/redirects/locale/el/LC_MESSAGES/django.po'
2025-04-22 17:58:56,804 wheel INFO adding 'django/contrib/redirects/locale/en/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,804 wheel INFO adding 'django/contrib/redirects/locale/en/LC_MESSAGES/django.po'
2025-04-22 17:58:56,804 wheel INFO adding 'django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,805 wheel INFO adding 'django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 17:58:56,805 wheel INFO adding 'django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,805 wheel INFO adding 'django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 17:58:56,805 wheel INFO adding 'django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,805 wheel INFO adding 'django/contrib/redirects/locale/eo/LC_MESSAGES/django.po'
2025-04-22 17:58:56,806 wheel INFO adding 'django/contrib/redirects/locale/es/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,806 wheel INFO adding 'django/contrib/redirects/locale/es/LC_MESSAGES/django.po'
2025-04-22 17:58:56,806 wheel INFO adding 'django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,806 wheel INFO adding 'django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,806 wheel INFO adding 'django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,807 wheel INFO adding 'django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 17:58:56,807 wheel INFO adding 'django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,807 wheel INFO adding 'django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 17:58:56,807 wheel INFO adding 'django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,807 wheel INFO adding 'django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 17:58:56,808 wheel INFO adding 'django/contrib/redirects/locale/et/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,808 wheel INFO adding 'django/contrib/redirects/locale/et/LC_MESSAGES/django.po'
2025-04-22 17:58:56,808 wheel INFO adding 'django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,808 wheel INFO adding 'django/contrib/redirects/locale/eu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,808 wheel INFO adding 'django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,809 wheel INFO adding 'django/contrib/redirects/locale/fa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,809 wheel INFO adding 'django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,809 wheel INFO adding 'django/contrib/redirects/locale/fi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,809 wheel INFO adding 'django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,809 wheel INFO adding 'django/contrib/redirects/locale/fr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,810 wheel INFO adding 'django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,810 wheel INFO adding 'django/contrib/redirects/locale/fy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,810 wheel INFO adding 'django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,810 wheel INFO adding 'django/contrib/redirects/locale/ga/LC_MESSAGES/django.po'
2025-04-22 17:58:56,810 wheel INFO adding 'django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,810 wheel INFO adding 'django/contrib/redirects/locale/gd/LC_MESSAGES/django.po'
2025-04-22 17:58:56,811 wheel INFO adding 'django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,811 wheel INFO adding 'django/contrib/redirects/locale/gl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,811 wheel INFO adding 'django/contrib/redirects/locale/he/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,811 wheel INFO adding 'django/contrib/redirects/locale/he/LC_MESSAGES/django.po'
2025-04-22 17:58:56,811 wheel INFO adding 'django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,812 wheel INFO adding 'django/contrib/redirects/locale/hi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,812 wheel INFO adding 'django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,812 wheel INFO adding 'django/contrib/redirects/locale/hr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,812 wheel INFO adding 'django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,812 wheel INFO adding 'django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,813 wheel INFO adding 'django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,813 wheel INFO adding 'django/contrib/redirects/locale/hu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,813 wheel INFO adding 'django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,813 wheel INFO adding 'django/contrib/redirects/locale/hy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,813 wheel INFO adding 'django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,814 wheel INFO adding 'django/contrib/redirects/locale/ia/LC_MESSAGES/django.po'
2025-04-22 17:58:56,814 wheel INFO adding 'django/contrib/redirects/locale/id/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,814 wheel INFO adding 'django/contrib/redirects/locale/id/LC_MESSAGES/django.po'
2025-04-22 17:58:56,814 wheel INFO adding 'django/contrib/redirects/locale/io/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,814 wheel INFO adding 'django/contrib/redirects/locale/io/LC_MESSAGES/django.po'
2025-04-22 17:58:56,815 wheel INFO adding 'django/contrib/redirects/locale/is/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,815 wheel INFO adding 'django/contrib/redirects/locale/is/LC_MESSAGES/django.po'
2025-04-22 17:58:56,815 wheel INFO adding 'django/contrib/redirects/locale/it/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,815 wheel INFO adding 'django/contrib/redirects/locale/it/LC_MESSAGES/django.po'
2025-04-22 17:58:56,815 wheel INFO adding 'django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,815 wheel INFO adding 'django/contrib/redirects/locale/ja/LC_MESSAGES/django.po'
2025-04-22 17:58:56,816 wheel INFO adding 'django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,816 wheel INFO adding 'django/contrib/redirects/locale/ka/LC_MESSAGES/django.po'
2025-04-22 17:58:56,816 wheel INFO adding 'django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,816 wheel INFO adding 'django/contrib/redirects/locale/kab/LC_MESSAGES/django.po'
2025-04-22 17:58:56,816 wheel INFO adding 'django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,817 wheel INFO adding 'django/contrib/redirects/locale/kk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,817 wheel INFO adding 'django/contrib/redirects/locale/km/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,817 wheel INFO adding 'django/contrib/redirects/locale/km/LC_MESSAGES/django.po'
2025-04-22 17:58:56,817 wheel INFO adding 'django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,817 wheel INFO adding 'django/contrib/redirects/locale/kn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,818 wheel INFO adding 'django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,818 wheel INFO adding 'django/contrib/redirects/locale/ko/LC_MESSAGES/django.po'
2025-04-22 17:58:56,818 wheel INFO adding 'django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,818 wheel INFO adding 'django/contrib/redirects/locale/ky/LC_MESSAGES/django.po'
2025-04-22 17:58:56,818 wheel INFO adding 'django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,819 wheel INFO adding 'django/contrib/redirects/locale/lb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,819 wheel INFO adding 'django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,819 wheel INFO adding 'django/contrib/redirects/locale/lt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,819 wheel INFO adding 'django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,819 wheel INFO adding 'django/contrib/redirects/locale/lv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,820 wheel INFO adding 'django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,820 wheel INFO adding 'django/contrib/redirects/locale/mk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,820 wheel INFO adding 'django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,820 wheel INFO adding 'django/contrib/redirects/locale/ml/LC_MESSAGES/django.po'
2025-04-22 17:58:56,820 wheel INFO adding 'django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,821 wheel INFO adding 'django/contrib/redirects/locale/mn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,821 wheel INFO adding 'django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,821 wheel INFO adding 'django/contrib/redirects/locale/mr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,821 wheel INFO adding 'django/contrib/redirects/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,821 wheel INFO adding 'django/contrib/redirects/locale/ms/LC_MESSAGES/django.po'
2025-04-22 17:58:56,822 wheel INFO adding 'django/contrib/redirects/locale/my/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,822 wheel INFO adding 'django/contrib/redirects/locale/my/LC_MESSAGES/django.po'
2025-04-22 17:58:56,822 wheel INFO adding 'django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,822 wheel INFO adding 'django/contrib/redirects/locale/nb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,822 wheel INFO adding 'django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,822 wheel INFO adding 'django/contrib/redirects/locale/ne/LC_MESSAGES/django.po'
2025-04-22 17:58:56,823 wheel INFO adding 'django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,823 wheel INFO adding 'django/contrib/redirects/locale/nl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,823 wheel INFO adding 'django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,823 wheel INFO adding 'django/contrib/redirects/locale/nn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,824 wheel INFO adding 'django/contrib/redirects/locale/os/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,824 wheel INFO adding 'django/contrib/redirects/locale/os/LC_MESSAGES/django.po'
2025-04-22 17:58:56,824 wheel INFO adding 'django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,824 wheel INFO adding 'django/contrib/redirects/locale/pa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,824 wheel INFO adding 'django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,824 wheel INFO adding 'django/contrib/redirects/locale/pl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,825 wheel INFO adding 'django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,825 wheel INFO adding 'django/contrib/redirects/locale/pt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,825 wheel INFO adding 'django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,825 wheel INFO adding 'django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,825 wheel INFO adding 'django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,826 wheel INFO adding 'django/contrib/redirects/locale/ro/LC_MESSAGES/django.po'
2025-04-22 17:58:56,826 wheel INFO adding 'django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,826 wheel INFO adding 'django/contrib/redirects/locale/ru/LC_MESSAGES/django.po'
2025-04-22 17:58:56,826 wheel INFO adding 'django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,826 wheel INFO adding 'django/contrib/redirects/locale/sk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,827 wheel INFO adding 'django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,827 wheel INFO adding 'django/contrib/redirects/locale/sl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,827 wheel INFO adding 'django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,827 wheel INFO adding 'django/contrib/redirects/locale/sq/LC_MESSAGES/django.po'
2025-04-22 17:58:56,827 wheel INFO adding 'django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,828 wheel INFO adding 'django/contrib/redirects/locale/sr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,828 wheel INFO adding 'django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,828 wheel INFO adding 'django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,828 wheel INFO adding 'django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,828 wheel INFO adding 'django/contrib/redirects/locale/sv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,829 wheel INFO adding 'django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,829 wheel INFO adding 'django/contrib/redirects/locale/sw/LC_MESSAGES/django.po'
2025-04-22 17:58:56,829 wheel INFO adding 'django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,829 wheel INFO adding 'django/contrib/redirects/locale/ta/LC_MESSAGES/django.po'
2025-04-22 17:58:56,829 wheel INFO adding 'django/contrib/redirects/locale/te/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,830 wheel INFO adding 'django/contrib/redirects/locale/te/LC_MESSAGES/django.po'
2025-04-22 17:58:56,830 wheel INFO adding 'django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,830 wheel INFO adding 'django/contrib/redirects/locale/tg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,830 wheel INFO adding 'django/contrib/redirects/locale/th/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,830 wheel INFO adding 'django/contrib/redirects/locale/th/LC_MESSAGES/django.po'
2025-04-22 17:58:56,831 wheel INFO adding 'django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,831 wheel INFO adding 'django/contrib/redirects/locale/tk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,831 wheel INFO adding 'django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,831 wheel INFO adding 'django/contrib/redirects/locale/tr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,831 wheel INFO adding 'django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,832 wheel INFO adding 'django/contrib/redirects/locale/tt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,832 wheel INFO adding 'django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,832 wheel INFO adding 'django/contrib/redirects/locale/udm/LC_MESSAGES/django.po'
2025-04-22 17:58:56,832 wheel INFO adding 'django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,832 wheel INFO adding 'django/contrib/redirects/locale/uk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,833 wheel INFO adding 'django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,833 wheel INFO adding 'django/contrib/redirects/locale/ur/LC_MESSAGES/django.po'
2025-04-22 17:58:56,833 wheel INFO adding 'django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,833 wheel INFO adding 'django/contrib/redirects/locale/uz/LC_MESSAGES/django.po'
2025-04-22 17:58:56,833 wheel INFO adding 'django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,834 wheel INFO adding 'django/contrib/redirects/locale/vi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,834 wheel INFO adding 'django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,834 wheel INFO adding 'django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 17:58:56,834 wheel INFO adding 'django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,834 wheel INFO adding 'django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 17:58:56,835 wheel INFO adding 'django/contrib/redirects/migrations/0001_initial.py'
2025-04-22 17:58:56,835 wheel INFO adding 'django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py'
2025-04-22 17:58:56,835 wheel INFO adding 'django/contrib/redirects/migrations/__init__.py'
2025-04-22 17:58:56,835 wheel INFO adding 'django/contrib/sessions/__init__.py'
2025-04-22 17:58:56,835 wheel INFO adding 'django/contrib/sessions/apps.py'
2025-04-22 17:58:56,835 wheel INFO adding 'django/contrib/sessions/base_session.py'
2025-04-22 17:58:56,836 wheel INFO adding 'django/contrib/sessions/exceptions.py'
2025-04-22 17:58:56,836 wheel INFO adding 'django/contrib/sessions/middleware.py'
2025-04-22 17:58:56,836 wheel INFO adding 'django/contrib/sessions/models.py'
2025-04-22 17:58:56,836 wheel INFO adding 'django/contrib/sessions/serializers.py'
2025-04-22 17:58:56,836 wheel INFO adding 'django/contrib/sessions/backends/__init__.py'
2025-04-22 17:58:56,837 wheel INFO adding 'django/contrib/sessions/backends/base.py'
2025-04-22 17:58:56,837 wheel INFO adding 'django/contrib/sessions/backends/cache.py'
2025-04-22 17:58:56,837 wheel INFO adding 'django/contrib/sessions/backends/cached_db.py'
2025-04-22 17:58:56,837 wheel INFO adding 'django/contrib/sessions/backends/db.py'
2025-04-22 17:58:56,837 wheel INFO adding 'django/contrib/sessions/backends/file.py'
2025-04-22 17:58:56,837 wheel INFO adding 'django/contrib/sessions/backends/signed_cookies.py'
2025-04-22 17:58:56,838 wheel INFO adding 'django/contrib/sessions/locale/af/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,839 wheel INFO adding 'django/contrib/sessions/locale/af/LC_MESSAGES/django.po'
2025-04-22 17:58:56,839 wheel INFO adding 'django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,839 wheel INFO adding 'django/contrib/sessions/locale/ar/LC_MESSAGES/django.po'
2025-04-22 17:58:56,839 wheel INFO adding 'django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,839 wheel INFO adding 'django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 17:58:56,840 wheel INFO adding 'django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,840 wheel INFO adding 'django/contrib/sessions/locale/ast/LC_MESSAGES/django.po'
2025-04-22 17:58:56,840 wheel INFO adding 'django/contrib/sessions/locale/az/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,841 wheel INFO adding 'django/contrib/sessions/locale/az/LC_MESSAGES/django.po'
2025-04-22 17:58:56,841 wheel INFO adding 'django/contrib/sessions/locale/be/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,841 wheel INFO adding 'django/contrib/sessions/locale/be/LC_MESSAGES/django.po'
2025-04-22 17:58:56,841 wheel INFO adding 'django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,841 wheel INFO adding 'django/contrib/sessions/locale/bg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,842 wheel INFO adding 'django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,842 wheel INFO adding 'django/contrib/sessions/locale/bn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,842 wheel INFO adding 'django/contrib/sessions/locale/br/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,842 wheel INFO adding 'django/contrib/sessions/locale/br/LC_MESSAGES/django.po'
2025-04-22 17:58:56,842 wheel INFO adding 'django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,842 wheel INFO adding 'django/contrib/sessions/locale/bs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,843 wheel INFO adding 'django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,843 wheel INFO adding 'django/contrib/sessions/locale/ca/LC_MESSAGES/django.po'
2025-04-22 17:58:56,843 wheel INFO adding 'django/contrib/sessions/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,843 wheel INFO adding 'django/contrib/sessions/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,844 wheel INFO adding 'django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,844 wheel INFO adding 'django/contrib/sessions/locale/cs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,844 wheel INFO adding 'django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,844 wheel INFO adding 'django/contrib/sessions/locale/cy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,844 wheel INFO adding 'django/contrib/sessions/locale/da/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,844 wheel INFO adding 'django/contrib/sessions/locale/da/LC_MESSAGES/django.po'
2025-04-22 17:58:56,845 wheel INFO adding 'django/contrib/sessions/locale/de/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,845 wheel INFO adding 'django/contrib/sessions/locale/de/LC_MESSAGES/django.po'
2025-04-22 17:58:56,845 wheel INFO adding 'django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,845 wheel INFO adding 'django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,845 wheel INFO adding 'django/contrib/sessions/locale/el/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,846 wheel INFO adding 'django/contrib/sessions/locale/el/LC_MESSAGES/django.po'
2025-04-22 17:58:56,846 wheel INFO adding 'django/contrib/sessions/locale/en/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,846 wheel INFO adding 'django/contrib/sessions/locale/en/LC_MESSAGES/django.po'
2025-04-22 17:58:56,846 wheel INFO adding 'django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,847 wheel INFO adding 'django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 17:58:56,847 wheel INFO adding 'django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,847 wheel INFO adding 'django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 17:58:56,847 wheel INFO adding 'django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,847 wheel INFO adding 'django/contrib/sessions/locale/eo/LC_MESSAGES/django.po'
2025-04-22 17:58:56,848 wheel INFO adding 'django/contrib/sessions/locale/es/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,848 wheel INFO adding 'django/contrib/sessions/locale/es/LC_MESSAGES/django.po'
2025-04-22 17:58:56,848 wheel INFO adding 'django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,848 wheel INFO adding 'django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,848 wheel INFO adding 'django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,848 wheel INFO adding 'django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 17:58:56,849 wheel INFO adding 'django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,849 wheel INFO adding 'django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 17:58:56,849 wheel INFO adding 'django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,849 wheel INFO adding 'django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 17:58:56,849 wheel INFO adding 'django/contrib/sessions/locale/et/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,850 wheel INFO adding 'django/contrib/sessions/locale/et/LC_MESSAGES/django.po'
2025-04-22 17:58:56,850 wheel INFO adding 'django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,850 wheel INFO adding 'django/contrib/sessions/locale/eu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,850 wheel INFO adding 'django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,850 wheel INFO adding 'django/contrib/sessions/locale/fa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,851 wheel INFO adding 'django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,851 wheel INFO adding 'django/contrib/sessions/locale/fi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,851 wheel INFO adding 'django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,851 wheel INFO adding 'django/contrib/sessions/locale/fr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,851 wheel INFO adding 'django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,852 wheel INFO adding 'django/contrib/sessions/locale/fy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,852 wheel INFO adding 'django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,852 wheel INFO adding 'django/contrib/sessions/locale/ga/LC_MESSAGES/django.po'
2025-04-22 17:58:56,852 wheel INFO adding 'django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,852 wheel INFO adding 'django/contrib/sessions/locale/gd/LC_MESSAGES/django.po'
2025-04-22 17:58:56,852 wheel INFO adding 'django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,853 wheel INFO adding 'django/contrib/sessions/locale/gl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,853 wheel INFO adding 'django/contrib/sessions/locale/he/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,853 wheel INFO adding 'django/contrib/sessions/locale/he/LC_MESSAGES/django.po'
2025-04-22 17:58:56,853 wheel INFO adding 'django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,853 wheel INFO adding 'django/contrib/sessions/locale/hi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,854 wheel INFO adding 'django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,854 wheel INFO adding 'django/contrib/sessions/locale/hr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,854 wheel INFO adding 'django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,854 wheel INFO adding 'django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,854 wheel INFO adding 'django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,855 wheel INFO adding 'django/contrib/sessions/locale/hu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,855 wheel INFO adding 'django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,855 wheel INFO adding 'django/contrib/sessions/locale/hy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,855 wheel INFO adding 'django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,855 wheel INFO adding 'django/contrib/sessions/locale/ia/LC_MESSAGES/django.po'
2025-04-22 17:58:56,856 wheel INFO adding 'django/contrib/sessions/locale/id/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,856 wheel INFO adding 'django/contrib/sessions/locale/id/LC_MESSAGES/django.po'
2025-04-22 17:58:56,856 wheel INFO adding 'django/contrib/sessions/locale/io/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,856 wheel INFO adding 'django/contrib/sessions/locale/io/LC_MESSAGES/django.po'
2025-04-22 17:58:56,856 wheel INFO adding 'django/contrib/sessions/locale/is/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,857 wheel INFO adding 'django/contrib/sessions/locale/is/LC_MESSAGES/django.po'
2025-04-22 17:58:56,857 wheel INFO adding 'django/contrib/sessions/locale/it/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,857 wheel INFO adding 'django/contrib/sessions/locale/it/LC_MESSAGES/django.po'
2025-04-22 17:58:56,857 wheel INFO adding 'django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,857 wheel INFO adding 'django/contrib/sessions/locale/ja/LC_MESSAGES/django.po'
2025-04-22 17:58:56,857 wheel INFO adding 'django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,858 wheel INFO adding 'django/contrib/sessions/locale/ka/LC_MESSAGES/django.po'
2025-04-22 17:58:56,858 wheel INFO adding 'django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,858 wheel INFO adding 'django/contrib/sessions/locale/kab/LC_MESSAGES/django.po'
2025-04-22 17:58:56,858 wheel INFO adding 'django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,858 wheel INFO adding 'django/contrib/sessions/locale/kk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,859 wheel INFO adding 'django/contrib/sessions/locale/km/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,859 wheel INFO adding 'django/contrib/sessions/locale/km/LC_MESSAGES/django.po'
2025-04-22 17:58:56,859 wheel INFO adding 'django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,859 wheel INFO adding 'django/contrib/sessions/locale/kn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,859 wheel INFO adding 'django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,860 wheel INFO adding 'django/contrib/sessions/locale/ko/LC_MESSAGES/django.po'
2025-04-22 17:58:56,860 wheel INFO adding 'django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,860 wheel INFO adding 'django/contrib/sessions/locale/ky/LC_MESSAGES/django.po'
2025-04-22 17:58:56,860 wheel INFO adding 'django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,860 wheel INFO adding 'django/contrib/sessions/locale/lb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,861 wheel INFO adding 'django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,861 wheel INFO adding 'django/contrib/sessions/locale/lt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,861 wheel INFO adding 'django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,861 wheel INFO adding 'django/contrib/sessions/locale/lv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,861 wheel INFO adding 'django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,861 wheel INFO adding 'django/contrib/sessions/locale/mk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,862 wheel INFO adding 'django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,862 wheel INFO adding 'django/contrib/sessions/locale/ml/LC_MESSAGES/django.po'
2025-04-22 17:58:56,862 wheel INFO adding 'django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,862 wheel INFO adding 'django/contrib/sessions/locale/mn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,862 wheel INFO adding 'django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,863 wheel INFO adding 'django/contrib/sessions/locale/mr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,863 wheel INFO adding 'django/contrib/sessions/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,863 wheel INFO adding 'django/contrib/sessions/locale/ms/LC_MESSAGES/django.po'
2025-04-22 17:58:56,863 wheel INFO adding 'django/contrib/sessions/locale/my/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,863 wheel INFO adding 'django/contrib/sessions/locale/my/LC_MESSAGES/django.po'
2025-04-22 17:58:56,864 wheel INFO adding 'django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,864 wheel INFO adding 'django/contrib/sessions/locale/nb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,864 wheel INFO adding 'django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,864 wheel INFO adding 'django/contrib/sessions/locale/ne/LC_MESSAGES/django.po'
2025-04-22 17:58:56,864 wheel INFO adding 'django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,865 wheel INFO adding 'django/contrib/sessions/locale/nl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,865 wheel INFO adding 'django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,865 wheel INFO adding 'django/contrib/sessions/locale/nn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,865 wheel INFO adding 'django/contrib/sessions/locale/os/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,865 wheel INFO adding 'django/contrib/sessions/locale/os/LC_MESSAGES/django.po'
2025-04-22 17:58:56,866 wheel INFO adding 'django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,866 wheel INFO adding 'django/contrib/sessions/locale/pa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,866 wheel INFO adding 'django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,866 wheel INFO adding 'django/contrib/sessions/locale/pl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,867 wheel INFO adding 'django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,867 wheel INFO adding 'django/contrib/sessions/locale/pt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,867 wheel INFO adding 'django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,867 wheel INFO adding 'django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,867 wheel INFO adding 'django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,867 wheel INFO adding 'django/contrib/sessions/locale/ro/LC_MESSAGES/django.po'
2025-04-22 17:58:56,868 wheel INFO adding 'django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,868 wheel INFO adding 'django/contrib/sessions/locale/ru/LC_MESSAGES/django.po'
2025-04-22 17:58:56,868 wheel INFO adding 'django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,868 wheel INFO adding 'django/contrib/sessions/locale/sk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,868 wheel INFO adding 'django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,869 wheel INFO adding 'django/contrib/sessions/locale/sl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,869 wheel INFO adding 'django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,869 wheel INFO adding 'django/contrib/sessions/locale/sq/LC_MESSAGES/django.po'
2025-04-22 17:58:56,869 wheel INFO adding 'django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,869 wheel INFO adding 'django/contrib/sessions/locale/sr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,870 wheel INFO adding 'django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,870 wheel INFO adding 'django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,870 wheel INFO adding 'django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,870 wheel INFO adding 'django/contrib/sessions/locale/sv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,870 wheel INFO adding 'django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,871 wheel INFO adding 'django/contrib/sessions/locale/sw/LC_MESSAGES/django.po'
2025-04-22 17:58:56,871 wheel INFO adding 'django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,871 wheel INFO adding 'django/contrib/sessions/locale/ta/LC_MESSAGES/django.po'
2025-04-22 17:58:56,871 wheel INFO adding 'django/contrib/sessions/locale/te/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,871 wheel INFO adding 'django/contrib/sessions/locale/te/LC_MESSAGES/django.po'
2025-04-22 17:58:56,872 wheel INFO adding 'django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,872 wheel INFO adding 'django/contrib/sessions/locale/tg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,872 wheel INFO adding 'django/contrib/sessions/locale/th/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,872 wheel INFO adding 'django/contrib/sessions/locale/th/LC_MESSAGES/django.po'
2025-04-22 17:58:56,872 wheel INFO adding 'django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,872 wheel INFO adding 'django/contrib/sessions/locale/tk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,873 wheel INFO adding 'django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,873 wheel INFO adding 'django/contrib/sessions/locale/tr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,873 wheel INFO adding 'django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,873 wheel INFO adding 'django/contrib/sessions/locale/tt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,873 wheel INFO adding 'django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,874 wheel INFO adding 'django/contrib/sessions/locale/udm/LC_MESSAGES/django.po'
2025-04-22 17:58:56,874 wheel INFO adding 'django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,874 wheel INFO adding 'django/contrib/sessions/locale/uk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,874 wheel INFO adding 'django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,874 wheel INFO adding 'django/contrib/sessions/locale/ur/LC_MESSAGES/django.po'
2025-04-22 17:58:56,875 wheel INFO adding 'django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,875 wheel INFO adding 'django/contrib/sessions/locale/uz/LC_MESSAGES/django.po'
2025-04-22 17:58:56,875 wheel INFO adding 'django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,875 wheel INFO adding 'django/contrib/sessions/locale/vi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,875 wheel INFO adding 'django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,876 wheel INFO adding 'django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 17:58:56,876 wheel INFO adding 'django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,876 wheel INFO adding 'django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 17:58:56,876 wheel INFO adding 'django/contrib/sessions/management/__init__.py'
2025-04-22 17:58:56,876 wheel INFO adding 'django/contrib/sessions/management/commands/__init__.py'
2025-04-22 17:58:56,877 wheel INFO adding 'django/contrib/sessions/management/commands/clearsessions.py'
2025-04-22 17:58:56,877 wheel INFO adding 'django/contrib/sessions/migrations/0001_initial.py'
2025-04-22 17:58:56,877 wheel INFO adding 'django/contrib/sessions/migrations/__init__.py'
2025-04-22 17:58:56,877 wheel INFO adding 'django/contrib/sitemaps/__init__.py'
2025-04-22 17:58:56,877 wheel INFO adding 'django/contrib/sitemaps/apps.py'
2025-04-22 17:58:56,877 wheel INFO adding 'django/contrib/sitemaps/views.py'
2025-04-22 17:58:56,878 wheel INFO adding 'django/contrib/sitemaps/management/__init__.py'
2025-04-22 17:58:56,878 wheel INFO adding 'django/contrib/sitemaps/management/commands/__init__.py'
2025-04-22 17:58:56,878 wheel INFO adding 'django/contrib/sitemaps/management/commands/ping_google.py'
2025-04-22 17:58:56,878 wheel INFO adding 'django/contrib/sitemaps/templates/sitemap.xml'
2025-04-22 17:58:56,878 wheel INFO adding 'django/contrib/sitemaps/templates/sitemap_index.xml'
2025-04-22 17:58:56,879 wheel INFO adding 'django/contrib/sites/__init__.py'
2025-04-22 17:58:56,879 wheel INFO adding 'django/contrib/sites/admin.py'
2025-04-22 17:58:56,879 wheel INFO adding 'django/contrib/sites/apps.py'
2025-04-22 17:58:56,879 wheel INFO adding 'django/contrib/sites/checks.py'
2025-04-22 17:58:56,879 wheel INFO adding 'django/contrib/sites/management.py'
2025-04-22 17:58:56,879 wheel INFO adding 'django/contrib/sites/managers.py'
2025-04-22 17:58:56,880 wheel INFO adding 'django/contrib/sites/middleware.py'
2025-04-22 17:58:56,880 wheel INFO adding 'django/contrib/sites/models.py'
2025-04-22 17:58:56,880 wheel INFO adding 'django/contrib/sites/requests.py'
2025-04-22 17:58:56,880 wheel INFO adding 'django/contrib/sites/shortcuts.py'
2025-04-22 17:58:56,881 wheel INFO adding 'django/contrib/sites/locale/af/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,881 wheel INFO adding 'django/contrib/sites/locale/af/LC_MESSAGES/django.po'
2025-04-22 17:58:56,881 wheel INFO adding 'django/contrib/sites/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,882 wheel INFO adding 'django/contrib/sites/locale/ar/LC_MESSAGES/django.po'
2025-04-22 17:58:56,882 wheel INFO adding 'django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,882 wheel INFO adding 'django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 17:58:56,882 wheel INFO adding 'django/contrib/sites/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,882 wheel INFO adding 'django/contrib/sites/locale/ast/LC_MESSAGES/django.po'
2025-04-22 17:58:56,882 wheel INFO adding 'django/contrib/sites/locale/az/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,883 wheel INFO adding 'django/contrib/sites/locale/az/LC_MESSAGES/django.po'
2025-04-22 17:58:56,883 wheel INFO adding 'django/contrib/sites/locale/be/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,883 wheel INFO adding 'django/contrib/sites/locale/be/LC_MESSAGES/django.po'
2025-04-22 17:58:56,883 wheel INFO adding 'django/contrib/sites/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,883 wheel INFO adding 'django/contrib/sites/locale/bg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,884 wheel INFO adding 'django/contrib/sites/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,884 wheel INFO adding 'django/contrib/sites/locale/bn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,884 wheel INFO adding 'django/contrib/sites/locale/br/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,884 wheel INFO adding 'django/contrib/sites/locale/br/LC_MESSAGES/django.po'
2025-04-22 17:58:56,884 wheel INFO adding 'django/contrib/sites/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,885 wheel INFO adding 'django/contrib/sites/locale/bs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,885 wheel INFO adding 'django/contrib/sites/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,885 wheel INFO adding 'django/contrib/sites/locale/ca/LC_MESSAGES/django.po'
2025-04-22 17:58:56,885 wheel INFO adding 'django/contrib/sites/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,885 wheel INFO adding 'django/contrib/sites/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,886 wheel INFO adding 'django/contrib/sites/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,886 wheel INFO adding 'django/contrib/sites/locale/cs/LC_MESSAGES/django.po'
2025-04-22 17:58:56,886 wheel INFO adding 'django/contrib/sites/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,886 wheel INFO adding 'django/contrib/sites/locale/cy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,886 wheel INFO adding 'django/contrib/sites/locale/da/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,887 wheel INFO adding 'django/contrib/sites/locale/da/LC_MESSAGES/django.po'
2025-04-22 17:58:56,887 wheel INFO adding 'django/contrib/sites/locale/de/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,887 wheel INFO adding 'django/contrib/sites/locale/de/LC_MESSAGES/django.po'
2025-04-22 17:58:56,887 wheel INFO adding 'django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,887 wheel INFO adding 'django/contrib/sites/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,887 wheel INFO adding 'django/contrib/sites/locale/el/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,888 wheel INFO adding 'django/contrib/sites/locale/el/LC_MESSAGES/django.po'
2025-04-22 17:58:56,888 wheel INFO adding 'django/contrib/sites/locale/en/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,888 wheel INFO adding 'django/contrib/sites/locale/en/LC_MESSAGES/django.po'
2025-04-22 17:58:56,888 wheel INFO adding 'django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,888 wheel INFO adding 'django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 17:58:56,889 wheel INFO adding 'django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,889 wheel INFO adding 'django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 17:58:56,889 wheel INFO adding 'django/contrib/sites/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,889 wheel INFO adding 'django/contrib/sites/locale/eo/LC_MESSAGES/django.po'
2025-04-22 17:58:56,889 wheel INFO adding 'django/contrib/sites/locale/es/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,890 wheel INFO adding 'django/contrib/sites/locale/es/LC_MESSAGES/django.po'
2025-04-22 17:58:56,890 wheel INFO adding 'django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,890 wheel INFO adding 'django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,890 wheel INFO adding 'django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,890 wheel INFO adding 'django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 17:58:56,891 wheel INFO adding 'django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,891 wheel INFO adding 'django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 17:58:56,891 wheel INFO adding 'django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,891 wheel INFO adding 'django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 17:58:56,891 wheel INFO adding 'django/contrib/sites/locale/et/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,891 wheel INFO adding 'django/contrib/sites/locale/et/LC_MESSAGES/django.po'
2025-04-22 17:58:56,892 wheel INFO adding 'django/contrib/sites/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,892 wheel INFO adding 'django/contrib/sites/locale/eu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,892 wheel INFO adding 'django/contrib/sites/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,892 wheel INFO adding 'django/contrib/sites/locale/fa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,892 wheel INFO adding 'django/contrib/sites/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,893 wheel INFO adding 'django/contrib/sites/locale/fi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,893 wheel INFO adding 'django/contrib/sites/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,893 wheel INFO adding 'django/contrib/sites/locale/fr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,893 wheel INFO adding 'django/contrib/sites/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,893 wheel INFO adding 'django/contrib/sites/locale/fy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,894 wheel INFO adding 'django/contrib/sites/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,894 wheel INFO adding 'django/contrib/sites/locale/ga/LC_MESSAGES/django.po'
2025-04-22 17:58:56,894 wheel INFO adding 'django/contrib/sites/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,894 wheel INFO adding 'django/contrib/sites/locale/gd/LC_MESSAGES/django.po'
2025-04-22 17:58:56,894 wheel INFO adding 'django/contrib/sites/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,895 wheel INFO adding 'django/contrib/sites/locale/gl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,895 wheel INFO adding 'django/contrib/sites/locale/he/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,895 wheel INFO adding 'django/contrib/sites/locale/he/LC_MESSAGES/django.po'
2025-04-22 17:58:56,895 wheel INFO adding 'django/contrib/sites/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,895 wheel INFO adding 'django/contrib/sites/locale/hi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,895 wheel INFO adding 'django/contrib/sites/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,896 wheel INFO adding 'django/contrib/sites/locale/hr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,896 wheel INFO adding 'django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,896 wheel INFO adding 'django/contrib/sites/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,896 wheel INFO adding 'django/contrib/sites/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,897 wheel INFO adding 'django/contrib/sites/locale/hu/LC_MESSAGES/django.po'
2025-04-22 17:58:56,897 wheel INFO adding 'django/contrib/sites/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,897 wheel INFO adding 'django/contrib/sites/locale/hy/LC_MESSAGES/django.po'
2025-04-22 17:58:56,897 wheel INFO adding 'django/contrib/sites/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,897 wheel INFO adding 'django/contrib/sites/locale/ia/LC_MESSAGES/django.po'
2025-04-22 17:58:56,898 wheel INFO adding 'django/contrib/sites/locale/id/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,898 wheel INFO adding 'django/contrib/sites/locale/id/LC_MESSAGES/django.po'
2025-04-22 17:58:56,898 wheel INFO adding 'django/contrib/sites/locale/io/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,898 wheel INFO adding 'django/contrib/sites/locale/io/LC_MESSAGES/django.po'
2025-04-22 17:58:56,898 wheel INFO adding 'django/contrib/sites/locale/is/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,898 wheel INFO adding 'django/contrib/sites/locale/is/LC_MESSAGES/django.po'
2025-04-22 17:58:56,899 wheel INFO adding 'django/contrib/sites/locale/it/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,899 wheel INFO adding 'django/contrib/sites/locale/it/LC_MESSAGES/django.po'
2025-04-22 17:58:56,899 wheel INFO adding 'django/contrib/sites/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,899 wheel INFO adding 'django/contrib/sites/locale/ja/LC_MESSAGES/django.po'
2025-04-22 17:58:56,899 wheel INFO adding 'django/contrib/sites/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,900 wheel INFO adding 'django/contrib/sites/locale/ka/LC_MESSAGES/django.po'
2025-04-22 17:58:56,900 wheel INFO adding 'django/contrib/sites/locale/kab/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,900 wheel INFO adding 'django/contrib/sites/locale/kab/LC_MESSAGES/django.po'
2025-04-22 17:58:56,900 wheel INFO adding 'django/contrib/sites/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,900 wheel INFO adding 'django/contrib/sites/locale/kk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,901 wheel INFO adding 'django/contrib/sites/locale/km/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,901 wheel INFO adding 'django/contrib/sites/locale/km/LC_MESSAGES/django.po'
2025-04-22 17:58:56,901 wheel INFO adding 'django/contrib/sites/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,901 wheel INFO adding 'django/contrib/sites/locale/kn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,901 wheel INFO adding 'django/contrib/sites/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,902 wheel INFO adding 'django/contrib/sites/locale/ko/LC_MESSAGES/django.po'
2025-04-22 17:58:56,902 wheel INFO adding 'django/contrib/sites/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,902 wheel INFO adding 'django/contrib/sites/locale/ky/LC_MESSAGES/django.po'
2025-04-22 17:58:56,902 wheel INFO adding 'django/contrib/sites/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,902 wheel INFO adding 'django/contrib/sites/locale/lb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,903 wheel INFO adding 'django/contrib/sites/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,903 wheel INFO adding 'django/contrib/sites/locale/lt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,903 wheel INFO adding 'django/contrib/sites/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,903 wheel INFO adding 'django/contrib/sites/locale/lv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,903 wheel INFO adding 'django/contrib/sites/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,903 wheel INFO adding 'django/contrib/sites/locale/mk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,904 wheel INFO adding 'django/contrib/sites/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,904 wheel INFO adding 'django/contrib/sites/locale/ml/LC_MESSAGES/django.po'
2025-04-22 17:58:56,904 wheel INFO adding 'django/contrib/sites/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,904 wheel INFO adding 'django/contrib/sites/locale/mn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,904 wheel INFO adding 'django/contrib/sites/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,905 wheel INFO adding 'django/contrib/sites/locale/mr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,905 wheel INFO adding 'django/contrib/sites/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,905 wheel INFO adding 'django/contrib/sites/locale/ms/LC_MESSAGES/django.po'
2025-04-22 17:58:56,905 wheel INFO adding 'django/contrib/sites/locale/my/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,905 wheel INFO adding 'django/contrib/sites/locale/my/LC_MESSAGES/django.po'
2025-04-22 17:58:56,906 wheel INFO adding 'django/contrib/sites/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,906 wheel INFO adding 'django/contrib/sites/locale/nb/LC_MESSAGES/django.po'
2025-04-22 17:58:56,906 wheel INFO adding 'django/contrib/sites/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,906 wheel INFO adding 'django/contrib/sites/locale/ne/LC_MESSAGES/django.po'
2025-04-22 17:58:56,906 wheel INFO adding 'django/contrib/sites/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,907 wheel INFO adding 'django/contrib/sites/locale/nl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,907 wheel INFO adding 'django/contrib/sites/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,907 wheel INFO adding 'django/contrib/sites/locale/nn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,907 wheel INFO adding 'django/contrib/sites/locale/os/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,907 wheel INFO adding 'django/contrib/sites/locale/os/LC_MESSAGES/django.po'
2025-04-22 17:58:56,908 wheel INFO adding 'django/contrib/sites/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,908 wheel INFO adding 'django/contrib/sites/locale/pa/LC_MESSAGES/django.po'
2025-04-22 17:58:56,908 wheel INFO adding 'django/contrib/sites/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,908 wheel INFO adding 'django/contrib/sites/locale/pl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,908 wheel INFO adding 'django/contrib/sites/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,908 wheel INFO adding 'django/contrib/sites/locale/pt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,909 wheel INFO adding 'django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,909 wheel INFO adding 'django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 17:58:56,909 wheel INFO adding 'django/contrib/sites/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,909 wheel INFO adding 'django/contrib/sites/locale/ro/LC_MESSAGES/django.po'
2025-04-22 17:58:56,909 wheel INFO adding 'django/contrib/sites/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,910 wheel INFO adding 'django/contrib/sites/locale/ru/LC_MESSAGES/django.po'
2025-04-22 17:58:56,910 wheel INFO adding 'django/contrib/sites/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,910 wheel INFO adding 'django/contrib/sites/locale/sk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,910 wheel INFO adding 'django/contrib/sites/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,910 wheel INFO adding 'django/contrib/sites/locale/sl/LC_MESSAGES/django.po'
2025-04-22 17:58:56,911 wheel INFO adding 'django/contrib/sites/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,911 wheel INFO adding 'django/contrib/sites/locale/sq/LC_MESSAGES/django.po'
2025-04-22 17:58:56,911 wheel INFO adding 'django/contrib/sites/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,911 wheel INFO adding 'django/contrib/sites/locale/sr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,911 wheel INFO adding 'django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,911 wheel INFO adding 'django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 17:58:56,912 wheel INFO adding 'django/contrib/sites/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,912 wheel INFO adding 'django/contrib/sites/locale/sv/LC_MESSAGES/django.po'
2025-04-22 17:58:56,912 wheel INFO adding 'django/contrib/sites/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,912 wheel INFO adding 'django/contrib/sites/locale/sw/LC_MESSAGES/django.po'
2025-04-22 17:58:56,912 wheel INFO adding 'django/contrib/sites/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,913 wheel INFO adding 'django/contrib/sites/locale/ta/LC_MESSAGES/django.po'
2025-04-22 17:58:56,913 wheel INFO adding 'django/contrib/sites/locale/te/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,913 wheel INFO adding 'django/contrib/sites/locale/te/LC_MESSAGES/django.po'
2025-04-22 17:58:56,913 wheel INFO adding 'django/contrib/sites/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,913 wheel INFO adding 'django/contrib/sites/locale/tg/LC_MESSAGES/django.po'
2025-04-22 17:58:56,914 wheel INFO adding 'django/contrib/sites/locale/th/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,914 wheel INFO adding 'django/contrib/sites/locale/th/LC_MESSAGES/django.po'
2025-04-22 17:58:56,914 wheel INFO adding 'django/contrib/sites/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,914 wheel INFO adding 'django/contrib/sites/locale/tk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,914 wheel INFO adding 'django/contrib/sites/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,915 wheel INFO adding 'django/contrib/sites/locale/tr/LC_MESSAGES/django.po'
2025-04-22 17:58:56,915 wheel INFO adding 'django/contrib/sites/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,915 wheel INFO adding 'django/contrib/sites/locale/tt/LC_MESSAGES/django.po'
2025-04-22 17:58:56,915 wheel INFO adding 'django/contrib/sites/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,915 wheel INFO adding 'django/contrib/sites/locale/udm/LC_MESSAGES/django.po'
2025-04-22 17:58:56,916 wheel INFO adding 'django/contrib/sites/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,916 wheel INFO adding 'django/contrib/sites/locale/uk/LC_MESSAGES/django.po'
2025-04-22 17:58:56,916 wheel INFO adding 'django/contrib/sites/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,916 wheel INFO adding 'django/contrib/sites/locale/ur/LC_MESSAGES/django.po'
2025-04-22 17:58:56,916 wheel INFO adding 'django/contrib/sites/locale/uz/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,917 wheel INFO adding 'django/contrib/sites/locale/uz/LC_MESSAGES/django.po'
2025-04-22 17:58:56,917 wheel INFO adding 'django/contrib/sites/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,917 wheel INFO adding 'django/contrib/sites/locale/vi/LC_MESSAGES/django.po'
2025-04-22 17:58:56,917 wheel INFO adding 'django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,917 wheel INFO adding 'django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 17:58:56,917 wheel INFO adding 'django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 17:58:56,918 wheel INFO adding 'django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 17:58:56,918 wheel INFO adding 'django/contrib/sites/migrations/0001_initial.py'
2025-04-22 17:58:56,918 wheel INFO adding 'django/contrib/sites/migrations/0002_alter_domain_unique.py'
2025-04-22 17:58:56,918 wheel INFO adding 'django/contrib/sites/migrations/__init__.py'
2025-04-22 17:58:56,918 wheel INFO adding 'django/contrib/staticfiles/__init__.py'
2025-04-22 17:58:56,919 wheel INFO adding 'django/contrib/staticfiles/apps.py'
2025-04-22 17:58:56,919 wheel INFO adding 'django/contrib/staticfiles/checks.py'
2025-04-22 17:58:56,919 wheel INFO adding 'django/contrib/staticfiles/finders.py'
2025-04-22 17:58:56,919 wheel INFO adding 'django/contrib/staticfiles/handlers.py'
2025-04-22 17:58:56,919 wheel INFO adding 'django/contrib/staticfiles/storage.py'
2025-04-22 17:58:56,920 wheel INFO adding 'django/contrib/staticfiles/testing.py'
2025-04-22 17:58:56,920 wheel INFO adding 'django/contrib/staticfiles/urls.py'
2025-04-22 17:58:56,920 wheel INFO adding 'django/contrib/staticfiles/utils.py'
2025-04-22 17:58:56,920 wheel INFO adding 'django/contrib/staticfiles/views.py'
2025-04-22 17:58:56,920 wheel INFO adding 'django/contrib/staticfiles/management/__init__.py'
2025-04-22 17:58:56,920 wheel INFO adding 'django/contrib/staticfiles/management/commands/__init__.py'
2025-04-22 17:58:56,921 wheel INFO adding 'django/contrib/staticfiles/management/commands/collectstatic.py'
2025-04-22 17:58:56,921 wheel INFO adding 'django/contrib/staticfiles/management/commands/findstatic.py'
2025-04-22 17:58:56,921 wheel INFO adding 'django/contrib/staticfiles/management/commands/runserver.py'
2025-04-22 17:58:56,921 wheel INFO adding 'django/contrib/syndication/__init__.py'
2025-04-22 17:58:56,921 wheel INFO adding 'django/contrib/syndication/apps.py'
2025-04-22 17:58:56,922 wheel INFO adding 'django/contrib/syndication/views.py'
2025-04-22 17:58:56,922 wheel INFO adding 'django/core/__init__.py'
2025-04-22 17:58:56,922 wheel INFO adding 'django/core/asgi.py'
2025-04-22 17:58:56,922 wheel INFO adding 'django/core/exceptions.py'
2025-04-22 17:58:56,922 wheel INFO adding 'django/core/paginator.py'
2025-04-22 17:58:56,923 wheel INFO adding 'django/core/signals.py'
2025-04-22 17:58:56,923 wheel INFO adding 'django/core/signing.py'
2025-04-22 17:58:56,923 wheel INFO adding 'django/core/validators.py'
2025-04-22 17:58:56,923 wheel INFO adding 'django/core/wsgi.py'
2025-04-22 17:58:56,923 wheel INFO adding 'django/core/cache/__init__.py'
2025-04-22 17:58:56,924 wheel INFO adding 'django/core/cache/utils.py'
2025-04-22 17:58:56,924 wheel INFO adding 'django/core/cache/backends/__init__.py'
2025-04-22 17:58:56,924 wheel INFO adding 'django/core/cache/backends/base.py'
2025-04-22 17:58:56,924 wheel INFO adding 'django/core/cache/backends/db.py'
2025-04-22 17:58:56,924 wheel INFO adding 'django/core/cache/backends/dummy.py'
2025-04-22 17:58:56,925 wheel INFO adding 'django/core/cache/backends/filebased.py'
2025-04-22 17:58:56,925 wheel INFO adding 'django/core/cache/backends/locmem.py'
2025-04-22 17:58:56,925 wheel INFO adding 'django/core/cache/backends/memcached.py'
2025-04-22 17:58:56,925 wheel INFO adding 'django/core/cache/backends/redis.py'
2025-04-22 17:58:56,925 wheel INFO adding 'django/core/checks/__init__.py'
2025-04-22 17:58:56,926 wheel INFO adding 'django/core/checks/async_checks.py'
2025-04-22 17:58:56,926 wheel INFO adding 'django/core/checks/caches.py'
2025-04-22 17:58:56,926 wheel INFO adding 'django/core/checks/database.py'
2025-04-22 17:58:56,926 wheel INFO adding 'django/core/checks/files.py'
2025-04-22 17:58:56,926 wheel INFO adding 'django/core/checks/messages.py'
2025-04-22 17:58:56,927 wheel INFO adding 'django/core/checks/model_checks.py'
2025-04-22 17:58:56,927 wheel INFO adding 'django/core/checks/registry.py'
2025-04-22 17:58:56,927 wheel INFO adding 'django/core/checks/templates.py'
2025-04-22 17:58:56,927 wheel INFO adding 'django/core/checks/translation.py'
2025-04-22 17:58:56,927 wheel INFO adding 'django/core/checks/urls.py'
2025-04-22 17:58:56,927 wheel INFO adding 'django/core/checks/compatibility/__init__.py'
2025-04-22 17:58:56,928 wheel INFO adding 'django/core/checks/compatibility/django_4_0.py'
2025-04-22 17:58:56,928 wheel INFO adding 'django/core/checks/security/__init__.py'
2025-04-22 17:58:56,928 wheel INFO adding 'django/core/checks/security/base.py'
2025-04-22 17:58:56,928 wheel INFO adding 'django/core/checks/security/csrf.py'
2025-04-22 17:58:56,928 wheel INFO adding 'django/core/checks/security/sessions.py'
2025-04-22 17:58:56,928 wheel INFO adding 'django/core/files/__init__.py'
2025-04-22 17:58:56,929 wheel INFO adding 'django/core/files/base.py'
2025-04-22 17:58:56,929 wheel INFO adding 'django/core/files/images.py'
2025-04-22 17:58:56,929 wheel INFO adding 'django/core/files/locks.py'
2025-04-22 17:58:56,929 wheel INFO adding 'django/core/files/move.py'
2025-04-22 17:58:56,929 wheel INFO adding 'django/core/files/temp.py'
2025-04-22 17:58:56,929 wheel INFO adding 'django/core/files/uploadedfile.py'
2025-04-22 17:58:56,930 wheel INFO adding 'django/core/files/uploadhandler.py'
2025-04-22 17:58:56,930 wheel INFO adding 'django/core/files/utils.py'
2025-04-22 17:58:56,930 wheel INFO adding 'django/core/files/storage/__init__.py'
2025-04-22 17:58:56,930 wheel INFO adding 'django/core/files/storage/base.py'
2025-04-22 17:58:56,930 wheel INFO adding 'django/core/files/storage/filesystem.py'
2025-04-22 17:58:56,931 wheel INFO adding 'django/core/files/storage/handler.py'
2025-04-22 17:58:56,931 wheel INFO adding 'django/core/files/storage/memory.py'
2025-04-22 17:58:56,931 wheel INFO adding 'django/core/files/storage/mixins.py'
2025-04-22 17:58:56,931 wheel INFO adding 'django/core/handlers/__init__.py'
2025-04-22 17:58:56,931 wheel INFO adding 'django/core/handlers/asgi.py'
2025-04-22 17:58:56,932 wheel INFO adding 'django/core/handlers/base.py'
2025-04-22 17:58:56,932 wheel INFO adding 'django/core/handlers/exception.py'
2025-04-22 17:58:56,932 wheel INFO adding 'django/core/handlers/wsgi.py'
2025-04-22 17:58:56,932 wheel INFO adding 'django/core/mail/__init__.py'
2025-04-22 17:58:56,932 wheel INFO adding 'django/core/mail/message.py'
2025-04-22 17:58:56,933 wheel INFO adding 'django/core/mail/utils.py'
2025-04-22 17:58:56,933 wheel INFO adding 'django/core/mail/backends/__init__.py'
2025-04-22 17:58:56,933 wheel INFO adding 'django/core/mail/backends/base.py'
2025-04-22 17:58:56,933 wheel INFO adding 'django/core/mail/backends/console.py'
2025-04-22 17:58:56,933 wheel INFO adding 'django/core/mail/backends/dummy.py'
2025-04-22 17:58:56,933 wheel INFO adding 'django/core/mail/backends/filebased.py'
2025-04-22 17:58:56,934 wheel INFO adding 'django/core/mail/backends/locmem.py'
2025-04-22 17:58:56,934 wheel INFO adding 'django/core/mail/backends/smtp.py'
2025-04-22 17:58:56,934 wheel INFO adding 'django/core/management/__init__.py'
2025-04-22 17:58:56,934 wheel INFO adding 'django/core/management/base.py'
2025-04-22 17:58:56,935 wheel INFO adding 'django/core/management/color.py'
2025-04-22 17:58:56,935 wheel INFO adding 'django/core/management/sql.py'
2025-04-22 17:58:56,935 wheel INFO adding 'django/core/management/templates.py'
2025-04-22 17:58:56,935 wheel INFO adding 'django/core/management/utils.py'
2025-04-22 17:58:56,935 wheel INFO adding 'django/core/management/commands/__init__.py'
2025-04-22 17:58:56,936 wheel INFO adding 'django/core/management/commands/check.py'
2025-04-22 17:58:56,936 wheel INFO adding 'django/core/management/commands/compilemessages.py'
2025-04-22 17:58:56,936 wheel INFO adding 'django/core/management/commands/createcachetable.py'
2025-04-22 17:58:56,936 wheel INFO adding 'django/core/management/commands/dbshell.py'
2025-04-22 17:58:56,936 wheel INFO adding 'django/core/management/commands/diffsettings.py'
2025-04-22 17:58:56,936 wheel INFO adding 'django/core/management/commands/dumpdata.py'
2025-04-22 17:58:56,937 wheel INFO adding 'django/core/management/commands/flush.py'
2025-04-22 17:58:56,937 wheel INFO adding 'django/core/management/commands/inspectdb.py'
2025-04-22 17:58:56,937 wheel INFO adding 'django/core/management/commands/loaddata.py'
2025-04-22 17:58:56,937 wheel INFO adding 'django/core/management/commands/makemessages.py'
2025-04-22 17:58:56,938 wheel INFO adding 'django/core/management/commands/makemigrations.py'
2025-04-22 17:58:56,938 wheel INFO adding 'django/core/management/commands/migrate.py'
2025-04-22 17:58:56,938 wheel INFO adding 'django/core/management/commands/optimizemigration.py'
2025-04-22 17:58:56,938 wheel INFO adding 'django/core/management/commands/runserver.py'
2025-04-22 17:58:56,938 wheel INFO adding 'django/core/management/commands/sendtestemail.py'
2025-04-22 17:58:56,939 wheel INFO adding 'django/core/management/commands/shell.py'
2025-04-22 17:58:56,939 wheel INFO adding 'django/core/management/commands/showmigrations.py'
2025-04-22 17:58:56,939 wheel INFO adding 'django/core/management/commands/sqlflush.py'
2025-04-22 17:58:56,939 wheel INFO adding 'django/core/management/commands/sqlmigrate.py'
2025-04-22 17:58:56,939 wheel INFO adding 'django/core/management/commands/sqlsequencereset.py'
2025-04-22 17:58:56,940 wheel INFO adding 'django/core/management/commands/squashmigrations.py'
2025-04-22 17:58:56,940 wheel INFO adding 'django/core/management/commands/startapp.py'
2025-04-22 17:58:56,940 wheel INFO adding 'django/core/management/commands/startproject.py'
2025-04-22 17:58:56,940 wheel INFO adding 'django/core/management/commands/test.py'
2025-04-22 17:58:56,940 wheel INFO adding 'django/core/management/commands/testserver.py'
2025-04-22 17:58:56,941 wheel INFO adding 'django/core/serializers/__init__.py'
2025-04-22 17:58:56,941 wheel INFO adding 'django/core/serializers/base.py'
2025-04-22 17:58:56,941 wheel INFO adding 'django/core/serializers/json.py'
2025-04-22 17:58:56,941 wheel INFO adding 'django/core/serializers/jsonl.py'
2025-04-22 17:58:56,941 wheel INFO adding 'django/core/serializers/python.py'
2025-04-22 17:58:56,942 wheel INFO adding 'django/core/serializers/pyyaml.py'
2025-04-22 17:58:56,942 wheel INFO adding 'django/core/serializers/xml_serializer.py'
2025-04-22 17:58:56,942 wheel INFO adding 'django/core/servers/__init__.py'
2025-04-22 17:58:56,942 wheel INFO adding 'django/core/servers/basehttp.py'
2025-04-22 17:58:56,942 wheel INFO adding 'django/db/__init__.py'
2025-04-22 17:58:56,943 wheel INFO adding 'django/db/transaction.py'
2025-04-22 17:58:56,943 wheel INFO adding 'django/db/utils.py'
2025-04-22 17:58:56,943 wheel INFO adding 'django/db/backends/__init__.py'
2025-04-22 17:58:56,943 wheel INFO adding 'django/db/backends/ddl_references.py'
2025-04-22 17:58:56,943 wheel INFO adding 'django/db/backends/signals.py'
2025-04-22 17:58:56,944 wheel INFO adding 'django/db/backends/utils.py'
2025-04-22 17:58:56,944 wheel INFO adding 'django/db/backends/base/__init__.py'
2025-04-22 17:58:56,944 wheel INFO adding 'django/db/backends/base/base.py'
2025-04-22 17:58:56,944 wheel INFO adding 'django/db/backends/base/client.py'
2025-04-22 17:58:56,944 wheel INFO adding 'django/db/backends/base/creation.py'
2025-04-22 17:58:56,945 wheel INFO adding 'django/db/backends/base/features.py'
2025-04-22 17:58:56,945 wheel INFO adding 'django/db/backends/base/introspection.py'
2025-04-22 17:58:56,945 wheel INFO adding 'django/db/backends/base/operations.py'
2025-04-22 17:58:56,946 wheel INFO adding 'django/db/backends/base/schema.py'
2025-04-22 17:58:56,946 wheel INFO adding 'django/db/backends/base/validation.py'
2025-04-22 17:58:56,946 wheel INFO adding 'django/db/backends/dummy/__init__.py'
2025-04-22 17:58:56,946 wheel INFO adding 'django/db/backends/dummy/base.py'
2025-04-22 17:58:56,946 wheel INFO adding 'django/db/backends/dummy/features.py'
2025-04-22 17:58:56,947 wheel INFO adding 'django/db/backends/mysql/__init__.py'
2025-04-22 17:58:56,947 wheel INFO adding 'django/db/backends/mysql/base.py'
2025-04-22 17:58:56,947 wheel INFO adding 'django/db/backends/mysql/client.py'
2025-04-22 17:58:56,947 wheel INFO adding 'django/db/backends/mysql/compiler.py'
2025-04-22 17:58:56,947 wheel INFO adding 'django/db/backends/mysql/creation.py'
2025-04-22 17:58:56,948 wheel INFO adding 'django/db/backends/mysql/features.py'
2025-04-22 17:58:56,948 wheel INFO adding 'django/db/backends/mysql/introspection.py'
2025-04-22 17:58:56,948 wheel INFO adding 'django/db/backends/mysql/operations.py'
2025-04-22 17:58:56,948 wheel INFO adding 'django/db/backends/mysql/schema.py'
2025-04-22 17:58:56,948 wheel INFO adding 'django/db/backends/mysql/validation.py'
2025-04-22 17:58:56,949 wheel INFO adding 'django/db/backends/oracle/__init__.py'
2025-04-22 17:58:56,949 wheel INFO adding 'django/db/backends/oracle/base.py'
2025-04-22 17:58:56,949 wheel INFO adding 'django/db/backends/oracle/client.py'
2025-04-22 17:58:56,949 wheel INFO adding 'django/db/backends/oracle/creation.py'
2025-04-22 17:58:56,950 wheel INFO adding 'django/db/backends/oracle/features.py'
2025-04-22 17:58:56,950 wheel INFO adding 'django/db/backends/oracle/functions.py'
2025-04-22 17:58:56,950 wheel INFO adding 'django/db/backends/oracle/introspection.py'
2025-04-22 17:58:56,950 wheel INFO adding 'django/db/backends/oracle/operations.py'
2025-04-22 17:58:56,950 wheel INFO adding 'django/db/backends/oracle/schema.py'
2025-04-22 17:58:56,951 wheel INFO adding 'django/db/backends/oracle/utils.py'
2025-04-22 17:58:56,951 wheel INFO adding 'django/db/backends/oracle/validation.py'
2025-04-22 17:58:56,951 wheel INFO adding 'django/db/backends/postgresql/__init__.py'
2025-04-22 17:58:56,951 wheel INFO adding 'django/db/backends/postgresql/base.py'
2025-04-22 17:58:56,951 wheel INFO adding 'django/db/backends/postgresql/client.py'
2025-04-22 17:58:56,952 wheel INFO adding 'django/db/backends/postgresql/creation.py'
2025-04-22 17:58:56,952 wheel INFO adding 'django/db/backends/postgresql/features.py'
2025-04-22 17:58:56,952 wheel INFO adding 'django/db/backends/postgresql/introspection.py'
2025-04-22 17:58:56,952 wheel INFO adding 'django/db/backends/postgresql/operations.py'
2025-04-22 17:58:56,952 wheel INFO adding 'django/db/backends/postgresql/psycopg_any.py'
2025-04-22 17:58:56,953 wheel INFO adding 'django/db/backends/postgresql/schema.py'
2025-04-22 17:58:56,953 wheel INFO adding 'django/db/backends/sqlite3/__init__.py'
2025-04-22 17:58:56,953 wheel INFO adding 'django/db/backends/sqlite3/_functions.py'
2025-04-22 17:58:56,953 wheel INFO adding 'django/db/backends/sqlite3/base.py'
2025-04-22 17:58:56,953 wheel INFO adding 'django/db/backends/sqlite3/client.py'
2025-04-22 17:58:56,954 wheel INFO adding 'django/db/backends/sqlite3/creation.py'
2025-04-22 17:58:56,954 wheel INFO adding 'django/db/backends/sqlite3/features.py'
2025-04-22 17:58:56,954 wheel INFO adding 'django/db/backends/sqlite3/introspection.py'
2025-04-22 17:58:56,954 wheel INFO adding 'django/db/backends/sqlite3/operations.py'
2025-04-22 17:58:56,955 wheel INFO adding 'django/db/backends/sqlite3/schema.py'
2025-04-22 17:58:56,955 wheel INFO adding 'django/db/migrations/__init__.py'
2025-04-22 17:58:56,955 wheel INFO adding 'django/db/migrations/autodetector.py'
2025-04-22 17:58:56,955 wheel INFO adding 'django/db/migrations/exceptions.py'
2025-04-22 17:58:56,956 wheel INFO adding 'django/db/migrations/executor.py'
2025-04-22 17:58:56,956 wheel INFO adding 'django/db/migrations/graph.py'
2025-04-22 17:58:56,956 wheel INFO adding 'django/db/migrations/loader.py'
2025-04-22 17:58:56,956 wheel INFO adding 'django/db/migrations/migration.py'
2025-04-22 17:58:56,956 wheel INFO adding 'django/db/migrations/optimizer.py'
2025-04-22 17:58:56,957 wheel INFO adding 'django/db/migrations/questioner.py'
2025-04-22 17:58:56,957 wheel INFO adding 'django/db/migrations/recorder.py'
2025-04-22 17:58:56,957 wheel INFO adding 'django/db/migrations/serializer.py'
2025-04-22 17:58:56,957 wheel INFO adding 'django/db/migrations/state.py'
2025-04-22 17:58:56,958 wheel INFO adding 'django/db/migrations/utils.py'
2025-04-22 17:58:56,958 wheel INFO adding 'django/db/migrations/writer.py'
2025-04-22 17:58:56,958 wheel INFO adding 'django/db/migrations/operations/__init__.py'
2025-04-22 17:58:56,958 wheel INFO adding 'django/db/migrations/operations/base.py'
2025-04-22 17:58:56,959 wheel INFO adding 'django/db/migrations/operations/fields.py'
2025-04-22 17:58:56,959 wheel INFO adding 'django/db/migrations/operations/models.py'
2025-04-22 17:58:56,959 wheel INFO adding 'django/db/migrations/operations/special.py'
2025-04-22 17:58:56,959 wheel INFO adding 'django/db/models/__init__.py'
2025-04-22 17:58:56,960 wheel INFO adding 'django/db/models/aggregates.py'
2025-04-22 17:58:56,960 wheel INFO adding 'django/db/models/base.py'
2025-04-22 17:58:56,960 wheel INFO adding 'django/db/models/constants.py'
2025-04-22 17:58:56,960 wheel INFO adding 'django/db/models/constraints.py'
2025-04-22 17:58:56,961 wheel INFO adding 'django/db/models/deletion.py'
2025-04-22 17:58:56,961 wheel INFO adding 'django/db/models/enums.py'
2025-04-22 17:58:56,961 wheel INFO adding 'django/db/models/expressions.py'
2025-04-22 17:58:56,962 wheel INFO adding 'django/db/models/indexes.py'
2025-04-22 17:58:56,962 wheel INFO adding 'django/db/models/lookups.py'
2025-04-22 17:58:56,962 wheel INFO adding 'django/db/models/manager.py'
2025-04-22 17:58:56,962 wheel INFO adding 'django/db/models/options.py'
2025-04-22 17:58:56,963 wheel INFO adding 'django/db/models/query.py'
2025-04-22 17:58:56,963 wheel INFO adding 'django/db/models/query_utils.py'
2025-04-22 17:58:56,963 wheel INFO adding 'django/db/models/signals.py'
2025-04-22 17:58:56,963 wheel INFO adding 'django/db/models/utils.py'
2025-04-22 17:58:56,964 wheel INFO adding 'django/db/models/fields/__init__.py'
2025-04-22 17:58:56,964 wheel INFO adding 'django/db/models/fields/files.py'
2025-04-22 17:58:56,964 wheel INFO adding 'django/db/models/fields/json.py'
2025-04-22 17:58:56,965 wheel INFO adding 'django/db/models/fields/mixins.py'
2025-04-22 17:58:56,965 wheel INFO adding 'django/db/models/fields/proxy.py'
2025-04-22 17:58:56,965 wheel INFO adding 'django/db/models/fields/related.py'
2025-04-22 17:58:56,966 wheel INFO adding 'django/db/models/fields/related_descriptors.py'
2025-04-22 17:58:56,966 wheel INFO adding 'django/db/models/fields/related_lookups.py'
2025-04-22 17:58:56,966 wheel INFO adding 'django/db/models/fields/reverse_related.py'
2025-04-22 17:58:56,967 wheel INFO adding 'django/db/models/functions/__init__.py'
2025-04-22 17:58:56,967 wheel INFO adding 'django/db/models/functions/comparison.py'
2025-04-22 17:58:56,967 wheel INFO adding 'django/db/models/functions/datetime.py'
2025-04-22 17:58:56,967 wheel INFO adding 'django/db/models/functions/math.py'
2025-04-22 17:58:56,967 wheel INFO adding 'django/db/models/functions/mixins.py'
2025-04-22 17:58:56,968 wheel INFO adding 'django/db/models/functions/text.py'
2025-04-22 17:58:56,968 wheel INFO adding 'django/db/models/functions/window.py'
2025-04-22 17:58:56,968 wheel INFO adding 'django/db/models/sql/__init__.py'
2025-04-22 17:58:56,968 wheel INFO adding 'django/db/models/sql/compiler.py'
2025-04-22 17:58:56,969 wheel INFO adding 'django/db/models/sql/constants.py'
2025-04-22 17:58:56,969 wheel INFO adding 'django/db/models/sql/datastructures.py'
2025-04-22 17:58:56,969 wheel INFO adding 'django/db/models/sql/query.py'
2025-04-22 17:58:56,970 wheel INFO adding 'django/db/models/sql/subqueries.py'
2025-04-22 17:58:56,970 wheel INFO adding 'django/db/models/sql/where.py'
2025-04-22 17:58:56,970 wheel INFO adding 'django/dispatch/__init__.py'
2025-04-22 17:58:56,970 wheel INFO adding 'django/dispatch/dispatcher.py'
2025-04-22 17:58:56,970 wheel INFO adding 'django/dispatch/license.txt'
2025-04-22 17:58:56,971 wheel INFO adding 'django/forms/__init__.py'
2025-04-22 17:58:56,971 wheel INFO adding 'django/forms/boundfield.py'
2025-04-22 17:58:56,971 wheel INFO adding 'django/forms/fields.py'
2025-04-22 17:58:56,971 wheel INFO adding 'django/forms/forms.py'
2025-04-22 17:58:56,972 wheel INFO adding 'django/forms/formsets.py'
2025-04-22 17:58:56,972 wheel INFO adding 'django/forms/models.py'
2025-04-22 17:58:56,972 wheel INFO adding 'django/forms/renderers.py'
2025-04-22 17:58:56,972 wheel INFO adding 'django/forms/utils.py'
2025-04-22 17:58:56,973 wheel INFO adding 'django/forms/widgets.py'
2025-04-22 17:58:56,973 wheel INFO adding 'django/forms/jinja2/django/forms/attrs.html'
2025-04-22 17:58:56,973 wheel INFO adding 'django/forms/jinja2/django/forms/default.html'
2025-04-22 17:58:56,973 wheel INFO adding 'django/forms/jinja2/django/forms/div.html'
2025-04-22 17:58:56,974 wheel INFO adding 'django/forms/jinja2/django/forms/label.html'
2025-04-22 17:58:56,974 wheel INFO adding 'django/forms/jinja2/django/forms/p.html'
2025-04-22 17:58:56,974 wheel INFO adding 'django/forms/jinja2/django/forms/table.html'
2025-04-22 17:58:56,974 wheel INFO adding 'django/forms/jinja2/django/forms/ul.html'
2025-04-22 17:58:56,974 wheel INFO adding 'django/forms/jinja2/django/forms/errors/dict/default.html'
2025-04-22 17:58:56,975 wheel INFO adding 'django/forms/jinja2/django/forms/errors/dict/text.txt'
2025-04-22 17:58:56,975 wheel INFO adding 'django/forms/jinja2/django/forms/errors/dict/ul.html'
2025-04-22 17:58:56,975 wheel INFO adding 'django/forms/jinja2/django/forms/errors/list/default.html'
2025-04-22 17:58:56,975 wheel INFO adding 'django/forms/jinja2/django/forms/errors/list/text.txt'
2025-04-22 17:58:56,975 wheel INFO adding 'django/forms/jinja2/django/forms/errors/list/ul.html'
2025-04-22 17:58:56,975 wheel INFO adding 'django/forms/jinja2/django/forms/formsets/default.html'
2025-04-22 17:58:56,976 wheel INFO adding 'django/forms/jinja2/django/forms/formsets/div.html'
2025-04-22 17:58:56,976 wheel INFO adding 'django/forms/jinja2/django/forms/formsets/p.html'
2025-04-22 17:58:56,976 wheel INFO adding 'django/forms/jinja2/django/forms/formsets/table.html'
2025-04-22 17:58:56,976 wheel INFO adding 'django/forms/jinja2/django/forms/formsets/ul.html'
2025-04-22 17:58:56,976 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/attrs.html'
2025-04-22 17:58:56,976 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/checkbox.html'
2025-04-22 17:58:56,977 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/checkbox_option.html'
2025-04-22 17:58:56,977 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/checkbox_select.html'
2025-04-22 17:58:56,977 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/clearable_file_input.html'
2025-04-22 17:58:56,977 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/date.html'
2025-04-22 17:58:56,977 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/datetime.html'
2025-04-22 17:58:56,977 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/email.html'
2025-04-22 17:58:56,977 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/file.html'
2025-04-22 17:58:56,978 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/hidden.html'
2025-04-22 17:58:56,978 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/input.html'
2025-04-22 17:58:56,978 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/input_option.html'
2025-04-22 17:58:56,978 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/multiple_hidden.html'
2025-04-22 17:58:56,978 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/multiple_input.html'
2025-04-22 17:58:56,978 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/multiwidget.html'
2025-04-22 17:58:56,979 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/number.html'
2025-04-22 17:58:56,979 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/password.html'
2025-04-22 17:58:56,979 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/radio.html'
2025-04-22 17:58:56,979 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/radio_option.html'
2025-04-22 17:58:56,979 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/select.html'
2025-04-22 17:58:56,979 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/select_date.html'
2025-04-22 17:58:56,980 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/select_option.html'
2025-04-22 17:58:56,980 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/splitdatetime.html'
2025-04-22 17:58:56,980 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/splithiddendatetime.html'
2025-04-22 17:58:56,980 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/text.html'
2025-04-22 17:58:56,980 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/textarea.html'
2025-04-22 17:58:56,980 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/time.html'
2025-04-22 17:58:56,980 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/url.html'
2025-04-22 17:58:56,981 wheel INFO adding 'django/forms/templates/django/forms/attrs.html'
2025-04-22 17:58:56,981 wheel INFO adding 'django/forms/templates/django/forms/default.html'
2025-04-22 17:58:56,981 wheel INFO adding 'django/forms/templates/django/forms/div.html'
2025-04-22 17:58:56,981 wheel INFO adding 'django/forms/templates/django/forms/label.html'
2025-04-22 17:58:56,981 wheel INFO adding 'django/forms/templates/django/forms/p.html'
2025-04-22 17:58:56,982 wheel INFO adding 'django/forms/templates/django/forms/table.html'
2025-04-22 17:58:56,982 wheel INFO adding 'django/forms/templates/django/forms/ul.html'
2025-04-22 17:58:56,982 wheel INFO adding 'django/forms/templates/django/forms/errors/dict/default.html'
2025-04-22 17:58:56,982 wheel INFO adding 'django/forms/templates/django/forms/errors/dict/text.txt'
2025-04-22 17:58:56,982 wheel INFO adding 'django/forms/templates/django/forms/errors/dict/ul.html'
2025-04-22 17:58:56,982 wheel INFO adding 'django/forms/templates/django/forms/errors/list/default.html'
2025-04-22 17:58:56,983 wheel INFO adding 'django/forms/templates/django/forms/errors/list/text.txt'
2025-04-22 17:58:56,983 wheel INFO adding 'django/forms/templates/django/forms/errors/list/ul.html'
2025-04-22 17:58:56,983 wheel INFO adding 'django/forms/templates/django/forms/formsets/default.html'
2025-04-22 17:58:56,983 wheel INFO adding 'django/forms/templates/django/forms/formsets/div.html'
2025-04-22 17:58:56,983 wheel INFO adding 'django/forms/templates/django/forms/formsets/p.html'
2025-04-22 17:58:56,983 wheel INFO adding 'django/forms/templates/django/forms/formsets/table.html'
2025-04-22 17:58:56,984 wheel INFO adding 'django/forms/templates/django/forms/formsets/ul.html'
2025-04-22 17:58:56,984 wheel INFO adding 'django/forms/templates/django/forms/widgets/attrs.html'
2025-04-22 17:58:56,984 wheel INFO adding 'django/forms/templates/django/forms/widgets/checkbox.html'
2025-04-22 17:58:56,984 wheel INFO adding 'django/forms/templates/django/forms/widgets/checkbox_option.html'
2025-04-22 17:58:56,984 wheel INFO adding 'django/forms/templates/django/forms/widgets/checkbox_select.html'
2025-04-22 17:58:56,984 wheel INFO adding 'django/forms/templates/django/forms/widgets/clearable_file_input.html'
2025-04-22 17:58:56,985 wheel INFO adding 'django/forms/templates/django/forms/widgets/date.html'
2025-04-22 17:58:56,985 wheel INFO adding 'django/forms/templates/django/forms/widgets/datetime.html'
2025-04-22 17:58:56,985 wheel INFO adding 'django/forms/templates/django/forms/widgets/email.html'
2025-04-22 17:58:56,985 wheel INFO adding 'django/forms/templates/django/forms/widgets/file.html'
2025-04-22 17:58:56,985 wheel INFO adding 'django/forms/templates/django/forms/widgets/hidden.html'
2025-04-22 17:58:56,985 wheel INFO adding 'django/forms/templates/django/forms/widgets/input.html'
2025-04-22 17:58:56,986 wheel INFO adding 'django/forms/templates/django/forms/widgets/input_option.html'
2025-04-22 17:58:56,986 wheel INFO adding 'django/forms/templates/django/forms/widgets/multiple_hidden.html'
2025-04-22 17:58:56,986 wheel INFO adding 'django/forms/templates/django/forms/widgets/multiple_input.html'
2025-04-22 17:58:56,986 wheel INFO adding 'django/forms/templates/django/forms/widgets/multiwidget.html'
2025-04-22 17:58:56,986 wheel INFO adding 'django/forms/templates/django/forms/widgets/number.html'
2025-04-22 17:58:56,986 wheel INFO adding 'django/forms/templates/django/forms/widgets/password.html'
2025-04-22 17:58:56,987 wheel INFO adding 'django/forms/templates/django/forms/widgets/radio.html'
2025-04-22 17:58:56,987 wheel INFO adding 'django/forms/templates/django/forms/widgets/radio_option.html'
2025-04-22 17:58:56,987 wheel INFO adding 'django/forms/templates/django/forms/widgets/select.html'
2025-04-22 17:58:56,987 wheel INFO adding 'django/forms/templates/django/forms/widgets/select_date.html'
2025-04-22 17:58:56,987 wheel INFO adding 'django/forms/templates/django/forms/widgets/select_option.html'
2025-04-22 17:58:56,987 wheel INFO adding 'django/forms/templates/django/forms/widgets/splitdatetime.html'
2025-04-22 17:58:56,987 wheel INFO adding 'django/forms/templates/django/forms/widgets/splithiddendatetime.html'
2025-04-22 17:58:56,988 wheel INFO adding 'django/forms/templates/django/forms/widgets/text.html'
2025-04-22 17:58:56,988 wheel INFO adding 'django/forms/templates/django/forms/widgets/textarea.html'
2025-04-22 17:58:56,988 wheel INFO adding 'django/forms/templates/django/forms/widgets/time.html'
2025-04-22 17:58:56,988 wheel INFO adding 'django/forms/templates/django/forms/widgets/url.html'
2025-04-22 17:58:56,988 wheel INFO adding 'django/http/__init__.py'
2025-04-22 17:58:56,988 wheel INFO adding 'django/http/cookie.py'
2025-04-22 17:58:56,989 wheel INFO adding 'django/http/multipartparser.py'
2025-04-22 17:58:56,989 wheel INFO adding 'django/http/request.py'
2025-04-22 17:58:56,989 wheel INFO adding 'django/http/response.py'
2025-04-22 17:58:56,990 wheel INFO adding 'django/middleware/__init__.py'
2025-04-22 17:58:56,990 wheel INFO adding 'django/middleware/cache.py'
2025-04-22 17:58:56,990 wheel INFO adding 'django/middleware/clickjacking.py'
2025-04-22 17:58:56,990 wheel INFO adding 'django/middleware/common.py'
2025-04-22 17:58:56,990 wheel INFO adding 'django/middleware/csrf.py'
2025-04-22 17:58:56,991 wheel INFO adding 'django/middleware/gzip.py'
2025-04-22 17:58:56,991 wheel INFO adding 'django/middleware/http.py'
2025-04-22 17:58:56,991 wheel INFO adding 'django/middleware/locale.py'
2025-04-22 17:58:56,991 wheel INFO adding 'django/middleware/security.py'
2025-04-22 17:58:56,991 wheel INFO adding 'django/template/__init__.py'
2025-04-22 17:58:56,991 wheel INFO adding 'django/template/autoreload.py'
2025-04-22 17:58:56,992 wheel INFO adding 'django/template/base.py'
2025-04-22 17:58:56,992 wheel INFO adding 'django/template/context.py'
2025-04-22 17:58:56,992 wheel INFO adding 'django/template/context_processors.py'
2025-04-22 17:58:56,992 wheel INFO adding 'django/template/defaultfilters.py'
2025-04-22 17:58:56,993 wheel INFO adding 'django/template/defaulttags.py'
2025-04-22 17:58:56,993 wheel INFO adding 'django/template/engine.py'
2025-04-22 17:58:56,993 wheel INFO adding 'django/template/exceptions.py'
2025-04-22 17:58:56,993 wheel INFO adding 'django/template/library.py'
2025-04-22 17:58:56,994 wheel INFO adding 'django/template/loader.py'
2025-04-22 17:58:56,994 wheel INFO adding 'django/template/loader_tags.py'
2025-04-22 17:58:56,994 wheel INFO adding 'django/template/response.py'
2025-04-22 17:58:56,994 wheel INFO adding 'django/template/smartif.py'
2025-04-22 17:58:56,994 wheel INFO adding 'django/template/utils.py'
2025-04-22 17:58:56,995 wheel INFO adding 'django/template/backends/__init__.py'
2025-04-22 17:58:56,995 wheel INFO adding 'django/template/backends/base.py'
2025-04-22 17:58:56,995 wheel INFO adding 'django/template/backends/django.py'
2025-04-22 17:58:56,995 wheel INFO adding 'django/template/backends/dummy.py'
2025-04-22 17:58:56,995 wheel INFO adding 'django/template/backends/jinja2.py'
2025-04-22 17:58:56,995 wheel INFO adding 'django/template/backends/utils.py'
2025-04-22 17:58:56,996 wheel INFO adding 'django/template/loaders/__init__.py'
2025-04-22 17:58:56,996 wheel INFO adding 'django/template/loaders/app_directories.py'
2025-04-22 17:58:56,996 wheel INFO adding 'django/template/loaders/base.py'
2025-04-22 17:58:56,996 wheel INFO adding 'django/template/loaders/cached.py'
2025-04-22 17:58:56,996 wheel INFO adding 'django/template/loaders/filesystem.py'
2025-04-22 17:58:56,996 wheel INFO adding 'django/template/loaders/locmem.py'
2025-04-22 17:58:56,997 wheel INFO adding 'django/templatetags/__init__.py'
2025-04-22 17:58:56,997 wheel INFO adding 'django/templatetags/cache.py'
2025-04-22 17:58:56,997 wheel INFO adding 'django/templatetags/i18n.py'
2025-04-22 17:58:56,997 wheel INFO adding 'django/templatetags/l10n.py'
2025-04-22 17:58:56,997 wheel INFO adding 'django/templatetags/static.py'
2025-04-22 17:58:56,998 wheel INFO adding 'django/templatetags/tz.py'
2025-04-22 17:58:56,998 wheel INFO adding 'django/test/__init__.py'
2025-04-22 17:58:56,998 wheel INFO adding 'django/test/client.py'
2025-04-22 17:58:56,998 wheel INFO adding 'django/test/html.py'
2025-04-22 17:58:56,999 wheel INFO adding 'django/test/runner.py'
2025-04-22 17:58:56,999 wheel INFO adding 'django/test/selenium.py'
2025-04-22 17:58:56,999 wheel INFO adding 'django/test/signals.py'
2025-04-22 17:58:56,999 wheel INFO adding 'django/test/testcases.py'
2025-04-22 17:58:57,000 wheel INFO adding 'django/test/utils.py'
2025-04-22 17:58:57,000 wheel INFO adding 'django/urls/__init__.py'
2025-04-22 17:58:57,000 wheel INFO adding 'django/urls/base.py'
2025-04-22 17:58:57,000 wheel INFO adding 'django/urls/conf.py'
2025-04-22 17:58:57,001 wheel INFO adding 'django/urls/converters.py'
2025-04-22 17:58:57,001 wheel INFO adding 'django/urls/exceptions.py'
2025-04-22 17:58:57,001 wheel INFO adding 'django/urls/resolvers.py'
2025-04-22 17:58:57,001 wheel INFO adding 'django/urls/utils.py'
2025-04-22 17:58:57,001 wheel INFO adding 'django/utils/__init__.py'
2025-04-22 17:58:57,002 wheel INFO adding 'django/utils/_os.py'
2025-04-22 17:58:57,002 wheel INFO adding 'django/utils/archive.py'
2025-04-22 17:58:57,002 wheel INFO adding 'django/utils/asyncio.py'
2025-04-22 17:58:57,002 wheel INFO adding 'django/utils/autoreload.py'
2025-04-22 17:58:57,002 wheel INFO adding 'django/utils/baseconv.py'
2025-04-22 17:58:57,003 wheel INFO adding 'django/utils/cache.py'
2025-04-22 17:58:57,003 wheel INFO adding 'django/utils/connection.py'
2025-04-22 17:58:57,003 wheel INFO adding 'django/utils/crypto.py'
2025-04-22 17:58:57,003 wheel INFO adding 'django/utils/datastructures.py'
2025-04-22 17:58:57,003 wheel INFO adding 'django/utils/dateformat.py'
2025-04-22 17:58:57,004 wheel INFO adding 'django/utils/dateparse.py'
2025-04-22 17:58:57,004 wheel INFO adding 'django/utils/dates.py'
2025-04-22 17:58:57,004 wheel INFO adding 'django/utils/datetime_safe.py'
2025-04-22 17:58:57,004 wheel INFO adding 'django/utils/deconstruct.py'
2025-04-22 17:58:57,004 wheel INFO adding 'django/utils/decorators.py'
2025-04-22 17:58:57,004 wheel INFO adding 'django/utils/deprecation.py'
2025-04-22 17:58:57,005 wheel INFO adding 'django/utils/duration.py'
2025-04-22 17:58:57,005 wheel INFO adding 'django/utils/encoding.py'
2025-04-22 17:58:57,005 wheel INFO adding 'django/utils/feedgenerator.py'
2025-04-22 17:58:57,005 wheel INFO adding 'django/utils/formats.py'
2025-04-22 17:58:57,005 wheel INFO adding 'django/utils/functional.py'
2025-04-22 17:58:57,006 wheel INFO adding 'django/utils/hashable.py'
2025-04-22 17:58:57,006 wheel INFO adding 'django/utils/html.py'
2025-04-22 17:58:57,006 wheel INFO adding 'django/utils/http.py'
2025-04-22 17:58:57,006 wheel INFO adding 'django/utils/inspect.py'
2025-04-22 17:58:57,007 wheel INFO adding 'django/utils/ipv6.py'
2025-04-22 17:58:57,007 wheel INFO adding 'django/utils/itercompat.py'
2025-04-22 17:58:57,007 wheel INFO adding 'django/utils/jslex.py'
2025-04-22 17:58:57,007 wheel INFO adding 'django/utils/log.py'
2025-04-22 17:58:57,007 wheel INFO adding 'django/utils/lorem_ipsum.py'
2025-04-22 17:58:57,007 wheel INFO adding 'django/utils/module_loading.py'
2025-04-22 17:58:57,008 wheel INFO adding 'django/utils/numberformat.py'
2025-04-22 17:58:57,008 wheel INFO adding 'django/utils/regex_helper.py'
2025-04-22 17:58:57,008 wheel INFO adding 'django/utils/safestring.py'
2025-04-22 17:58:57,008 wheel INFO adding 'django/utils/termcolors.py'
2025-04-22 17:58:57,008 wheel INFO adding 'django/utils/text.py'
2025-04-22 17:58:57,009 wheel INFO adding 'django/utils/timesince.py'
2025-04-22 17:58:57,009 wheel INFO adding 'django/utils/timezone.py'
2025-04-22 17:58:57,009 wheel INFO adding 'django/utils/topological_sort.py'
2025-04-22 17:58:57,009 wheel INFO adding 'django/utils/tree.py'
2025-04-22 17:58:57,009 wheel INFO adding 'django/utils/version.py'
2025-04-22 17:58:57,009 wheel INFO adding 'django/utils/xmlutils.py'
2025-04-22 17:58:57,010 wheel INFO adding 'django/utils/translation/__init__.py'
2025-04-22 17:58:57,010 wheel INFO adding 'django/utils/translation/reloader.py'
2025-04-22 17:58:57,010 wheel INFO adding 'django/utils/translation/template.py'
2025-04-22 17:58:57,010 wheel INFO adding 'django/utils/translation/trans_null.py'
2025-04-22 17:58:57,010 wheel INFO adding 'django/utils/translation/trans_real.py'
2025-04-22 17:58:57,011 wheel INFO adding 'django/views/__init__.py'
2025-04-22 17:58:57,011 wheel INFO adding 'django/views/csrf.py'
2025-04-22 17:58:57,011 wheel INFO adding 'django/views/debug.py'
2025-04-22 17:58:57,011 wheel INFO adding 'django/views/defaults.py'
2025-04-22 17:58:57,012 wheel INFO adding 'django/views/i18n.py'
2025-04-22 17:58:57,012 wheel INFO adding 'django/views/static.py'
2025-04-22 17:58:57,012 wheel INFO adding 'django/views/decorators/__init__.py'
2025-04-22 17:58:57,012 wheel INFO adding 'django/views/decorators/cache.py'
2025-04-22 17:58:57,012 wheel INFO adding 'django/views/decorators/clickjacking.py'
2025-04-22 17:58:57,012 wheel INFO adding 'django/views/decorators/common.py'
2025-04-22 17:58:57,013 wheel INFO adding 'django/views/decorators/csrf.py'
2025-04-22 17:58:57,013 wheel INFO adding 'django/views/decorators/debug.py'
2025-04-22 17:58:57,013 wheel INFO adding 'django/views/decorators/gzip.py'
2025-04-22 17:58:57,013 wheel INFO adding 'django/views/decorators/http.py'
2025-04-22 17:58:57,013 wheel INFO adding 'django/views/decorators/vary.py'
2025-04-22 17:58:57,014 wheel INFO adding 'django/views/generic/__init__.py'
2025-04-22 17:58:57,014 wheel INFO adding 'django/views/generic/base.py'
2025-04-22 17:58:57,014 wheel INFO adding 'django/views/generic/dates.py'
2025-04-22 17:58:57,014 wheel INFO adding 'django/views/generic/detail.py'
2025-04-22 17:58:57,015 wheel INFO adding 'django/views/generic/edit.py'
2025-04-22 17:58:57,015 wheel INFO adding 'django/views/generic/list.py'
2025-04-22 17:58:57,015 wheel INFO adding 'django/views/templates/default_urlconf.html'
2025-04-22 17:58:57,015 wheel INFO adding 'django/views/templates/technical_404.html'
2025-04-22 17:58:57,015 wheel INFO adding 'django/views/templates/technical_500.html'
2025-04-22 17:58:57,016 wheel INFO adding 'django/views/templates/technical_500.txt'
2025-04-22 17:58:57,016 wheel INFO adding 'django-4.2.20.dist-info/licenses/AUTHORS'
2025-04-22 17:58:57,016 wheel INFO adding 'django-4.2.20.dist-info/licenses/LICENSE'
2025-04-22 17:58:57,017 wheel INFO adding 'django-4.2.20.dist-info/licenses/LICENSE.python'
2025-04-22 17:58:57,017 wheel INFO adding 'django-4.2.20.dist-info/METADATA'
2025-04-22 17:58:57,017 wheel INFO adding 'django-4.2.20.dist-info/WHEEL'
2025-04-22 17:58:57,017 wheel INFO adding 'django-4.2.20.dist-info/entry_points.txt'
2025-04-22 17:58:57,017 wheel INFO adding 'django-4.2.20.dist-info/top_level.txt'
2025-04-22 17:58:57,034 wheel INFO adding 'django-4.2.20.dist-info/RECORD'
2025-04-22 17:58:57,048 root INFO removing build/bdist.linux-armv8l/wheel
2025-04-22 17:58:57,208 gpep517 INFO The backend produced .dist/django-4.2.20-py3-none-any.whl
django-4.2.20-py3-none-any.whl
>>> py3-django: Entering fakeroot...
>>> py3-django-pyc*: Running split function pyc...
'usr/lib/python3.12/site-packages/django/db/models/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/db/models/__pycache__'
'usr/lib/python3.12/site-packages/django/db/models/functions/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/db/models/functions/__pycache__'
'usr/lib/python3.12/site-packages/django/db/models/sql/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/db/models/sql/__pycache__'
'usr/lib/python3.12/site-packages/django/db/models/fields/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/db/models/fields/__pycache__'
'usr/lib/python3.12/site-packages/django/db/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/db/__pycache__'
'usr/lib/python3.12/site-packages/django/db/migrations/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/db/migrations/__pycache__'
'usr/lib/python3.12/site-packages/django/db/migrations/operations/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/db/migrations/operations/__pycache__'
'usr/lib/python3.12/site-packages/django/db/backends/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/db/backends/__pycache__'
'usr/lib/python3.12/site-packages/django/db/backends/base/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/db/backends/base/__pycache__'
'usr/lib/python3.12/site-packages/django/db/backends/postgresql/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/db/backends/postgresql/__pycache__'
'usr/lib/python3.12/site-packages/django/db/backends/dummy/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/db/backends/dummy/__pycache__'
'usr/lib/python3.12/site-packages/django/db/backends/sqlite3/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/db/backends/sqlite3/__pycache__'
'usr/lib/python3.12/site-packages/django/db/backends/oracle/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/db/backends/oracle/__pycache__'
'usr/lib/python3.12/site-packages/django/db/backends/mysql/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/db/backends/mysql/__pycache__'
'usr/lib/python3.12/site-packages/django/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/__pycache__'
'usr/lib/python3.12/site-packages/django/views/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/views/__pycache__'
'usr/lib/python3.12/site-packages/django/views/generic/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/views/generic/__pycache__'
'usr/lib/python3.12/site-packages/django/views/decorators/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/views/decorators/__pycache__'
'usr/lib/python3.12/site-packages/django/middleware/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/middleware/__pycache__'
'usr/lib/python3.12/site-packages/django/http/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/http/__pycache__'
'usr/lib/python3.12/site-packages/django/dispatch/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/dispatch/__pycache__'
'usr/lib/python3.12/site-packages/django/urls/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/urls/__pycache__'
'usr/lib/python3.12/site-packages/django/template/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/template/__pycache__'
'usr/lib/python3.12/site-packages/django/template/loaders/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/template/loaders/__pycache__'
'usr/lib/python3.12/site-packages/django/template/backends/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/template/backends/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/urls/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/urls/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/lv/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/lv/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/es_PR/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/es_PR/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/en_AU/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/en_AU/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/de_CH/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/de_CH/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/ca/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/ca/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/en_GB/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/en_GB/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/el/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/el/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/en/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/en/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/et/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/et/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/nn/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/nn/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/cy/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/cy/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/ko/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/ko/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/is/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/is/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/sr_Latn/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/sr_Latn/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/fy/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/fy/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/bg/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/bg/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/ga/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/ga/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/gl/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/gl/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/ig/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/ig/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/uk/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/uk/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/uz/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/uz/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/kn/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/kn/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/ja/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/ja/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/cs/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/cs/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/tr/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/tr/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/sl/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/sl/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/sq/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/sq/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/az/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/az/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/eo/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/eo/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/pt_BR/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/pt_BR/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/pl/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/pl/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/gd/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/gd/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/hr/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/hr/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/ru/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/ru/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/es/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/es/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/id/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/id/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/fi/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/fi/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/mk/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/mk/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/hi/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/hi/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/sk/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/sk/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/lt/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/lt/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/de/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/de/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/it/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/it/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/sr/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/sr/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/bs/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/bs/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/es_NI/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/es_NI/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/ro/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/ro/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/ky/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/ky/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/fr/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/fr/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/ar/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/ar/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/es_AR/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/es_AR/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/vi/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/vi/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/ckb/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/ckb/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/sv/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/sv/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/zh_Hant/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/zh_Hant/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/es_CO/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/es_CO/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/ml/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/ml/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/ar_DZ/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/ar_DZ/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/ms/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/ms/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/zh_Hans/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/zh_Hans/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/hu/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/hu/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/ta/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/ta/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/eu/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/eu/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/es_MX/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/es_MX/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/tk/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/tk/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/th/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/th/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/nb/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/nb/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/mn/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/mn/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/ka/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/ka/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/nl/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/nl/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/te/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/te/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/pt/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/pt/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/bn/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/bn/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/he/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/he/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/fa/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/fa/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/tg/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/tg/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/km/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/km/__pycache__'
'usr/lib/python3.12/site-packages/django/conf/locale/da/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/conf/locale/da/__pycache__'
'usr/lib/python3.12/site-packages/django/utils/translation/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/utils/translation/__pycache__'
'usr/lib/python3.12/site-packages/django/utils/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/utils/__pycache__'
'usr/lib/python3.12/site-packages/django/templatetags/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/templatetags/__pycache__'
'usr/lib/python3.12/site-packages/django/test/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/test/__pycache__'
'usr/lib/python3.12/site-packages/django/core/files/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/core/files/__pycache__'
'usr/lib/python3.12/site-packages/django/core/files/storage/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/core/files/storage/__pycache__'
'usr/lib/python3.12/site-packages/django/core/handlers/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/core/handlers/__pycache__'
'usr/lib/python3.12/site-packages/django/core/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/core/__pycache__'
'usr/lib/python3.12/site-packages/django/core/servers/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/core/servers/__pycache__'
'usr/lib/python3.12/site-packages/django/core/mail/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/core/mail/__pycache__'
'usr/lib/python3.12/site-packages/django/core/mail/backends/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/core/mail/backends/__pycache__'
'usr/lib/python3.12/site-packages/django/core/cache/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/core/cache/__pycache__'
'usr/lib/python3.12/site-packages/django/core/cache/backends/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/core/cache/backends/__pycache__'
'usr/lib/python3.12/site-packages/django/core/management/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/core/management/__pycache__'
'usr/lib/python3.12/site-packages/django/core/management/commands/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/core/management/commands/__pycache__'
'usr/lib/python3.12/site-packages/django/core/serializers/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/core/serializers/__pycache__'
'usr/lib/python3.12/site-packages/django/core/checks/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/core/checks/__pycache__'
'usr/lib/python3.12/site-packages/django/core/checks/compatibility/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/core/checks/compatibility/__pycache__'
'usr/lib/python3.12/site-packages/django/core/checks/security/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/core/checks/security/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/auth/handlers/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/auth/handlers/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/auth/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/auth/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/auth/migrations/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/auth/migrations/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/auth/management/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/auth/management/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/auth/management/commands/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/auth/management/commands/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/contenttypes/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/contenttypes/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/contenttypes/migrations/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/contenttypes/migrations/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/contenttypes/management/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/contenttypes/management/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/contenttypes/management/commands/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/contenttypes/management/commands/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/redirects/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/redirects/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/redirects/migrations/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/redirects/migrations/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/messages/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/messages/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/messages/storage/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/messages/storage/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/sites/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/sites/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/sites/migrations/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/sites/migrations/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/sitemaps/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/sitemaps/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/sitemaps/management/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/sitemaps/management/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/sitemaps/management/commands/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/sitemaps/management/commands/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/flatpages/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/flatpages/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/flatpages/migrations/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/flatpages/migrations/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/flatpages/templatetags/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/flatpages/templatetags/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/staticfiles/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/staticfiles/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/staticfiles/management/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/staticfiles/management/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/staticfiles/management/commands/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/staticfiles/management/commands/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/sessions/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/sessions/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/sessions/migrations/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/sessions/migrations/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/sessions/management/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/sessions/management/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/sessions/management/commands/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/sessions/management/commands/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/sessions/backends/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/sessions/backends/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/admindocs/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/admindocs/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/syndication/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/syndication/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/postgres/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/postgres/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/postgres/aggregates/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/postgres/aggregates/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/postgres/fields/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/postgres/fields/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/postgres/forms/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/postgres/forms/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/db/models/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/db/models/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/db/models/sql/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/db/models/sql/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/db/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/db/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/db/backends/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/db/backends/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/db/backends/spatialite/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/db/backends/spatialite/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/db/backends/base/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/db/backends/base/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/db/backends/postgis/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/db/backends/postgis/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/db/backends/oracle/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/db/backends/oracle/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/db/backends/mysql/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/db/backends/mysql/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/sitemaps/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/sitemaps/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/utils/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/utils/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/geoip2/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/geoip2/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/management/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/management/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/management/commands/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/management/commands/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/serializers/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/serializers/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/admin/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/admin/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/geos/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/geos/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/geos/prototypes/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/geos/prototypes/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/gdal/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/gdal/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/gdal/raster/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/gdal/raster/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/gdal/prototypes/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/gdal/prototypes/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/gis/forms/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/gis/forms/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/admin/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/admin/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/admin/views/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/admin/views/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/admin/migrations/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/admin/migrations/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/admin/templatetags/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/admin/templatetags/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/humanize/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/humanize/__pycache__'
'usr/lib/python3.12/site-packages/django/contrib/humanize/templatetags/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/contrib/humanize/templatetags/__pycache__'
'usr/lib/python3.12/site-packages/django/forms/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/forms/__pycache__'
'usr/lib/python3.12/site-packages/django/apps/__pycache__' -> '/home/buildozer/aports/community/py3-django/pkg/py3-django-pyc/usr/lib/python3.12/site-packages/django/apps/__pycache__'
>>> py3-django-pyc*: Preparing subpackage py3-django-pyc...
>>> py3-django-pyc*: Running postcheck for py3-django-pyc
>>> py3-django*: Running postcheck for py3-django
>>> py3-django*: Preparing package py3-django...
>>> py3-django-pyc*: Tracing dependencies...
	python3
	py3-asgiref
	py3-sqlparse
	tzdata
	python3~3.12
>>> py3-django-pyc*: Package size: 6.2 MB
>>> py3-django-pyc*: Compressing data...
>>> py3-django-pyc*: Create checksum...
>>> py3-django-pyc*: Create py3-django-pyc-4.2.20-r0.apk
>>> py3-django*: Tracing dependencies...
	python3
	py3-asgiref
	py3-sqlparse
	tzdata
	python3~3.12
>>> py3-django*: Package size: 21.2 MB
>>> py3-django*: Compressing data...
>>> py3-django*: Create checksum...
>>> py3-django*: Create py3-django-4.2.20-r0.apk
>>> py3-django: Build complete at Tue, 22 Apr 2025 17:59:12 +0000 elapsed time 0h 0m 23s
>>> py3-django: Cleaning up srcdir
>>> py3-django: Cleaning up pkgdir
>>> py3-django: Uninstalling dependencies...
(1/29) Purging .makedepends-py3-django (20250422.175850)
(2/29) Purging py3-asgiref-pyc (3.8.1-r1)
(3/29) Purging py3-asgiref (3.8.1-r1)
(4/29) Purging py3-sqlparse-pyc (0.5.1-r0)
(5/29) Purging py3-sqlparse (0.5.1-r0)
(6/29) Purging tzdata (2025b-r0)
(7/29) Purging py3-gpep517-pyc (16-r0)
(8/29) Purging py3-gpep517 (16-r0)
(9/29) Purging py3-installer-pyc (0.7.0-r2)
(10/29) Purging py3-installer (0.7.0-r2)
(11/29) Purging py3-setuptools-pyc (77.0.3-r0)
(12/29) Purging py3-setuptools (77.0.3-r0)
(13/29) Purging py3-wheel-pyc (0.43.0-r0)
(14/29) Purging py3-wheel (0.43.0-r0)
(15/29) Purging py3-packaging-pyc (24.2-r0)
(16/29) Purging py3-packaging (24.2-r0)
(17/29) Purging py3-parsing-pyc (3.2.0-r0)
(18/29) Purging py3-parsing (3.2.0-r0)
(19/29) Purging python3-pyc (3.12.10-r0)
(20/29) Purging python3-pycache-pyc0 (3.12.10-r0)
(21/29) Purging pyc (3.12.10-r0)
(22/29) Purging python3 (3.12.10-r0)
(23/29) Purging gdbm (1.24-r0)
(24/29) Purging libbz2 (1.0.8-r6)
(25/29) Purging libffi (3.4.8-r0)
(26/29) Purging libpanelw (6.5_p20250412-r0)
(27/29) Purging mpdecimal (4.0.0-r0)
(28/29) Purging sqlite-libs (3.49.1-r0)
(29/29) Purging xz-libs (5.8.1-r0)
Executing busybox-1.37.0-r16.trigger
OK: 275 MiB in 104 packages
>>> py3-django: Updating the community/armv7 repository index...
>>> py3-django: Signing the index...