>>> py3-django: Building community/py3-django 4.2.20-r0 (using abuild 3.14.1-r4) started Tue, 22 Apr 2025 20:54:00 +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.7-r0)
(3/29) Installing gdbm (1.24-r0)
(4/29) Installing xz-libs (5.6.3-r1)
(5/29) Installing mpdecimal (4.0.0-r0)
(6/29) Installing libpanelw (6.5_p20241006-r3)
(7/29) Installing sqlite-libs (3.48.0-r1)
(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.1.4-r0)
(22/29) Installing py3-parsing-pyc (3.1.4-r0)
(23/29) Installing py3-packaging (24.2-r0)
(24/29) Installing py3-packaging-pyc (24.2-r0)
(25/29) Installing py3-setuptools (70.3.0-r0)
(26/29) Installing py3-setuptools-pyc (70.3.0-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.205401)
Executing busybox-1.37.0-r12.trigger
OK: 443 MiB in 131 packages
>>> py3-django: Cleaning up srcdir
>>> py3-django: Cleaning up pkgdir
>>> py3-django: Cleaning up tmpdir
>>> py3-django: Fetching https://distfiles.alpinelinux.org/distfiles/v3.21/Django-4.2.20.tar.gz
>>> py3-django: Fetching https://distfiles.alpinelinux.org/distfiles/v3.21/Django-4.2.20.tar.gz
>>> py3-django: Checking sha512sums...
Django-4.2.20.tar.gz: OK
>>> py3-django: Unpacking /var/cache/distfiles/v3.21/Django-4.2.20.tar.gz...
2025-04-22 20:54:02,836 gpep517 INFO Building wheel via backend setuptools.build_meta
2025-04-22 20:54:02,883 root INFO running bdist_wheel
2025-04-22 20:54:02,898 root INFO running build
2025-04-22 20:54:02,898 root INFO running build_py
2025-04-22 20:54:02,900 root INFO creating build
2025-04-22 20:54:02,901 root INFO creating build/lib
2025-04-22 20:54:02,901 root INFO creating build/lib/django
2025-04-22 20:54:02,901 root INFO copying django/__init__.py -> build/lib/django
2025-04-22 20:54:02,901 root INFO copying django/__main__.py -> build/lib/django
2025-04-22 20:54:02,901 root INFO copying django/shortcuts.py -> build/lib/django
2025-04-22 20:54:02,901 root INFO creating build/lib/django/db
2025-04-22 20:54:02,902 root INFO copying django/db/__init__.py -> build/lib/django/db
2025-04-22 20:54:02,902 root INFO copying django/db/utils.py -> build/lib/django/db
2025-04-22 20:54:02,902 root INFO copying django/db/transaction.py -> build/lib/django/db
2025-04-22 20:54:02,902 root INFO creating build/lib/django/views
2025-04-22 20:54:02,902 root INFO copying django/views/__init__.py -> build/lib/django/views
2025-04-22 20:54:02,903 root INFO copying django/views/i18n.py -> build/lib/django/views
2025-04-22 20:54:02,903 root INFO copying django/views/defaults.py -> build/lib/django/views
2025-04-22 20:54:02,903 root INFO copying django/views/csrf.py -> build/lib/django/views
2025-04-22 20:54:02,903 root INFO copying django/views/static.py -> build/lib/django/views
2025-04-22 20:54:02,903 root INFO copying django/views/debug.py -> build/lib/django/views
2025-04-22 20:54:02,904 root INFO creating build/lib/django/middleware
2025-04-22 20:54:02,904 root INFO copying django/middleware/__init__.py -> build/lib/django/middleware
2025-04-22 20:54:02,904 root INFO copying django/middleware/locale.py -> build/lib/django/middleware
2025-04-22 20:54:02,904 root INFO copying django/middleware/cache.py -> build/lib/django/middleware
2025-04-22 20:54:02,904 root INFO copying django/middleware/http.py -> build/lib/django/middleware
2025-04-22 20:54:02,905 root INFO copying django/middleware/security.py -> build/lib/django/middleware
2025-04-22 20:54:02,905 root INFO copying django/middleware/gzip.py -> build/lib/django/middleware
2025-04-22 20:54:02,905 root INFO copying django/middleware/csrf.py -> build/lib/django/middleware
2025-04-22 20:54:02,905 root INFO copying django/middleware/clickjacking.py -> build/lib/django/middleware
2025-04-22 20:54:02,905 root INFO copying django/middleware/common.py -> build/lib/django/middleware
2025-04-22 20:54:02,906 root INFO creating build/lib/django/http
2025-04-22 20:54:02,906 root INFO copying django/http/__init__.py -> build/lib/django/http
2025-04-22 20:54:02,906 root INFO copying django/http/response.py -> build/lib/django/http
2025-04-22 20:54:02,906 root INFO copying django/http/multipartparser.py -> build/lib/django/http
2025-04-22 20:54:02,906 root INFO copying django/http/cookie.py -> build/lib/django/http
2025-04-22 20:54:02,907 root INFO copying django/http/request.py -> build/lib/django/http
2025-04-22 20:54:02,907 root INFO creating build/lib/django/dispatch
2025-04-22 20:54:02,907 root INFO copying django/dispatch/__init__.py -> build/lib/django/dispatch
2025-04-22 20:54:02,907 root INFO copying django/dispatch/dispatcher.py -> build/lib/django/dispatch
2025-04-22 20:54:02,908 root INFO creating build/lib/django/urls
2025-04-22 20:54:02,908 root INFO copying django/urls/__init__.py -> build/lib/django/urls
2025-04-22 20:54:02,908 root INFO copying django/urls/converters.py -> build/lib/django/urls
2025-04-22 20:54:02,908 root INFO copying django/urls/exceptions.py -> build/lib/django/urls
2025-04-22 20:54:02,908 root INFO copying django/urls/conf.py -> build/lib/django/urls
2025-04-22 20:54:02,908 root INFO copying django/urls/utils.py -> build/lib/django/urls
2025-04-22 20:54:02,908 root INFO copying django/urls/resolvers.py -> build/lib/django/urls
2025-04-22 20:54:02,909 root INFO copying django/urls/base.py -> build/lib/django/urls
2025-04-22 20:54:02,909 root INFO creating build/lib/django/template
2025-04-22 20:54:02,909 root INFO copying django/template/__init__.py -> build/lib/django/template
2025-04-22 20:54:02,909 root INFO copying django/template/library.py -> build/lib/django/template
2025-04-22 20:54:02,909 root INFO copying django/template/engine.py -> build/lib/django/template
2025-04-22 20:54:02,910 root INFO copying django/template/response.py -> build/lib/django/template
2025-04-22 20:54:02,910 root INFO copying django/template/loader_tags.py -> build/lib/django/template
2025-04-22 20:54:02,910 root INFO copying django/template/loader.py -> build/lib/django/template
2025-04-22 20:54:02,910 root INFO copying django/template/autoreload.py -> build/lib/django/template
2025-04-22 20:54:02,910 root INFO copying django/template/exceptions.py -> build/lib/django/template
2025-04-22 20:54:02,910 root INFO copying django/template/smartif.py -> build/lib/django/template
2025-04-22 20:54:02,910 root INFO copying django/template/defaulttags.py -> build/lib/django/template
2025-04-22 20:54:02,911 root INFO copying django/template/context.py -> build/lib/django/template
2025-04-22 20:54:02,911 root INFO copying django/template/utils.py -> build/lib/django/template
2025-04-22 20:54:02,911 root INFO copying django/template/defaultfilters.py -> build/lib/django/template
2025-04-22 20:54:02,911 root INFO copying django/template/context_processors.py -> build/lib/django/template
2025-04-22 20:54:02,911 root INFO copying django/template/base.py -> build/lib/django/template
2025-04-22 20:54:02,912 root INFO creating build/lib/django/conf
2025-04-22 20:54:02,912 root INFO copying django/conf/__init__.py -> build/lib/django/conf
2025-04-22 20:54:02,912 root INFO copying django/conf/global_settings.py -> build/lib/django/conf
2025-04-22 20:54:02,912 root INFO creating build/lib/django/utils
2025-04-22 20:54:02,913 root INFO copying django/utils/datetime_safe.py -> build/lib/django/utils
2025-04-22 20:54:02,913 root INFO copying django/utils/__init__.py -> build/lib/django/utils
2025-04-22 20:54:02,913 root INFO copying django/utils/itercompat.py -> build/lib/django/utils
2025-04-22 20:54:02,913 root INFO copying django/utils/functional.py -> build/lib/django/utils
2025-04-22 20:54:02,913 root INFO copying django/utils/hashable.py -> build/lib/django/utils
2025-04-22 20:54:02,913 root INFO copying django/utils/log.py -> build/lib/django/utils
2025-04-22 20:54:02,913 root INFO copying django/utils/_os.py -> build/lib/django/utils
2025-04-22 20:54:02,914 root INFO copying django/utils/dateparse.py -> build/lib/django/utils
2025-04-22 20:54:02,914 root INFO copying django/utils/decorators.py -> build/lib/django/utils
2025-04-22 20:54:02,914 root INFO copying django/utils/topological_sort.py -> build/lib/django/utils
2025-04-22 20:54:02,914 root INFO copying django/utils/deprecation.py -> build/lib/django/utils
2025-04-22 20:54:02,914 root INFO copying django/utils/formats.py -> build/lib/django/utils
2025-04-22 20:54:02,914 root INFO copying django/utils/autoreload.py -> build/lib/django/utils
2025-04-22 20:54:02,915 root INFO copying django/utils/timezone.py -> build/lib/django/utils
2025-04-22 20:54:02,915 root INFO copying django/utils/timesince.py -> build/lib/django/utils
2025-04-22 20:54:02,915 root INFO copying django/utils/cache.py -> build/lib/django/utils
2025-04-22 20:54:02,915 root INFO copying django/utils/version.py -> build/lib/django/utils
2025-04-22 20:54:02,915 root INFO copying django/utils/datastructures.py -> build/lib/django/utils
2025-04-22 20:54:02,915 root INFO copying django/utils/dateformat.py -> build/lib/django/utils
2025-04-22 20:54:02,916 root INFO copying django/utils/html.py -> build/lib/django/utils
2025-04-22 20:54:02,916 root INFO copying django/utils/termcolors.py -> build/lib/django/utils
2025-04-22 20:54:02,916 root INFO copying django/utils/tree.py -> build/lib/django/utils
2025-04-22 20:54:02,916 root INFO copying django/utils/http.py -> build/lib/django/utils
2025-04-22 20:54:02,916 root INFO copying django/utils/ipv6.py -> build/lib/django/utils
2025-04-22 20:54:02,916 root INFO copying django/utils/asyncio.py -> build/lib/django/utils
2025-04-22 20:54:02,917 root INFO copying django/utils/connection.py -> build/lib/django/utils
2025-04-22 20:54:02,917 root INFO copying django/utils/lorem_ipsum.py -> build/lib/django/utils
2025-04-22 20:54:02,917 root INFO copying django/utils/baseconv.py -> build/lib/django/utils
2025-04-22 20:54:02,917 root INFO copying django/utils/numberformat.py -> build/lib/django/utils
2025-04-22 20:54:02,917 root INFO copying django/utils/inspect.py -> build/lib/django/utils
2025-04-22 20:54:02,917 root INFO copying django/utils/feedgenerator.py -> build/lib/django/utils
2025-04-22 20:54:02,917 root INFO copying django/utils/duration.py -> build/lib/django/utils
2025-04-22 20:54:02,918 root INFO copying django/utils/deconstruct.py -> build/lib/django/utils
2025-04-22 20:54:02,918 root INFO copying django/utils/safestring.py -> build/lib/django/utils
2025-04-22 20:54:02,918 root INFO copying django/utils/module_loading.py -> build/lib/django/utils
2025-04-22 20:54:02,918 root INFO copying django/utils/archive.py -> build/lib/django/utils
2025-04-22 20:54:02,918 root INFO copying django/utils/crypto.py -> build/lib/django/utils
2025-04-22 20:54:02,918 root INFO copying django/utils/regex_helper.py -> build/lib/django/utils
2025-04-22 20:54:02,919 root INFO copying django/utils/dates.py -> build/lib/django/utils
2025-04-22 20:54:02,919 root INFO copying django/utils/xmlutils.py -> build/lib/django/utils
2025-04-22 20:54:02,919 root INFO copying django/utils/encoding.py -> build/lib/django/utils
2025-04-22 20:54:02,919 root INFO copying django/utils/jslex.py -> build/lib/django/utils
2025-04-22 20:54:02,919 root INFO copying django/utils/text.py -> build/lib/django/utils
2025-04-22 20:54:02,919 root INFO creating build/lib/django/templatetags
2025-04-22 20:54:02,920 root INFO copying django/templatetags/__init__.py -> build/lib/django/templatetags
2025-04-22 20:54:02,920 root INFO copying django/templatetags/tz.py -> build/lib/django/templatetags
2025-04-22 20:54:02,920 root INFO copying django/templatetags/i18n.py -> build/lib/django/templatetags
2025-04-22 20:54:02,920 root INFO copying django/templatetags/cache.py -> build/lib/django/templatetags
2025-04-22 20:54:02,920 root INFO copying django/templatetags/static.py -> build/lib/django/templatetags
2025-04-22 20:54:02,920 root INFO copying django/templatetags/l10n.py -> build/lib/django/templatetags
2025-04-22 20:54:02,921 root INFO creating build/lib/django/test
2025-04-22 20:54:02,921 root INFO copying django/test/__init__.py -> build/lib/django/test
2025-04-22 20:54:02,921 root INFO copying django/test/signals.py -> build/lib/django/test
2025-04-22 20:54:02,921 root INFO copying django/test/selenium.py -> build/lib/django/test
2025-04-22 20:54:02,921 root INFO copying django/test/testcases.py -> build/lib/django/test
2025-04-22 20:54:02,921 root INFO copying django/test/html.py -> build/lib/django/test
2025-04-22 20:54:02,922 root INFO copying django/test/utils.py -> build/lib/django/test
2025-04-22 20:54:02,922 root INFO copying django/test/runner.py -> build/lib/django/test
2025-04-22 20:54:02,922 root INFO copying django/test/client.py -> build/lib/django/test
2025-04-22 20:54:02,923 root INFO creating build/lib/django/core
2025-04-22 20:54:02,923 root INFO copying django/core/__init__.py -> build/lib/django/core
2025-04-22 20:54:02,923 root INFO copying django/core/signals.py -> build/lib/django/core
2025-04-22 20:54:02,923 root INFO copying django/core/asgi.py -> build/lib/django/core
2025-04-22 20:54:02,923 root INFO copying django/core/validators.py -> build/lib/django/core
2025-04-22 20:54:02,923 root INFO copying django/core/exceptions.py -> build/lib/django/core
2025-04-22 20:54:02,923 root INFO copying django/core/paginator.py -> build/lib/django/core
2025-04-22 20:54:02,924 root INFO copying django/core/wsgi.py -> build/lib/django/core
2025-04-22 20:54:02,924 root INFO copying django/core/signing.py -> build/lib/django/core
2025-04-22 20:54:02,924 root INFO creating build/lib/django/contrib
2025-04-22 20:54:02,924 root INFO copying django/contrib/__init__.py -> build/lib/django/contrib
2025-04-22 20:54:02,924 root INFO creating build/lib/django/forms
2025-04-22 20:54:02,924 root INFO copying django/forms/__init__.py -> build/lib/django/forms
2025-04-22 20:54:02,925 root INFO copying django/forms/widgets.py -> build/lib/django/forms
2025-04-22 20:54:02,925 root INFO copying django/forms/forms.py -> build/lib/django/forms
2025-04-22 20:54:02,925 root INFO copying django/forms/models.py -> build/lib/django/forms
2025-04-22 20:54:02,925 root INFO copying django/forms/utils.py -> build/lib/django/forms
2025-04-22 20:54:02,926 root INFO copying django/forms/renderers.py -> build/lib/django/forms
2025-04-22 20:54:02,926 root INFO copying django/forms/fields.py -> build/lib/django/forms
2025-04-22 20:54:02,926 root INFO copying django/forms/boundfield.py -> build/lib/django/forms
2025-04-22 20:54:02,926 root INFO copying django/forms/formsets.py -> build/lib/django/forms
2025-04-22 20:54:02,926 root INFO creating build/lib/django/apps
2025-04-22 20:54:02,926 root INFO copying django/apps/__init__.py -> build/lib/django/apps
2025-04-22 20:54:02,927 root INFO copying django/apps/registry.py -> build/lib/django/apps
2025-04-22 20:54:02,927 root INFO copying django/apps/config.py -> build/lib/django/apps
2025-04-22 20:54:02,927 root INFO creating build/lib/django/db/models
2025-04-22 20:54:02,927 root INFO copying django/db/models/__init__.py -> build/lib/django/db/models
2025-04-22 20:54:02,927 root INFO copying django/db/models/options.py -> build/lib/django/db/models
2025-04-22 20:54:02,928 root INFO copying django/db/models/enums.py -> build/lib/django/db/models
2025-04-22 20:54:02,928 root INFO copying django/db/models/signals.py -> build/lib/django/db/models
2025-04-22 20:54:02,928 root INFO copying django/db/models/query.py -> build/lib/django/db/models
2025-04-22 20:54:02,928 root INFO copying django/db/models/lookups.py -> build/lib/django/db/models
2025-04-22 20:54:02,929 root INFO copying django/db/models/manager.py -> build/lib/django/db/models
2025-04-22 20:54:02,929 root INFO copying django/db/models/indexes.py -> build/lib/django/db/models
2025-04-22 20:54:02,929 root INFO copying django/db/models/utils.py -> build/lib/django/db/models
2025-04-22 20:54:02,929 root INFO copying django/db/models/deletion.py -> build/lib/django/db/models
2025-04-22 20:54:02,929 root INFO copying django/db/models/expressions.py -> build/lib/django/db/models
2025-04-22 20:54:02,930 root INFO copying django/db/models/constraints.py -> build/lib/django/db/models
2025-04-22 20:54:02,930 root INFO copying django/db/models/query_utils.py -> build/lib/django/db/models
2025-04-22 20:54:02,930 root INFO copying django/db/models/constants.py -> build/lib/django/db/models
2025-04-22 20:54:02,930 root INFO copying django/db/models/base.py -> build/lib/django/db/models
2025-04-22 20:54:02,930 root INFO copying django/db/models/aggregates.py -> build/lib/django/db/models
2025-04-22 20:54:02,931 root INFO creating build/lib/django/db/migrations
2025-04-22 20:54:02,931 root INFO copying django/db/migrations/__init__.py -> build/lib/django/db/migrations
2025-04-22 20:54:02,931 root INFO copying django/db/migrations/state.py -> build/lib/django/db/migrations
2025-04-22 20:54:02,931 root INFO copying django/db/migrations/graph.py -> build/lib/django/db/migrations
2025-04-22 20:54:02,932 root INFO copying django/db/migrations/writer.py -> build/lib/django/db/migrations
2025-04-22 20:54:02,932 root INFO copying django/db/migrations/serializer.py -> build/lib/django/db/migrations
2025-04-22 20:54:02,932 root INFO copying django/db/migrations/loader.py -> build/lib/django/db/migrations
2025-04-22 20:54:02,932 root INFO copying django/db/migrations/executor.py -> build/lib/django/db/migrations
2025-04-22 20:54:02,932 root INFO copying django/db/migrations/exceptions.py -> build/lib/django/db/migrations
2025-04-22 20:54:02,932 root INFO copying django/db/migrations/optimizer.py -> build/lib/django/db/migrations
2025-04-22 20:54:02,933 root INFO copying django/db/migrations/utils.py -> build/lib/django/db/migrations
2025-04-22 20:54:02,933 root INFO copying django/db/migrations/recorder.py -> build/lib/django/db/migrations
2025-04-22 20:54:02,933 root INFO copying django/db/migrations/migration.py -> build/lib/django/db/migrations
2025-04-22 20:54:02,933 root INFO copying django/db/migrations/autodetector.py -> build/lib/django/db/migrations
2025-04-22 20:54:02,933 root INFO copying django/db/migrations/questioner.py -> build/lib/django/db/migrations
2025-04-22 20:54:02,934 root INFO creating build/lib/django/db/backends
2025-04-22 20:54:02,934 root INFO copying django/db/backends/__init__.py -> build/lib/django/db/backends
2025-04-22 20:54:02,934 root INFO copying django/db/backends/signals.py -> build/lib/django/db/backends
2025-04-22 20:54:02,934 root INFO copying django/db/backends/ddl_references.py -> build/lib/django/db/backends
2025-04-22 20:54:02,934 root INFO copying django/db/backends/utils.py -> build/lib/django/db/backends
2025-04-22 20:54:02,934 root INFO creating build/lib/django/db/models/functions
2025-04-22 20:54:02,935 root INFO copying django/db/models/functions/__init__.py -> build/lib/django/db/models/functions
2025-04-22 20:54:02,935 root INFO copying django/db/models/functions/datetime.py -> build/lib/django/db/models/functions
2025-04-22 20:54:02,935 root INFO copying django/db/models/functions/window.py -> build/lib/django/db/models/functions
2025-04-22 20:54:02,935 root INFO copying django/db/models/functions/comparison.py -> build/lib/django/db/models/functions
2025-04-22 20:54:02,935 root INFO copying django/db/models/functions/math.py -> build/lib/django/db/models/functions
2025-04-22 20:54:02,935 root INFO copying django/db/models/functions/text.py -> build/lib/django/db/models/functions
2025-04-22 20:54:02,936 root INFO copying django/db/models/functions/mixins.py -> build/lib/django/db/models/functions
2025-04-22 20:54:02,936 root INFO creating build/lib/django/db/models/sql
2025-04-22 20:54:02,936 root INFO copying django/db/models/sql/__init__.py -> build/lib/django/db/models/sql
2025-04-22 20:54:02,936 root INFO copying django/db/models/sql/query.py -> build/lib/django/db/models/sql
2025-04-22 20:54:02,936 root INFO copying django/db/models/sql/compiler.py -> build/lib/django/db/models/sql
2025-04-22 20:54:02,937 root INFO copying django/db/models/sql/subqueries.py -> build/lib/django/db/models/sql
2025-04-22 20:54:02,937 root INFO copying django/db/models/sql/datastructures.py -> build/lib/django/db/models/sql
2025-04-22 20:54:02,937 root INFO copying django/db/models/sql/where.py -> build/lib/django/db/models/sql
2025-04-22 20:54:02,937 root INFO copying django/db/models/sql/constants.py -> build/lib/django/db/models/sql
2025-04-22 20:54:02,938 root INFO creating build/lib/django/db/models/fields
2025-04-22 20:54:02,938 root INFO copying django/db/models/fields/__init__.py -> build/lib/django/db/models/fields
2025-04-22 20:54:02,938 root INFO copying django/db/models/fields/related_descriptors.py -> build/lib/django/db/models/fields
2025-04-22 20:54:02,938 root INFO copying django/db/models/fields/json.py -> build/lib/django/db/models/fields
2025-04-22 20:54:02,938 root INFO copying django/db/models/fields/related_lookups.py -> build/lib/django/db/models/fields
2025-04-22 20:54:02,939 root INFO copying django/db/models/fields/proxy.py -> build/lib/django/db/models/fields
2025-04-22 20:54:02,939 root INFO copying django/db/models/fields/reverse_related.py -> build/lib/django/db/models/fields
2025-04-22 20:54:02,939 root INFO copying django/db/models/fields/files.py -> build/lib/django/db/models/fields
2025-04-22 20:54:02,939 root INFO copying django/db/models/fields/related.py -> build/lib/django/db/models/fields
2025-04-22 20:54:02,939 root INFO copying django/db/models/fields/mixins.py -> build/lib/django/db/models/fields
2025-04-22 20:54:02,940 root INFO creating build/lib/django/db/migrations/operations
2025-04-22 20:54:02,940 root INFO copying django/db/migrations/operations/__init__.py -> build/lib/django/db/migrations/operations
2025-04-22 20:54:02,940 root INFO copying django/db/migrations/operations/models.py -> build/lib/django/db/migrations/operations
2025-04-22 20:54:02,940 root INFO copying django/db/migrations/operations/fields.py -> build/lib/django/db/migrations/operations
2025-04-22 20:54:02,940 root INFO copying django/db/migrations/operations/special.py -> build/lib/django/db/migrations/operations
2025-04-22 20:54:02,941 root INFO copying django/db/migrations/operations/base.py -> build/lib/django/db/migrations/operations
2025-04-22 20:54:02,941 root INFO creating build/lib/django/db/backends/base
2025-04-22 20:54:02,941 root INFO copying django/db/backends/base/__init__.py -> build/lib/django/db/backends/base
2025-04-22 20:54:02,941 root INFO copying django/db/backends/base/schema.py -> build/lib/django/db/backends/base
2025-04-22 20:54:02,941 root INFO copying django/db/backends/base/features.py -> build/lib/django/db/backends/base
2025-04-22 20:54:02,942 root INFO copying django/db/backends/base/operations.py -> build/lib/django/db/backends/base
2025-04-22 20:54:02,942 root INFO copying django/db/backends/base/validation.py -> build/lib/django/db/backends/base
2025-04-22 20:54:02,942 root INFO copying django/db/backends/base/creation.py -> build/lib/django/db/backends/base
2025-04-22 20:54:02,942 root INFO copying django/db/backends/base/introspection.py -> build/lib/django/db/backends/base
2025-04-22 20:54:02,942 root INFO copying django/db/backends/base/base.py -> build/lib/django/db/backends/base
2025-04-22 20:54:02,943 root INFO copying django/db/backends/base/client.py -> build/lib/django/db/backends/base
2025-04-22 20:54:02,943 root INFO creating build/lib/django/db/backends/postgresql
2025-04-22 20:54:02,943 root INFO copying django/db/backends/postgresql/__init__.py -> build/lib/django/db/backends/postgresql
2025-04-22 20:54:02,943 root INFO copying django/db/backends/postgresql/schema.py -> build/lib/django/db/backends/postgresql
2025-04-22 20:54:02,943 root INFO copying django/db/backends/postgresql/features.py -> build/lib/django/db/backends/postgresql
2025-04-22 20:54:02,943 root INFO copying django/db/backends/postgresql/operations.py -> build/lib/django/db/backends/postgresql
2025-04-22 20:54:02,944 root INFO copying django/db/backends/postgresql/psycopg_any.py -> build/lib/django/db/backends/postgresql
2025-04-22 20:54:02,944 root INFO copying django/db/backends/postgresql/creation.py -> build/lib/django/db/backends/postgresql
2025-04-22 20:54:02,944 root INFO copying django/db/backends/postgresql/introspection.py -> build/lib/django/db/backends/postgresql
2025-04-22 20:54:02,944 root INFO copying django/db/backends/postgresql/base.py -> build/lib/django/db/backends/postgresql
2025-04-22 20:54:02,944 root INFO copying django/db/backends/postgresql/client.py -> build/lib/django/db/backends/postgresql
2025-04-22 20:54:02,944 root INFO creating build/lib/django/db/backends/dummy
2025-04-22 20:54:02,945 root INFO copying django/db/backends/dummy/__init__.py -> build/lib/django/db/backends/dummy
2025-04-22 20:54:02,945 root INFO copying django/db/backends/dummy/features.py -> build/lib/django/db/backends/dummy
2025-04-22 20:54:02,945 root INFO copying django/db/backends/dummy/base.py -> build/lib/django/db/backends/dummy
2025-04-22 20:54:02,945 root INFO creating build/lib/django/db/backends/sqlite3
2025-04-22 20:54:02,945 root INFO copying django/db/backends/sqlite3/__init__.py -> build/lib/django/db/backends/sqlite3
2025-04-22 20:54:02,945 root INFO copying django/db/backends/sqlite3/schema.py -> build/lib/django/db/backends/sqlite3
2025-04-22 20:54:02,946 root INFO copying django/db/backends/sqlite3/features.py -> build/lib/django/db/backends/sqlite3
2025-04-22 20:54:02,946 root INFO copying django/db/backends/sqlite3/operations.py -> build/lib/django/db/backends/sqlite3
2025-04-22 20:54:02,946 root INFO copying django/db/backends/sqlite3/creation.py -> build/lib/django/db/backends/sqlite3
2025-04-22 20:54:02,946 root INFO copying django/db/backends/sqlite3/introspection.py -> build/lib/django/db/backends/sqlite3
2025-04-22 20:54:02,946 root INFO copying django/db/backends/sqlite3/_functions.py -> build/lib/django/db/backends/sqlite3
2025-04-22 20:54:02,946 root INFO copying django/db/backends/sqlite3/base.py -> build/lib/django/db/backends/sqlite3
2025-04-22 20:54:02,947 root INFO copying django/db/backends/sqlite3/client.py -> build/lib/django/db/backends/sqlite3
2025-04-22 20:54:02,947 root INFO creating build/lib/django/db/backends/oracle
2025-04-22 20:54:02,947 root INFO copying django/db/backends/oracle/__init__.py -> build/lib/django/db/backends/oracle
2025-04-22 20:54:02,947 root INFO copying django/db/backends/oracle/functions.py -> build/lib/django/db/backends/oracle
2025-04-22 20:54:02,947 root INFO copying django/db/backends/oracle/schema.py -> build/lib/django/db/backends/oracle
2025-04-22 20:54:02,947 root INFO copying django/db/backends/oracle/features.py -> build/lib/django/db/backends/oracle
2025-04-22 20:54:02,948 root INFO copying django/db/backends/oracle/operations.py -> build/lib/django/db/backends/oracle
2025-04-22 20:54:02,948 root INFO copying django/db/backends/oracle/utils.py -> build/lib/django/db/backends/oracle
2025-04-22 20:54:02,948 root INFO copying django/db/backends/oracle/validation.py -> build/lib/django/db/backends/oracle
2025-04-22 20:54:02,948 root INFO copying django/db/backends/oracle/creation.py -> build/lib/django/db/backends/oracle
2025-04-22 20:54:02,948 root INFO copying django/db/backends/oracle/introspection.py -> build/lib/django/db/backends/oracle
2025-04-22 20:54:02,949 root INFO copying django/db/backends/oracle/base.py -> build/lib/django/db/backends/oracle
2025-04-22 20:54:02,949 root INFO copying django/db/backends/oracle/client.py -> build/lib/django/db/backends/oracle
2025-04-22 20:54:02,949 root INFO creating build/lib/django/db/backends/mysql
2025-04-22 20:54:02,949 root INFO copying django/db/backends/mysql/__init__.py -> build/lib/django/db/backends/mysql
2025-04-22 20:54:02,949 root INFO copying django/db/backends/mysql/compiler.py -> build/lib/django/db/backends/mysql
2025-04-22 20:54:02,949 root INFO copying django/db/backends/mysql/schema.py -> build/lib/django/db/backends/mysql
2025-04-22 20:54:02,950 root INFO copying django/db/backends/mysql/features.py -> build/lib/django/db/backends/mysql
2025-04-22 20:54:02,950 root INFO copying django/db/backends/mysql/operations.py -> build/lib/django/db/backends/mysql
2025-04-22 20:54:02,950 root INFO copying django/db/backends/mysql/validation.py -> build/lib/django/db/backends/mysql
2025-04-22 20:54:02,950 root INFO copying django/db/backends/mysql/creation.py -> build/lib/django/db/backends/mysql
2025-04-22 20:54:02,950 root INFO copying django/db/backends/mysql/introspection.py -> build/lib/django/db/backends/mysql
2025-04-22 20:54:02,950 root INFO copying django/db/backends/mysql/base.py -> build/lib/django/db/backends/mysql
2025-04-22 20:54:02,951 root INFO copying django/db/backends/mysql/client.py -> build/lib/django/db/backends/mysql
2025-04-22 20:54:02,951 root INFO creating build/lib/django/views/generic
2025-04-22 20:54:02,951 root INFO copying django/views/generic/__init__.py -> build/lib/django/views/generic
2025-04-22 20:54:02,951 root INFO copying django/views/generic/list.py -> build/lib/django/views/generic
2025-04-22 20:54:02,951 root INFO copying django/views/generic/detail.py -> build/lib/django/views/generic
2025-04-22 20:54:02,951 root INFO copying django/views/generic/base.py -> build/lib/django/views/generic
2025-04-22 20:54:02,952 root INFO copying django/views/generic/dates.py -> build/lib/django/views/generic
2025-04-22 20:54:02,952 root INFO copying django/views/generic/edit.py -> build/lib/django/views/generic
2025-04-22 20:54:02,952 root INFO creating build/lib/django/views/decorators
2025-04-22 20:54:02,952 root INFO copying django/views/decorators/__init__.py -> build/lib/django/views/decorators
2025-04-22 20:54:02,952 root INFO copying django/views/decorators/cache.py -> build/lib/django/views/decorators
2025-04-22 20:54:02,953 root INFO copying django/views/decorators/http.py -> build/lib/django/views/decorators
2025-04-22 20:54:02,953 root INFO copying django/views/decorators/vary.py -> build/lib/django/views/decorators
2025-04-22 20:54:02,953 root INFO copying django/views/decorators/gzip.py -> build/lib/django/views/decorators
2025-04-22 20:54:02,953 root INFO copying django/views/decorators/csrf.py -> build/lib/django/views/decorators
2025-04-22 20:54:02,953 root INFO copying django/views/decorators/clickjacking.py -> build/lib/django/views/decorators
2025-04-22 20:54:02,953 root INFO copying django/views/decorators/debug.py -> build/lib/django/views/decorators
2025-04-22 20:54:02,953 root INFO copying django/views/decorators/common.py -> build/lib/django/views/decorators
2025-04-22 20:54:02,954 root INFO creating build/lib/django/template/loaders
2025-04-22 20:54:02,954 root INFO copying django/template/loaders/__init__.py -> build/lib/django/template/loaders
2025-04-22 20:54:02,954 root INFO copying django/template/loaders/locmem.py -> build/lib/django/template/loaders
2025-04-22 20:54:02,954 root INFO copying django/template/loaders/cached.py -> build/lib/django/template/loaders
2025-04-22 20:54:02,954 root INFO copying django/template/loaders/app_directories.py -> build/lib/django/template/loaders
2025-04-22 20:54:02,954 root INFO copying django/template/loaders/filesystem.py -> build/lib/django/template/loaders
2025-04-22 20:54:02,954 root INFO copying django/template/loaders/base.py -> build/lib/django/template/loaders
2025-04-22 20:54:02,955 root INFO creating build/lib/django/template/backends
2025-04-22 20:54:02,955 root INFO copying django/template/backends/__init__.py -> build/lib/django/template/backends
2025-04-22 20:54:02,955 root INFO copying django/template/backends/jinja2.py -> build/lib/django/template/backends
2025-04-22 20:54:02,955 root INFO copying django/template/backends/utils.py -> build/lib/django/template/backends
2025-04-22 20:54:02,955 root INFO copying django/template/backends/django.py -> build/lib/django/template/backends
2025-04-22 20:54:02,956 root INFO copying django/template/backends/base.py -> build/lib/django/template/backends
2025-04-22 20:54:02,956 root INFO copying django/template/backends/dummy.py -> build/lib/django/template/backends
2025-04-22 20:54:02,956 root INFO creating build/lib/django/conf/urls
2025-04-22 20:54:02,956 root INFO copying django/conf/urls/__init__.py -> build/lib/django/conf/urls
2025-04-22 20:54:02,956 root INFO copying django/conf/urls/i18n.py -> build/lib/django/conf/urls
2025-04-22 20:54:02,956 root INFO copying django/conf/urls/static.py -> build/lib/django/conf/urls
2025-04-22 20:54:02,957 root INFO creating build/lib/django/conf/locale
2025-04-22 20:54:02,957 root INFO copying django/conf/locale/__init__.py -> build/lib/django/conf/locale
2025-04-22 20:54:02,957 root INFO creating build/lib/django/conf/locale/lv
2025-04-22 20:54:02,957 root INFO copying django/conf/locale/lv/__init__.py -> build/lib/django/conf/locale/lv
2025-04-22 20:54:02,957 root INFO copying django/conf/locale/lv/formats.py -> build/lib/django/conf/locale/lv
2025-04-22 20:54:02,957 root INFO creating build/lib/django/conf/locale/es_PR
2025-04-22 20:54:02,958 root INFO copying django/conf/locale/es_PR/__init__.py -> build/lib/django/conf/locale/es_PR
2025-04-22 20:54:02,958 root INFO copying django/conf/locale/es_PR/formats.py -> build/lib/django/conf/locale/es_PR
2025-04-22 20:54:02,958 root INFO creating build/lib/django/conf/locale/en_AU
2025-04-22 20:54:02,958 root INFO copying django/conf/locale/en_AU/__init__.py -> build/lib/django/conf/locale/en_AU
2025-04-22 20:54:02,958 root INFO copying django/conf/locale/en_AU/formats.py -> build/lib/django/conf/locale/en_AU
2025-04-22 20:54:02,958 root INFO creating build/lib/django/conf/locale/de_CH
2025-04-22 20:54:02,958 root INFO copying django/conf/locale/de_CH/__init__.py -> build/lib/django/conf/locale/de_CH
2025-04-22 20:54:02,959 root INFO copying django/conf/locale/de_CH/formats.py -> build/lib/django/conf/locale/de_CH
2025-04-22 20:54:02,959 root INFO creating build/lib/django/conf/locale/ca
2025-04-22 20:54:02,959 root INFO copying django/conf/locale/ca/__init__.py -> build/lib/django/conf/locale/ca
2025-04-22 20:54:02,959 root INFO copying django/conf/locale/ca/formats.py -> build/lib/django/conf/locale/ca
2025-04-22 20:54:02,959 root INFO creating build/lib/django/conf/locale/en_GB
2025-04-22 20:54:02,959 root INFO copying django/conf/locale/en_GB/__init__.py -> build/lib/django/conf/locale/en_GB
2025-04-22 20:54:02,960 root INFO copying django/conf/locale/en_GB/formats.py -> build/lib/django/conf/locale/en_GB
2025-04-22 20:54:02,960 root INFO creating build/lib/django/conf/locale/el
2025-04-22 20:54:02,960 root INFO copying django/conf/locale/el/__init__.py -> build/lib/django/conf/locale/el
2025-04-22 20:54:02,960 root INFO copying django/conf/locale/el/formats.py -> build/lib/django/conf/locale/el
2025-04-22 20:54:02,960 root INFO creating build/lib/django/conf/locale/en
2025-04-22 20:54:02,960 root INFO copying django/conf/locale/en/__init__.py -> build/lib/django/conf/locale/en
2025-04-22 20:54:02,960 root INFO copying django/conf/locale/en/formats.py -> build/lib/django/conf/locale/en
2025-04-22 20:54:02,961 root INFO creating build/lib/django/conf/locale/et
2025-04-22 20:54:02,961 root INFO copying django/conf/locale/et/__init__.py -> build/lib/django/conf/locale/et
2025-04-22 20:54:02,961 root INFO copying django/conf/locale/et/formats.py -> build/lib/django/conf/locale/et
2025-04-22 20:54:02,961 root INFO creating build/lib/django/conf/locale/nn
2025-04-22 20:54:02,961 root INFO copying django/conf/locale/nn/__init__.py -> build/lib/django/conf/locale/nn
2025-04-22 20:54:02,961 root INFO copying django/conf/locale/nn/formats.py -> build/lib/django/conf/locale/nn
2025-04-22 20:54:02,962 root INFO creating build/lib/django/conf/locale/cy
2025-04-22 20:54:02,962 root INFO copying django/conf/locale/cy/__init__.py -> build/lib/django/conf/locale/cy
2025-04-22 20:54:02,962 root INFO copying django/conf/locale/cy/formats.py -> build/lib/django/conf/locale/cy
2025-04-22 20:54:02,962 root INFO creating build/lib/django/conf/locale/ko
2025-04-22 20:54:02,962 root INFO copying django/conf/locale/ko/__init__.py -> build/lib/django/conf/locale/ko
2025-04-22 20:54:02,962 root INFO copying django/conf/locale/ko/formats.py -> build/lib/django/conf/locale/ko
2025-04-22 20:54:02,963 root INFO creating build/lib/django/conf/locale/is
2025-04-22 20:54:02,963 root INFO copying django/conf/locale/is/__init__.py -> build/lib/django/conf/locale/is
2025-04-22 20:54:02,963 root INFO copying django/conf/locale/is/formats.py -> build/lib/django/conf/locale/is
2025-04-22 20:54:02,963 root INFO creating build/lib/django/conf/locale/sr_Latn
2025-04-22 20:54:02,963 root INFO copying django/conf/locale/sr_Latn/__init__.py -> build/lib/django/conf/locale/sr_Latn
2025-04-22 20:54:02,963 root INFO copying django/conf/locale/sr_Latn/formats.py -> build/lib/django/conf/locale/sr_Latn
2025-04-22 20:54:02,963 root INFO creating build/lib/django/conf/locale/fy
2025-04-22 20:54:02,963 root INFO copying django/conf/locale/fy/__init__.py -> build/lib/django/conf/locale/fy
2025-04-22 20:54:02,964 root INFO copying django/conf/locale/fy/formats.py -> build/lib/django/conf/locale/fy
2025-04-22 20:54:02,964 root INFO creating build/lib/django/conf/locale/bg
2025-04-22 20:54:02,964 root INFO copying django/conf/locale/bg/__init__.py -> build/lib/django/conf/locale/bg
2025-04-22 20:54:02,964 root INFO copying django/conf/locale/bg/formats.py -> build/lib/django/conf/locale/bg
2025-04-22 20:54:02,964 root INFO creating build/lib/django/conf/locale/ga
2025-04-22 20:54:02,964 root INFO copying django/conf/locale/ga/__init__.py -> build/lib/django/conf/locale/ga
2025-04-22 20:54:02,964 root INFO copying django/conf/locale/ga/formats.py -> build/lib/django/conf/locale/ga
2025-04-22 20:54:02,965 root INFO creating build/lib/django/conf/locale/gl
2025-04-22 20:54:02,965 root INFO copying django/conf/locale/gl/__init__.py -> build/lib/django/conf/locale/gl
2025-04-22 20:54:02,965 root INFO copying django/conf/locale/gl/formats.py -> build/lib/django/conf/locale/gl
2025-04-22 20:54:02,965 root INFO creating build/lib/django/conf/locale/ig
2025-04-22 20:54:02,965 root INFO copying django/conf/locale/ig/__init__.py -> build/lib/django/conf/locale/ig
2025-04-22 20:54:02,965 root INFO copying django/conf/locale/ig/formats.py -> build/lib/django/conf/locale/ig
2025-04-22 20:54:02,966 root INFO creating build/lib/django/conf/locale/uk
2025-04-22 20:54:02,966 root INFO copying django/conf/locale/uk/__init__.py -> build/lib/django/conf/locale/uk
2025-04-22 20:54:02,966 root INFO copying django/conf/locale/uk/formats.py -> build/lib/django/conf/locale/uk
2025-04-22 20:54:02,966 root INFO creating build/lib/django/conf/locale/uz
2025-04-22 20:54:02,966 root INFO copying django/conf/locale/uz/__init__.py -> build/lib/django/conf/locale/uz
2025-04-22 20:54:02,966 root INFO copying django/conf/locale/uz/formats.py -> build/lib/django/conf/locale/uz
2025-04-22 20:54:02,967 root INFO creating build/lib/django/conf/locale/kn
2025-04-22 20:54:02,967 root INFO copying django/conf/locale/kn/__init__.py -> build/lib/django/conf/locale/kn
2025-04-22 20:54:02,967 root INFO copying django/conf/locale/kn/formats.py -> build/lib/django/conf/locale/kn
2025-04-22 20:54:02,967 root INFO creating build/lib/django/conf/locale/ja
2025-04-22 20:54:02,967 root INFO copying django/conf/locale/ja/__init__.py -> build/lib/django/conf/locale/ja
2025-04-22 20:54:02,967 root INFO copying django/conf/locale/ja/formats.py -> build/lib/django/conf/locale/ja
2025-04-22 20:54:02,967 root INFO creating build/lib/django/conf/locale/cs
2025-04-22 20:54:02,968 root INFO copying django/conf/locale/cs/__init__.py -> build/lib/django/conf/locale/cs
2025-04-22 20:54:02,968 root INFO copying django/conf/locale/cs/formats.py -> build/lib/django/conf/locale/cs
2025-04-22 20:54:02,968 root INFO creating build/lib/django/conf/locale/tr
2025-04-22 20:54:02,968 root INFO copying django/conf/locale/tr/__init__.py -> build/lib/django/conf/locale/tr
2025-04-22 20:54:02,968 root INFO copying django/conf/locale/tr/formats.py -> build/lib/django/conf/locale/tr
2025-04-22 20:54:02,968 root INFO creating build/lib/django/conf/locale/sl
2025-04-22 20:54:02,968 root INFO copying django/conf/locale/sl/__init__.py -> build/lib/django/conf/locale/sl
2025-04-22 20:54:02,969 root INFO copying django/conf/locale/sl/formats.py -> build/lib/django/conf/locale/sl
2025-04-22 20:54:02,969 root INFO creating build/lib/django/conf/locale/sq
2025-04-22 20:54:02,969 root INFO copying django/conf/locale/sq/__init__.py -> build/lib/django/conf/locale/sq
2025-04-22 20:54:02,969 root INFO copying django/conf/locale/sq/formats.py -> build/lib/django/conf/locale/sq
2025-04-22 20:54:02,969 root INFO creating build/lib/django/conf/locale/az
2025-04-22 20:54:02,969 root INFO copying django/conf/locale/az/__init__.py -> build/lib/django/conf/locale/az
2025-04-22 20:54:02,970 root INFO copying django/conf/locale/az/formats.py -> build/lib/django/conf/locale/az
2025-04-22 20:54:02,970 root INFO creating build/lib/django/conf/locale/eo
2025-04-22 20:54:02,970 root INFO copying django/conf/locale/eo/__init__.py -> build/lib/django/conf/locale/eo
2025-04-22 20:54:02,970 root INFO copying django/conf/locale/eo/formats.py -> build/lib/django/conf/locale/eo
2025-04-22 20:54:02,970 root INFO creating build/lib/django/conf/locale/pt_BR
2025-04-22 20:54:02,970 root INFO copying django/conf/locale/pt_BR/__init__.py -> build/lib/django/conf/locale/pt_BR
2025-04-22 20:54:02,970 root INFO copying django/conf/locale/pt_BR/formats.py -> build/lib/django/conf/locale/pt_BR
2025-04-22 20:54:02,971 root INFO creating build/lib/django/conf/locale/pl
2025-04-22 20:54:02,971 root INFO copying django/conf/locale/pl/__init__.py -> build/lib/django/conf/locale/pl
2025-04-22 20:54:02,971 root INFO copying django/conf/locale/pl/formats.py -> build/lib/django/conf/locale/pl
2025-04-22 20:54:02,971 root INFO creating build/lib/django/conf/locale/gd
2025-04-22 20:54:02,971 root INFO copying django/conf/locale/gd/__init__.py -> build/lib/django/conf/locale/gd
2025-04-22 20:54:02,971 root INFO copying django/conf/locale/gd/formats.py -> build/lib/django/conf/locale/gd
2025-04-22 20:54:02,972 root INFO creating build/lib/django/conf/locale/hr
2025-04-22 20:54:02,972 root INFO copying django/conf/locale/hr/__init__.py -> build/lib/django/conf/locale/hr
2025-04-22 20:54:02,972 root INFO copying django/conf/locale/hr/formats.py -> build/lib/django/conf/locale/hr
2025-04-22 20:54:02,972 root INFO creating build/lib/django/conf/locale/ru
2025-04-22 20:54:02,972 root INFO copying django/conf/locale/ru/__init__.py -> build/lib/django/conf/locale/ru
2025-04-22 20:54:02,972 root INFO copying django/conf/locale/ru/formats.py -> build/lib/django/conf/locale/ru
2025-04-22 20:54:02,972 root INFO creating build/lib/django/conf/locale/es
2025-04-22 20:54:02,973 root INFO copying django/conf/locale/es/__init__.py -> build/lib/django/conf/locale/es
2025-04-22 20:54:02,973 root INFO copying django/conf/locale/es/formats.py -> build/lib/django/conf/locale/es
2025-04-22 20:54:02,973 root INFO creating build/lib/django/conf/locale/id
2025-04-22 20:54:02,973 root INFO copying django/conf/locale/id/__init__.py -> build/lib/django/conf/locale/id
2025-04-22 20:54:02,973 root INFO copying django/conf/locale/id/formats.py -> build/lib/django/conf/locale/id
2025-04-22 20:54:02,973 root INFO creating build/lib/django/conf/locale/fi
2025-04-22 20:54:02,973 root INFO copying django/conf/locale/fi/__init__.py -> build/lib/django/conf/locale/fi
2025-04-22 20:54:02,974 root INFO copying django/conf/locale/fi/formats.py -> build/lib/django/conf/locale/fi
2025-04-22 20:54:02,974 root INFO creating build/lib/django/conf/locale/mk
2025-04-22 20:54:02,974 root INFO copying django/conf/locale/mk/__init__.py -> build/lib/django/conf/locale/mk
2025-04-22 20:54:02,974 root INFO copying django/conf/locale/mk/formats.py -> build/lib/django/conf/locale/mk
2025-04-22 20:54:02,974 root INFO creating build/lib/django/conf/locale/hi
2025-04-22 20:54:02,974 root INFO copying django/conf/locale/hi/__init__.py -> build/lib/django/conf/locale/hi
2025-04-22 20:54:02,974 root INFO copying django/conf/locale/hi/formats.py -> build/lib/django/conf/locale/hi
2025-04-22 20:54:02,975 root INFO creating build/lib/django/conf/locale/sk
2025-04-22 20:54:02,975 root INFO copying django/conf/locale/sk/__init__.py -> build/lib/django/conf/locale/sk
2025-04-22 20:54:02,975 root INFO copying django/conf/locale/sk/formats.py -> build/lib/django/conf/locale/sk
2025-04-22 20:54:02,975 root INFO creating build/lib/django/conf/locale/lt
2025-04-22 20:54:02,975 root INFO copying django/conf/locale/lt/__init__.py -> build/lib/django/conf/locale/lt
2025-04-22 20:54:02,975 root INFO copying django/conf/locale/lt/formats.py -> build/lib/django/conf/locale/lt
2025-04-22 20:54:02,976 root INFO creating build/lib/django/conf/locale/de
2025-04-22 20:54:02,976 root INFO copying django/conf/locale/de/__init__.py -> build/lib/django/conf/locale/de
2025-04-22 20:54:02,976 root INFO copying django/conf/locale/de/formats.py -> build/lib/django/conf/locale/de
2025-04-22 20:54:02,976 root INFO creating build/lib/django/conf/locale/it
2025-04-22 20:54:02,976 root INFO copying django/conf/locale/it/__init__.py -> build/lib/django/conf/locale/it
2025-04-22 20:54:02,976 root INFO copying django/conf/locale/it/formats.py -> build/lib/django/conf/locale/it
2025-04-22 20:54:02,977 root INFO creating build/lib/django/conf/locale/sr
2025-04-22 20:54:02,977 root INFO copying django/conf/locale/sr/__init__.py -> build/lib/django/conf/locale/sr
2025-04-22 20:54:02,977 root INFO copying django/conf/locale/sr/formats.py -> build/lib/django/conf/locale/sr
2025-04-22 20:54:02,977 root INFO creating build/lib/django/conf/locale/bs
2025-04-22 20:54:02,977 root INFO copying django/conf/locale/bs/__init__.py -> build/lib/django/conf/locale/bs
2025-04-22 20:54:02,977 root INFO copying django/conf/locale/bs/formats.py -> build/lib/django/conf/locale/bs
2025-04-22 20:54:02,977 root INFO creating build/lib/django/conf/locale/es_NI
2025-04-22 20:54:02,978 root INFO copying django/conf/locale/es_NI/__init__.py -> build/lib/django/conf/locale/es_NI
2025-04-22 20:54:02,978 root INFO copying django/conf/locale/es_NI/formats.py -> build/lib/django/conf/locale/es_NI
2025-04-22 20:54:02,978 root INFO creating build/lib/django/conf/locale/ro
2025-04-22 20:54:02,978 root INFO copying django/conf/locale/ro/__init__.py -> build/lib/django/conf/locale/ro
2025-04-22 20:54:02,978 root INFO copying django/conf/locale/ro/formats.py -> build/lib/django/conf/locale/ro
2025-04-22 20:54:02,979 root INFO creating build/lib/django/conf/locale/ky
2025-04-22 20:54:02,979 root INFO copying django/conf/locale/ky/__init__.py -> build/lib/django/conf/locale/ky
2025-04-22 20:54:02,979 root INFO copying django/conf/locale/ky/formats.py -> build/lib/django/conf/locale/ky
2025-04-22 20:54:02,979 root INFO creating build/lib/django/conf/locale/fr
2025-04-22 20:54:02,979 root INFO copying django/conf/locale/fr/__init__.py -> build/lib/django/conf/locale/fr
2025-04-22 20:54:02,979 root INFO copying django/conf/locale/fr/formats.py -> build/lib/django/conf/locale/fr
2025-04-22 20:54:02,980 root INFO creating build/lib/django/conf/locale/ar
2025-04-22 20:54:02,980 root INFO copying django/conf/locale/ar/__init__.py -> build/lib/django/conf/locale/ar
2025-04-22 20:54:02,980 root INFO copying django/conf/locale/ar/formats.py -> build/lib/django/conf/locale/ar
2025-04-22 20:54:02,980 root INFO creating build/lib/django/conf/locale/es_AR
2025-04-22 20:54:02,980 root INFO copying django/conf/locale/es_AR/__init__.py -> build/lib/django/conf/locale/es_AR
2025-04-22 20:54:02,980 root INFO copying django/conf/locale/es_AR/formats.py -> build/lib/django/conf/locale/es_AR
2025-04-22 20:54:02,980 root INFO creating build/lib/django/conf/locale/vi
2025-04-22 20:54:02,981 root INFO copying django/conf/locale/vi/__init__.py -> build/lib/django/conf/locale/vi
2025-04-22 20:54:02,981 root INFO copying django/conf/locale/vi/formats.py -> build/lib/django/conf/locale/vi
2025-04-22 20:54:02,981 root INFO creating build/lib/django/conf/locale/ckb
2025-04-22 20:54:02,981 root INFO copying django/conf/locale/ckb/__init__.py -> build/lib/django/conf/locale/ckb
2025-04-22 20:54:02,981 root INFO copying django/conf/locale/ckb/formats.py -> build/lib/django/conf/locale/ckb
2025-04-22 20:54:02,981 root INFO creating build/lib/django/conf/locale/sv
2025-04-22 20:54:02,981 root INFO copying django/conf/locale/sv/__init__.py -> build/lib/django/conf/locale/sv
2025-04-22 20:54:02,982 root INFO copying django/conf/locale/sv/formats.py -> build/lib/django/conf/locale/sv
2025-04-22 20:54:02,982 root INFO creating build/lib/django/conf/locale/zh_Hant
2025-04-22 20:54:02,982 root INFO copying django/conf/locale/zh_Hant/__init__.py -> build/lib/django/conf/locale/zh_Hant
2025-04-22 20:54:02,982 root INFO copying django/conf/locale/zh_Hant/formats.py -> build/lib/django/conf/locale/zh_Hant
2025-04-22 20:54:02,982 root INFO creating build/lib/django/conf/locale/es_CO
2025-04-22 20:54:02,982 root INFO copying django/conf/locale/es_CO/__init__.py -> build/lib/django/conf/locale/es_CO
2025-04-22 20:54:02,983 root INFO copying django/conf/locale/es_CO/formats.py -> build/lib/django/conf/locale/es_CO
2025-04-22 20:54:02,983 root INFO creating build/lib/django/conf/locale/ml
2025-04-22 20:54:02,983 root INFO copying django/conf/locale/ml/__init__.py -> build/lib/django/conf/locale/ml
2025-04-22 20:54:02,983 root INFO copying django/conf/locale/ml/formats.py -> build/lib/django/conf/locale/ml
2025-04-22 20:54:02,983 root INFO creating build/lib/django/conf/locale/ar_DZ
2025-04-22 20:54:02,983 root INFO copying django/conf/locale/ar_DZ/__init__.py -> build/lib/django/conf/locale/ar_DZ
2025-04-22 20:54:02,983 root INFO copying django/conf/locale/ar_DZ/formats.py -> build/lib/django/conf/locale/ar_DZ
2025-04-22 20:54:02,984 root INFO creating build/lib/django/conf/locale/ms
2025-04-22 20:54:02,984 root INFO copying django/conf/locale/ms/__init__.py -> build/lib/django/conf/locale/ms
2025-04-22 20:54:02,984 root INFO copying django/conf/locale/ms/formats.py -> build/lib/django/conf/locale/ms
2025-04-22 20:54:02,984 root INFO creating build/lib/django/conf/locale/zh_Hans
2025-04-22 20:54:02,984 root INFO copying django/conf/locale/zh_Hans/__init__.py -> build/lib/django/conf/locale/zh_Hans
2025-04-22 20:54:02,984 root INFO copying django/conf/locale/zh_Hans/formats.py -> build/lib/django/conf/locale/zh_Hans
2025-04-22 20:54:02,985 root INFO creating build/lib/django/conf/locale/hu
2025-04-22 20:54:02,985 root INFO copying django/conf/locale/hu/__init__.py -> build/lib/django/conf/locale/hu
2025-04-22 20:54:02,985 root INFO copying django/conf/locale/hu/formats.py -> build/lib/django/conf/locale/hu
2025-04-22 20:54:02,985 root INFO creating build/lib/django/conf/locale/ta
2025-04-22 20:54:02,985 root INFO copying django/conf/locale/ta/__init__.py -> build/lib/django/conf/locale/ta
2025-04-22 20:54:02,985 root INFO copying django/conf/locale/ta/formats.py -> build/lib/django/conf/locale/ta
2025-04-22 20:54:02,985 root INFO creating build/lib/django/conf/locale/eu
2025-04-22 20:54:02,986 root INFO copying django/conf/locale/eu/__init__.py -> build/lib/django/conf/locale/eu
2025-04-22 20:54:02,986 root INFO copying django/conf/locale/eu/formats.py -> build/lib/django/conf/locale/eu
2025-04-22 20:54:02,986 root INFO creating build/lib/django/conf/locale/es_MX
2025-04-22 20:54:02,986 root INFO copying django/conf/locale/es_MX/__init__.py -> build/lib/django/conf/locale/es_MX
2025-04-22 20:54:02,986 root INFO copying django/conf/locale/es_MX/formats.py -> build/lib/django/conf/locale/es_MX
2025-04-22 20:54:02,986 root INFO creating build/lib/django/conf/locale/tk
2025-04-22 20:54:02,986 root INFO copying django/conf/locale/tk/__init__.py -> build/lib/django/conf/locale/tk
2025-04-22 20:54:02,987 root INFO copying django/conf/locale/tk/formats.py -> build/lib/django/conf/locale/tk
2025-04-22 20:54:02,987 root INFO creating build/lib/django/conf/locale/th
2025-04-22 20:54:02,987 root INFO copying django/conf/locale/th/__init__.py -> build/lib/django/conf/locale/th
2025-04-22 20:54:02,987 root INFO copying django/conf/locale/th/formats.py -> build/lib/django/conf/locale/th
2025-04-22 20:54:02,987 root INFO creating build/lib/django/conf/locale/nb
2025-04-22 20:54:02,987 root INFO copying django/conf/locale/nb/__init__.py -> build/lib/django/conf/locale/nb
2025-04-22 20:54:02,988 root INFO copying django/conf/locale/nb/formats.py -> build/lib/django/conf/locale/nb
2025-04-22 20:54:02,988 root INFO creating build/lib/django/conf/locale/mn
2025-04-22 20:54:02,988 root INFO copying django/conf/locale/mn/__init__.py -> build/lib/django/conf/locale/mn
2025-04-22 20:54:02,988 root INFO copying django/conf/locale/mn/formats.py -> build/lib/django/conf/locale/mn
2025-04-22 20:54:02,988 root INFO creating build/lib/django/conf/locale/ka
2025-04-22 20:54:02,988 root INFO copying django/conf/locale/ka/__init__.py -> build/lib/django/conf/locale/ka
2025-04-22 20:54:02,988 root INFO copying django/conf/locale/ka/formats.py -> build/lib/django/conf/locale/ka
2025-04-22 20:54:02,989 root INFO creating build/lib/django/conf/locale/nl
2025-04-22 20:54:02,989 root INFO copying django/conf/locale/nl/__init__.py -> build/lib/django/conf/locale/nl
2025-04-22 20:54:02,989 root INFO copying django/conf/locale/nl/formats.py -> build/lib/django/conf/locale/nl
2025-04-22 20:54:02,989 root INFO creating build/lib/django/conf/locale/te
2025-04-22 20:54:02,989 root INFO copying django/conf/locale/te/__init__.py -> build/lib/django/conf/locale/te
2025-04-22 20:54:02,989 root INFO copying django/conf/locale/te/formats.py -> build/lib/django/conf/locale/te
2025-04-22 20:54:02,990 root INFO creating build/lib/django/conf/locale/pt
2025-04-22 20:54:02,990 root INFO copying django/conf/locale/pt/__init__.py -> build/lib/django/conf/locale/pt
2025-04-22 20:54:02,990 root INFO copying django/conf/locale/pt/formats.py -> build/lib/django/conf/locale/pt
2025-04-22 20:54:02,990 root INFO creating build/lib/django/conf/locale/bn
2025-04-22 20:54:02,990 root INFO copying django/conf/locale/bn/__init__.py -> build/lib/django/conf/locale/bn
2025-04-22 20:54:02,990 root INFO copying django/conf/locale/bn/formats.py -> build/lib/django/conf/locale/bn
2025-04-22 20:54:02,991 root INFO creating build/lib/django/conf/locale/he
2025-04-22 20:54:02,991 root INFO copying django/conf/locale/he/__init__.py -> build/lib/django/conf/locale/he
2025-04-22 20:54:02,991 root INFO copying django/conf/locale/he/formats.py -> build/lib/django/conf/locale/he
2025-04-22 20:54:02,991 root INFO creating build/lib/django/conf/locale/fa
2025-04-22 20:54:02,991 root INFO copying django/conf/locale/fa/__init__.py -> build/lib/django/conf/locale/fa
2025-04-22 20:54:02,991 root INFO copying django/conf/locale/fa/formats.py -> build/lib/django/conf/locale/fa
2025-04-22 20:54:02,992 root INFO creating build/lib/django/conf/locale/tg
2025-04-22 20:54:02,992 root INFO copying django/conf/locale/tg/__init__.py -> build/lib/django/conf/locale/tg
2025-04-22 20:54:02,992 root INFO copying django/conf/locale/tg/formats.py -> build/lib/django/conf/locale/tg
2025-04-22 20:54:02,992 root INFO creating build/lib/django/conf/locale/km
2025-04-22 20:54:02,992 root INFO copying django/conf/locale/km/__init__.py -> build/lib/django/conf/locale/km
2025-04-22 20:54:02,992 root INFO copying django/conf/locale/km/formats.py -> build/lib/django/conf/locale/km
2025-04-22 20:54:02,992 root INFO creating build/lib/django/conf/locale/da
2025-04-22 20:54:02,993 root INFO copying django/conf/locale/da/__init__.py -> build/lib/django/conf/locale/da
2025-04-22 20:54:02,993 root INFO copying django/conf/locale/da/formats.py -> build/lib/django/conf/locale/da
2025-04-22 20:54:02,993 root INFO creating build/lib/django/utils/translation
2025-04-22 20:54:02,993 root INFO copying django/utils/translation/__init__.py -> build/lib/django/utils/translation
2025-04-22 20:54:02,993 root INFO copying django/utils/translation/template.py -> build/lib/django/utils/translation
2025-04-22 20:54:02,993 root INFO copying django/utils/translation/reloader.py -> build/lib/django/utils/translation
2025-04-22 20:54:02,994 root INFO copying django/utils/translation/trans_null.py -> build/lib/django/utils/translation
2025-04-22 20:54:02,994 root INFO copying django/utils/translation/trans_real.py -> build/lib/django/utils/translation
2025-04-22 20:54:02,994 root INFO creating build/lib/django/core/files
2025-04-22 20:54:02,994 root INFO copying django/core/files/__init__.py -> build/lib/django/core/files
2025-04-22 20:54:02,994 root INFO copying django/core/files/uploadhandler.py -> build/lib/django/core/files
2025-04-22 20:54:02,994 root INFO copying django/core/files/uploadedfile.py -> build/lib/django/core/files
2025-04-22 20:54:02,995 root INFO copying django/core/files/utils.py -> build/lib/django/core/files
2025-04-22 20:54:02,995 root INFO copying django/core/files/temp.py -> build/lib/django/core/files
2025-04-22 20:54:02,995 root INFO copying django/core/files/move.py -> build/lib/django/core/files
2025-04-22 20:54:02,995 root INFO copying django/core/files/locks.py -> build/lib/django/core/files
2025-04-22 20:54:02,995 root INFO copying django/core/files/base.py -> build/lib/django/core/files
2025-04-22 20:54:02,995 root INFO copying django/core/files/images.py -> build/lib/django/core/files
2025-04-22 20:54:02,996 root INFO creating build/lib/django/core/handlers
2025-04-22 20:54:02,996 root INFO copying django/core/handlers/__init__.py -> build/lib/django/core/handlers
2025-04-22 20:54:02,996 root INFO copying django/core/handlers/asgi.py -> build/lib/django/core/handlers
2025-04-22 20:54:02,996 root INFO copying django/core/handlers/exception.py -> build/lib/django/core/handlers
2025-04-22 20:54:02,996 root INFO copying django/core/handlers/wsgi.py -> build/lib/django/core/handlers
2025-04-22 20:54:02,996 root INFO copying django/core/handlers/base.py -> build/lib/django/core/handlers
2025-04-22 20:54:02,997 root INFO creating build/lib/django/core/servers
2025-04-22 20:54:02,997 root INFO copying django/core/servers/__init__.py -> build/lib/django/core/servers
2025-04-22 20:54:02,997 root INFO copying django/core/servers/basehttp.py -> build/lib/django/core/servers
2025-04-22 20:54:02,997 root INFO creating build/lib/django/core/mail
2025-04-22 20:54:02,997 root INFO copying django/core/mail/__init__.py -> build/lib/django/core/mail
2025-04-22 20:54:02,997 root INFO copying django/core/mail/utils.py -> build/lib/django/core/mail
2025-04-22 20:54:02,998 root INFO copying django/core/mail/message.py -> build/lib/django/core/mail
2025-04-22 20:54:02,998 root INFO creating build/lib/django/core/cache
2025-04-22 20:54:02,998 root INFO copying django/core/cache/__init__.py -> build/lib/django/core/cache
2025-04-22 20:54:02,998 root INFO copying django/core/cache/utils.py -> build/lib/django/core/cache
2025-04-22 20:54:02,998 root INFO creating build/lib/django/core/management
2025-04-22 20:54:02,998 root INFO copying django/core/management/__init__.py -> build/lib/django/core/management
2025-04-22 20:54:02,999 root INFO copying django/core/management/color.py -> build/lib/django/core/management
2025-04-22 20:54:02,999 root INFO copying django/core/management/utils.py -> build/lib/django/core/management
2025-04-22 20:54:02,999 root INFO copying django/core/management/sql.py -> build/lib/django/core/management
2025-04-22 20:54:02,999 root INFO copying django/core/management/templates.py -> build/lib/django/core/management
2025-04-22 20:54:02,999 root INFO copying django/core/management/base.py -> build/lib/django/core/management
2025-04-22 20:54:03,000 root INFO creating build/lib/django/core/serializers
2025-04-22 20:54:03,000 root INFO copying django/core/serializers/python.py -> build/lib/django/core/serializers
2025-04-22 20:54:03,000 root INFO copying django/core/serializers/__init__.py -> build/lib/django/core/serializers
2025-04-22 20:54:03,000 root INFO copying django/core/serializers/xml_serializer.py -> build/lib/django/core/serializers
2025-04-22 20:54:03,000 root INFO copying django/core/serializers/jsonl.py -> build/lib/django/core/serializers
2025-04-22 20:54:03,001 root INFO copying django/core/serializers/json.py -> build/lib/django/core/serializers
2025-04-22 20:54:03,001 root INFO copying django/core/serializers/pyyaml.py -> build/lib/django/core/serializers
2025-04-22 20:54:03,001 root INFO copying django/core/serializers/base.py -> build/lib/django/core/serializers
2025-04-22 20:54:03,001 root INFO creating build/lib/django/core/checks
2025-04-22 20:54:03,001 root INFO copying django/core/checks/__init__.py -> build/lib/django/core/checks
2025-04-22 20:54:03,001 root INFO copying django/core/checks/registry.py -> build/lib/django/core/checks
2025-04-22 20:54:03,002 root INFO copying django/core/checks/database.py -> build/lib/django/core/checks
2025-04-22 20:54:03,002 root INFO copying django/core/checks/messages.py -> build/lib/django/core/checks
2025-04-22 20:54:03,002 root INFO copying django/core/checks/urls.py -> build/lib/django/core/checks
2025-04-22 20:54:03,002 root INFO copying django/core/checks/model_checks.py -> build/lib/django/core/checks
2025-04-22 20:54:03,002 root INFO copying django/core/checks/caches.py -> build/lib/django/core/checks
2025-04-22 20:54:03,002 root INFO copying django/core/checks/translation.py -> build/lib/django/core/checks
2025-04-22 20:54:03,003 root INFO copying django/core/checks/templates.py -> build/lib/django/core/checks
2025-04-22 20:54:03,003 root INFO copying django/core/checks/async_checks.py -> build/lib/django/core/checks
2025-04-22 20:54:03,003 root INFO copying django/core/checks/files.py -> build/lib/django/core/checks
2025-04-22 20:54:03,003 root INFO creating build/lib/django/core/files/storage
2025-04-22 20:54:03,003 root INFO copying django/core/files/storage/__init__.py -> build/lib/django/core/files/storage
2025-04-22 20:54:03,003 root INFO copying django/core/files/storage/handler.py -> build/lib/django/core/files/storage
2025-04-22 20:54:03,004 root INFO copying django/core/files/storage/memory.py -> build/lib/django/core/files/storage
2025-04-22 20:54:03,004 root INFO copying django/core/files/storage/filesystem.py -> build/lib/django/core/files/storage
2025-04-22 20:54:03,004 root INFO copying django/core/files/storage/base.py -> build/lib/django/core/files/storage
2025-04-22 20:54:03,004 root INFO copying django/core/files/storage/mixins.py -> build/lib/django/core/files/storage
2025-04-22 20:54:03,004 root INFO creating build/lib/django/core/mail/backends
2025-04-22 20:54:03,005 root INFO copying django/core/mail/backends/__init__.py -> build/lib/django/core/mail/backends
2025-04-22 20:54:03,005 root INFO copying django/core/mail/backends/locmem.py -> build/lib/django/core/mail/backends
2025-04-22 20:54:03,005 root INFO copying django/core/mail/backends/base.py -> build/lib/django/core/mail/backends
2025-04-22 20:54:03,005 root INFO copying django/core/mail/backends/console.py -> build/lib/django/core/mail/backends
2025-04-22 20:54:03,005 root INFO copying django/core/mail/backends/dummy.py -> build/lib/django/core/mail/backends
2025-04-22 20:54:03,006 root INFO copying django/core/mail/backends/smtp.py -> build/lib/django/core/mail/backends
2025-04-22 20:54:03,006 root INFO copying django/core/mail/backends/filebased.py -> build/lib/django/core/mail/backends
2025-04-22 20:54:03,006 root INFO creating build/lib/django/core/cache/backends
2025-04-22 20:54:03,006 root INFO copying django/core/cache/backends/__init__.py -> build/lib/django/core/cache/backends
2025-04-22 20:54:03,006 root INFO copying django/core/cache/backends/locmem.py -> build/lib/django/core/cache/backends
2025-04-22 20:54:03,007 root INFO copying django/core/cache/backends/db.py -> build/lib/django/core/cache/backends
2025-04-22 20:54:03,007 root INFO copying django/core/cache/backends/memcached.py -> build/lib/django/core/cache/backends
2025-04-22 20:54:03,007 root INFO copying django/core/cache/backends/redis.py -> build/lib/django/core/cache/backends
2025-04-22 20:54:03,007 root INFO copying django/core/cache/backends/base.py -> build/lib/django/core/cache/backends
2025-04-22 20:54:03,007 root INFO copying django/core/cache/backends/dummy.py -> build/lib/django/core/cache/backends
2025-04-22 20:54:03,007 root INFO copying django/core/cache/backends/filebased.py -> build/lib/django/core/cache/backends
2025-04-22 20:54:03,008 root INFO creating build/lib/django/core/management/commands
2025-04-22 20:54:03,008 root INFO copying django/core/management/commands/__init__.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,008 root INFO copying django/core/management/commands/sqlmigrate.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,008 root INFO copying django/core/management/commands/startapp.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,009 root INFO copying django/core/management/commands/showmigrations.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,009 root INFO copying django/core/management/commands/optimizemigration.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,009 root INFO copying django/core/management/commands/dumpdata.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,009 root INFO copying django/core/management/commands/migrate.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,009 root INFO copying django/core/management/commands/shell.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,009 root INFO copying django/core/management/commands/loaddata.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,010 root INFO copying django/core/management/commands/createcachetable.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,010 root INFO copying django/core/management/commands/dbshell.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,010 root INFO copying django/core/management/commands/inspectdb.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,010 root INFO copying django/core/management/commands/compilemessages.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,010 root INFO copying django/core/management/commands/startproject.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,011 root INFO copying django/core/management/commands/testserver.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,011 root INFO copying django/core/management/commands/flush.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,011 root INFO copying django/core/management/commands/diffsettings.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,011 root INFO copying django/core/management/commands/sqlflush.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,011 root INFO copying django/core/management/commands/makemigrations.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,011 root INFO copying django/core/management/commands/sqlsequencereset.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,012 root INFO copying django/core/management/commands/makemessages.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,012 root INFO copying django/core/management/commands/runserver.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,012 root INFO copying django/core/management/commands/check.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,012 root INFO copying django/core/management/commands/sendtestemail.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,012 root INFO copying django/core/management/commands/squashmigrations.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,012 root INFO copying django/core/management/commands/test.py -> build/lib/django/core/management/commands
2025-04-22 20:54:03,013 root INFO creating build/lib/django/core/checks/compatibility
2025-04-22 20:54:03,013 root INFO copying django/core/checks/compatibility/__init__.py -> build/lib/django/core/checks/compatibility
2025-04-22 20:54:03,013 root INFO copying django/core/checks/compatibility/django_4_0.py -> build/lib/django/core/checks/compatibility
2025-04-22 20:54:03,013 root INFO creating build/lib/django/core/checks/security
2025-04-22 20:54:03,013 root INFO copying django/core/checks/security/__init__.py -> build/lib/django/core/checks/security
2025-04-22 20:54:03,013 root INFO copying django/core/checks/security/sessions.py -> build/lib/django/core/checks/security
2025-04-22 20:54:03,014 root INFO copying django/core/checks/security/csrf.py -> build/lib/django/core/checks/security
2025-04-22 20:54:03,014 root INFO copying django/core/checks/security/base.py -> build/lib/django/core/checks/security
2025-04-22 20:54:03,014 root INFO creating build/lib/django/contrib/auth
2025-04-22 20:54:03,014 root INFO copying django/contrib/auth/__init__.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,014 root INFO copying django/contrib/auth/hashers.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,015 root INFO copying django/contrib/auth/signals.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,015 root INFO copying django/contrib/auth/middleware.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,015 root INFO copying django/contrib/auth/views.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,015 root INFO copying django/contrib/auth/forms.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,015 root INFO copying django/contrib/auth/validators.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,015 root INFO copying django/contrib/auth/decorators.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,016 root INFO copying django/contrib/auth/models.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,016 root INFO copying django/contrib/auth/backends.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,016 root INFO copying django/contrib/auth/apps.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,016 root INFO copying django/contrib/auth/urls.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,016 root INFO copying django/contrib/auth/admin.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,016 root INFO copying django/contrib/auth/checks.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,017 root INFO copying django/contrib/auth/context_processors.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,017 root INFO copying django/contrib/auth/tokens.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,017 root INFO copying django/contrib/auth/base_user.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,017 root INFO copying django/contrib/auth/password_validation.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,017 root INFO copying django/contrib/auth/mixins.py -> build/lib/django/contrib/auth
2025-04-22 20:54:03,018 root INFO creating build/lib/django/contrib/contenttypes
2025-04-22 20:54:03,018 root INFO copying django/contrib/contenttypes/__init__.py -> build/lib/django/contrib/contenttypes
2025-04-22 20:54:03,018 root INFO copying django/contrib/contenttypes/views.py -> build/lib/django/contrib/contenttypes
2025-04-22 20:54:03,018 root INFO copying django/contrib/contenttypes/forms.py -> build/lib/django/contrib/contenttypes
2025-04-22 20:54:03,018 root INFO copying django/contrib/contenttypes/models.py -> build/lib/django/contrib/contenttypes
2025-04-22 20:54:03,018 root INFO copying django/contrib/contenttypes/apps.py -> build/lib/django/contrib/contenttypes
2025-04-22 20:54:03,018 root INFO copying django/contrib/contenttypes/admin.py -> build/lib/django/contrib/contenttypes
2025-04-22 20:54:03,019 root INFO copying django/contrib/contenttypes/checks.py -> build/lib/django/contrib/contenttypes
2025-04-22 20:54:03,019 root INFO copying django/contrib/contenttypes/fields.py -> build/lib/django/contrib/contenttypes
2025-04-22 20:54:03,019 root INFO creating build/lib/django/contrib/redirects
2025-04-22 20:54:03,019 root INFO copying django/contrib/redirects/__init__.py -> build/lib/django/contrib/redirects
2025-04-22 20:54:03,019 root INFO copying django/contrib/redirects/middleware.py -> build/lib/django/contrib/redirects
2025-04-22 20:54:03,019 root INFO copying django/contrib/redirects/models.py -> build/lib/django/contrib/redirects
2025-04-22 20:54:03,020 root INFO copying django/contrib/redirects/apps.py -> build/lib/django/contrib/redirects
2025-04-22 20:54:03,020 root INFO copying django/contrib/redirects/admin.py -> build/lib/django/contrib/redirects
2025-04-22 20:54:03,020 root INFO creating build/lib/django/contrib/messages
2025-04-22 20:54:03,020 root INFO copying django/contrib/messages/__init__.py -> build/lib/django/contrib/messages
2025-04-22 20:54:03,020 root INFO copying django/contrib/messages/middleware.py -> build/lib/django/contrib/messages
2025-04-22 20:54:03,021 root INFO copying django/contrib/messages/views.py -> build/lib/django/contrib/messages
2025-04-22 20:54:03,021 root INFO copying django/contrib/messages/apps.py -> build/lib/django/contrib/messages
2025-04-22 20:54:03,021 root INFO copying django/contrib/messages/utils.py -> build/lib/django/contrib/messages
2025-04-22 20:54:03,021 root INFO copying django/contrib/messages/api.py -> build/lib/django/contrib/messages
2025-04-22 20:54:03,021 root INFO copying django/contrib/messages/context_processors.py -> build/lib/django/contrib/messages
2025-04-22 20:54:03,021 root INFO copying django/contrib/messages/constants.py -> build/lib/django/contrib/messages
2025-04-22 20:54:03,022 root INFO creating build/lib/django/contrib/sites
2025-04-22 20:54:03,022 root INFO copying django/contrib/sites/__init__.py -> build/lib/django/contrib/sites
2025-04-22 20:54:03,022 root INFO copying django/contrib/sites/managers.py -> build/lib/django/contrib/sites
2025-04-22 20:54:03,022 root INFO copying django/contrib/sites/middleware.py -> build/lib/django/contrib/sites
2025-04-22 20:54:03,022 root INFO copying django/contrib/sites/models.py -> build/lib/django/contrib/sites
2025-04-22 20:54:03,022 root INFO copying django/contrib/sites/apps.py -> build/lib/django/contrib/sites
2025-04-22 20:54:03,023 root INFO copying django/contrib/sites/admin.py -> build/lib/django/contrib/sites
2025-04-22 20:54:03,023 root INFO copying django/contrib/sites/checks.py -> build/lib/django/contrib/sites
2025-04-22 20:54:03,023 root INFO copying django/contrib/sites/management.py -> build/lib/django/contrib/sites
2025-04-22 20:54:03,023 root INFO copying django/contrib/sites/requests.py -> build/lib/django/contrib/sites
2025-04-22 20:54:03,023 root INFO copying django/contrib/sites/shortcuts.py -> build/lib/django/contrib/sites
2025-04-22 20:54:03,023 root INFO creating build/lib/django/contrib/sitemaps
2025-04-22 20:54:03,023 root INFO copying django/contrib/sitemaps/__init__.py -> build/lib/django/contrib/sitemaps
2025-04-22 20:54:03,024 root INFO copying django/contrib/sitemaps/views.py -> build/lib/django/contrib/sitemaps
2025-04-22 20:54:03,024 root INFO copying django/contrib/sitemaps/apps.py -> build/lib/django/contrib/sitemaps
2025-04-22 20:54:03,024 root INFO creating build/lib/django/contrib/flatpages
2025-04-22 20:54:03,024 root INFO copying django/contrib/flatpages/__init__.py -> build/lib/django/contrib/flatpages
2025-04-22 20:54:03,024 root INFO copying django/contrib/flatpages/middleware.py -> build/lib/django/contrib/flatpages
2025-04-22 20:54:03,024 root INFO copying django/contrib/flatpages/views.py -> build/lib/django/contrib/flatpages
2025-04-22 20:54:03,025 root INFO copying django/contrib/flatpages/forms.py -> build/lib/django/contrib/flatpages
2025-04-22 20:54:03,025 root INFO copying django/contrib/flatpages/models.py -> build/lib/django/contrib/flatpages
2025-04-22 20:54:03,025 root INFO copying django/contrib/flatpages/apps.py -> build/lib/django/contrib/flatpages
2025-04-22 20:54:03,025 root INFO copying django/contrib/flatpages/urls.py -> build/lib/django/contrib/flatpages
2025-04-22 20:54:03,025 root INFO copying django/contrib/flatpages/admin.py -> build/lib/django/contrib/flatpages
2025-04-22 20:54:03,025 root INFO copying django/contrib/flatpages/sitemaps.py -> build/lib/django/contrib/flatpages
2025-04-22 20:54:03,026 root INFO creating build/lib/django/contrib/staticfiles
2025-04-22 20:54:03,026 root INFO copying django/contrib/staticfiles/__init__.py -> build/lib/django/contrib/staticfiles
2025-04-22 20:54:03,026 root INFO copying django/contrib/staticfiles/handlers.py -> build/lib/django/contrib/staticfiles
2025-04-22 20:54:03,026 root INFO copying django/contrib/staticfiles/views.py -> build/lib/django/contrib/staticfiles
2025-04-22 20:54:03,026 root INFO copying django/contrib/staticfiles/testing.py -> build/lib/django/contrib/staticfiles
2025-04-22 20:54:03,026 root INFO copying django/contrib/staticfiles/apps.py -> build/lib/django/contrib/staticfiles
2025-04-22 20:54:03,027 root INFO copying django/contrib/staticfiles/urls.py -> build/lib/django/contrib/staticfiles
2025-04-22 20:54:03,027 root INFO copying django/contrib/staticfiles/utils.py -> build/lib/django/contrib/staticfiles
2025-04-22 20:54:03,027 root INFO copying django/contrib/staticfiles/checks.py -> build/lib/django/contrib/staticfiles
2025-04-22 20:54:03,027 root INFO copying django/contrib/staticfiles/finders.py -> build/lib/django/contrib/staticfiles
2025-04-22 20:54:03,027 root INFO copying django/contrib/staticfiles/storage.py -> build/lib/django/contrib/staticfiles
2025-04-22 20:54:03,027 root INFO creating build/lib/django/contrib/sessions
2025-04-22 20:54:03,028 root INFO copying django/contrib/sessions/__init__.py -> build/lib/django/contrib/sessions
2025-04-22 20:54:03,028 root INFO copying django/contrib/sessions/middleware.py -> build/lib/django/contrib/sessions
2025-04-22 20:54:03,028 root INFO copying django/contrib/sessions/exceptions.py -> build/lib/django/contrib/sessions
2025-04-22 20:54:03,028 root INFO copying django/contrib/sessions/base_session.py -> build/lib/django/contrib/sessions
2025-04-22 20:54:03,028 root INFO copying django/contrib/sessions/models.py -> build/lib/django/contrib/sessions
2025-04-22 20:54:03,028 root INFO copying django/contrib/sessions/apps.py -> build/lib/django/contrib/sessions
2025-04-22 20:54:03,029 root INFO copying django/contrib/sessions/serializers.py -> build/lib/django/contrib/sessions
2025-04-22 20:54:03,029 root INFO creating build/lib/django/contrib/admindocs
2025-04-22 20:54:03,029 root INFO copying django/contrib/admindocs/__init__.py -> build/lib/django/contrib/admindocs
2025-04-22 20:54:03,029 root INFO copying django/contrib/admindocs/middleware.py -> build/lib/django/contrib/admindocs
2025-04-22 20:54:03,029 root INFO copying django/contrib/admindocs/views.py -> build/lib/django/contrib/admindocs
2025-04-22 20:54:03,029 root INFO copying django/contrib/admindocs/apps.py -> build/lib/django/contrib/admindocs
2025-04-22 20:54:03,030 root INFO copying django/contrib/admindocs/urls.py -> build/lib/django/contrib/admindocs
2025-04-22 20:54:03,030 root INFO copying django/contrib/admindocs/utils.py -> build/lib/django/contrib/admindocs
2025-04-22 20:54:03,030 root INFO creating build/lib/django/contrib/syndication
2025-04-22 20:54:03,030 root INFO copying django/contrib/syndication/__init__.py -> build/lib/django/contrib/syndication
2025-04-22 20:54:03,030 root INFO copying django/contrib/syndication/views.py -> build/lib/django/contrib/syndication
2025-04-22 20:54:03,030 root INFO copying django/contrib/syndication/apps.py -> build/lib/django/contrib/syndication
2025-04-22 20:54:03,031 root INFO creating build/lib/django/contrib/postgres
2025-04-22 20:54:03,031 root INFO copying django/contrib/postgres/__init__.py -> build/lib/django/contrib/postgres
2025-04-22 20:54:03,031 root INFO copying django/contrib/postgres/functions.py -> build/lib/django/contrib/postgres
2025-04-22 20:54:03,031 root INFO copying django/contrib/postgres/signals.py -> build/lib/django/contrib/postgres
2025-04-22 20:54:03,031 root INFO copying django/contrib/postgres/lookups.py -> build/lib/django/contrib/postgres
2025-04-22 20:54:03,031 root INFO copying django/contrib/postgres/validators.py -> build/lib/django/contrib/postgres
2025-04-22 20:54:03,031 root INFO copying django/contrib/postgres/operations.py -> build/lib/django/contrib/postgres
2025-04-22 20:54:03,032 root INFO copying django/contrib/postgres/apps.py -> build/lib/django/contrib/postgres
2025-04-22 20:54:03,032 root INFO copying django/contrib/postgres/indexes.py -> build/lib/django/contrib/postgres
2025-04-22 20:54:03,032 root INFO copying django/contrib/postgres/utils.py -> build/lib/django/contrib/postgres
2025-04-22 20:54:03,032 root INFO copying django/contrib/postgres/expressions.py -> build/lib/django/contrib/postgres
2025-04-22 20:54:03,032 root INFO copying django/contrib/postgres/search.py -> build/lib/django/contrib/postgres
2025-04-22 20:54:03,032 root INFO copying django/contrib/postgres/constraints.py -> build/lib/django/contrib/postgres
2025-04-22 20:54:03,033 root INFO copying django/contrib/postgres/serializers.py -> build/lib/django/contrib/postgres
2025-04-22 20:54:03,033 root INFO creating build/lib/django/contrib/gis
2025-04-22 20:54:03,033 root INFO copying django/contrib/gis/__init__.py -> build/lib/django/contrib/gis
2025-04-22 20:54:03,033 root INFO copying django/contrib/gis/views.py -> build/lib/django/contrib/gis
2025-04-22 20:54:03,033 root INFO copying django/contrib/gis/apps.py -> build/lib/django/contrib/gis
2025-04-22 20:54:03,034 root INFO copying django/contrib/gis/geometry.py -> build/lib/django/contrib/gis
2025-04-22 20:54:03,034 root INFO copying django/contrib/gis/feeds.py -> build/lib/django/contrib/gis
2025-04-22 20:54:03,034 root INFO copying django/contrib/gis/ptr.py -> build/lib/django/contrib/gis
2025-04-22 20:54:03,034 root INFO copying django/contrib/gis/shortcuts.py -> build/lib/django/contrib/gis
2025-04-22 20:54:03,034 root INFO copying django/contrib/gis/measure.py -> build/lib/django/contrib/gis
2025-04-22 20:54:03,034 root INFO creating build/lib/django/contrib/admin
2025-04-22 20:54:03,035 root INFO copying django/contrib/admin/__init__.py -> build/lib/django/contrib/admin
2025-04-22 20:54:03,035 root INFO copying django/contrib/admin/options.py -> build/lib/django/contrib/admin
2025-04-22 20:54:03,035 root INFO copying django/contrib/admin/widgets.py -> build/lib/django/contrib/admin
2025-04-22 20:54:03,035 root INFO copying django/contrib/admin/forms.py -> build/lib/django/contrib/admin
2025-04-22 20:54:03,035 root INFO copying django/contrib/admin/decorators.py -> build/lib/django/contrib/admin
2025-04-22 20:54:03,036 root INFO copying django/contrib/admin/filters.py -> build/lib/django/contrib/admin
2025-04-22 20:54:03,036 root INFO copying django/contrib/admin/exceptions.py -> build/lib/django/contrib/admin
2025-04-22 20:54:03,036 root INFO copying django/contrib/admin/models.py -> build/lib/django/contrib/admin
2025-04-22 20:54:03,036 root INFO copying django/contrib/admin/apps.py -> build/lib/django/contrib/admin
2025-04-22 20:54:03,036 root INFO copying django/contrib/admin/utils.py -> build/lib/django/contrib/admin
2025-04-22 20:54:03,036 root INFO copying django/contrib/admin/checks.py -> build/lib/django/contrib/admin
2025-04-22 20:54:03,037 root INFO copying django/contrib/admin/tests.py -> build/lib/django/contrib/admin
2025-04-22 20:54:03,037 root INFO copying django/contrib/admin/helpers.py -> build/lib/django/contrib/admin
2025-04-22 20:54:03,037 root INFO copying django/contrib/admin/sites.py -> build/lib/django/contrib/admin
2025-04-22 20:54:03,037 root INFO copying django/contrib/admin/actions.py -> build/lib/django/contrib/admin
2025-04-22 20:54:03,037 root INFO creating build/lib/django/contrib/humanize
2025-04-22 20:54:03,038 root INFO copying django/contrib/humanize/__init__.py -> build/lib/django/contrib/humanize
2025-04-22 20:54:03,038 root INFO copying django/contrib/humanize/apps.py -> build/lib/django/contrib/humanize
2025-04-22 20:54:03,038 root INFO creating build/lib/django/contrib/auth/handlers
2025-04-22 20:54:03,038 root INFO copying django/contrib/auth/handlers/__init__.py -> build/lib/django/contrib/auth/handlers
2025-04-22 20:54:03,038 root INFO copying django/contrib/auth/handlers/modwsgi.py -> build/lib/django/contrib/auth/handlers
2025-04-22 20:54:03,039 root INFO creating build/lib/django/contrib/auth/migrations
2025-04-22 20:54:03,039 root INFO copying django/contrib/auth/migrations/__init__.py -> build/lib/django/contrib/auth/migrations
2025-04-22 20:54:03,039 root INFO copying django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py -> build/lib/django/contrib/auth/migrations
2025-04-22 20:54:03,039 root INFO copying django/contrib/auth/migrations/0002_alter_permission_name_max_length.py -> build/lib/django/contrib/auth/migrations
2025-04-22 20:54:03,039 root INFO copying django/contrib/auth/migrations/0008_alter_user_username_max_length.py -> build/lib/django/contrib/auth/migrations
2025-04-22 20:54:03,039 root INFO copying django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py -> build/lib/django/contrib/auth/migrations
2025-04-22 20:54:03,039 root INFO copying django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py -> build/lib/django/contrib/auth/migrations
2025-04-22 20:54:03,039 root INFO copying django/contrib/auth/migrations/0006_require_contenttypes_0002.py -> build/lib/django/contrib/auth/migrations
2025-04-22 20:54:03,040 root INFO copying django/contrib/auth/migrations/0011_update_proxy_permissions.py -> build/lib/django/contrib/auth/migrations
2025-04-22 20:54:03,040 root INFO copying django/contrib/auth/migrations/0005_alter_user_last_login_null.py -> build/lib/django/contrib/auth/migrations
2025-04-22 20:54:03,040 root INFO copying django/contrib/auth/migrations/0001_initial.py -> build/lib/django/contrib/auth/migrations
2025-04-22 20:54:03,040 root INFO copying django/contrib/auth/migrations/0010_alter_group_name_max_length.py -> build/lib/django/contrib/auth/migrations
2025-04-22 20:54:03,040 root INFO copying django/contrib/auth/migrations/0003_alter_user_email_max_length.py -> build/lib/django/contrib/auth/migrations
2025-04-22 20:54:03,040 root INFO copying django/contrib/auth/migrations/0004_alter_user_username_opts.py -> build/lib/django/contrib/auth/migrations
2025-04-22 20:54:03,041 root INFO creating build/lib/django/contrib/auth/management
2025-04-22 20:54:03,041 root INFO copying django/contrib/auth/management/__init__.py -> build/lib/django/contrib/auth/management
2025-04-22 20:54:03,041 root INFO creating build/lib/django/contrib/auth/management/commands
2025-04-22 20:54:03,041 root INFO copying django/contrib/auth/management/commands/__init__.py -> build/lib/django/contrib/auth/management/commands
2025-04-22 20:54:03,041 root INFO copying django/contrib/auth/management/commands/createsuperuser.py -> build/lib/django/contrib/auth/management/commands
2025-04-22 20:54:03,041 root INFO copying django/contrib/auth/management/commands/changepassword.py -> build/lib/django/contrib/auth/management/commands
2025-04-22 20:54:03,042 root INFO creating build/lib/django/contrib/contenttypes/migrations
2025-04-22 20:54:03,042 root INFO copying django/contrib/contenttypes/migrations/__init__.py -> build/lib/django/contrib/contenttypes/migrations
2025-04-22 20:54:03,042 root INFO copying django/contrib/contenttypes/migrations/0001_initial.py -> build/lib/django/contrib/contenttypes/migrations
2025-04-22 20:54:03,042 root INFO copying django/contrib/contenttypes/migrations/0002_remove_content_type_name.py -> build/lib/django/contrib/contenttypes/migrations
2025-04-22 20:54:03,042 root INFO creating build/lib/django/contrib/contenttypes/management
2025-04-22 20:54:03,042 root INFO copying django/contrib/contenttypes/management/__init__.py -> build/lib/django/contrib/contenttypes/management
2025-04-22 20:54:03,043 root INFO creating build/lib/django/contrib/contenttypes/management/commands
2025-04-22 20:54:03,043 root INFO copying django/contrib/contenttypes/management/commands/__init__.py -> build/lib/django/contrib/contenttypes/management/commands
2025-04-22 20:54:03,043 root INFO copying django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py -> build/lib/django/contrib/contenttypes/management/commands
2025-04-22 20:54:03,043 root INFO creating build/lib/django/contrib/redirects/migrations
2025-04-22 20:54:03,043 root INFO copying django/contrib/redirects/migrations/__init__.py -> build/lib/django/contrib/redirects/migrations
2025-04-22 20:54:03,043 root INFO copying django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py -> build/lib/django/contrib/redirects/migrations
2025-04-22 20:54:03,044 root INFO copying django/contrib/redirects/migrations/0001_initial.py -> build/lib/django/contrib/redirects/migrations
2025-04-22 20:54:03,044 root INFO creating build/lib/django/contrib/messages/storage
2025-04-22 20:54:03,044 root INFO copying django/contrib/messages/storage/__init__.py -> build/lib/django/contrib/messages/storage
2025-04-22 20:54:03,044 root INFO copying django/contrib/messages/storage/session.py -> build/lib/django/contrib/messages/storage
2025-04-22 20:54:03,044 root INFO copying django/contrib/messages/storage/cookie.py -> build/lib/django/contrib/messages/storage
2025-04-22 20:54:03,044 root INFO copying django/contrib/messages/storage/fallback.py -> build/lib/django/contrib/messages/storage
2025-04-22 20:54:03,045 root INFO copying django/contrib/messages/storage/base.py -> build/lib/django/contrib/messages/storage
2025-04-22 20:54:03,045 root INFO creating build/lib/django/contrib/sites/migrations
2025-04-22 20:54:03,045 root INFO copying django/contrib/sites/migrations/__init__.py -> build/lib/django/contrib/sites/migrations
2025-04-22 20:54:03,045 root INFO copying django/contrib/sites/migrations/0001_initial.py -> build/lib/django/contrib/sites/migrations
2025-04-22 20:54:03,045 root INFO copying django/contrib/sites/migrations/0002_alter_domain_unique.py -> build/lib/django/contrib/sites/migrations
2025-04-22 20:54:03,045 root INFO creating build/lib/django/contrib/sitemaps/management
2025-04-22 20:54:03,045 root INFO copying django/contrib/sitemaps/management/__init__.py -> build/lib/django/contrib/sitemaps/management
2025-04-22 20:54:03,046 root INFO creating build/lib/django/contrib/sitemaps/management/commands
2025-04-22 20:54:03,046 root INFO copying django/contrib/sitemaps/management/commands/__init__.py -> build/lib/django/contrib/sitemaps/management/commands
2025-04-22 20:54:03,046 root INFO copying django/contrib/sitemaps/management/commands/ping_google.py -> build/lib/django/contrib/sitemaps/management/commands
2025-04-22 20:54:03,046 root INFO creating build/lib/django/contrib/flatpages/migrations
2025-04-22 20:54:03,046 root INFO copying django/contrib/flatpages/migrations/__init__.py -> build/lib/django/contrib/flatpages/migrations
2025-04-22 20:54:03,046 root INFO copying django/contrib/flatpages/migrations/0001_initial.py -> build/lib/django/contrib/flatpages/migrations
2025-04-22 20:54:03,047 root INFO creating build/lib/django/contrib/flatpages/templatetags
2025-04-22 20:54:03,047 root INFO copying django/contrib/flatpages/templatetags/__init__.py -> build/lib/django/contrib/flatpages/templatetags
2025-04-22 20:54:03,047 root INFO copying django/contrib/flatpages/templatetags/flatpages.py -> build/lib/django/contrib/flatpages/templatetags
2025-04-22 20:54:03,047 root INFO creating build/lib/django/contrib/staticfiles/management
2025-04-22 20:54:03,047 root INFO copying django/contrib/staticfiles/management/__init__.py -> build/lib/django/contrib/staticfiles/management
2025-04-22 20:54:03,047 root INFO creating build/lib/django/contrib/staticfiles/management/commands
2025-04-22 20:54:03,048 root INFO copying django/contrib/staticfiles/management/commands/__init__.py -> build/lib/django/contrib/staticfiles/management/commands
2025-04-22 20:54:03,048 root INFO copying django/contrib/staticfiles/management/commands/collectstatic.py -> build/lib/django/contrib/staticfiles/management/commands
2025-04-22 20:54:03,048 root INFO copying django/contrib/staticfiles/management/commands/findstatic.py -> build/lib/django/contrib/staticfiles/management/commands
2025-04-22 20:54:03,048 root INFO copying django/contrib/staticfiles/management/commands/runserver.py -> build/lib/django/contrib/staticfiles/management/commands
2025-04-22 20:54:03,048 root INFO creating build/lib/django/contrib/sessions/migrations
2025-04-22 20:54:03,049 root INFO copying django/contrib/sessions/migrations/__init__.py -> build/lib/django/contrib/sessions/migrations
2025-04-22 20:54:03,049 root INFO copying django/contrib/sessions/migrations/0001_initial.py -> build/lib/django/contrib/sessions/migrations
2025-04-22 20:54:03,049 root INFO creating build/lib/django/contrib/sessions/management
2025-04-22 20:54:03,049 root INFO copying django/contrib/sessions/management/__init__.py -> build/lib/django/contrib/sessions/management
2025-04-22 20:54:03,049 root INFO creating build/lib/django/contrib/sessions/backends
2025-04-22 20:54:03,049 root INFO copying django/contrib/sessions/backends/__init__.py -> build/lib/django/contrib/sessions/backends
2025-04-22 20:54:03,050 root INFO copying django/contrib/sessions/backends/cache.py -> build/lib/django/contrib/sessions/backends
2025-04-22 20:54:03,050 root INFO copying django/contrib/sessions/backends/db.py -> build/lib/django/contrib/sessions/backends
2025-04-22 20:54:03,050 root INFO copying django/contrib/sessions/backends/cached_db.py -> build/lib/django/contrib/sessions/backends
2025-04-22 20:54:03,050 root INFO copying django/contrib/sessions/backends/signed_cookies.py -> build/lib/django/contrib/sessions/backends
2025-04-22 20:54:03,050 root INFO copying django/contrib/sessions/backends/base.py -> build/lib/django/contrib/sessions/backends
2025-04-22 20:54:03,050 root INFO copying django/contrib/sessions/backends/file.py -> build/lib/django/contrib/sessions/backends
2025-04-22 20:54:03,051 root INFO creating build/lib/django/contrib/sessions/management/commands
2025-04-22 20:54:03,051 root INFO copying django/contrib/sessions/management/commands/__init__.py -> build/lib/django/contrib/sessions/management/commands
2025-04-22 20:54:03,051 root INFO copying django/contrib/sessions/management/commands/clearsessions.py -> build/lib/django/contrib/sessions/management/commands
2025-04-22 20:54:03,051 root INFO creating build/lib/django/contrib/postgres/aggregates
2025-04-22 20:54:03,051 root INFO copying django/contrib/postgres/aggregates/__init__.py -> build/lib/django/contrib/postgres/aggregates
2025-04-22 20:54:03,051 root INFO copying django/contrib/postgres/aggregates/statistics.py -> build/lib/django/contrib/postgres/aggregates
2025-04-22 20:54:03,051 root INFO copying django/contrib/postgres/aggregates/general.py -> build/lib/django/contrib/postgres/aggregates
2025-04-22 20:54:03,052 root INFO copying django/contrib/postgres/aggregates/mixins.py -> build/lib/django/contrib/postgres/aggregates
2025-04-22 20:54:03,052 root INFO creating build/lib/django/contrib/postgres/fields
2025-04-22 20:54:03,052 root INFO copying django/contrib/postgres/fields/__init__.py -> build/lib/django/contrib/postgres/fields
2025-04-22 20:54:03,052 root INFO copying django/contrib/postgres/fields/hstore.py -> build/lib/django/contrib/postgres/fields
2025-04-22 20:54:03,052 root INFO copying django/contrib/postgres/fields/citext.py -> build/lib/django/contrib/postgres/fields
2025-04-22 20:54:03,053 root INFO copying django/contrib/postgres/fields/jsonb.py -> build/lib/django/contrib/postgres/fields
2025-04-22 20:54:03,053 root INFO copying django/contrib/postgres/fields/utils.py -> build/lib/django/contrib/postgres/fields
2025-04-22 20:54:03,053 root INFO copying django/contrib/postgres/fields/ranges.py -> build/lib/django/contrib/postgres/fields
2025-04-22 20:54:03,053 root INFO copying django/contrib/postgres/fields/array.py -> build/lib/django/contrib/postgres/fields
2025-04-22 20:54:03,053 root INFO creating build/lib/django/contrib/postgres/forms
2025-04-22 20:54:03,053 root INFO copying django/contrib/postgres/forms/__init__.py -> build/lib/django/contrib/postgres/forms
2025-04-22 20:54:03,054 root INFO copying django/contrib/postgres/forms/hstore.py -> build/lib/django/contrib/postgres/forms
2025-04-22 20:54:03,054 root INFO copying django/contrib/postgres/forms/ranges.py -> build/lib/django/contrib/postgres/forms
2025-04-22 20:54:03,054 root INFO copying django/contrib/postgres/forms/array.py -> build/lib/django/contrib/postgres/forms
2025-04-22 20:54:03,054 root INFO creating build/lib/django/contrib/gis/db
2025-04-22 20:54:03,054 root INFO copying django/contrib/gis/db/__init__.py -> build/lib/django/contrib/gis/db
2025-04-22 20:54:03,054 root INFO creating build/lib/django/contrib/gis/sitemaps
2025-04-22 20:54:03,054 root INFO copying django/contrib/gis/sitemaps/__init__.py -> build/lib/django/contrib/gis/sitemaps
2025-04-22 20:54:03,055 root INFO copying django/contrib/gis/sitemaps/views.py -> build/lib/django/contrib/gis/sitemaps
2025-04-22 20:54:03,055 root INFO copying django/contrib/gis/sitemaps/kml.py -> build/lib/django/contrib/gis/sitemaps
2025-04-22 20:54:03,055 root INFO creating build/lib/django/contrib/gis/utils
2025-04-22 20:54:03,055 root INFO copying django/contrib/gis/utils/__init__.py -> build/lib/django/contrib/gis/utils
2025-04-22 20:54:03,055 root INFO copying django/contrib/gis/utils/layermapping.py -> build/lib/django/contrib/gis/utils
2025-04-22 20:54:03,056 root INFO copying django/contrib/gis/utils/srs.py -> build/lib/django/contrib/gis/utils
2025-04-22 20:54:03,056 root INFO copying django/contrib/gis/utils/ogrinfo.py -> build/lib/django/contrib/gis/utils
2025-04-22 20:54:03,056 root INFO copying django/contrib/gis/utils/ogrinspect.py -> build/lib/django/contrib/gis/utils
2025-04-22 20:54:03,056 root INFO creating build/lib/django/contrib/gis/geoip2
2025-04-22 20:54:03,056 root INFO copying django/contrib/gis/geoip2/__init__.py -> build/lib/django/contrib/gis/geoip2
2025-04-22 20:54:03,056 root INFO copying django/contrib/gis/geoip2/resources.py -> build/lib/django/contrib/gis/geoip2
2025-04-22 20:54:03,057 root INFO copying django/contrib/gis/geoip2/base.py -> build/lib/django/contrib/gis/geoip2
2025-04-22 20:54:03,057 root INFO creating build/lib/django/contrib/gis/management
2025-04-22 20:54:03,057 root INFO copying django/contrib/gis/management/__init__.py -> build/lib/django/contrib/gis/management
2025-04-22 20:54:03,057 root INFO creating build/lib/django/contrib/gis/serializers
2025-04-22 20:54:03,057 root INFO copying django/contrib/gis/serializers/__init__.py -> build/lib/django/contrib/gis/serializers
2025-04-22 20:54:03,057 root INFO copying django/contrib/gis/serializers/geojson.py -> build/lib/django/contrib/gis/serializers
2025-04-22 20:54:03,058 root INFO creating build/lib/django/contrib/gis/admin
2025-04-22 20:54:03,058 root INFO copying django/contrib/gis/admin/__init__.py -> build/lib/django/contrib/gis/admin
2025-04-22 20:54:03,058 root INFO copying django/contrib/gis/admin/options.py -> build/lib/django/contrib/gis/admin
2025-04-22 20:54:03,058 root INFO copying django/contrib/gis/admin/widgets.py -> build/lib/django/contrib/gis/admin
2025-04-22 20:54:03,058 root INFO creating build/lib/django/contrib/gis/geos
2025-04-22 20:54:03,058 root INFO copying django/contrib/gis/geos/__init__.py -> build/lib/django/contrib/gis/geos
2025-04-22 20:54:03,059 root INFO copying django/contrib/gis/geos/libgeos.py -> build/lib/django/contrib/gis/geos
2025-04-22 20:54:03,059 root INFO copying django/contrib/gis/geos/collections.py -> build/lib/django/contrib/gis/geos
2025-04-22 20:54:03,059 root INFO copying django/contrib/gis/geos/linestring.py -> build/lib/django/contrib/gis/geos
2025-04-22 20:54:03,059 root INFO copying django/contrib/gis/geos/prepared.py -> build/lib/django/contrib/gis/geos
2025-04-22 20:54:03,059 root INFO copying django/contrib/gis/geos/io.py -> build/lib/django/contrib/gis/geos
2025-04-22 20:54:03,059 root INFO copying django/contrib/gis/geos/mutable_list.py -> build/lib/django/contrib/gis/geos
2025-04-22 20:54:03,060 root INFO copying django/contrib/gis/geos/point.py -> build/lib/django/contrib/gis/geos
2025-04-22 20:54:03,060 root INFO copying django/contrib/gis/geos/geometry.py -> build/lib/django/contrib/gis/geos
2025-04-22 20:54:03,060 root INFO copying django/contrib/gis/geos/polygon.py -> build/lib/django/contrib/gis/geos
2025-04-22 20:54:03,060 root INFO copying django/contrib/gis/geos/error.py -> build/lib/django/contrib/gis/geos
2025-04-22 20:54:03,060 root INFO copying django/contrib/gis/geos/factory.py -> build/lib/django/contrib/gis/geos
2025-04-22 20:54:03,060 root INFO copying django/contrib/gis/geos/base.py -> build/lib/django/contrib/gis/geos
2025-04-22 20:54:03,060 root INFO copying django/contrib/gis/geos/coordseq.py -> build/lib/django/contrib/gis/geos
2025-04-22 20:54:03,061 root INFO creating build/lib/django/contrib/gis/gdal
2025-04-22 20:54:03,061 root INFO copying django/contrib/gis/gdal/__init__.py -> build/lib/django/contrib/gis/gdal
2025-04-22 20:54:03,061 root INFO copying django/contrib/gis/gdal/geomtype.py -> build/lib/django/contrib/gis/gdal
2025-04-22 20:54:03,061 root INFO copying django/contrib/gis/gdal/field.py -> build/lib/django/contrib/gis/gdal
2025-04-22 20:54:03,061 root INFO copying django/contrib/gis/gdal/geometries.py -> build/lib/django/contrib/gis/gdal
2025-04-22 20:54:03,062 root INFO copying django/contrib/gis/gdal/feature.py -> build/lib/django/contrib/gis/gdal
2025-04-22 20:54:03,062 root INFO copying django/contrib/gis/gdal/envelope.py -> build/lib/django/contrib/gis/gdal
2025-04-22 20:54:03,062 root INFO copying django/contrib/gis/gdal/libgdal.py -> build/lib/django/contrib/gis/gdal
2025-04-22 20:54:03,062 root INFO copying django/contrib/gis/gdal/srs.py -> build/lib/django/contrib/gis/gdal
2025-04-22 20:54:03,062 root INFO copying django/contrib/gis/gdal/error.py -> build/lib/django/contrib/gis/gdal
2025-04-22 20:54:03,062 root INFO copying django/contrib/gis/gdal/datasource.py -> build/lib/django/contrib/gis/gdal
2025-04-22 20:54:03,063 root INFO copying django/contrib/gis/gdal/driver.py -> build/lib/django/contrib/gis/gdal
2025-04-22 20:54:03,063 root INFO copying django/contrib/gis/gdal/layer.py -> build/lib/django/contrib/gis/gdal
2025-04-22 20:54:03,063 root INFO copying django/contrib/gis/gdal/base.py -> build/lib/django/contrib/gis/gdal
2025-04-22 20:54:03,063 root INFO creating build/lib/django/contrib/gis/forms
2025-04-22 20:54:03,063 root INFO copying django/contrib/gis/forms/__init__.py -> build/lib/django/contrib/gis/forms
2025-04-22 20:54:03,063 root INFO copying django/contrib/gis/forms/widgets.py -> build/lib/django/contrib/gis/forms
2025-04-22 20:54:03,064 root INFO copying django/contrib/gis/forms/fields.py -> build/lib/django/contrib/gis/forms
2025-04-22 20:54:03,064 root INFO creating build/lib/django/contrib/gis/db/models
2025-04-22 20:54:03,064 root INFO copying django/contrib/gis/db/models/__init__.py -> build/lib/django/contrib/gis/db/models
2025-04-22 20:54:03,064 root INFO copying django/contrib/gis/db/models/functions.py -> build/lib/django/contrib/gis/db/models
2025-04-22 20:54:03,064 root INFO copying django/contrib/gis/db/models/lookups.py -> build/lib/django/contrib/gis/db/models
2025-04-22 20:54:03,065 root INFO copying django/contrib/gis/db/models/fields.py -> build/lib/django/contrib/gis/db/models
2025-04-22 20:54:03,065 root INFO copying django/contrib/gis/db/models/aggregates.py -> build/lib/django/contrib/gis/db/models
2025-04-22 20:54:03,065 root INFO copying django/contrib/gis/db/models/proxy.py -> build/lib/django/contrib/gis/db/models
2025-04-22 20:54:03,065 root INFO creating build/lib/django/contrib/gis/db/backends
2025-04-22 20:54:03,065 root INFO copying django/contrib/gis/db/backends/__init__.py -> build/lib/django/contrib/gis/db/backends
2025-04-22 20:54:03,065 root INFO copying django/contrib/gis/db/backends/utils.py -> build/lib/django/contrib/gis/db/backends
2025-04-22 20:54:03,066 root INFO creating build/lib/django/contrib/gis/db/models/sql
2025-04-22 20:54:03,066 root INFO copying django/contrib/gis/db/models/sql/__init__.py -> build/lib/django/contrib/gis/db/models/sql
2025-04-22 20:54:03,066 root INFO copying django/contrib/gis/db/models/sql/conversion.py -> build/lib/django/contrib/gis/db/models/sql
2025-04-22 20:54:03,066 root INFO creating build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:03,066 root INFO copying django/contrib/gis/db/backends/spatialite/__init__.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:03,066 root INFO copying django/contrib/gis/db/backends/spatialite/schema.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:03,067 root INFO copying django/contrib/gis/db/backends/spatialite/features.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:03,067 root INFO copying django/contrib/gis/db/backends/spatialite/operations.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:03,067 root INFO copying django/contrib/gis/db/backends/spatialite/models.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:03,067 root INFO copying django/contrib/gis/db/backends/spatialite/introspection.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:03,067 root INFO copying django/contrib/gis/db/backends/spatialite/base.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:03,067 root INFO copying django/contrib/gis/db/backends/spatialite/client.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:03,068 root INFO copying django/contrib/gis/db/backends/spatialite/adapter.py -> build/lib/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:03,068 root INFO creating build/lib/django/contrib/gis/db/backends/base
2025-04-22 20:54:03,068 root INFO copying django/contrib/gis/db/backends/base/__init__.py -> build/lib/django/contrib/gis/db/backends/base
2025-04-22 20:54:03,068 root INFO copying django/contrib/gis/db/backends/base/features.py -> build/lib/django/contrib/gis/db/backends/base
2025-04-22 20:54:03,068 root INFO copying django/contrib/gis/db/backends/base/operations.py -> build/lib/django/contrib/gis/db/backends/base
2025-04-22 20:54:03,068 root INFO copying django/contrib/gis/db/backends/base/models.py -> build/lib/django/contrib/gis/db/backends/base
2025-04-22 20:54:03,069 root INFO copying django/contrib/gis/db/backends/base/adapter.py -> build/lib/django/contrib/gis/db/backends/base
2025-04-22 20:54:03,069 root INFO creating build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:03,069 root INFO copying django/contrib/gis/db/backends/postgis/__init__.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:03,069 root INFO copying django/contrib/gis/db/backends/postgis/schema.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:03,069 root INFO copying django/contrib/gis/db/backends/postgis/features.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:03,069 root INFO copying django/contrib/gis/db/backends/postgis/operations.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:03,070 root INFO copying django/contrib/gis/db/backends/postgis/models.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:03,070 root INFO copying django/contrib/gis/db/backends/postgis/introspection.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:03,070 root INFO copying django/contrib/gis/db/backends/postgis/base.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:03,070 root INFO copying django/contrib/gis/db/backends/postgis/const.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:03,070 root INFO copying django/contrib/gis/db/backends/postgis/pgraster.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:03,070 root INFO copying django/contrib/gis/db/backends/postgis/adapter.py -> build/lib/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:03,071 root INFO creating build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:03,071 root INFO copying django/contrib/gis/db/backends/oracle/__init__.py -> build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:03,071 root INFO copying django/contrib/gis/db/backends/oracle/schema.py -> build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:03,071 root INFO copying django/contrib/gis/db/backends/oracle/features.py -> build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:03,071 root INFO copying django/contrib/gis/db/backends/oracle/operations.py -> build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:03,071 root INFO copying django/contrib/gis/db/backends/oracle/models.py -> build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:03,072 root INFO copying django/contrib/gis/db/backends/oracle/introspection.py -> build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:03,072 root INFO copying django/contrib/gis/db/backends/oracle/base.py -> build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:03,072 root INFO copying django/contrib/gis/db/backends/oracle/adapter.py -> build/lib/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:03,072 root INFO creating build/lib/django/contrib/gis/db/backends/mysql
2025-04-22 20:54:03,072 root INFO copying django/contrib/gis/db/backends/mysql/__init__.py -> build/lib/django/contrib/gis/db/backends/mysql
2025-04-22 20:54:03,072 root INFO copying django/contrib/gis/db/backends/mysql/schema.py -> build/lib/django/contrib/gis/db/backends/mysql
2025-04-22 20:54:03,073 root INFO copying django/contrib/gis/db/backends/mysql/features.py -> build/lib/django/contrib/gis/db/backends/mysql
2025-04-22 20:54:03,073 root INFO copying django/contrib/gis/db/backends/mysql/operations.py -> build/lib/django/contrib/gis/db/backends/mysql
2025-04-22 20:54:03,073 root INFO copying django/contrib/gis/db/backends/mysql/introspection.py -> build/lib/django/contrib/gis/db/backends/mysql
2025-04-22 20:54:03,073 root INFO copying django/contrib/gis/db/backends/mysql/base.py -> build/lib/django/contrib/gis/db/backends/mysql
2025-04-22 20:54:03,073 root INFO creating build/lib/django/contrib/gis/management/commands
2025-04-22 20:54:03,073 root INFO copying django/contrib/gis/management/commands/__init__.py -> build/lib/django/contrib/gis/management/commands
2025-04-22 20:54:03,074 root INFO copying django/contrib/gis/management/commands/inspectdb.py -> build/lib/django/contrib/gis/management/commands
2025-04-22 20:54:03,074 root INFO copying django/contrib/gis/management/commands/ogrinspect.py -> build/lib/django/contrib/gis/management/commands
2025-04-22 20:54:03,074 root INFO creating build/lib/django/contrib/gis/geos/prototypes
2025-04-22 20:54:03,074 root INFO copying django/contrib/gis/geos/prototypes/__init__.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 20:54:03,074 root INFO copying django/contrib/gis/geos/prototypes/prepared.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 20:54:03,074 root INFO copying django/contrib/gis/geos/prototypes/io.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 20:54:03,075 root INFO copying django/contrib/gis/geos/prototypes/threadsafe.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 20:54:03,075 root INFO copying django/contrib/gis/geos/prototypes/errcheck.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 20:54:03,075 root INFO copying django/contrib/gis/geos/prototypes/misc.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 20:54:03,075 root INFO copying django/contrib/gis/geos/prototypes/predicates.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 20:54:03,075 root INFO copying django/contrib/gis/geos/prototypes/topology.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 20:54:03,075 root INFO copying django/contrib/gis/geos/prototypes/geom.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 20:54:03,076 root INFO copying django/contrib/gis/geos/prototypes/coordseq.py -> build/lib/django/contrib/gis/geos/prototypes
2025-04-22 20:54:03,076 root INFO creating build/lib/django/contrib/gis/gdal/raster
2025-04-22 20:54:03,076 root INFO copying django/contrib/gis/gdal/raster/__init__.py -> build/lib/django/contrib/gis/gdal/raster
2025-04-22 20:54:03,076 root INFO copying django/contrib/gis/gdal/raster/source.py -> build/lib/django/contrib/gis/gdal/raster
2025-04-22 20:54:03,076 root INFO copying django/contrib/gis/gdal/raster/band.py -> build/lib/django/contrib/gis/gdal/raster
2025-04-22 20:54:03,077 root INFO copying django/contrib/gis/gdal/raster/base.py -> build/lib/django/contrib/gis/gdal/raster
2025-04-22 20:54:03,077 root INFO copying django/contrib/gis/gdal/raster/const.py -> build/lib/django/contrib/gis/gdal/raster
2025-04-22 20:54:03,077 root INFO creating build/lib/django/contrib/gis/gdal/prototypes
2025-04-22 20:54:03,077 root INFO copying django/contrib/gis/gdal/prototypes/__init__.py -> build/lib/django/contrib/gis/gdal/prototypes
2025-04-22 20:54:03,077 root INFO copying django/contrib/gis/gdal/prototypes/generation.py -> build/lib/django/contrib/gis/gdal/prototypes
2025-04-22 20:54:03,077 root INFO copying django/contrib/gis/gdal/prototypes/ds.py -> build/lib/django/contrib/gis/gdal/prototypes
2025-04-22 20:54:03,078 root INFO copying django/contrib/gis/gdal/prototypes/raster.py -> build/lib/django/contrib/gis/gdal/prototypes
2025-04-22 20:54:03,078 root INFO copying django/contrib/gis/gdal/prototypes/srs.py -> build/lib/django/contrib/gis/gdal/prototypes
2025-04-22 20:54:03,078 root INFO copying django/contrib/gis/gdal/prototypes/errcheck.py -> build/lib/django/contrib/gis/gdal/prototypes
2025-04-22 20:54:03,078 root INFO copying django/contrib/gis/gdal/prototypes/geom.py -> build/lib/django/contrib/gis/gdal/prototypes
2025-04-22 20:54:03,078 root INFO creating build/lib/django/contrib/admin/views
2025-04-22 20:54:03,078 root INFO copying django/contrib/admin/views/__init__.py -> build/lib/django/contrib/admin/views
2025-04-22 20:54:03,079 root INFO copying django/contrib/admin/views/decorators.py -> build/lib/django/contrib/admin/views
2025-04-22 20:54:03,079 root INFO copying django/contrib/admin/views/autocomplete.py -> build/lib/django/contrib/admin/views
2025-04-22 20:54:03,079 root INFO copying django/contrib/admin/views/main.py -> build/lib/django/contrib/admin/views
2025-04-22 20:54:03,079 root INFO creating build/lib/django/contrib/admin/migrations
2025-04-22 20:54:03,079 root INFO copying django/contrib/admin/migrations/__init__.py -> build/lib/django/contrib/admin/migrations
2025-04-22 20:54:03,079 root INFO copying django/contrib/admin/migrations/0002_logentry_remove_auto_add.py -> build/lib/django/contrib/admin/migrations
2025-04-22 20:54:03,080 root INFO copying django/contrib/admin/migrations/0001_initial.py -> build/lib/django/contrib/admin/migrations
2025-04-22 20:54:03,080 root INFO copying django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py -> build/lib/django/contrib/admin/migrations
2025-04-22 20:54:03,080 root INFO creating build/lib/django/contrib/admin/templatetags
2025-04-22 20:54:03,080 root INFO copying django/contrib/admin/templatetags/__init__.py -> build/lib/django/contrib/admin/templatetags
2025-04-22 20:54:03,080 root INFO copying django/contrib/admin/templatetags/log.py -> build/lib/django/contrib/admin/templatetags
2025-04-22 20:54:03,080 root INFO copying django/contrib/admin/templatetags/admin_urls.py -> build/lib/django/contrib/admin/templatetags
2025-04-22 20:54:03,081 root INFO copying django/contrib/admin/templatetags/admin_modify.py -> build/lib/django/contrib/admin/templatetags
2025-04-22 20:54:03,081 root INFO copying django/contrib/admin/templatetags/admin_list.py -> build/lib/django/contrib/admin/templatetags
2025-04-22 20:54:03,081 root INFO copying django/contrib/admin/templatetags/base.py -> build/lib/django/contrib/admin/templatetags
2025-04-22 20:54:03,081 root INFO creating build/lib/django/contrib/humanize/templatetags
2025-04-22 20:54:03,081 root INFO copying django/contrib/humanize/templatetags/__init__.py -> build/lib/django/contrib/humanize/templatetags
2025-04-22 20:54:03,081 root INFO copying django/contrib/humanize/templatetags/humanize.py -> build/lib/django/contrib/humanize/templatetags
2025-04-22 20:54:03,082 root INFO running egg_info
2025-04-22 20:54:03,083 root INFO writing Django.egg-info/PKG-INFO
2025-04-22 20:54:03,085 root INFO writing dependency_links to Django.egg-info/dependency_links.txt
2025-04-22 20:54:03,085 root INFO writing entry points to Django.egg-info/entry_points.txt
2025-04-22 20:54:03,086 root INFO writing requirements to Django.egg-info/requires.txt
2025-04-22 20:54:03,086 root INFO writing top-level names to Django.egg-info/top_level.txt
2025-04-22 20:54:03,110 root INFO reading manifest file 'Django.egg-info/SOURCES.txt'
2025-04-22 20:54:03,142 root INFO reading manifest template 'MANIFEST.in'
2025-04-22 20:54:03,259 root WARNING warning: no previously-included files matching '__pycache__' found anywhere in distribution
2025-04-22 20:54:03,268 root INFO adding license file 'LICENSE'
2025-04-22 20:54:03,268 root INFO adding license file 'LICENSE.python'
2025-04-22 20:54:03,268 root INFO adding license file 'AUTHORS'
2025-04-22 20:54:03,372 root INFO writing manifest file 'Django.egg-info/SOURCES.txt'
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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 20:54:03,543 root INFO creating build/lib/django/views/templates
2025-04-22 20:54:03,544 root INFO copying django/views/templates/default_urlconf.html -> build/lib/django/views/templates
2025-04-22 20:54:03,544 root INFO copying django/views/templates/technical_404.html -> build/lib/django/views/templates
2025-04-22 20:54:03,544 root INFO copying django/views/templates/technical_500.html -> build/lib/django/views/templates
2025-04-22 20:54:03,544 root INFO copying django/views/templates/technical_500.txt -> build/lib/django/views/templates
2025-04-22 20:54:03,544 root INFO copying django/dispatch/license.txt -> build/lib/django/dispatch
2025-04-22 20:54:03,545 root INFO creating build/lib/django/conf/app_template
2025-04-22 20:54:03,545 root INFO copying django/conf/app_template/__init__.py-tpl -> build/lib/django/conf/app_template
2025-04-22 20:54:03,545 root INFO copying django/conf/app_template/admin.py-tpl -> build/lib/django/conf/app_template
2025-04-22 20:54:03,545 root INFO copying django/conf/app_template/apps.py-tpl -> build/lib/django/conf/app_template
2025-04-22 20:54:03,545 root INFO copying django/conf/app_template/models.py-tpl -> build/lib/django/conf/app_template
2025-04-22 20:54:03,545 root INFO copying django/conf/app_template/tests.py-tpl -> build/lib/django/conf/app_template
2025-04-22 20:54:03,545 root INFO copying django/conf/app_template/views.py-tpl -> build/lib/django/conf/app_template
2025-04-22 20:54:03,546 root INFO creating build/lib/django/conf/app_template/migrations
2025-04-22 20:54:03,546 root INFO copying django/conf/app_template/migrations/__init__.py-tpl -> build/lib/django/conf/app_template/migrations
2025-04-22 20:54:03,546 root INFO creating build/lib/django/conf/project_template
2025-04-22 20:54:03,546 root INFO copying django/conf/project_template/manage.py-tpl -> build/lib/django/conf/project_template
2025-04-22 20:54:03,546 root INFO creating build/lib/django/conf/project_template/project_name
2025-04-22 20:54:03,546 root INFO copying django/conf/project_template/project_name/__init__.py-tpl -> build/lib/django/conf/project_template/project_name
2025-04-22 20:54:03,546 root INFO copying django/conf/project_template/project_name/asgi.py-tpl -> build/lib/django/conf/project_template/project_name
2025-04-22 20:54:03,547 root INFO copying django/conf/project_template/project_name/settings.py-tpl -> build/lib/django/conf/project_template/project_name
2025-04-22 20:54:03,547 root INFO copying django/conf/project_template/project_name/urls.py-tpl -> build/lib/django/conf/project_template/project_name
2025-04-22 20:54:03,547 root INFO copying django/conf/project_template/project_name/wsgi.py-tpl -> build/lib/django/conf/project_template/project_name
2025-04-22 20:54:03,547 root INFO creating build/lib/django/forms/jinja2
2025-04-22 20:54:03,547 root INFO creating build/lib/django/forms/jinja2/django
2025-04-22 20:54:03,547 root INFO creating build/lib/django/forms/jinja2/django/forms
2025-04-22 20:54:03,547 root INFO copying django/forms/jinja2/django/forms/attrs.html -> build/lib/django/forms/jinja2/django/forms
2025-04-22 20:54:03,547 root INFO copying django/forms/jinja2/django/forms/default.html -> build/lib/django/forms/jinja2/django/forms
2025-04-22 20:54:03,548 root INFO copying django/forms/jinja2/django/forms/div.html -> build/lib/django/forms/jinja2/django/forms
2025-04-22 20:54:03,548 root INFO copying django/forms/jinja2/django/forms/label.html -> build/lib/django/forms/jinja2/django/forms
2025-04-22 20:54:03,548 root INFO copying django/forms/jinja2/django/forms/p.html -> build/lib/django/forms/jinja2/django/forms
2025-04-22 20:54:03,548 root INFO copying django/forms/jinja2/django/forms/table.html -> build/lib/django/forms/jinja2/django/forms
2025-04-22 20:54:03,548 root INFO copying django/forms/jinja2/django/forms/ul.html -> build/lib/django/forms/jinja2/django/forms
2025-04-22 20:54:03,548 root INFO creating build/lib/django/forms/jinja2/django/forms/errors
2025-04-22 20:54:03,548 root INFO creating build/lib/django/forms/jinja2/django/forms/errors/dict
2025-04-22 20:54:03,549 root INFO copying django/forms/jinja2/django/forms/errors/dict/default.html -> build/lib/django/forms/jinja2/django/forms/errors/dict
2025-04-22 20:54:03,549 root INFO copying django/forms/jinja2/django/forms/errors/dict/text.txt -> build/lib/django/forms/jinja2/django/forms/errors/dict
2025-04-22 20:54:03,549 root INFO copying django/forms/jinja2/django/forms/errors/dict/ul.html -> build/lib/django/forms/jinja2/django/forms/errors/dict
2025-04-22 20:54:03,549 root INFO creating build/lib/django/forms/jinja2/django/forms/errors/list
2025-04-22 20:54:03,549 root INFO copying django/forms/jinja2/django/forms/errors/list/default.html -> build/lib/django/forms/jinja2/django/forms/errors/list
2025-04-22 20:54:03,549 root INFO copying django/forms/jinja2/django/forms/errors/list/text.txt -> build/lib/django/forms/jinja2/django/forms/errors/list
2025-04-22 20:54:03,549 root INFO copying django/forms/jinja2/django/forms/errors/list/ul.html -> build/lib/django/forms/jinja2/django/forms/errors/list
2025-04-22 20:54:03,550 root INFO creating build/lib/django/forms/jinja2/django/forms/formsets
2025-04-22 20:54:03,550 root INFO copying django/forms/jinja2/django/forms/formsets/default.html -> build/lib/django/forms/jinja2/django/forms/formsets
2025-04-22 20:54:03,550 root INFO copying django/forms/jinja2/django/forms/formsets/div.html -> build/lib/django/forms/jinja2/django/forms/formsets
2025-04-22 20:54:03,550 root INFO copying django/forms/jinja2/django/forms/formsets/p.html -> build/lib/django/forms/jinja2/django/forms/formsets
2025-04-22 20:54:03,550 root INFO copying django/forms/jinja2/django/forms/formsets/table.html -> build/lib/django/forms/jinja2/django/forms/formsets
2025-04-22 20:54:03,550 root INFO copying django/forms/jinja2/django/forms/formsets/ul.html -> build/lib/django/forms/jinja2/django/forms/formsets
2025-04-22 20:54:03,550 root INFO creating build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,551 root INFO copying django/forms/jinja2/django/forms/widgets/attrs.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,551 root INFO copying django/forms/jinja2/django/forms/widgets/checkbox.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,551 root INFO copying django/forms/jinja2/django/forms/widgets/checkbox_option.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,551 root INFO copying django/forms/jinja2/django/forms/widgets/checkbox_select.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,551 root INFO copying django/forms/jinja2/django/forms/widgets/clearable_file_input.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,551 root INFO copying django/forms/jinja2/django/forms/widgets/date.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,551 root INFO copying django/forms/jinja2/django/forms/widgets/datetime.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,552 root INFO copying django/forms/jinja2/django/forms/widgets/email.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,552 root INFO copying django/forms/jinja2/django/forms/widgets/file.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,552 root INFO copying django/forms/jinja2/django/forms/widgets/hidden.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,552 root INFO copying django/forms/jinja2/django/forms/widgets/input.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,552 root INFO copying django/forms/jinja2/django/forms/widgets/input_option.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,552 root INFO copying django/forms/jinja2/django/forms/widgets/multiple_hidden.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,553 root INFO copying django/forms/jinja2/django/forms/widgets/multiple_input.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,553 root INFO copying django/forms/jinja2/django/forms/widgets/multiwidget.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,553 root INFO copying django/forms/jinja2/django/forms/widgets/number.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,553 root INFO copying django/forms/jinja2/django/forms/widgets/password.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,553 root INFO copying django/forms/jinja2/django/forms/widgets/radio.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,553 root INFO copying django/forms/jinja2/django/forms/widgets/radio_option.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,553 root INFO copying django/forms/jinja2/django/forms/widgets/select.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,554 root INFO copying django/forms/jinja2/django/forms/widgets/select_date.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,554 root INFO copying django/forms/jinja2/django/forms/widgets/select_option.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,554 root INFO copying django/forms/jinja2/django/forms/widgets/splitdatetime.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,554 root INFO copying django/forms/jinja2/django/forms/widgets/splithiddendatetime.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,554 root INFO copying django/forms/jinja2/django/forms/widgets/text.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,554 root INFO copying django/forms/jinja2/django/forms/widgets/textarea.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,554 root INFO copying django/forms/jinja2/django/forms/widgets/time.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,555 root INFO copying django/forms/jinja2/django/forms/widgets/url.html -> build/lib/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:03,555 root INFO creating build/lib/django/forms/templates
2025-04-22 20:54:03,555 root INFO creating build/lib/django/forms/templates/django
2025-04-22 20:54:03,555 root INFO creating build/lib/django/forms/templates/django/forms
2025-04-22 20:54:03,555 root INFO copying django/forms/templates/django/forms/attrs.html -> build/lib/django/forms/templates/django/forms
2025-04-22 20:54:03,555 root INFO copying django/forms/templates/django/forms/default.html -> build/lib/django/forms/templates/django/forms
2025-04-22 20:54:03,555 root INFO copying django/forms/templates/django/forms/div.html -> build/lib/django/forms/templates/django/forms
2025-04-22 20:54:03,556 root INFO copying django/forms/templates/django/forms/label.html -> build/lib/django/forms/templates/django/forms
2025-04-22 20:54:03,556 root INFO copying django/forms/templates/django/forms/p.html -> build/lib/django/forms/templates/django/forms
2025-04-22 20:54:03,556 root INFO copying django/forms/templates/django/forms/table.html -> build/lib/django/forms/templates/django/forms
2025-04-22 20:54:03,556 root INFO copying django/forms/templates/django/forms/ul.html -> build/lib/django/forms/templates/django/forms
2025-04-22 20:54:03,556 root INFO creating build/lib/django/forms/templates/django/forms/errors
2025-04-22 20:54:03,556 root INFO creating build/lib/django/forms/templates/django/forms/errors/dict
2025-04-22 20:54:03,556 root INFO copying django/forms/templates/django/forms/errors/dict/default.html -> build/lib/django/forms/templates/django/forms/errors/dict
2025-04-22 20:54:03,556 root INFO copying django/forms/templates/django/forms/errors/dict/text.txt -> build/lib/django/forms/templates/django/forms/errors/dict
2025-04-22 20:54:03,557 root INFO copying django/forms/templates/django/forms/errors/dict/ul.html -> build/lib/django/forms/templates/django/forms/errors/dict
2025-04-22 20:54:03,557 root INFO creating build/lib/django/forms/templates/django/forms/errors/list
2025-04-22 20:54:03,557 root INFO copying django/forms/templates/django/forms/errors/list/default.html -> build/lib/django/forms/templates/django/forms/errors/list
2025-04-22 20:54:03,557 root INFO copying django/forms/templates/django/forms/errors/list/text.txt -> build/lib/django/forms/templates/django/forms/errors/list
2025-04-22 20:54:03,557 root INFO copying django/forms/templates/django/forms/errors/list/ul.html -> build/lib/django/forms/templates/django/forms/errors/list
2025-04-22 20:54:03,557 root INFO creating build/lib/django/forms/templates/django/forms/formsets
2025-04-22 20:54:03,557 root INFO copying django/forms/templates/django/forms/formsets/default.html -> build/lib/django/forms/templates/django/forms/formsets
2025-04-22 20:54:03,558 root INFO copying django/forms/templates/django/forms/formsets/div.html -> build/lib/django/forms/templates/django/forms/formsets
2025-04-22 20:54:03,558 root INFO copying django/forms/templates/django/forms/formsets/p.html -> build/lib/django/forms/templates/django/forms/formsets
2025-04-22 20:54:03,558 root INFO copying django/forms/templates/django/forms/formsets/table.html -> build/lib/django/forms/templates/django/forms/formsets
2025-04-22 20:54:03,558 root INFO copying django/forms/templates/django/forms/formsets/ul.html -> build/lib/django/forms/templates/django/forms/formsets
2025-04-22 20:54:03,558 root INFO creating build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,558 root INFO copying django/forms/templates/django/forms/widgets/attrs.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,558 root INFO copying django/forms/templates/django/forms/widgets/checkbox.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,559 root INFO copying django/forms/templates/django/forms/widgets/checkbox_option.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,559 root INFO copying django/forms/templates/django/forms/widgets/checkbox_select.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,559 root INFO copying django/forms/templates/django/forms/widgets/clearable_file_input.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,559 root INFO copying django/forms/templates/django/forms/widgets/date.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,559 root INFO copying django/forms/templates/django/forms/widgets/datetime.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,559 root INFO copying django/forms/templates/django/forms/widgets/email.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,560 root INFO copying django/forms/templates/django/forms/widgets/file.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,560 root INFO copying django/forms/templates/django/forms/widgets/hidden.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,560 root INFO copying django/forms/templates/django/forms/widgets/input.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,560 root INFO copying django/forms/templates/django/forms/widgets/input_option.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,560 root INFO copying django/forms/templates/django/forms/widgets/multiple_hidden.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,560 root INFO copying django/forms/templates/django/forms/widgets/multiple_input.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,560 root INFO copying django/forms/templates/django/forms/widgets/multiwidget.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,561 root INFO copying django/forms/templates/django/forms/widgets/number.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,561 root INFO copying django/forms/templates/django/forms/widgets/password.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,561 root INFO copying django/forms/templates/django/forms/widgets/radio.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,561 root INFO copying django/forms/templates/django/forms/widgets/radio_option.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,561 root INFO copying django/forms/templates/django/forms/widgets/select.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,561 root INFO copying django/forms/templates/django/forms/widgets/select_date.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,561 root INFO copying django/forms/templates/django/forms/widgets/select_option.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,562 root INFO copying django/forms/templates/django/forms/widgets/splitdatetime.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,562 root INFO copying django/forms/templates/django/forms/widgets/splithiddendatetime.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,562 root INFO copying django/forms/templates/django/forms/widgets/text.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,562 root INFO copying django/forms/templates/django/forms/widgets/textarea.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,562 root INFO copying django/forms/templates/django/forms/widgets/time.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,562 root INFO copying django/forms/templates/django/forms/widgets/url.html -> build/lib/django/forms/templates/django/forms/widgets
2025-04-22 20:54:03,563 root INFO creating build/lib/django/conf/locale/af
2025-04-22 20:54:03,563 root INFO creating build/lib/django/conf/locale/af/LC_MESSAGES
2025-04-22 20:54:03,563 root INFO copying django/conf/locale/af/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/af/LC_MESSAGES
2025-04-22 20:54:03,563 root INFO copying django/conf/locale/af/LC_MESSAGES/django.po -> build/lib/django/conf/locale/af/LC_MESSAGES
2025-04-22 20:54:03,563 root INFO creating build/lib/django/conf/locale/ast
2025-04-22 20:54:03,563 root INFO creating build/lib/django/conf/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,563 root INFO copying django/conf/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,564 root INFO copying django/conf/locale/ast/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,564 root INFO creating build/lib/django/conf/locale/be
2025-04-22 20:54:03,564 root INFO creating build/lib/django/conf/locale/be/LC_MESSAGES
2025-04-22 20:54:03,564 root INFO copying django/conf/locale/be/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/be/LC_MESSAGES
2025-04-22 20:54:03,564 root INFO copying django/conf/locale/be/LC_MESSAGES/django.po -> build/lib/django/conf/locale/be/LC_MESSAGES
2025-04-22 20:54:03,564 root INFO creating build/lib/django/conf/locale/br
2025-04-22 20:54:03,564 root INFO creating build/lib/django/conf/locale/br/LC_MESSAGES
2025-04-22 20:54:03,564 root INFO copying django/conf/locale/br/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/br/LC_MESSAGES
2025-04-22 20:54:03,565 root INFO copying django/conf/locale/br/LC_MESSAGES/django.po -> build/lib/django/conf/locale/br/LC_MESSAGES
2025-04-22 20:54:03,565 root INFO creating build/lib/django/conf/locale/dsb
2025-04-22 20:54:03,565 root INFO creating build/lib/django/conf/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,565 root INFO copying django/conf/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,565 root INFO copying django/conf/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,565 root INFO creating build/lib/django/conf/locale/es_VE
2025-04-22 20:54:03,566 root INFO creating build/lib/django/conf/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:03,566 root INFO copying django/conf/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:03,566 root INFO copying django/conf/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:03,566 root INFO creating build/lib/django/conf/locale/hsb
2025-04-22 20:54:03,566 root INFO creating build/lib/django/conf/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,566 root INFO copying django/conf/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,566 root INFO copying django/conf/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,567 root INFO creating build/lib/django/conf/locale/hy
2025-04-22 20:54:03,567 root INFO creating build/lib/django/conf/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,567 root INFO copying django/conf/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,567 root INFO copying django/conf/locale/hy/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,567 root INFO creating build/lib/django/conf/locale/ia
2025-04-22 20:54:03,567 root INFO creating build/lib/django/conf/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,567 root INFO copying django/conf/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,567 root INFO copying django/conf/locale/ia/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,568 root INFO creating build/lib/django/conf/locale/io
2025-04-22 20:54:03,568 root INFO creating build/lib/django/conf/locale/io/LC_MESSAGES
2025-04-22 20:54:03,568 root INFO copying django/conf/locale/io/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/io/LC_MESSAGES
2025-04-22 20:54:03,568 root INFO copying django/conf/locale/io/LC_MESSAGES/django.po -> build/lib/django/conf/locale/io/LC_MESSAGES
2025-04-22 20:54:03,568 root INFO creating build/lib/django/conf/locale/kab
2025-04-22 20:54:03,568 root INFO creating build/lib/django/conf/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,568 root INFO copying django/conf/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,569 root INFO copying django/conf/locale/kab/LC_MESSAGES/django.po -> build/lib/django/conf/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,569 root INFO creating build/lib/django/conf/locale/kk
2025-04-22 20:54:03,569 root INFO creating build/lib/django/conf/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,569 root INFO copying django/conf/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,569 root INFO copying django/conf/locale/kk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,569 root INFO creating build/lib/django/conf/locale/lb
2025-04-22 20:54:03,569 root INFO creating build/lib/django/conf/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,569 root INFO copying django/conf/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,570 root INFO copying django/conf/locale/lb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,570 root INFO creating build/lib/django/conf/locale/mr
2025-04-22 20:54:03,570 root INFO creating build/lib/django/conf/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,570 root INFO copying django/conf/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,570 root INFO copying django/conf/locale/mr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,570 root INFO creating build/lib/django/conf/locale/my
2025-04-22 20:54:03,570 root INFO creating build/lib/django/conf/locale/my/LC_MESSAGES
2025-04-22 20:54:03,570 root INFO copying django/conf/locale/my/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/my/LC_MESSAGES
2025-04-22 20:54:03,571 root INFO copying django/conf/locale/my/LC_MESSAGES/django.po -> build/lib/django/conf/locale/my/LC_MESSAGES
2025-04-22 20:54:03,571 root INFO creating build/lib/django/conf/locale/ne
2025-04-22 20:54:03,571 root INFO creating build/lib/django/conf/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,571 root INFO copying django/conf/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,571 root INFO copying django/conf/locale/ne/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,571 root INFO creating build/lib/django/conf/locale/os
2025-04-22 20:54:03,571 root INFO creating build/lib/django/conf/locale/os/LC_MESSAGES
2025-04-22 20:54:03,571 root INFO copying django/conf/locale/os/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/os/LC_MESSAGES
2025-04-22 20:54:03,572 root INFO copying django/conf/locale/os/LC_MESSAGES/django.po -> build/lib/django/conf/locale/os/LC_MESSAGES
2025-04-22 20:54:03,572 root INFO creating build/lib/django/conf/locale/pa
2025-04-22 20:54:03,572 root INFO creating build/lib/django/conf/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,572 root INFO copying django/conf/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,572 root INFO copying django/conf/locale/pa/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,572 root INFO creating build/lib/django/conf/locale/sw
2025-04-22 20:54:03,572 root INFO creating build/lib/django/conf/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,573 root INFO copying django/conf/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,573 root INFO copying django/conf/locale/sw/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,573 root INFO creating build/lib/django/conf/locale/tt
2025-04-22 20:54:03,573 root INFO creating build/lib/django/conf/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,573 root INFO copying django/conf/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,573 root INFO copying django/conf/locale/tt/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,573 root INFO creating build/lib/django/conf/locale/udm
2025-04-22 20:54:03,574 root INFO creating build/lib/django/conf/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,574 root INFO copying django/conf/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,574 root INFO copying django/conf/locale/udm/LC_MESSAGES/django.po -> build/lib/django/conf/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,574 root INFO creating build/lib/django/conf/locale/ur
2025-04-22 20:54:03,574 root INFO creating build/lib/django/conf/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,574 root INFO copying django/conf/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,574 root INFO copying django/conf/locale/ur/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,575 root INFO creating build/lib/django/conf/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,575 root INFO copying django/conf/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,575 root INFO copying django/conf/locale/lv/LC_MESSAGES/django.po -> build/lib/django/conf/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,575 root INFO creating build/lib/django/conf/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:03,575 root INFO copying django/conf/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:03,575 root INFO copying django/conf/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:03,576 root INFO creating build/lib/django/conf/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,576 root INFO copying django/conf/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,576 root INFO copying django/conf/locale/ca/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,576 root INFO creating build/lib/django/conf/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:03,576 root INFO copying django/conf/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:03,576 root INFO copying django/conf/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:03,577 root INFO creating build/lib/django/conf/locale/el/LC_MESSAGES
2025-04-22 20:54:03,577 root INFO copying django/conf/locale/el/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/el/LC_MESSAGES
2025-04-22 20:54:03,577 root INFO copying django/conf/locale/el/LC_MESSAGES/django.po -> build/lib/django/conf/locale/el/LC_MESSAGES
2025-04-22 20:54:03,577 root INFO creating build/lib/django/conf/locale/en/LC_MESSAGES
2025-04-22 20:54:03,577 root INFO copying django/conf/locale/en/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en/LC_MESSAGES
2025-04-22 20:54:03,577 root INFO copying django/conf/locale/en/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en/LC_MESSAGES
2025-04-22 20:54:03,578 root INFO creating build/lib/django/conf/locale/et/LC_MESSAGES
2025-04-22 20:54:03,578 root INFO copying django/conf/locale/et/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/et/LC_MESSAGES
2025-04-22 20:54:03,578 root INFO copying django/conf/locale/et/LC_MESSAGES/django.po -> build/lib/django/conf/locale/et/LC_MESSAGES
2025-04-22 20:54:03,578 root INFO creating build/lib/django/conf/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,578 root INFO copying django/conf/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,578 root INFO copying django/conf/locale/nn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,579 root INFO creating build/lib/django/conf/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,579 root INFO copying django/conf/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,579 root INFO copying django/conf/locale/cy/LC_MESSAGES/django.po -> build/lib/django/conf/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,579 root INFO creating build/lib/django/conf/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,579 root INFO copying django/conf/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,579 root INFO copying django/conf/locale/ko/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,580 root INFO creating build/lib/django/conf/locale/is/LC_MESSAGES
2025-04-22 20:54:03,580 root INFO copying django/conf/locale/is/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/is/LC_MESSAGES
2025-04-22 20:54:03,580 root INFO copying django/conf/locale/is/LC_MESSAGES/django.po -> build/lib/django/conf/locale/is/LC_MESSAGES
2025-04-22 20:54:03,580 root INFO creating build/lib/django/conf/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:03,580 root INFO copying django/conf/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:03,580 root INFO copying django/conf/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:03,581 root INFO creating build/lib/django/conf/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,581 root INFO copying django/conf/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,581 root INFO copying django/conf/locale/fy/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,581 root INFO creating build/lib/django/conf/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,581 root INFO copying django/conf/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,581 root INFO copying django/conf/locale/bg/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,582 root INFO creating build/lib/django/conf/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,582 root INFO copying django/conf/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,582 root INFO copying django/conf/locale/ga/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,582 root INFO creating build/lib/django/conf/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,582 root INFO copying django/conf/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,582 root INFO copying django/conf/locale/gl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,583 root INFO creating build/lib/django/conf/locale/ig/LC_MESSAGES
2025-04-22 20:54:03,583 root INFO copying django/conf/locale/ig/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ig/LC_MESSAGES
2025-04-22 20:54:03,583 root INFO copying django/conf/locale/ig/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ig/LC_MESSAGES
2025-04-22 20:54:03,583 root INFO creating build/lib/django/conf/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,583 root INFO copying django/conf/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,583 root INFO copying django/conf/locale/uk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,584 root INFO creating build/lib/django/conf/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,584 root INFO copying django/conf/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,584 root INFO copying django/conf/locale/uz/LC_MESSAGES/django.po -> build/lib/django/conf/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,584 root INFO creating build/lib/django/conf/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,584 root INFO copying django/conf/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,584 root INFO copying django/conf/locale/kn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,585 root INFO creating build/lib/django/conf/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,585 root INFO copying django/conf/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,585 root INFO copying django/conf/locale/ja/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,585 root INFO creating build/lib/django/conf/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,585 root INFO copying django/conf/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,586 root INFO copying django/conf/locale/cs/LC_MESSAGES/django.po -> build/lib/django/conf/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,586 root INFO creating build/lib/django/conf/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,586 root INFO copying django/conf/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,586 root INFO copying django/conf/locale/tr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,586 root INFO creating build/lib/django/conf/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,586 root INFO copying django/conf/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,587 root INFO copying django/conf/locale/sl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,587 root INFO creating build/lib/django/conf/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,587 root INFO copying django/conf/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,587 root INFO copying django/conf/locale/sq/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,587 root INFO creating build/lib/django/conf/locale/az/LC_MESSAGES
2025-04-22 20:54:03,588 root INFO copying django/conf/locale/az/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/az/LC_MESSAGES
2025-04-22 20:54:03,588 root INFO copying django/conf/locale/az/LC_MESSAGES/django.po -> build/lib/django/conf/locale/az/LC_MESSAGES
2025-04-22 20:54:03,588 root INFO creating build/lib/django/conf/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,588 root INFO copying django/conf/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,588 root INFO copying django/conf/locale/eo/LC_MESSAGES/django.po -> build/lib/django/conf/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,588 root INFO creating build/lib/django/conf/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:03,589 root INFO copying django/conf/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:03,589 root INFO copying django/conf/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:03,589 root INFO creating build/lib/django/conf/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,589 root INFO copying django/conf/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,589 root INFO copying django/conf/locale/pl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,590 root INFO creating build/lib/django/conf/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,590 root INFO copying django/conf/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,590 root INFO copying django/conf/locale/gd/LC_MESSAGES/django.po -> build/lib/django/conf/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,590 root INFO creating build/lib/django/conf/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,590 root INFO copying django/conf/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,590 root INFO copying django/conf/locale/hr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,591 root INFO creating build/lib/django/conf/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,591 root INFO copying django/conf/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,591 root INFO copying django/conf/locale/ru/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,591 root INFO creating build/lib/django/conf/locale/es/LC_MESSAGES
2025-04-22 20:54:03,591 root INFO copying django/conf/locale/es/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es/LC_MESSAGES
2025-04-22 20:54:03,591 root INFO copying django/conf/locale/es/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es/LC_MESSAGES
2025-04-22 20:54:03,592 root INFO creating build/lib/django/conf/locale/id/LC_MESSAGES
2025-04-22 20:54:03,592 root INFO copying django/conf/locale/id/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/id/LC_MESSAGES
2025-04-22 20:54:03,592 root INFO copying django/conf/locale/id/LC_MESSAGES/django.po -> build/lib/django/conf/locale/id/LC_MESSAGES
2025-04-22 20:54:03,592 root INFO creating build/lib/django/conf/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,592 root INFO copying django/conf/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,592 root INFO copying django/conf/locale/fi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,593 root INFO creating build/lib/django/conf/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,593 root INFO copying django/conf/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,593 root INFO copying django/conf/locale/mk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,593 root INFO creating build/lib/django/conf/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,593 root INFO copying django/conf/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,593 root INFO copying django/conf/locale/hi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,594 root INFO creating build/lib/django/conf/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,594 root INFO copying django/conf/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,594 root INFO copying django/conf/locale/sk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,594 root INFO creating build/lib/django/conf/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,594 root INFO copying django/conf/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,594 root INFO copying django/conf/locale/lt/LC_MESSAGES/django.po -> build/lib/django/conf/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,595 root INFO creating build/lib/django/conf/locale/de/LC_MESSAGES
2025-04-22 20:54:03,595 root INFO copying django/conf/locale/de/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/de/LC_MESSAGES
2025-04-22 20:54:03,595 root INFO copying django/conf/locale/de/LC_MESSAGES/django.po -> build/lib/django/conf/locale/de/LC_MESSAGES
2025-04-22 20:54:03,595 root INFO creating build/lib/django/conf/locale/it/LC_MESSAGES
2025-04-22 20:54:03,595 root INFO copying django/conf/locale/it/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/it/LC_MESSAGES
2025-04-22 20:54:03,596 root INFO copying django/conf/locale/it/LC_MESSAGES/django.po -> build/lib/django/conf/locale/it/LC_MESSAGES
2025-04-22 20:54:03,596 root INFO creating build/lib/django/conf/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,596 root INFO copying django/conf/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,596 root INFO copying django/conf/locale/sr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,596 root INFO creating build/lib/django/conf/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,596 root INFO copying django/conf/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,597 root INFO copying django/conf/locale/bs/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,597 root INFO creating build/lib/django/conf/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,597 root INFO copying django/conf/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,597 root INFO copying django/conf/locale/ro/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,597 root INFO creating build/lib/django/conf/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,597 root INFO copying django/conf/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,597 root INFO copying django/conf/locale/ky/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,598 root INFO creating build/lib/django/conf/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,598 root INFO copying django/conf/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,598 root INFO copying django/conf/locale/fr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,598 root INFO creating build/lib/django/conf/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,598 root INFO copying django/conf/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,598 root INFO copying django/conf/locale/ar/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,599 root INFO creating build/lib/django/conf/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:03,599 root INFO copying django/conf/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:03,599 root INFO copying django/conf/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:03,599 root INFO creating build/lib/django/conf/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,599 root INFO copying django/conf/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,600 root INFO copying django/conf/locale/vi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,600 root INFO creating build/lib/django/conf/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,600 root INFO copying django/conf/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,600 root INFO copying django/conf/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,600 root INFO creating build/lib/django/conf/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,600 root INFO copying django/conf/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,601 root INFO copying django/conf/locale/sv/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,601 root INFO creating build/lib/django/conf/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:03,601 root INFO copying django/conf/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:03,601 root INFO copying django/conf/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/conf/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:03,601 root INFO creating build/lib/django/conf/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:03,601 root INFO copying django/conf/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:03,602 root INFO copying django/conf/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:03,602 root INFO creating build/lib/django/conf/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,602 root INFO copying django/conf/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,602 root INFO copying django/conf/locale/ml/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,603 root INFO creating build/lib/django/conf/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:03,603 root INFO copying django/conf/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:03,603 root INFO copying django/conf/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:03,603 root INFO creating build/lib/django/conf/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,603 root INFO copying django/conf/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,603 root INFO copying django/conf/locale/ms/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,604 root INFO creating build/lib/django/conf/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:03,604 root INFO copying django/conf/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:03,604 root INFO copying django/conf/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/conf/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:03,604 root INFO creating build/lib/django/conf/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,604 root INFO copying django/conf/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,604 root INFO copying django/conf/locale/hu/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,605 root INFO creating build/lib/django/conf/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,605 root INFO copying django/conf/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,605 root INFO copying django/conf/locale/ta/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,605 root INFO creating build/lib/django/conf/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,605 root INFO copying django/conf/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,605 root INFO copying django/conf/locale/eu/LC_MESSAGES/django.po -> build/lib/django/conf/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,606 root INFO creating build/lib/django/conf/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:03,606 root INFO copying django/conf/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:03,606 root INFO copying django/conf/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:03,606 root INFO creating build/lib/django/conf/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,606 root INFO copying django/conf/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,606 root INFO copying django/conf/locale/tk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,607 root INFO creating build/lib/django/conf/locale/th/LC_MESSAGES
2025-04-22 20:54:03,607 root INFO copying django/conf/locale/th/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/th/LC_MESSAGES
2025-04-22 20:54:03,607 root INFO copying django/conf/locale/th/LC_MESSAGES/django.po -> build/lib/django/conf/locale/th/LC_MESSAGES
2025-04-22 20:54:03,607 root INFO creating build/lib/django/conf/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,607 root INFO copying django/conf/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,607 root INFO copying django/conf/locale/nb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,608 root INFO creating build/lib/django/conf/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,608 root INFO copying django/conf/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,608 root INFO copying django/conf/locale/mn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,608 root INFO creating build/lib/django/conf/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,608 root INFO copying django/conf/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,608 root INFO copying django/conf/locale/ka/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,609 root INFO creating build/lib/django/conf/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,609 root INFO copying django/conf/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,609 root INFO copying django/conf/locale/nl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,609 root INFO creating build/lib/django/conf/locale/te/LC_MESSAGES
2025-04-22 20:54:03,609 root INFO copying django/conf/locale/te/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/te/LC_MESSAGES
2025-04-22 20:54:03,609 root INFO copying django/conf/locale/te/LC_MESSAGES/django.po -> build/lib/django/conf/locale/te/LC_MESSAGES
2025-04-22 20:54:03,610 root INFO creating build/lib/django/conf/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,610 root INFO copying django/conf/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,610 root INFO copying django/conf/locale/pt/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,610 root INFO creating build/lib/django/conf/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,610 root INFO copying django/conf/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,610 root INFO copying django/conf/locale/bn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,611 root INFO creating build/lib/django/conf/locale/he/LC_MESSAGES
2025-04-22 20:54:03,611 root INFO copying django/conf/locale/he/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/he/LC_MESSAGES
2025-04-22 20:54:03,611 root INFO copying django/conf/locale/he/LC_MESSAGES/django.po -> build/lib/django/conf/locale/he/LC_MESSAGES
2025-04-22 20:54:03,611 root INFO creating build/lib/django/conf/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,611 root INFO copying django/conf/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,611 root INFO copying django/conf/locale/fa/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,612 root INFO creating build/lib/django/conf/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,612 root INFO copying django/conf/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,612 root INFO copying django/conf/locale/tg/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,612 root INFO creating build/lib/django/conf/locale/km/LC_MESSAGES
2025-04-22 20:54:03,612 root INFO copying django/conf/locale/km/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/km/LC_MESSAGES
2025-04-22 20:54:03,613 root INFO copying django/conf/locale/km/LC_MESSAGES/django.po -> build/lib/django/conf/locale/km/LC_MESSAGES
2025-04-22 20:54:03,613 root INFO creating build/lib/django/conf/locale/da/LC_MESSAGES
2025-04-22 20:54:03,613 root INFO copying django/conf/locale/da/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/da/LC_MESSAGES
2025-04-22 20:54:03,613 root INFO copying django/conf/locale/da/LC_MESSAGES/django.po -> build/lib/django/conf/locale/da/LC_MESSAGES
2025-04-22 20:54:03,613 root INFO copying django/contrib/auth/common-passwords.txt.gz -> build/lib/django/contrib/auth
2025-04-22 20:54:03,614 root INFO creating build/lib/django/contrib/auth/locale
2025-04-22 20:54:03,614 root INFO creating build/lib/django/contrib/auth/locale/af
2025-04-22 20:54:03,614 root INFO creating build/lib/django/contrib/auth/locale/af/LC_MESSAGES
2025-04-22 20:54:03,614 root INFO copying django/contrib/auth/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/af/LC_MESSAGES
2025-04-22 20:54:03,614 root INFO copying django/contrib/auth/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/af/LC_MESSAGES
2025-04-22 20:54:03,614 root INFO creating build/lib/django/contrib/auth/locale/ar
2025-04-22 20:54:03,614 root INFO creating build/lib/django/contrib/auth/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,614 root INFO copying django/contrib/auth/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,614 root INFO copying django/contrib/auth/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,615 root INFO creating build/lib/django/contrib/auth/locale/ar_DZ
2025-04-22 20:54:03,615 root INFO creating build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:03,615 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 20:54:03,615 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 20:54:03,615 root INFO creating build/lib/django/contrib/auth/locale/ast
2025-04-22 20:54:03,615 root INFO creating build/lib/django/contrib/auth/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,615 root INFO copying django/contrib/auth/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,615 root INFO copying django/contrib/auth/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,616 root INFO creating build/lib/django/contrib/auth/locale/az
2025-04-22 20:54:03,616 root INFO creating build/lib/django/contrib/auth/locale/az/LC_MESSAGES
2025-04-22 20:54:03,616 root INFO copying django/contrib/auth/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/az/LC_MESSAGES
2025-04-22 20:54:03,616 root INFO copying django/contrib/auth/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/az/LC_MESSAGES
2025-04-22 20:54:03,616 root INFO creating build/lib/django/contrib/auth/locale/be
2025-04-22 20:54:03,616 root INFO creating build/lib/django/contrib/auth/locale/be/LC_MESSAGES
2025-04-22 20:54:03,616 root INFO copying django/contrib/auth/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/be/LC_MESSAGES
2025-04-22 20:54:03,616 root INFO copying django/contrib/auth/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/be/LC_MESSAGES
2025-04-22 20:54:03,617 root INFO creating build/lib/django/contrib/auth/locale/bg
2025-04-22 20:54:03,617 root INFO creating build/lib/django/contrib/auth/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,617 root INFO copying django/contrib/auth/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,617 root INFO copying django/contrib/auth/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,617 root INFO creating build/lib/django/contrib/auth/locale/bn
2025-04-22 20:54:03,617 root INFO creating build/lib/django/contrib/auth/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,617 root INFO copying django/contrib/auth/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,618 root INFO copying django/contrib/auth/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,618 root INFO creating build/lib/django/contrib/auth/locale/br
2025-04-22 20:54:03,618 root INFO creating build/lib/django/contrib/auth/locale/br/LC_MESSAGES
2025-04-22 20:54:03,618 root INFO copying django/contrib/auth/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/br/LC_MESSAGES
2025-04-22 20:54:03,618 root INFO copying django/contrib/auth/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/br/LC_MESSAGES
2025-04-22 20:54:03,618 root INFO creating build/lib/django/contrib/auth/locale/bs
2025-04-22 20:54:03,618 root INFO creating build/lib/django/contrib/auth/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,618 root INFO copying django/contrib/auth/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,618 root INFO copying django/contrib/auth/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,619 root INFO creating build/lib/django/contrib/auth/locale/ca
2025-04-22 20:54:03,619 root INFO creating build/lib/django/contrib/auth/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,619 root INFO copying django/contrib/auth/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,619 root INFO copying django/contrib/auth/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,619 root INFO creating build/lib/django/contrib/auth/locale/ckb
2025-04-22 20:54:03,619 root INFO creating build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,619 root INFO copying django/contrib/auth/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,619 root INFO copying django/contrib/auth/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,620 root INFO creating build/lib/django/contrib/auth/locale/cs
2025-04-22 20:54:03,620 root INFO creating build/lib/django/contrib/auth/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,620 root INFO copying django/contrib/auth/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,620 root INFO copying django/contrib/auth/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,620 root INFO creating build/lib/django/contrib/auth/locale/cy
2025-04-22 20:54:03,620 root INFO creating build/lib/django/contrib/auth/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,620 root INFO copying django/contrib/auth/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,620 root INFO copying django/contrib/auth/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,621 root INFO creating build/lib/django/contrib/auth/locale/da
2025-04-22 20:54:03,621 root INFO creating build/lib/django/contrib/auth/locale/da/LC_MESSAGES
2025-04-22 20:54:03,621 root INFO copying django/contrib/auth/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/da/LC_MESSAGES
2025-04-22 20:54:03,621 root INFO copying django/contrib/auth/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/da/LC_MESSAGES
2025-04-22 20:54:03,621 root INFO creating build/lib/django/contrib/auth/locale/de
2025-04-22 20:54:03,621 root INFO creating build/lib/django/contrib/auth/locale/de/LC_MESSAGES
2025-04-22 20:54:03,621 root INFO copying django/contrib/auth/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/de/LC_MESSAGES
2025-04-22 20:54:03,621 root INFO copying django/contrib/auth/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/de/LC_MESSAGES
2025-04-22 20:54:03,622 root INFO creating build/lib/django/contrib/auth/locale/dsb
2025-04-22 20:54:03,622 root INFO creating build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,622 root INFO copying django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,622 root INFO copying django/contrib/auth/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,622 root INFO creating build/lib/django/contrib/auth/locale/el
2025-04-22 20:54:03,622 root INFO creating build/lib/django/contrib/auth/locale/el/LC_MESSAGES
2025-04-22 20:54:03,622 root INFO copying django/contrib/auth/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/el/LC_MESSAGES
2025-04-22 20:54:03,623 root INFO copying django/contrib/auth/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/el/LC_MESSAGES
2025-04-22 20:54:03,623 root INFO creating build/lib/django/contrib/auth/locale/en
2025-04-22 20:54:03,623 root INFO creating build/lib/django/contrib/auth/locale/en/LC_MESSAGES
2025-04-22 20:54:03,623 root INFO copying django/contrib/auth/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/en/LC_MESSAGES
2025-04-22 20:54:03,623 root INFO copying django/contrib/auth/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/en/LC_MESSAGES
2025-04-22 20:54:03,623 root INFO creating build/lib/django/contrib/auth/locale/en_AU
2025-04-22 20:54:03,623 root INFO creating build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:03,623 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 20:54:03,623 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 20:54:03,624 root INFO creating build/lib/django/contrib/auth/locale/en_GB
2025-04-22 20:54:03,624 root INFO creating build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:03,624 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 20:54:03,624 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 20:54:03,624 root INFO creating build/lib/django/contrib/auth/locale/eo
2025-04-22 20:54:03,624 root INFO creating build/lib/django/contrib/auth/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,624 root INFO copying django/contrib/auth/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,624 root INFO copying django/contrib/auth/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,625 root INFO creating build/lib/django/contrib/auth/locale/es
2025-04-22 20:54:03,625 root INFO creating build/lib/django/contrib/auth/locale/es/LC_MESSAGES
2025-04-22 20:54:03,625 root INFO copying django/contrib/auth/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es/LC_MESSAGES
2025-04-22 20:54:03,625 root INFO copying django/contrib/auth/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es/LC_MESSAGES
2025-04-22 20:54:03,625 root INFO creating build/lib/django/contrib/auth/locale/es_AR
2025-04-22 20:54:03,625 root INFO creating build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:03,625 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 20:54:03,626 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 20:54:03,626 root INFO creating build/lib/django/contrib/auth/locale/es_CO
2025-04-22 20:54:03,626 root INFO creating build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:03,626 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 20:54:03,626 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 20:54:03,626 root INFO creating build/lib/django/contrib/auth/locale/es_MX
2025-04-22 20:54:03,626 root INFO creating build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:03,626 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 20:54:03,627 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 20:54:03,627 root INFO creating build/lib/django/contrib/auth/locale/es_VE
2025-04-22 20:54:03,627 root INFO creating build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:03,627 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 20:54:03,627 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 20:54:03,627 root INFO creating build/lib/django/contrib/auth/locale/et
2025-04-22 20:54:03,627 root INFO creating build/lib/django/contrib/auth/locale/et/LC_MESSAGES
2025-04-22 20:54:03,627 root INFO copying django/contrib/auth/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/et/LC_MESSAGES
2025-04-22 20:54:03,628 root INFO copying django/contrib/auth/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/et/LC_MESSAGES
2025-04-22 20:54:03,628 root INFO creating build/lib/django/contrib/auth/locale/eu
2025-04-22 20:54:03,628 root INFO creating build/lib/django/contrib/auth/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,628 root INFO copying django/contrib/auth/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,628 root INFO copying django/contrib/auth/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,628 root INFO creating build/lib/django/contrib/auth/locale/fa
2025-04-22 20:54:03,628 root INFO creating build/lib/django/contrib/auth/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,628 root INFO copying django/contrib/auth/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,629 root INFO copying django/contrib/auth/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,629 root INFO creating build/lib/django/contrib/auth/locale/fi
2025-04-22 20:54:03,629 root INFO creating build/lib/django/contrib/auth/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,629 root INFO copying django/contrib/auth/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,629 root INFO copying django/contrib/auth/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,629 root INFO creating build/lib/django/contrib/auth/locale/fr
2025-04-22 20:54:03,629 root INFO creating build/lib/django/contrib/auth/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,629 root INFO copying django/contrib/auth/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,630 root INFO copying django/contrib/auth/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,630 root INFO creating build/lib/django/contrib/auth/locale/fy
2025-04-22 20:54:03,630 root INFO creating build/lib/django/contrib/auth/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,630 root INFO copying django/contrib/auth/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,630 root INFO copying django/contrib/auth/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,630 root INFO creating build/lib/django/contrib/auth/locale/ga
2025-04-22 20:54:03,630 root INFO creating build/lib/django/contrib/auth/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,630 root INFO copying django/contrib/auth/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,630 root INFO copying django/contrib/auth/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,631 root INFO creating build/lib/django/contrib/auth/locale/gd
2025-04-22 20:54:03,631 root INFO creating build/lib/django/contrib/auth/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,631 root INFO copying django/contrib/auth/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,631 root INFO copying django/contrib/auth/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,631 root INFO creating build/lib/django/contrib/auth/locale/gl
2025-04-22 20:54:03,631 root INFO creating build/lib/django/contrib/auth/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,631 root INFO copying django/contrib/auth/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,631 root INFO copying django/contrib/auth/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,632 root INFO creating build/lib/django/contrib/auth/locale/he
2025-04-22 20:54:03,632 root INFO creating build/lib/django/contrib/auth/locale/he/LC_MESSAGES
2025-04-22 20:54:03,632 root INFO copying django/contrib/auth/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/he/LC_MESSAGES
2025-04-22 20:54:03,632 root INFO copying django/contrib/auth/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/he/LC_MESSAGES
2025-04-22 20:54:03,632 root INFO creating build/lib/django/contrib/auth/locale/hi
2025-04-22 20:54:03,632 root INFO creating build/lib/django/contrib/auth/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,632 root INFO copying django/contrib/auth/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,633 root INFO copying django/contrib/auth/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,633 root INFO creating build/lib/django/contrib/auth/locale/hr
2025-04-22 20:54:03,633 root INFO creating build/lib/django/contrib/auth/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,633 root INFO copying django/contrib/auth/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,633 root INFO copying django/contrib/auth/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,633 root INFO creating build/lib/django/contrib/auth/locale/hsb
2025-04-22 20:54:03,633 root INFO creating build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,633 root INFO copying django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,633 root INFO copying django/contrib/auth/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,634 root INFO creating build/lib/django/contrib/auth/locale/hu
2025-04-22 20:54:03,634 root INFO creating build/lib/django/contrib/auth/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,634 root INFO copying django/contrib/auth/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,634 root INFO copying django/contrib/auth/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,634 root INFO creating build/lib/django/contrib/auth/locale/hy
2025-04-22 20:54:03,634 root INFO creating build/lib/django/contrib/auth/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,634 root INFO copying django/contrib/auth/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,634 root INFO copying django/contrib/auth/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,635 root INFO creating build/lib/django/contrib/auth/locale/ia
2025-04-22 20:54:03,635 root INFO creating build/lib/django/contrib/auth/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,635 root INFO copying django/contrib/auth/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,635 root INFO copying django/contrib/auth/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,635 root INFO creating build/lib/django/contrib/auth/locale/id
2025-04-22 20:54:03,635 root INFO creating build/lib/django/contrib/auth/locale/id/LC_MESSAGES
2025-04-22 20:54:03,635 root INFO copying django/contrib/auth/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/id/LC_MESSAGES
2025-04-22 20:54:03,635 root INFO copying django/contrib/auth/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/id/LC_MESSAGES
2025-04-22 20:54:03,636 root INFO creating build/lib/django/contrib/auth/locale/io
2025-04-22 20:54:03,636 root INFO creating build/lib/django/contrib/auth/locale/io/LC_MESSAGES
2025-04-22 20:54:03,636 root INFO copying django/contrib/auth/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/io/LC_MESSAGES
2025-04-22 20:54:03,636 root INFO copying django/contrib/auth/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/io/LC_MESSAGES
2025-04-22 20:54:03,636 root INFO creating build/lib/django/contrib/auth/locale/is
2025-04-22 20:54:03,636 root INFO creating build/lib/django/contrib/auth/locale/is/LC_MESSAGES
2025-04-22 20:54:03,636 root INFO copying django/contrib/auth/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/is/LC_MESSAGES
2025-04-22 20:54:03,636 root INFO copying django/contrib/auth/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/is/LC_MESSAGES
2025-04-22 20:54:03,637 root INFO creating build/lib/django/contrib/auth/locale/it
2025-04-22 20:54:03,637 root INFO creating build/lib/django/contrib/auth/locale/it/LC_MESSAGES
2025-04-22 20:54:03,637 root INFO copying django/contrib/auth/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/it/LC_MESSAGES
2025-04-22 20:54:03,637 root INFO copying django/contrib/auth/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/it/LC_MESSAGES
2025-04-22 20:54:03,637 root INFO creating build/lib/django/contrib/auth/locale/ja
2025-04-22 20:54:03,637 root INFO creating build/lib/django/contrib/auth/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,637 root INFO copying django/contrib/auth/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,637 root INFO copying django/contrib/auth/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,638 root INFO creating build/lib/django/contrib/auth/locale/ka
2025-04-22 20:54:03,638 root INFO creating build/lib/django/contrib/auth/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,638 root INFO copying django/contrib/auth/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,638 root INFO copying django/contrib/auth/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,638 root INFO creating build/lib/django/contrib/auth/locale/kab
2025-04-22 20:54:03,638 root INFO creating build/lib/django/contrib/auth/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,638 root INFO copying django/contrib/auth/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,639 root INFO copying django/contrib/auth/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,639 root INFO creating build/lib/django/contrib/auth/locale/kk
2025-04-22 20:54:03,639 root INFO creating build/lib/django/contrib/auth/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,639 root INFO copying django/contrib/auth/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,639 root INFO copying django/contrib/auth/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,639 root INFO creating build/lib/django/contrib/auth/locale/km
2025-04-22 20:54:03,639 root INFO creating build/lib/django/contrib/auth/locale/km/LC_MESSAGES
2025-04-22 20:54:03,639 root INFO copying django/contrib/auth/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/km/LC_MESSAGES
2025-04-22 20:54:03,639 root INFO copying django/contrib/auth/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/km/LC_MESSAGES
2025-04-22 20:54:03,640 root INFO creating build/lib/django/contrib/auth/locale/kn
2025-04-22 20:54:03,640 root INFO creating build/lib/django/contrib/auth/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,640 root INFO copying django/contrib/auth/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,640 root INFO copying django/contrib/auth/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,640 root INFO creating build/lib/django/contrib/auth/locale/ko
2025-04-22 20:54:03,640 root INFO creating build/lib/django/contrib/auth/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,640 root INFO copying django/contrib/auth/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,640 root INFO copying django/contrib/auth/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,641 root INFO creating build/lib/django/contrib/auth/locale/ky
2025-04-22 20:54:03,641 root INFO creating build/lib/django/contrib/auth/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,641 root INFO copying django/contrib/auth/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,641 root INFO copying django/contrib/auth/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,641 root INFO creating build/lib/django/contrib/auth/locale/lb
2025-04-22 20:54:03,641 root INFO creating build/lib/django/contrib/auth/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,641 root INFO copying django/contrib/auth/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,641 root INFO copying django/contrib/auth/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,642 root INFO creating build/lib/django/contrib/auth/locale/lt
2025-04-22 20:54:03,642 root INFO creating build/lib/django/contrib/auth/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,642 root INFO copying django/contrib/auth/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,642 root INFO copying django/contrib/auth/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,642 root INFO creating build/lib/django/contrib/auth/locale/lv
2025-04-22 20:54:03,642 root INFO creating build/lib/django/contrib/auth/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,642 root INFO copying django/contrib/auth/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,642 root INFO copying django/contrib/auth/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,643 root INFO creating build/lib/django/contrib/auth/locale/mk
2025-04-22 20:54:03,643 root INFO creating build/lib/django/contrib/auth/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,643 root INFO copying django/contrib/auth/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,643 root INFO copying django/contrib/auth/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,643 root INFO creating build/lib/django/contrib/auth/locale/ml
2025-04-22 20:54:03,643 root INFO creating build/lib/django/contrib/auth/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,643 root INFO copying django/contrib/auth/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,644 root INFO copying django/contrib/auth/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,644 root INFO creating build/lib/django/contrib/auth/locale/mn
2025-04-22 20:54:03,644 root INFO creating build/lib/django/contrib/auth/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,644 root INFO copying django/contrib/auth/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,644 root INFO copying django/contrib/auth/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,644 root INFO creating build/lib/django/contrib/auth/locale/mr
2025-04-22 20:54:03,644 root INFO creating build/lib/django/contrib/auth/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,644 root INFO copying django/contrib/auth/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,645 root INFO copying django/contrib/auth/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,645 root INFO creating build/lib/django/contrib/auth/locale/ms
2025-04-22 20:54:03,645 root INFO creating build/lib/django/contrib/auth/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,645 root INFO copying django/contrib/auth/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,645 root INFO copying django/contrib/auth/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,645 root INFO creating build/lib/django/contrib/auth/locale/my
2025-04-22 20:54:03,645 root INFO creating build/lib/django/contrib/auth/locale/my/LC_MESSAGES
2025-04-22 20:54:03,645 root INFO copying django/contrib/auth/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/my/LC_MESSAGES
2025-04-22 20:54:03,646 root INFO copying django/contrib/auth/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/my/LC_MESSAGES
2025-04-22 20:54:03,646 root INFO creating build/lib/django/contrib/auth/locale/nb
2025-04-22 20:54:03,646 root INFO creating build/lib/django/contrib/auth/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,646 root INFO copying django/contrib/auth/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,646 root INFO copying django/contrib/auth/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,646 root INFO creating build/lib/django/contrib/auth/locale/ne
2025-04-22 20:54:03,646 root INFO creating build/lib/django/contrib/auth/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,646 root INFO copying django/contrib/auth/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,647 root INFO copying django/contrib/auth/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,647 root INFO creating build/lib/django/contrib/auth/locale/nl
2025-04-22 20:54:03,647 root INFO creating build/lib/django/contrib/auth/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,647 root INFO copying django/contrib/auth/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,647 root INFO copying django/contrib/auth/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,647 root INFO creating build/lib/django/contrib/auth/locale/nn
2025-04-22 20:54:03,647 root INFO creating build/lib/django/contrib/auth/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,647 root INFO copying django/contrib/auth/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,648 root INFO copying django/contrib/auth/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,648 root INFO creating build/lib/django/contrib/auth/locale/os
2025-04-22 20:54:03,648 root INFO creating build/lib/django/contrib/auth/locale/os/LC_MESSAGES
2025-04-22 20:54:03,648 root INFO copying django/contrib/auth/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/os/LC_MESSAGES
2025-04-22 20:54:03,648 root INFO copying django/contrib/auth/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/os/LC_MESSAGES
2025-04-22 20:54:03,648 root INFO creating build/lib/django/contrib/auth/locale/pa
2025-04-22 20:54:03,648 root INFO creating build/lib/django/contrib/auth/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,648 root INFO copying django/contrib/auth/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,649 root INFO copying django/contrib/auth/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,649 root INFO creating build/lib/django/contrib/auth/locale/pl
2025-04-22 20:54:03,649 root INFO creating build/lib/django/contrib/auth/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,649 root INFO copying django/contrib/auth/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,649 root INFO copying django/contrib/auth/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,649 root INFO creating build/lib/django/contrib/auth/locale/pt
2025-04-22 20:54:03,649 root INFO creating build/lib/django/contrib/auth/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,649 root INFO copying django/contrib/auth/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,650 root INFO copying django/contrib/auth/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,650 root INFO creating build/lib/django/contrib/auth/locale/pt_BR
2025-04-22 20:54:03,650 root INFO creating build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:03,650 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 20:54:03,650 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 20:54:03,650 root INFO creating build/lib/django/contrib/auth/locale/ro
2025-04-22 20:54:03,650 root INFO creating build/lib/django/contrib/auth/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,650 root INFO copying django/contrib/auth/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,651 root INFO copying django/contrib/auth/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,651 root INFO creating build/lib/django/contrib/auth/locale/ru
2025-04-22 20:54:03,651 root INFO creating build/lib/django/contrib/auth/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,651 root INFO copying django/contrib/auth/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,651 root INFO copying django/contrib/auth/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,651 root INFO creating build/lib/django/contrib/auth/locale/sk
2025-04-22 20:54:03,651 root INFO creating build/lib/django/contrib/auth/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,651 root INFO copying django/contrib/auth/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,652 root INFO copying django/contrib/auth/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,652 root INFO creating build/lib/django/contrib/auth/locale/sl
2025-04-22 20:54:03,652 root INFO creating build/lib/django/contrib/auth/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,652 root INFO copying django/contrib/auth/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,652 root INFO copying django/contrib/auth/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,652 root INFO creating build/lib/django/contrib/auth/locale/sq
2025-04-22 20:54:03,652 root INFO creating build/lib/django/contrib/auth/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,652 root INFO copying django/contrib/auth/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,653 root INFO copying django/contrib/auth/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,653 root INFO creating build/lib/django/contrib/auth/locale/sr
2025-04-22 20:54:03,653 root INFO creating build/lib/django/contrib/auth/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,653 root INFO copying django/contrib/auth/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,653 root INFO copying django/contrib/auth/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,653 root INFO creating build/lib/django/contrib/auth/locale/sr_Latn
2025-04-22 20:54:03,653 root INFO creating build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:03,653 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 20:54:03,654 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 20:54:03,654 root INFO creating build/lib/django/contrib/auth/locale/sv
2025-04-22 20:54:03,654 root INFO creating build/lib/django/contrib/auth/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,654 root INFO copying django/contrib/auth/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,654 root INFO copying django/contrib/auth/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,654 root INFO creating build/lib/django/contrib/auth/locale/sw
2025-04-22 20:54:03,654 root INFO creating build/lib/django/contrib/auth/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,654 root INFO copying django/contrib/auth/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,655 root INFO copying django/contrib/auth/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,655 root INFO creating build/lib/django/contrib/auth/locale/ta
2025-04-22 20:54:03,655 root INFO creating build/lib/django/contrib/auth/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,655 root INFO copying django/contrib/auth/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,655 root INFO copying django/contrib/auth/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,655 root INFO creating build/lib/django/contrib/auth/locale/te
2025-04-22 20:54:03,655 root INFO creating build/lib/django/contrib/auth/locale/te/LC_MESSAGES
2025-04-22 20:54:03,655 root INFO copying django/contrib/auth/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/te/LC_MESSAGES
2025-04-22 20:54:03,656 root INFO copying django/contrib/auth/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/te/LC_MESSAGES
2025-04-22 20:54:03,656 root INFO creating build/lib/django/contrib/auth/locale/tg
2025-04-22 20:54:03,656 root INFO creating build/lib/django/contrib/auth/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,656 root INFO copying django/contrib/auth/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,656 root INFO copying django/contrib/auth/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,656 root INFO creating build/lib/django/contrib/auth/locale/th
2025-04-22 20:54:03,656 root INFO creating build/lib/django/contrib/auth/locale/th/LC_MESSAGES
2025-04-22 20:54:03,656 root INFO copying django/contrib/auth/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/th/LC_MESSAGES
2025-04-22 20:54:03,656 root INFO copying django/contrib/auth/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/th/LC_MESSAGES
2025-04-22 20:54:03,657 root INFO creating build/lib/django/contrib/auth/locale/tk
2025-04-22 20:54:03,657 root INFO creating build/lib/django/contrib/auth/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,657 root INFO copying django/contrib/auth/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,657 root INFO copying django/contrib/auth/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,657 root INFO creating build/lib/django/contrib/auth/locale/tr
2025-04-22 20:54:03,657 root INFO creating build/lib/django/contrib/auth/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,657 root INFO copying django/contrib/auth/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,657 root INFO copying django/contrib/auth/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,658 root INFO creating build/lib/django/contrib/auth/locale/tt
2025-04-22 20:54:03,658 root INFO creating build/lib/django/contrib/auth/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,658 root INFO copying django/contrib/auth/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,658 root INFO copying django/contrib/auth/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,658 root INFO creating build/lib/django/contrib/auth/locale/udm
2025-04-22 20:54:03,658 root INFO creating build/lib/django/contrib/auth/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,658 root INFO copying django/contrib/auth/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,659 root INFO copying django/contrib/auth/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,659 root INFO creating build/lib/django/contrib/auth/locale/uk
2025-04-22 20:54:03,659 root INFO creating build/lib/django/contrib/auth/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,659 root INFO copying django/contrib/auth/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,659 root INFO copying django/contrib/auth/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,659 root INFO creating build/lib/django/contrib/auth/locale/ur
2025-04-22 20:54:03,659 root INFO creating build/lib/django/contrib/auth/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,659 root INFO copying django/contrib/auth/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,660 root INFO copying django/contrib/auth/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,660 root INFO creating build/lib/django/contrib/auth/locale/uz
2025-04-22 20:54:03,660 root INFO creating build/lib/django/contrib/auth/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,660 root INFO copying django/contrib/auth/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,660 root INFO copying django/contrib/auth/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,660 root INFO creating build/lib/django/contrib/auth/locale/vi
2025-04-22 20:54:03,660 root INFO creating build/lib/django/contrib/auth/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,660 root INFO copying django/contrib/auth/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,660 root INFO copying django/contrib/auth/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,661 root INFO creating build/lib/django/contrib/auth/locale/zh_Hans
2025-04-22 20:54:03,661 root INFO creating build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:03,661 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 20:54:03,661 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 20:54:03,661 root INFO creating build/lib/django/contrib/auth/locale/zh_Hant
2025-04-22 20:54:03,661 root INFO creating build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:03,661 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 20:54:03,662 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 20:54:03,662 root INFO creating build/lib/django/contrib/auth/templates
2025-04-22 20:54:03,662 root INFO creating build/lib/django/contrib/auth/templates/auth
2025-04-22 20:54:03,662 root INFO creating build/lib/django/contrib/auth/templates/auth/widgets
2025-04-22 20:54:03,662 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 20:54:03,662 root INFO creating build/lib/django/contrib/auth/templates/registration
2025-04-22 20:54:03,662 root INFO copying django/contrib/auth/templates/registration/password_reset_subject.txt -> build/lib/django/contrib/auth/templates/registration
2025-04-22 20:54:03,662 root INFO creating build/lib/django/contrib/contenttypes/locale
2025-04-22 20:54:03,662 root INFO creating build/lib/django/contrib/contenttypes/locale/af
2025-04-22 20:54:03,662 root INFO creating build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES
2025-04-22 20:54:03,663 root INFO copying django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES
2025-04-22 20:54:03,663 root INFO copying django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES
2025-04-22 20:54:03,663 root INFO creating build/lib/django/contrib/contenttypes/locale/ar
2025-04-22 20:54:03,663 root INFO creating build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,663 root INFO copying django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,663 root INFO copying django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,663 root INFO creating build/lib/django/contrib/contenttypes/locale/ar_DZ
2025-04-22 20:54:03,663 root INFO creating build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:03,663 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 20:54:03,664 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 20:54:03,664 root INFO creating build/lib/django/contrib/contenttypes/locale/ast
2025-04-22 20:54:03,664 root INFO creating build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,664 root INFO copying django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,664 root INFO copying django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,664 root INFO creating build/lib/django/contrib/contenttypes/locale/az
2025-04-22 20:54:03,664 root INFO creating build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES
2025-04-22 20:54:03,664 root INFO copying django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES
2025-04-22 20:54:03,664 root INFO copying django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES
2025-04-22 20:54:03,665 root INFO creating build/lib/django/contrib/contenttypes/locale/be
2025-04-22 20:54:03,665 root INFO creating build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES
2025-04-22 20:54:03,665 root INFO copying django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES
2025-04-22 20:54:03,665 root INFO copying django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES
2025-04-22 20:54:03,665 root INFO creating build/lib/django/contrib/contenttypes/locale/bg
2025-04-22 20:54:03,665 root INFO creating build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,665 root INFO copying django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,665 root INFO copying django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,666 root INFO creating build/lib/django/contrib/contenttypes/locale/bn
2025-04-22 20:54:03,666 root INFO creating build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,666 root INFO copying django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,666 root INFO copying django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,666 root INFO creating build/lib/django/contrib/contenttypes/locale/br
2025-04-22 20:54:03,666 root INFO creating build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES
2025-04-22 20:54:03,666 root INFO copying django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES
2025-04-22 20:54:03,666 root INFO copying django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES
2025-04-22 20:54:03,667 root INFO creating build/lib/django/contrib/contenttypes/locale/bs
2025-04-22 20:54:03,667 root INFO creating build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,667 root INFO copying django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,667 root INFO copying django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,667 root INFO creating build/lib/django/contrib/contenttypes/locale/ca
2025-04-22 20:54:03,667 root INFO creating build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,667 root INFO copying django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,667 root INFO copying django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,667 root INFO creating build/lib/django/contrib/contenttypes/locale/ckb
2025-04-22 20:54:03,668 root INFO creating build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,668 root INFO copying django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,668 root INFO copying django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,668 root INFO creating build/lib/django/contrib/contenttypes/locale/cs
2025-04-22 20:54:03,668 root INFO creating build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,668 root INFO copying django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,668 root INFO copying django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,668 root INFO creating build/lib/django/contrib/contenttypes/locale/cy
2025-04-22 20:54:03,668 root INFO creating build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,669 root INFO copying django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,669 root INFO copying django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,669 root INFO creating build/lib/django/contrib/contenttypes/locale/da
2025-04-22 20:54:03,669 root INFO creating build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES
2025-04-22 20:54:03,669 root INFO copying django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES
2025-04-22 20:54:03,669 root INFO copying django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES
2025-04-22 20:54:03,669 root INFO creating build/lib/django/contrib/contenttypes/locale/de
2025-04-22 20:54:03,669 root INFO creating build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES
2025-04-22 20:54:03,669 root INFO copying django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES
2025-04-22 20:54:03,670 root INFO copying django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES
2025-04-22 20:54:03,670 root INFO creating build/lib/django/contrib/contenttypes/locale/dsb
2025-04-22 20:54:03,670 root INFO creating build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,670 root INFO copying django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,670 root INFO copying django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,670 root INFO creating build/lib/django/contrib/contenttypes/locale/el
2025-04-22 20:54:03,670 root INFO creating build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES
2025-04-22 20:54:03,670 root INFO copying django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES
2025-04-22 20:54:03,671 root INFO copying django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES
2025-04-22 20:54:03,671 root INFO creating build/lib/django/contrib/contenttypes/locale/en
2025-04-22 20:54:03,671 root INFO creating build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES
2025-04-22 20:54:03,671 root INFO copying django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES
2025-04-22 20:54:03,671 root INFO copying django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES
2025-04-22 20:54:03,671 root INFO creating build/lib/django/contrib/contenttypes/locale/en_AU
2025-04-22 20:54:03,671 root INFO creating build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:03,671 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 20:54:03,672 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 20:54:03,672 root INFO creating build/lib/django/contrib/contenttypes/locale/en_GB
2025-04-22 20:54:03,672 root INFO creating build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:03,672 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 20:54:03,672 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 20:54:03,672 root INFO creating build/lib/django/contrib/contenttypes/locale/eo
2025-04-22 20:54:03,672 root INFO creating build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,672 root INFO copying django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,673 root INFO copying django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,673 root INFO creating build/lib/django/contrib/contenttypes/locale/es
2025-04-22 20:54:03,673 root INFO creating build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES
2025-04-22 20:54:03,673 root INFO copying django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES
2025-04-22 20:54:03,673 root INFO copying django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES
2025-04-22 20:54:03,673 root INFO creating build/lib/django/contrib/contenttypes/locale/es_AR
2025-04-22 20:54:03,673 root INFO creating build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:03,673 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 20:54:03,674 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 20:54:03,674 root INFO creating build/lib/django/contrib/contenttypes/locale/es_CO
2025-04-22 20:54:03,674 root INFO creating build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:03,674 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 20:54:03,674 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 20:54:03,674 root INFO creating build/lib/django/contrib/contenttypes/locale/es_MX
2025-04-22 20:54:03,674 root INFO creating build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:03,674 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 20:54:03,674 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 20:54:03,675 root INFO creating build/lib/django/contrib/contenttypes/locale/es_VE
2025-04-22 20:54:03,675 root INFO creating build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:03,675 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 20:54:03,675 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 20:54:03,675 root INFO creating build/lib/django/contrib/contenttypes/locale/et
2025-04-22 20:54:03,675 root INFO creating build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES
2025-04-22 20:54:03,675 root INFO copying django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES
2025-04-22 20:54:03,675 root INFO copying django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES
2025-04-22 20:54:03,676 root INFO creating build/lib/django/contrib/contenttypes/locale/eu
2025-04-22 20:54:03,676 root INFO creating build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,676 root INFO copying django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,676 root INFO copying django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,676 root INFO creating build/lib/django/contrib/contenttypes/locale/fa
2025-04-22 20:54:03,676 root INFO creating build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,676 root INFO copying django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,676 root INFO copying django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,676 root INFO creating build/lib/django/contrib/contenttypes/locale/fi
2025-04-22 20:54:03,677 root INFO creating build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,677 root INFO copying django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,677 root INFO copying django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,677 root INFO creating build/lib/django/contrib/contenttypes/locale/fr
2025-04-22 20:54:03,677 root INFO creating build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,677 root INFO copying django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,677 root INFO copying django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,677 root INFO creating build/lib/django/contrib/contenttypes/locale/fy
2025-04-22 20:54:03,678 root INFO creating build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,678 root INFO copying django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,678 root INFO copying django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,678 root INFO creating build/lib/django/contrib/contenttypes/locale/ga
2025-04-22 20:54:03,678 root INFO creating build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,678 root INFO copying django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,678 root INFO copying django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,678 root INFO creating build/lib/django/contrib/contenttypes/locale/gd
2025-04-22 20:54:03,679 root INFO creating build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,679 root INFO copying django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,679 root INFO copying django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,679 root INFO creating build/lib/django/contrib/contenttypes/locale/gl
2025-04-22 20:54:03,679 root INFO creating build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,679 root INFO copying django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,679 root INFO copying django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,679 root INFO creating build/lib/django/contrib/contenttypes/locale/he
2025-04-22 20:54:03,680 root INFO creating build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES
2025-04-22 20:54:03,680 root INFO copying django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES
2025-04-22 20:54:03,680 root INFO copying django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES
2025-04-22 20:54:03,680 root INFO creating build/lib/django/contrib/contenttypes/locale/hi
2025-04-22 20:54:03,680 root INFO creating build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,680 root INFO copying django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,680 root INFO copying django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,680 root INFO creating build/lib/django/contrib/contenttypes/locale/hr
2025-04-22 20:54:03,681 root INFO creating build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,681 root INFO copying django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,681 root INFO copying django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,681 root INFO creating build/lib/django/contrib/contenttypes/locale/hsb
2025-04-22 20:54:03,681 root INFO creating build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,681 root INFO copying django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,681 root INFO copying django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,681 root INFO creating build/lib/django/contrib/contenttypes/locale/hu
2025-04-22 20:54:03,682 root INFO creating build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,682 root INFO copying django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,682 root INFO copying django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,682 root INFO creating build/lib/django/contrib/contenttypes/locale/hy
2025-04-22 20:54:03,682 root INFO creating build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,682 root INFO copying django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,682 root INFO copying django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,682 root INFO creating build/lib/django/contrib/contenttypes/locale/ia
2025-04-22 20:54:03,682 root INFO creating build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,683 root INFO copying django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,683 root INFO copying django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,683 root INFO creating build/lib/django/contrib/contenttypes/locale/id
2025-04-22 20:54:03,683 root INFO creating build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES
2025-04-22 20:54:03,683 root INFO copying django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES
2025-04-22 20:54:03,683 root INFO copying django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES
2025-04-22 20:54:03,683 root INFO creating build/lib/django/contrib/contenttypes/locale/io
2025-04-22 20:54:03,683 root INFO creating build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES
2025-04-22 20:54:03,684 root INFO copying django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES
2025-04-22 20:54:03,684 root INFO copying django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES
2025-04-22 20:54:03,684 root INFO creating build/lib/django/contrib/contenttypes/locale/is
2025-04-22 20:54:03,684 root INFO creating build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES
2025-04-22 20:54:03,684 root INFO copying django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES
2025-04-22 20:54:03,684 root INFO copying django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES
2025-04-22 20:54:03,684 root INFO creating build/lib/django/contrib/contenttypes/locale/it
2025-04-22 20:54:03,684 root INFO creating build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES
2025-04-22 20:54:03,685 root INFO copying django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES
2025-04-22 20:54:03,685 root INFO copying django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES
2025-04-22 20:54:03,685 root INFO creating build/lib/django/contrib/contenttypes/locale/ja
2025-04-22 20:54:03,685 root INFO creating build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,685 root INFO copying django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,685 root INFO copying django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,685 root INFO creating build/lib/django/contrib/contenttypes/locale/ka
2025-04-22 20:54:03,685 root INFO creating build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,685 root INFO copying django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,686 root INFO copying django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,686 root INFO creating build/lib/django/contrib/contenttypes/locale/kk
2025-04-22 20:54:03,686 root INFO creating build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,686 root INFO copying django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,686 root INFO copying django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,686 root INFO creating build/lib/django/contrib/contenttypes/locale/km
2025-04-22 20:54:03,686 root INFO creating build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES
2025-04-22 20:54:03,686 root INFO copying django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES
2025-04-22 20:54:03,687 root INFO copying django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES
2025-04-22 20:54:03,687 root INFO creating build/lib/django/contrib/contenttypes/locale/kn
2025-04-22 20:54:03,687 root INFO creating build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,687 root INFO copying django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,687 root INFO copying django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,687 root INFO creating build/lib/django/contrib/contenttypes/locale/ko
2025-04-22 20:54:03,687 root INFO creating build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,687 root INFO copying django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,688 root INFO copying django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,688 root INFO creating build/lib/django/contrib/contenttypes/locale/ky
2025-04-22 20:54:03,688 root INFO creating build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,688 root INFO copying django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,688 root INFO copying django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,688 root INFO creating build/lib/django/contrib/contenttypes/locale/lb
2025-04-22 20:54:03,688 root INFO creating build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,688 root INFO copying django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,689 root INFO copying django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,689 root INFO creating build/lib/django/contrib/contenttypes/locale/lt
2025-04-22 20:54:03,689 root INFO creating build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,689 root INFO copying django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,689 root INFO copying django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,689 root INFO creating build/lib/django/contrib/contenttypes/locale/lv
2025-04-22 20:54:03,689 root INFO creating build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,689 root INFO copying django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,690 root INFO copying django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,690 root INFO creating build/lib/django/contrib/contenttypes/locale/mk
2025-04-22 20:54:03,690 root INFO creating build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,690 root INFO copying django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,690 root INFO copying django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,690 root INFO creating build/lib/django/contrib/contenttypes/locale/ml
2025-04-22 20:54:03,690 root INFO creating build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,690 root INFO copying django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,691 root INFO copying django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,691 root INFO creating build/lib/django/contrib/contenttypes/locale/mn
2025-04-22 20:54:03,691 root INFO creating build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,691 root INFO copying django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,691 root INFO copying django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,691 root INFO creating build/lib/django/contrib/contenttypes/locale/mr
2025-04-22 20:54:03,691 root INFO creating build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,691 root INFO copying django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,692 root INFO copying django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,692 root INFO creating build/lib/django/contrib/contenttypes/locale/ms
2025-04-22 20:54:03,692 root INFO creating build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,692 root INFO copying django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,692 root INFO copying django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,692 root INFO creating build/lib/django/contrib/contenttypes/locale/my
2025-04-22 20:54:03,692 root INFO creating build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES
2025-04-22 20:54:03,692 root INFO copying django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES
2025-04-22 20:54:03,693 root INFO copying django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES
2025-04-22 20:54:03,693 root INFO creating build/lib/django/contrib/contenttypes/locale/nb
2025-04-22 20:54:03,693 root INFO creating build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,693 root INFO copying django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,693 root INFO copying django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,693 root INFO creating build/lib/django/contrib/contenttypes/locale/ne
2025-04-22 20:54:03,693 root INFO creating build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,693 root INFO copying django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,694 root INFO copying django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,694 root INFO creating build/lib/django/contrib/contenttypes/locale/nl
2025-04-22 20:54:03,694 root INFO creating build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,694 root INFO copying django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,694 root INFO copying django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,694 root INFO creating build/lib/django/contrib/contenttypes/locale/nn
2025-04-22 20:54:03,694 root INFO creating build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,694 root INFO copying django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,695 root INFO copying django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,695 root INFO creating build/lib/django/contrib/contenttypes/locale/os
2025-04-22 20:54:03,695 root INFO creating build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES
2025-04-22 20:54:03,695 root INFO copying django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES
2025-04-22 20:54:03,695 root INFO copying django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES
2025-04-22 20:54:03,695 root INFO creating build/lib/django/contrib/contenttypes/locale/pa
2025-04-22 20:54:03,695 root INFO creating build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,695 root INFO copying django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,695 root INFO copying django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,696 root INFO creating build/lib/django/contrib/contenttypes/locale/pl
2025-04-22 20:54:03,696 root INFO creating build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,696 root INFO copying django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,696 root INFO copying django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,696 root INFO creating build/lib/django/contrib/contenttypes/locale/pt
2025-04-22 20:54:03,696 root INFO creating build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,696 root INFO copying django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,696 root INFO copying django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,697 root INFO creating build/lib/django/contrib/contenttypes/locale/pt_BR
2025-04-22 20:54:03,697 root INFO creating build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:03,697 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 20:54:03,697 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 20:54:03,697 root INFO creating build/lib/django/contrib/contenttypes/locale/ro
2025-04-22 20:54:03,697 root INFO creating build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,697 root INFO copying django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,697 root INFO copying django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,698 root INFO creating build/lib/django/contrib/contenttypes/locale/ru
2025-04-22 20:54:03,698 root INFO creating build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,698 root INFO copying django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,698 root INFO copying django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,698 root INFO creating build/lib/django/contrib/contenttypes/locale/sk
2025-04-22 20:54:03,698 root INFO creating build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,698 root INFO copying django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,699 root INFO copying django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,699 root INFO creating build/lib/django/contrib/contenttypes/locale/sl
2025-04-22 20:54:03,699 root INFO creating build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,699 root INFO copying django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,699 root INFO copying django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,699 root INFO creating build/lib/django/contrib/contenttypes/locale/sq
2025-04-22 20:54:03,699 root INFO creating build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,699 root INFO copying django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,700 root INFO copying django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,700 root INFO creating build/lib/django/contrib/contenttypes/locale/sr
2025-04-22 20:54:03,700 root INFO creating build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,700 root INFO copying django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,700 root INFO copying django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,700 root INFO creating build/lib/django/contrib/contenttypes/locale/sr_Latn
2025-04-22 20:54:03,700 root INFO creating build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:03,700 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 20:54:03,701 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 20:54:03,701 root INFO creating build/lib/django/contrib/contenttypes/locale/sv
2025-04-22 20:54:03,701 root INFO creating build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,701 root INFO copying django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,701 root INFO copying django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,701 root INFO creating build/lib/django/contrib/contenttypes/locale/sw
2025-04-22 20:54:03,701 root INFO creating build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,701 root INFO copying django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,702 root INFO copying django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,702 root INFO creating build/lib/django/contrib/contenttypes/locale/ta
2025-04-22 20:54:03,702 root INFO creating build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,702 root INFO copying django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,702 root INFO copying django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,702 root INFO creating build/lib/django/contrib/contenttypes/locale/te
2025-04-22 20:54:03,702 root INFO creating build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES
2025-04-22 20:54:03,702 root INFO copying django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES
2025-04-22 20:54:03,703 root INFO copying django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES
2025-04-22 20:54:03,703 root INFO creating build/lib/django/contrib/contenttypes/locale/tg
2025-04-22 20:54:03,703 root INFO creating build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,703 root INFO copying django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,703 root INFO copying django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,703 root INFO creating build/lib/django/contrib/contenttypes/locale/th
2025-04-22 20:54:03,703 root INFO creating build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES
2025-04-22 20:54:03,703 root INFO copying django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES
2025-04-22 20:54:03,704 root INFO copying django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES
2025-04-22 20:54:03,704 root INFO creating build/lib/django/contrib/contenttypes/locale/tk
2025-04-22 20:54:03,704 root INFO creating build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,704 root INFO copying django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,704 root INFO copying django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,704 root INFO creating build/lib/django/contrib/contenttypes/locale/tr
2025-04-22 20:54:03,704 root INFO creating build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,704 root INFO copying django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,705 root INFO copying django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,705 root INFO creating build/lib/django/contrib/contenttypes/locale/tt
2025-04-22 20:54:03,705 root INFO creating build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,705 root INFO copying django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,705 root INFO copying django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,705 root INFO creating build/lib/django/contrib/contenttypes/locale/udm
2025-04-22 20:54:03,705 root INFO creating build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,705 root INFO copying django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,706 root INFO copying django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,706 root INFO creating build/lib/django/contrib/contenttypes/locale/uk
2025-04-22 20:54:03,706 root INFO creating build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,706 root INFO copying django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,706 root INFO copying django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,706 root INFO creating build/lib/django/contrib/contenttypes/locale/ur
2025-04-22 20:54:03,706 root INFO creating build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,706 root INFO copying django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,707 root INFO copying django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,707 root INFO creating build/lib/django/contrib/contenttypes/locale/vi
2025-04-22 20:54:03,707 root INFO creating build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,707 root INFO copying django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,707 root INFO copying django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,707 root INFO creating build/lib/django/contrib/contenttypes/locale/zh_Hans
2025-04-22 20:54:03,707 root INFO creating build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:03,707 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 20:54:03,708 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 20:54:03,708 root INFO creating build/lib/django/contrib/contenttypes/locale/zh_Hant
2025-04-22 20:54:03,708 root INFO creating build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:03,708 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 20:54:03,708 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 20:54:03,708 root INFO creating build/lib/django/contrib/redirects/locale
2025-04-22 20:54:03,708 root INFO creating build/lib/django/contrib/redirects/locale/af
2025-04-22 20:54:03,708 root INFO creating build/lib/django/contrib/redirects/locale/af/LC_MESSAGES
2025-04-22 20:54:03,708 root INFO copying django/contrib/redirects/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/af/LC_MESSAGES
2025-04-22 20:54:03,709 root INFO copying django/contrib/redirects/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/af/LC_MESSAGES
2025-04-22 20:54:03,709 root INFO creating build/lib/django/contrib/redirects/locale/ar
2025-04-22 20:54:03,709 root INFO creating build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,709 root INFO copying django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,709 root INFO copying django/contrib/redirects/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,709 root INFO creating build/lib/django/contrib/redirects/locale/ar_DZ
2025-04-22 20:54:03,709 root INFO creating build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:03,709 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 20:54:03,710 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 20:54:03,710 root INFO creating build/lib/django/contrib/redirects/locale/ast
2025-04-22 20:54:03,710 root INFO creating build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,710 root INFO copying django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,710 root INFO copying django/contrib/redirects/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,710 root INFO creating build/lib/django/contrib/redirects/locale/az
2025-04-22 20:54:03,710 root INFO creating build/lib/django/contrib/redirects/locale/az/LC_MESSAGES
2025-04-22 20:54:03,710 root INFO copying django/contrib/redirects/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/az/LC_MESSAGES
2025-04-22 20:54:03,711 root INFO copying django/contrib/redirects/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/az/LC_MESSAGES
2025-04-22 20:54:03,711 root INFO creating build/lib/django/contrib/redirects/locale/be
2025-04-22 20:54:03,711 root INFO creating build/lib/django/contrib/redirects/locale/be/LC_MESSAGES
2025-04-22 20:54:03,711 root INFO copying django/contrib/redirects/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/be/LC_MESSAGES
2025-04-22 20:54:03,711 root INFO copying django/contrib/redirects/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/be/LC_MESSAGES
2025-04-22 20:54:03,711 root INFO creating build/lib/django/contrib/redirects/locale/bg
2025-04-22 20:54:03,711 root INFO creating build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,711 root INFO copying django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,712 root INFO copying django/contrib/redirects/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,712 root INFO creating build/lib/django/contrib/redirects/locale/bn
2025-04-22 20:54:03,712 root INFO creating build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,712 root INFO copying django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,712 root INFO copying django/contrib/redirects/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,712 root INFO creating build/lib/django/contrib/redirects/locale/br
2025-04-22 20:54:03,712 root INFO creating build/lib/django/contrib/redirects/locale/br/LC_MESSAGES
2025-04-22 20:54:03,713 root INFO copying django/contrib/redirects/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/br/LC_MESSAGES
2025-04-22 20:54:03,713 root INFO copying django/contrib/redirects/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/br/LC_MESSAGES
2025-04-22 20:54:03,713 root INFO creating build/lib/django/contrib/redirects/locale/bs
2025-04-22 20:54:03,713 root INFO creating build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,713 root INFO copying django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,713 root INFO copying django/contrib/redirects/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,713 root INFO creating build/lib/django/contrib/redirects/locale/ca
2025-04-22 20:54:03,713 root INFO creating build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,713 root INFO copying django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,714 root INFO copying django/contrib/redirects/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,714 root INFO creating build/lib/django/contrib/redirects/locale/ckb
2025-04-22 20:54:03,714 root INFO creating build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,714 root INFO copying django/contrib/redirects/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,714 root INFO copying django/contrib/redirects/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,714 root INFO creating build/lib/django/contrib/redirects/locale/cs
2025-04-22 20:54:03,714 root INFO creating build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,714 root INFO copying django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,715 root INFO copying django/contrib/redirects/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,715 root INFO creating build/lib/django/contrib/redirects/locale/cy
2025-04-22 20:54:03,715 root INFO creating build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,715 root INFO copying django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,715 root INFO copying django/contrib/redirects/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,715 root INFO creating build/lib/django/contrib/redirects/locale/da
2025-04-22 20:54:03,715 root INFO creating build/lib/django/contrib/redirects/locale/da/LC_MESSAGES
2025-04-22 20:54:03,715 root INFO copying django/contrib/redirects/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/da/LC_MESSAGES
2025-04-22 20:54:03,716 root INFO copying django/contrib/redirects/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/da/LC_MESSAGES
2025-04-22 20:54:03,716 root INFO creating build/lib/django/contrib/redirects/locale/de
2025-04-22 20:54:03,716 root INFO creating build/lib/django/contrib/redirects/locale/de/LC_MESSAGES
2025-04-22 20:54:03,716 root INFO copying django/contrib/redirects/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/de/LC_MESSAGES
2025-04-22 20:54:03,716 root INFO copying django/contrib/redirects/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/de/LC_MESSAGES
2025-04-22 20:54:03,716 root INFO creating build/lib/django/contrib/redirects/locale/dsb
2025-04-22 20:54:03,716 root INFO creating build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,716 root INFO copying django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,717 root INFO copying django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,717 root INFO creating build/lib/django/contrib/redirects/locale/el
2025-04-22 20:54:03,717 root INFO creating build/lib/django/contrib/redirects/locale/el/LC_MESSAGES
2025-04-22 20:54:03,717 root INFO copying django/contrib/redirects/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/el/LC_MESSAGES
2025-04-22 20:54:03,717 root INFO copying django/contrib/redirects/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/el/LC_MESSAGES
2025-04-22 20:54:03,717 root INFO creating build/lib/django/contrib/redirects/locale/en
2025-04-22 20:54:03,717 root INFO creating build/lib/django/contrib/redirects/locale/en/LC_MESSAGES
2025-04-22 20:54:03,717 root INFO copying django/contrib/redirects/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/en/LC_MESSAGES
2025-04-22 20:54:03,718 root INFO copying django/contrib/redirects/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/en/LC_MESSAGES
2025-04-22 20:54:03,718 root INFO creating build/lib/django/contrib/redirects/locale/en_AU
2025-04-22 20:54:03,718 root INFO creating build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:03,718 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 20:54:03,718 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 20:54:03,718 root INFO creating build/lib/django/contrib/redirects/locale/en_GB
2025-04-22 20:54:03,718 root INFO creating build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:03,718 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 20:54:03,719 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 20:54:03,719 root INFO creating build/lib/django/contrib/redirects/locale/eo
2025-04-22 20:54:03,719 root INFO creating build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,719 root INFO copying django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,719 root INFO copying django/contrib/redirects/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,719 root INFO creating build/lib/django/contrib/redirects/locale/es
2025-04-22 20:54:03,719 root INFO creating build/lib/django/contrib/redirects/locale/es/LC_MESSAGES
2025-04-22 20:54:03,719 root INFO copying django/contrib/redirects/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es/LC_MESSAGES
2025-04-22 20:54:03,720 root INFO copying django/contrib/redirects/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es/LC_MESSAGES
2025-04-22 20:54:03,720 root INFO creating build/lib/django/contrib/redirects/locale/es_AR
2025-04-22 20:54:03,720 root INFO creating build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:03,720 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 20:54:03,720 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 20:54:03,720 root INFO creating build/lib/django/contrib/redirects/locale/es_CO
2025-04-22 20:54:03,720 root INFO creating build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:03,720 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 20:54:03,721 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 20:54:03,721 root INFO creating build/lib/django/contrib/redirects/locale/es_MX
2025-04-22 20:54:03,721 root INFO creating build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:03,721 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 20:54:03,721 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 20:54:03,721 root INFO creating build/lib/django/contrib/redirects/locale/es_VE
2025-04-22 20:54:03,721 root INFO creating build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:03,721 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 20:54:03,722 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 20:54:03,722 root INFO creating build/lib/django/contrib/redirects/locale/et
2025-04-22 20:54:03,722 root INFO creating build/lib/django/contrib/redirects/locale/et/LC_MESSAGES
2025-04-22 20:54:03,722 root INFO copying django/contrib/redirects/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/et/LC_MESSAGES
2025-04-22 20:54:03,722 root INFO copying django/contrib/redirects/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/et/LC_MESSAGES
2025-04-22 20:54:03,722 root INFO creating build/lib/django/contrib/redirects/locale/eu
2025-04-22 20:54:03,722 root INFO creating build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,722 root INFO copying django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,723 root INFO copying django/contrib/redirects/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,723 root INFO creating build/lib/django/contrib/redirects/locale/fa
2025-04-22 20:54:03,723 root INFO creating build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,723 root INFO copying django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,723 root INFO copying django/contrib/redirects/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,723 root INFO creating build/lib/django/contrib/redirects/locale/fi
2025-04-22 20:54:03,723 root INFO creating build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,723 root INFO copying django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,724 root INFO copying django/contrib/redirects/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,724 root INFO creating build/lib/django/contrib/redirects/locale/fr
2025-04-22 20:54:03,724 root INFO creating build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,724 root INFO copying django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,724 root INFO copying django/contrib/redirects/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,724 root INFO creating build/lib/django/contrib/redirects/locale/fy
2025-04-22 20:54:03,724 root INFO creating build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,724 root INFO copying django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,725 root INFO copying django/contrib/redirects/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,725 root INFO creating build/lib/django/contrib/redirects/locale/ga
2025-04-22 20:54:03,725 root INFO creating build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,725 root INFO copying django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,725 root INFO copying django/contrib/redirects/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,725 root INFO creating build/lib/django/contrib/redirects/locale/gd
2025-04-22 20:54:03,725 root INFO creating build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,725 root INFO copying django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,726 root INFO copying django/contrib/redirects/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,726 root INFO creating build/lib/django/contrib/redirects/locale/gl
2025-04-22 20:54:03,726 root INFO creating build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,726 root INFO copying django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,726 root INFO copying django/contrib/redirects/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,726 root INFO creating build/lib/django/contrib/redirects/locale/he
2025-04-22 20:54:03,726 root INFO creating build/lib/django/contrib/redirects/locale/he/LC_MESSAGES
2025-04-22 20:54:03,726 root INFO copying django/contrib/redirects/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/he/LC_MESSAGES
2025-04-22 20:54:03,727 root INFO copying django/contrib/redirects/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/he/LC_MESSAGES
2025-04-22 20:54:03,727 root INFO creating build/lib/django/contrib/redirects/locale/hi
2025-04-22 20:54:03,727 root INFO creating build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,727 root INFO copying django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,727 root INFO copying django/contrib/redirects/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,727 root INFO creating build/lib/django/contrib/redirects/locale/hr
2025-04-22 20:54:03,727 root INFO creating build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,727 root INFO copying django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,728 root INFO copying django/contrib/redirects/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,728 root INFO creating build/lib/django/contrib/redirects/locale/hsb
2025-04-22 20:54:03,728 root INFO creating build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,728 root INFO copying django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,728 root INFO copying django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,728 root INFO creating build/lib/django/contrib/redirects/locale/hu
2025-04-22 20:54:03,728 root INFO creating build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,728 root INFO copying django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,729 root INFO copying django/contrib/redirects/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,729 root INFO creating build/lib/django/contrib/redirects/locale/hy
2025-04-22 20:54:03,729 root INFO creating build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,729 root INFO copying django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,729 root INFO copying django/contrib/redirects/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,729 root INFO creating build/lib/django/contrib/redirects/locale/ia
2025-04-22 20:54:03,729 root INFO creating build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,729 root INFO copying django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,730 root INFO copying django/contrib/redirects/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,730 root INFO creating build/lib/django/contrib/redirects/locale/id
2025-04-22 20:54:03,730 root INFO creating build/lib/django/contrib/redirects/locale/id/LC_MESSAGES
2025-04-22 20:54:03,730 root INFO copying django/contrib/redirects/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/id/LC_MESSAGES
2025-04-22 20:54:03,730 root INFO copying django/contrib/redirects/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/id/LC_MESSAGES
2025-04-22 20:54:03,730 root INFO creating build/lib/django/contrib/redirects/locale/io
2025-04-22 20:54:03,730 root INFO creating build/lib/django/contrib/redirects/locale/io/LC_MESSAGES
2025-04-22 20:54:03,730 root INFO copying django/contrib/redirects/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/io/LC_MESSAGES
2025-04-22 20:54:03,731 root INFO copying django/contrib/redirects/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/io/LC_MESSAGES
2025-04-22 20:54:03,731 root INFO creating build/lib/django/contrib/redirects/locale/is
2025-04-22 20:54:03,731 root INFO creating build/lib/django/contrib/redirects/locale/is/LC_MESSAGES
2025-04-22 20:54:03,731 root INFO copying django/contrib/redirects/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/is/LC_MESSAGES
2025-04-22 20:54:03,731 root INFO copying django/contrib/redirects/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/is/LC_MESSAGES
2025-04-22 20:54:03,731 root INFO creating build/lib/django/contrib/redirects/locale/it
2025-04-22 20:54:03,731 root INFO creating build/lib/django/contrib/redirects/locale/it/LC_MESSAGES
2025-04-22 20:54:03,731 root INFO copying django/contrib/redirects/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/it/LC_MESSAGES
2025-04-22 20:54:03,732 root INFO copying django/contrib/redirects/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/it/LC_MESSAGES
2025-04-22 20:54:03,732 root INFO creating build/lib/django/contrib/redirects/locale/ja
2025-04-22 20:54:03,732 root INFO creating build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,732 root INFO copying django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,732 root INFO copying django/contrib/redirects/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,732 root INFO creating build/lib/django/contrib/redirects/locale/ka
2025-04-22 20:54:03,732 root INFO creating build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,732 root INFO copying django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,733 root INFO copying django/contrib/redirects/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,733 root INFO creating build/lib/django/contrib/redirects/locale/kab
2025-04-22 20:54:03,733 root INFO creating build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,733 root INFO copying django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,733 root INFO copying django/contrib/redirects/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,733 root INFO creating build/lib/django/contrib/redirects/locale/kk
2025-04-22 20:54:03,733 root INFO creating build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,733 root INFO copying django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,733 root INFO copying django/contrib/redirects/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,734 root INFO creating build/lib/django/contrib/redirects/locale/km
2025-04-22 20:54:03,734 root INFO creating build/lib/django/contrib/redirects/locale/km/LC_MESSAGES
2025-04-22 20:54:03,734 root INFO copying django/contrib/redirects/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/km/LC_MESSAGES
2025-04-22 20:54:03,734 root INFO copying django/contrib/redirects/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/km/LC_MESSAGES
2025-04-22 20:54:03,734 root INFO creating build/lib/django/contrib/redirects/locale/kn
2025-04-22 20:54:03,734 root INFO creating build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,734 root INFO copying django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,734 root INFO copying django/contrib/redirects/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,735 root INFO creating build/lib/django/contrib/redirects/locale/ko
2025-04-22 20:54:03,735 root INFO creating build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,735 root INFO copying django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,735 root INFO copying django/contrib/redirects/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,735 root INFO creating build/lib/django/contrib/redirects/locale/ky
2025-04-22 20:54:03,735 root INFO creating build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,735 root INFO copying django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,736 root INFO copying django/contrib/redirects/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,736 root INFO creating build/lib/django/contrib/redirects/locale/lb
2025-04-22 20:54:03,736 root INFO creating build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,736 root INFO copying django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,736 root INFO copying django/contrib/redirects/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,736 root INFO creating build/lib/django/contrib/redirects/locale/lt
2025-04-22 20:54:03,736 root INFO creating build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,736 root INFO copying django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,737 root INFO copying django/contrib/redirects/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,737 root INFO creating build/lib/django/contrib/redirects/locale/lv
2025-04-22 20:54:03,737 root INFO creating build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,737 root INFO copying django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,737 root INFO copying django/contrib/redirects/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,737 root INFO creating build/lib/django/contrib/redirects/locale/mk
2025-04-22 20:54:03,737 root INFO creating build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,737 root INFO copying django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,738 root INFO copying django/contrib/redirects/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,738 root INFO creating build/lib/django/contrib/redirects/locale/ml
2025-04-22 20:54:03,738 root INFO creating build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,738 root INFO copying django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,738 root INFO copying django/contrib/redirects/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,738 root INFO creating build/lib/django/contrib/redirects/locale/mn
2025-04-22 20:54:03,738 root INFO creating build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,738 root INFO copying django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,739 root INFO copying django/contrib/redirects/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,739 root INFO creating build/lib/django/contrib/redirects/locale/mr
2025-04-22 20:54:03,739 root INFO creating build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,739 root INFO copying django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,739 root INFO copying django/contrib/redirects/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,739 root INFO creating build/lib/django/contrib/redirects/locale/ms
2025-04-22 20:54:03,739 root INFO creating build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,739 root INFO copying django/contrib/redirects/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,740 root INFO copying django/contrib/redirects/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,740 root INFO creating build/lib/django/contrib/redirects/locale/my
2025-04-22 20:54:03,740 root INFO creating build/lib/django/contrib/redirects/locale/my/LC_MESSAGES
2025-04-22 20:54:03,740 root INFO copying django/contrib/redirects/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/my/LC_MESSAGES
2025-04-22 20:54:03,740 root INFO copying django/contrib/redirects/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/my/LC_MESSAGES
2025-04-22 20:54:03,740 root INFO creating build/lib/django/contrib/redirects/locale/nb
2025-04-22 20:54:03,740 root INFO creating build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,740 root INFO copying django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,741 root INFO copying django/contrib/redirects/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,741 root INFO creating build/lib/django/contrib/redirects/locale/ne
2025-04-22 20:54:03,741 root INFO creating build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,741 root INFO copying django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,741 root INFO copying django/contrib/redirects/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,741 root INFO creating build/lib/django/contrib/redirects/locale/nl
2025-04-22 20:54:03,741 root INFO creating build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,741 root INFO copying django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,742 root INFO copying django/contrib/redirects/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,742 root INFO creating build/lib/django/contrib/redirects/locale/nn
2025-04-22 20:54:03,742 root INFO creating build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,742 root INFO copying django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,742 root INFO copying django/contrib/redirects/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,742 root INFO creating build/lib/django/contrib/redirects/locale/os
2025-04-22 20:54:03,742 root INFO creating build/lib/django/contrib/redirects/locale/os/LC_MESSAGES
2025-04-22 20:54:03,742 root INFO copying django/contrib/redirects/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/os/LC_MESSAGES
2025-04-22 20:54:03,743 root INFO copying django/contrib/redirects/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/os/LC_MESSAGES
2025-04-22 20:54:03,743 root INFO creating build/lib/django/contrib/redirects/locale/pa
2025-04-22 20:54:03,743 root INFO creating build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,743 root INFO copying django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,743 root INFO copying django/contrib/redirects/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,743 root INFO creating build/lib/django/contrib/redirects/locale/pl
2025-04-22 20:54:03,743 root INFO creating build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,743 root INFO copying django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,744 root INFO copying django/contrib/redirects/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,744 root INFO creating build/lib/django/contrib/redirects/locale/pt
2025-04-22 20:54:03,744 root INFO creating build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,744 root INFO copying django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,744 root INFO copying django/contrib/redirects/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,744 root INFO creating build/lib/django/contrib/redirects/locale/pt_BR
2025-04-22 20:54:03,744 root INFO creating build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:03,744 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 20:54:03,745 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 20:54:03,745 root INFO creating build/lib/django/contrib/redirects/locale/ro
2025-04-22 20:54:03,745 root INFO creating build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,745 root INFO copying django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,745 root INFO copying django/contrib/redirects/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,745 root INFO creating build/lib/django/contrib/redirects/locale/ru
2025-04-22 20:54:03,746 root INFO creating build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,746 root INFO copying django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,746 root INFO copying django/contrib/redirects/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,746 root INFO creating build/lib/django/contrib/redirects/locale/sk
2025-04-22 20:54:03,746 root INFO creating build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,746 root INFO copying django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,746 root INFO copying django/contrib/redirects/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,746 root INFO creating build/lib/django/contrib/redirects/locale/sl
2025-04-22 20:54:03,747 root INFO creating build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,747 root INFO copying django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,747 root INFO copying django/contrib/redirects/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,747 root INFO creating build/lib/django/contrib/redirects/locale/sq
2025-04-22 20:54:03,747 root INFO creating build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,747 root INFO copying django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,747 root INFO copying django/contrib/redirects/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,747 root INFO creating build/lib/django/contrib/redirects/locale/sr
2025-04-22 20:54:03,748 root INFO creating build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,748 root INFO copying django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,748 root INFO copying django/contrib/redirects/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,748 root INFO creating build/lib/django/contrib/redirects/locale/sr_Latn
2025-04-22 20:54:03,748 root INFO creating build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:03,748 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 20:54:03,748 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 20:54:03,749 root INFO creating build/lib/django/contrib/redirects/locale/sv
2025-04-22 20:54:03,749 root INFO creating build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,749 root INFO copying django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,749 root INFO copying django/contrib/redirects/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,749 root INFO creating build/lib/django/contrib/redirects/locale/sw
2025-04-22 20:54:03,749 root INFO creating build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,749 root INFO copying django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,749 root INFO copying django/contrib/redirects/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,750 root INFO creating build/lib/django/contrib/redirects/locale/ta
2025-04-22 20:54:03,750 root INFO creating build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,750 root INFO copying django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,750 root INFO copying django/contrib/redirects/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,750 root INFO creating build/lib/django/contrib/redirects/locale/te
2025-04-22 20:54:03,750 root INFO creating build/lib/django/contrib/redirects/locale/te/LC_MESSAGES
2025-04-22 20:54:03,750 root INFO copying django/contrib/redirects/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/te/LC_MESSAGES
2025-04-22 20:54:03,750 root INFO copying django/contrib/redirects/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/te/LC_MESSAGES
2025-04-22 20:54:03,751 root INFO creating build/lib/django/contrib/redirects/locale/tg
2025-04-22 20:54:03,751 root INFO creating build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,751 root INFO copying django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,751 root INFO copying django/contrib/redirects/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,751 root INFO creating build/lib/django/contrib/redirects/locale/th
2025-04-22 20:54:03,751 root INFO creating build/lib/django/contrib/redirects/locale/th/LC_MESSAGES
2025-04-22 20:54:03,751 root INFO copying django/contrib/redirects/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/th/LC_MESSAGES
2025-04-22 20:54:03,751 root INFO copying django/contrib/redirects/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/th/LC_MESSAGES
2025-04-22 20:54:03,752 root INFO creating build/lib/django/contrib/redirects/locale/tk
2025-04-22 20:54:03,752 root INFO creating build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,752 root INFO copying django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,752 root INFO copying django/contrib/redirects/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,752 root INFO creating build/lib/django/contrib/redirects/locale/tr
2025-04-22 20:54:03,752 root INFO creating build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,752 root INFO copying django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,752 root INFO copying django/contrib/redirects/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,753 root INFO creating build/lib/django/contrib/redirects/locale/tt
2025-04-22 20:54:03,753 root INFO creating build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,753 root INFO copying django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,753 root INFO copying django/contrib/redirects/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,753 root INFO creating build/lib/django/contrib/redirects/locale/udm
2025-04-22 20:54:03,753 root INFO creating build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,753 root INFO copying django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,753 root INFO copying django/contrib/redirects/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,753 root INFO creating build/lib/django/contrib/redirects/locale/uk
2025-04-22 20:54:03,754 root INFO creating build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,754 root INFO copying django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,754 root INFO copying django/contrib/redirects/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,754 root INFO creating build/lib/django/contrib/redirects/locale/ur
2025-04-22 20:54:03,754 root INFO creating build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,754 root INFO copying django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,754 root INFO copying django/contrib/redirects/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,754 root INFO creating build/lib/django/contrib/redirects/locale/uz
2025-04-22 20:54:03,755 root INFO creating build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,755 root INFO copying django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,755 root INFO copying django/contrib/redirects/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,755 root INFO creating build/lib/django/contrib/redirects/locale/vi
2025-04-22 20:54:03,755 root INFO creating build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,755 root INFO copying django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,755 root INFO copying django/contrib/redirects/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,755 root INFO creating build/lib/django/contrib/redirects/locale/zh_Hans
2025-04-22 20:54:03,756 root INFO creating build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:03,756 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 20:54:03,756 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 20:54:03,756 root INFO creating build/lib/django/contrib/redirects/locale/zh_Hant
2025-04-22 20:54:03,756 root INFO creating build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:03,756 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 20:54:03,756 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 20:54:03,756 root INFO creating build/lib/django/contrib/sites/locale
2025-04-22 20:54:03,757 root INFO creating build/lib/django/contrib/sites/locale/af
2025-04-22 20:54:03,757 root INFO creating build/lib/django/contrib/sites/locale/af/LC_MESSAGES
2025-04-22 20:54:03,757 root INFO copying django/contrib/sites/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/af/LC_MESSAGES
2025-04-22 20:54:03,757 root INFO copying django/contrib/sites/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/af/LC_MESSAGES
2025-04-22 20:54:03,757 root INFO creating build/lib/django/contrib/sites/locale/ar
2025-04-22 20:54:03,757 root INFO creating build/lib/django/contrib/sites/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,757 root INFO copying django/contrib/sites/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,757 root INFO copying django/contrib/sites/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,757 root INFO creating build/lib/django/contrib/sites/locale/ar_DZ
2025-04-22 20:54:03,758 root INFO creating build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:03,758 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 20:54:03,758 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 20:54:03,758 root INFO creating build/lib/django/contrib/sites/locale/ast
2025-04-22 20:54:03,758 root INFO creating build/lib/django/contrib/sites/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,758 root INFO copying django/contrib/sites/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,758 root INFO copying django/contrib/sites/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,759 root INFO creating build/lib/django/contrib/sites/locale/az
2025-04-22 20:54:03,759 root INFO creating build/lib/django/contrib/sites/locale/az/LC_MESSAGES
2025-04-22 20:54:03,759 root INFO copying django/contrib/sites/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/az/LC_MESSAGES
2025-04-22 20:54:03,759 root INFO copying django/contrib/sites/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/az/LC_MESSAGES
2025-04-22 20:54:03,759 root INFO creating build/lib/django/contrib/sites/locale/be
2025-04-22 20:54:03,759 root INFO creating build/lib/django/contrib/sites/locale/be/LC_MESSAGES
2025-04-22 20:54:03,759 root INFO copying django/contrib/sites/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/be/LC_MESSAGES
2025-04-22 20:54:03,759 root INFO copying django/contrib/sites/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/be/LC_MESSAGES
2025-04-22 20:54:03,759 root INFO creating build/lib/django/contrib/sites/locale/bg
2025-04-22 20:54:03,760 root INFO creating build/lib/django/contrib/sites/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,760 root INFO copying django/contrib/sites/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,760 root INFO copying django/contrib/sites/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,760 root INFO creating build/lib/django/contrib/sites/locale/bn
2025-04-22 20:54:03,760 root INFO creating build/lib/django/contrib/sites/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,760 root INFO copying django/contrib/sites/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,760 root INFO copying django/contrib/sites/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,760 root INFO creating build/lib/django/contrib/sites/locale/br
2025-04-22 20:54:03,761 root INFO creating build/lib/django/contrib/sites/locale/br/LC_MESSAGES
2025-04-22 20:54:03,761 root INFO copying django/contrib/sites/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/br/LC_MESSAGES
2025-04-22 20:54:03,761 root INFO copying django/contrib/sites/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/br/LC_MESSAGES
2025-04-22 20:54:03,761 root INFO creating build/lib/django/contrib/sites/locale/bs
2025-04-22 20:54:03,761 root INFO creating build/lib/django/contrib/sites/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,761 root INFO copying django/contrib/sites/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,761 root INFO copying django/contrib/sites/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,761 root INFO creating build/lib/django/contrib/sites/locale/ca
2025-04-22 20:54:03,761 root INFO creating build/lib/django/contrib/sites/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,762 root INFO copying django/contrib/sites/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,762 root INFO copying django/contrib/sites/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,762 root INFO creating build/lib/django/contrib/sites/locale/ckb
2025-04-22 20:54:03,762 root INFO creating build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,762 root INFO copying django/contrib/sites/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,762 root INFO copying django/contrib/sites/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,762 root INFO creating build/lib/django/contrib/sites/locale/cs
2025-04-22 20:54:03,762 root INFO creating build/lib/django/contrib/sites/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,762 root INFO copying django/contrib/sites/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,763 root INFO copying django/contrib/sites/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,763 root INFO creating build/lib/django/contrib/sites/locale/cy
2025-04-22 20:54:03,763 root INFO creating build/lib/django/contrib/sites/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,763 root INFO copying django/contrib/sites/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,763 root INFO copying django/contrib/sites/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,763 root INFO creating build/lib/django/contrib/sites/locale/da
2025-04-22 20:54:03,763 root INFO creating build/lib/django/contrib/sites/locale/da/LC_MESSAGES
2025-04-22 20:54:03,763 root INFO copying django/contrib/sites/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/da/LC_MESSAGES
2025-04-22 20:54:03,764 root INFO copying django/contrib/sites/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/da/LC_MESSAGES
2025-04-22 20:54:03,764 root INFO creating build/lib/django/contrib/sites/locale/de
2025-04-22 20:54:03,764 root INFO creating build/lib/django/contrib/sites/locale/de/LC_MESSAGES
2025-04-22 20:54:03,764 root INFO copying django/contrib/sites/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/de/LC_MESSAGES
2025-04-22 20:54:03,764 root INFO copying django/contrib/sites/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/de/LC_MESSAGES
2025-04-22 20:54:03,764 root INFO creating build/lib/django/contrib/sites/locale/dsb
2025-04-22 20:54:03,764 root INFO creating build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,764 root INFO copying django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,765 root INFO copying django/contrib/sites/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,765 root INFO creating build/lib/django/contrib/sites/locale/el
2025-04-22 20:54:03,765 root INFO creating build/lib/django/contrib/sites/locale/el/LC_MESSAGES
2025-04-22 20:54:03,765 root INFO copying django/contrib/sites/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/el/LC_MESSAGES
2025-04-22 20:54:03,765 root INFO copying django/contrib/sites/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/el/LC_MESSAGES
2025-04-22 20:54:03,765 root INFO creating build/lib/django/contrib/sites/locale/en
2025-04-22 20:54:03,765 root INFO creating build/lib/django/contrib/sites/locale/en/LC_MESSAGES
2025-04-22 20:54:03,765 root INFO copying django/contrib/sites/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/en/LC_MESSAGES
2025-04-22 20:54:03,766 root INFO copying django/contrib/sites/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/en/LC_MESSAGES
2025-04-22 20:54:03,766 root INFO creating build/lib/django/contrib/sites/locale/en_AU
2025-04-22 20:54:03,766 root INFO creating build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:03,766 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 20:54:03,766 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 20:54:03,766 root INFO creating build/lib/django/contrib/sites/locale/en_GB
2025-04-22 20:54:03,766 root INFO creating build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:03,766 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 20:54:03,767 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 20:54:03,767 root INFO creating build/lib/django/contrib/sites/locale/eo
2025-04-22 20:54:03,767 root INFO creating build/lib/django/contrib/sites/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,767 root INFO copying django/contrib/sites/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,767 root INFO copying django/contrib/sites/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,767 root INFO creating build/lib/django/contrib/sites/locale/es
2025-04-22 20:54:03,767 root INFO creating build/lib/django/contrib/sites/locale/es/LC_MESSAGES
2025-04-22 20:54:03,767 root INFO copying django/contrib/sites/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es/LC_MESSAGES
2025-04-22 20:54:03,768 root INFO copying django/contrib/sites/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es/LC_MESSAGES
2025-04-22 20:54:03,768 root INFO creating build/lib/django/contrib/sites/locale/es_AR
2025-04-22 20:54:03,768 root INFO creating build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:03,768 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 20:54:03,768 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 20:54:03,768 root INFO creating build/lib/django/contrib/sites/locale/es_CO
2025-04-22 20:54:03,768 root INFO creating build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:03,768 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 20:54:03,769 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 20:54:03,769 root INFO creating build/lib/django/contrib/sites/locale/es_MX
2025-04-22 20:54:03,769 root INFO creating build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:03,769 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 20:54:03,769 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 20:54:03,769 root INFO creating build/lib/django/contrib/sites/locale/es_VE
2025-04-22 20:54:03,769 root INFO creating build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:03,769 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 20:54:03,770 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 20:54:03,770 root INFO creating build/lib/django/contrib/sites/locale/et
2025-04-22 20:54:03,770 root INFO creating build/lib/django/contrib/sites/locale/et/LC_MESSAGES
2025-04-22 20:54:03,770 root INFO copying django/contrib/sites/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/et/LC_MESSAGES
2025-04-22 20:54:03,770 root INFO copying django/contrib/sites/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/et/LC_MESSAGES
2025-04-22 20:54:03,770 root INFO creating build/lib/django/contrib/sites/locale/eu
2025-04-22 20:54:03,770 root INFO creating build/lib/django/contrib/sites/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,770 root INFO copying django/contrib/sites/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,771 root INFO copying django/contrib/sites/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,771 root INFO creating build/lib/django/contrib/sites/locale/fa
2025-04-22 20:54:03,771 root INFO creating build/lib/django/contrib/sites/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,771 root INFO copying django/contrib/sites/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,771 root INFO copying django/contrib/sites/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,771 root INFO creating build/lib/django/contrib/sites/locale/fi
2025-04-22 20:54:03,771 root INFO creating build/lib/django/contrib/sites/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,771 root INFO copying django/contrib/sites/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,772 root INFO copying django/contrib/sites/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,772 root INFO creating build/lib/django/contrib/sites/locale/fr
2025-04-22 20:54:03,772 root INFO creating build/lib/django/contrib/sites/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,772 root INFO copying django/contrib/sites/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,772 root INFO copying django/contrib/sites/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,772 root INFO creating build/lib/django/contrib/sites/locale/fy
2025-04-22 20:54:03,772 root INFO creating build/lib/django/contrib/sites/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,772 root INFO copying django/contrib/sites/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,772 root INFO copying django/contrib/sites/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,773 root INFO creating build/lib/django/contrib/sites/locale/ga
2025-04-22 20:54:03,773 root INFO creating build/lib/django/contrib/sites/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,773 root INFO copying django/contrib/sites/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,773 root INFO copying django/contrib/sites/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,773 root INFO creating build/lib/django/contrib/sites/locale/gd
2025-04-22 20:54:03,773 root INFO creating build/lib/django/contrib/sites/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,773 root INFO copying django/contrib/sites/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,773 root INFO copying django/contrib/sites/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,774 root INFO creating build/lib/django/contrib/sites/locale/gl
2025-04-22 20:54:03,774 root INFO creating build/lib/django/contrib/sites/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,774 root INFO copying django/contrib/sites/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,774 root INFO copying django/contrib/sites/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,774 root INFO creating build/lib/django/contrib/sites/locale/he
2025-04-22 20:54:03,774 root INFO creating build/lib/django/contrib/sites/locale/he/LC_MESSAGES
2025-04-22 20:54:03,774 root INFO copying django/contrib/sites/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/he/LC_MESSAGES
2025-04-22 20:54:03,774 root INFO copying django/contrib/sites/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/he/LC_MESSAGES
2025-04-22 20:54:03,774 root INFO creating build/lib/django/contrib/sites/locale/hi
2025-04-22 20:54:03,775 root INFO creating build/lib/django/contrib/sites/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,775 root INFO copying django/contrib/sites/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,775 root INFO copying django/contrib/sites/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,775 root INFO creating build/lib/django/contrib/sites/locale/hr
2025-04-22 20:54:03,775 root INFO creating build/lib/django/contrib/sites/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,775 root INFO copying django/contrib/sites/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,775 root INFO copying django/contrib/sites/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,775 root INFO creating build/lib/django/contrib/sites/locale/hsb
2025-04-22 20:54:03,776 root INFO creating build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,776 root INFO copying django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,776 root INFO copying django/contrib/sites/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,776 root INFO creating build/lib/django/contrib/sites/locale/hu
2025-04-22 20:54:03,776 root INFO creating build/lib/django/contrib/sites/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,776 root INFO copying django/contrib/sites/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,776 root INFO copying django/contrib/sites/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,776 root INFO creating build/lib/django/contrib/sites/locale/hy
2025-04-22 20:54:03,776 root INFO creating build/lib/django/contrib/sites/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,777 root INFO copying django/contrib/sites/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,777 root INFO copying django/contrib/sites/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,777 root INFO creating build/lib/django/contrib/sites/locale/ia
2025-04-22 20:54:03,777 root INFO creating build/lib/django/contrib/sites/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,777 root INFO copying django/contrib/sites/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,777 root INFO copying django/contrib/sites/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,777 root INFO creating build/lib/django/contrib/sites/locale/id
2025-04-22 20:54:03,777 root INFO creating build/lib/django/contrib/sites/locale/id/LC_MESSAGES
2025-04-22 20:54:03,778 root INFO copying django/contrib/sites/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/id/LC_MESSAGES
2025-04-22 20:54:03,778 root INFO copying django/contrib/sites/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/id/LC_MESSAGES
2025-04-22 20:54:03,778 root INFO creating build/lib/django/contrib/sites/locale/io
2025-04-22 20:54:03,778 root INFO creating build/lib/django/contrib/sites/locale/io/LC_MESSAGES
2025-04-22 20:54:03,778 root INFO copying django/contrib/sites/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/io/LC_MESSAGES
2025-04-22 20:54:03,778 root INFO copying django/contrib/sites/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/io/LC_MESSAGES
2025-04-22 20:54:03,778 root INFO creating build/lib/django/contrib/sites/locale/is
2025-04-22 20:54:03,778 root INFO creating build/lib/django/contrib/sites/locale/is/LC_MESSAGES
2025-04-22 20:54:03,778 root INFO copying django/contrib/sites/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/is/LC_MESSAGES
2025-04-22 20:54:03,779 root INFO copying django/contrib/sites/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/is/LC_MESSAGES
2025-04-22 20:54:03,779 root INFO creating build/lib/django/contrib/sites/locale/it
2025-04-22 20:54:03,779 root INFO creating build/lib/django/contrib/sites/locale/it/LC_MESSAGES
2025-04-22 20:54:03,779 root INFO copying django/contrib/sites/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/it/LC_MESSAGES
2025-04-22 20:54:03,779 root INFO copying django/contrib/sites/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/it/LC_MESSAGES
2025-04-22 20:54:03,779 root INFO creating build/lib/django/contrib/sites/locale/ja
2025-04-22 20:54:03,779 root INFO creating build/lib/django/contrib/sites/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,779 root INFO copying django/contrib/sites/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,780 root INFO copying django/contrib/sites/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,780 root INFO creating build/lib/django/contrib/sites/locale/ka
2025-04-22 20:54:03,780 root INFO creating build/lib/django/contrib/sites/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,780 root INFO copying django/contrib/sites/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,780 root INFO copying django/contrib/sites/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,780 root INFO creating build/lib/django/contrib/sites/locale/kab
2025-04-22 20:54:03,780 root INFO creating build/lib/django/contrib/sites/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,780 root INFO copying django/contrib/sites/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,780 root INFO copying django/contrib/sites/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,781 root INFO creating build/lib/django/contrib/sites/locale/kk
2025-04-22 20:54:03,781 root INFO creating build/lib/django/contrib/sites/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,781 root INFO copying django/contrib/sites/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,781 root INFO copying django/contrib/sites/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,781 root INFO creating build/lib/django/contrib/sites/locale/km
2025-04-22 20:54:03,781 root INFO creating build/lib/django/contrib/sites/locale/km/LC_MESSAGES
2025-04-22 20:54:03,781 root INFO copying django/contrib/sites/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/km/LC_MESSAGES
2025-04-22 20:54:03,781 root INFO copying django/contrib/sites/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/km/LC_MESSAGES
2025-04-22 20:54:03,781 root INFO creating build/lib/django/contrib/sites/locale/kn
2025-04-22 20:54:03,782 root INFO creating build/lib/django/contrib/sites/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,782 root INFO copying django/contrib/sites/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,782 root INFO copying django/contrib/sites/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,782 root INFO creating build/lib/django/contrib/sites/locale/ko
2025-04-22 20:54:03,782 root INFO creating build/lib/django/contrib/sites/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,782 root INFO copying django/contrib/sites/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,782 root INFO copying django/contrib/sites/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,782 root INFO creating build/lib/django/contrib/sites/locale/ky
2025-04-22 20:54:03,782 root INFO creating build/lib/django/contrib/sites/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,783 root INFO copying django/contrib/sites/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,783 root INFO copying django/contrib/sites/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,783 root INFO creating build/lib/django/contrib/sites/locale/lb
2025-04-22 20:54:03,783 root INFO creating build/lib/django/contrib/sites/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,783 root INFO copying django/contrib/sites/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,783 root INFO copying django/contrib/sites/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,783 root INFO creating build/lib/django/contrib/sites/locale/lt
2025-04-22 20:54:03,783 root INFO creating build/lib/django/contrib/sites/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,784 root INFO copying django/contrib/sites/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,784 root INFO copying django/contrib/sites/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,784 root INFO creating build/lib/django/contrib/sites/locale/lv
2025-04-22 20:54:03,784 root INFO creating build/lib/django/contrib/sites/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,784 root INFO copying django/contrib/sites/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,784 root INFO copying django/contrib/sites/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,784 root INFO creating build/lib/django/contrib/sites/locale/mk
2025-04-22 20:54:03,784 root INFO creating build/lib/django/contrib/sites/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,784 root INFO copying django/contrib/sites/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,785 root INFO copying django/contrib/sites/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,785 root INFO creating build/lib/django/contrib/sites/locale/ml
2025-04-22 20:54:03,785 root INFO creating build/lib/django/contrib/sites/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,785 root INFO copying django/contrib/sites/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,785 root INFO copying django/contrib/sites/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,785 root INFO creating build/lib/django/contrib/sites/locale/mn
2025-04-22 20:54:03,785 root INFO creating build/lib/django/contrib/sites/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,785 root INFO copying django/contrib/sites/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,786 root INFO copying django/contrib/sites/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,786 root INFO creating build/lib/django/contrib/sites/locale/mr
2025-04-22 20:54:03,786 root INFO creating build/lib/django/contrib/sites/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,786 root INFO copying django/contrib/sites/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,786 root INFO copying django/contrib/sites/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,786 root INFO creating build/lib/django/contrib/sites/locale/ms
2025-04-22 20:54:03,786 root INFO creating build/lib/django/contrib/sites/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,786 root INFO copying django/contrib/sites/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,786 root INFO copying django/contrib/sites/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,787 root INFO creating build/lib/django/contrib/sites/locale/my
2025-04-22 20:54:03,787 root INFO creating build/lib/django/contrib/sites/locale/my/LC_MESSAGES
2025-04-22 20:54:03,787 root INFO copying django/contrib/sites/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/my/LC_MESSAGES
2025-04-22 20:54:03,787 root INFO copying django/contrib/sites/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/my/LC_MESSAGES
2025-04-22 20:54:03,787 root INFO creating build/lib/django/contrib/sites/locale/nb
2025-04-22 20:54:03,787 root INFO creating build/lib/django/contrib/sites/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,787 root INFO copying django/contrib/sites/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,787 root INFO copying django/contrib/sites/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,788 root INFO creating build/lib/django/contrib/sites/locale/ne
2025-04-22 20:54:03,788 root INFO creating build/lib/django/contrib/sites/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,788 root INFO copying django/contrib/sites/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,788 root INFO copying django/contrib/sites/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,788 root INFO creating build/lib/django/contrib/sites/locale/nl
2025-04-22 20:54:03,788 root INFO creating build/lib/django/contrib/sites/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,788 root INFO copying django/contrib/sites/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,788 root INFO copying django/contrib/sites/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,789 root INFO creating build/lib/django/contrib/sites/locale/nn
2025-04-22 20:54:03,789 root INFO creating build/lib/django/contrib/sites/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,789 root INFO copying django/contrib/sites/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,789 root INFO copying django/contrib/sites/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,789 root INFO creating build/lib/django/contrib/sites/locale/os
2025-04-22 20:54:03,789 root INFO creating build/lib/django/contrib/sites/locale/os/LC_MESSAGES
2025-04-22 20:54:03,789 root INFO copying django/contrib/sites/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/os/LC_MESSAGES
2025-04-22 20:54:03,789 root INFO copying django/contrib/sites/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/os/LC_MESSAGES
2025-04-22 20:54:03,789 root INFO creating build/lib/django/contrib/sites/locale/pa
2025-04-22 20:54:03,790 root INFO creating build/lib/django/contrib/sites/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,790 root INFO copying django/contrib/sites/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,790 root INFO copying django/contrib/sites/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,790 root INFO creating build/lib/django/contrib/sites/locale/pl
2025-04-22 20:54:03,790 root INFO creating build/lib/django/contrib/sites/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,790 root INFO copying django/contrib/sites/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,790 root INFO copying django/contrib/sites/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,790 root INFO creating build/lib/django/contrib/sites/locale/pt
2025-04-22 20:54:03,791 root INFO creating build/lib/django/contrib/sites/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,791 root INFO copying django/contrib/sites/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,791 root INFO copying django/contrib/sites/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,791 root INFO creating build/lib/django/contrib/sites/locale/pt_BR
2025-04-22 20:54:03,791 root INFO creating build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:03,791 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 20:54:03,791 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 20:54:03,791 root INFO creating build/lib/django/contrib/sites/locale/ro
2025-04-22 20:54:03,791 root INFO creating build/lib/django/contrib/sites/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,792 root INFO copying django/contrib/sites/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,792 root INFO copying django/contrib/sites/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,792 root INFO creating build/lib/django/contrib/sites/locale/ru
2025-04-22 20:54:03,792 root INFO creating build/lib/django/contrib/sites/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,792 root INFO copying django/contrib/sites/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,792 root INFO copying django/contrib/sites/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,792 root INFO creating build/lib/django/contrib/sites/locale/sk
2025-04-22 20:54:03,792 root INFO creating build/lib/django/contrib/sites/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,793 root INFO copying django/contrib/sites/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,793 root INFO copying django/contrib/sites/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,793 root INFO creating build/lib/django/contrib/sites/locale/sl
2025-04-22 20:54:03,793 root INFO creating build/lib/django/contrib/sites/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,793 root INFO copying django/contrib/sites/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,793 root INFO copying django/contrib/sites/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,793 root INFO creating build/lib/django/contrib/sites/locale/sq
2025-04-22 20:54:03,793 root INFO creating build/lib/django/contrib/sites/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,793 root INFO copying django/contrib/sites/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,794 root INFO copying django/contrib/sites/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,794 root INFO creating build/lib/django/contrib/sites/locale/sr
2025-04-22 20:54:03,794 root INFO creating build/lib/django/contrib/sites/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,794 root INFO copying django/contrib/sites/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,794 root INFO copying django/contrib/sites/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,794 root INFO creating build/lib/django/contrib/sites/locale/sr_Latn
2025-04-22 20:54:03,794 root INFO creating build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:03,794 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 20:54:03,795 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 20:54:03,795 root INFO creating build/lib/django/contrib/sites/locale/sv
2025-04-22 20:54:03,795 root INFO creating build/lib/django/contrib/sites/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,795 root INFO copying django/contrib/sites/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,795 root INFO copying django/contrib/sites/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,795 root INFO creating build/lib/django/contrib/sites/locale/sw
2025-04-22 20:54:03,795 root INFO creating build/lib/django/contrib/sites/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,795 root INFO copying django/contrib/sites/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,796 root INFO copying django/contrib/sites/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,796 root INFO creating build/lib/django/contrib/sites/locale/ta
2025-04-22 20:54:03,796 root INFO creating build/lib/django/contrib/sites/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,796 root INFO copying django/contrib/sites/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,796 root INFO copying django/contrib/sites/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,796 root INFO creating build/lib/django/contrib/sites/locale/te
2025-04-22 20:54:03,796 root INFO creating build/lib/django/contrib/sites/locale/te/LC_MESSAGES
2025-04-22 20:54:03,796 root INFO copying django/contrib/sites/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/te/LC_MESSAGES
2025-04-22 20:54:03,796 root INFO copying django/contrib/sites/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/te/LC_MESSAGES
2025-04-22 20:54:03,797 root INFO creating build/lib/django/contrib/sites/locale/tg
2025-04-22 20:54:03,797 root INFO creating build/lib/django/contrib/sites/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,797 root INFO copying django/contrib/sites/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,797 root INFO copying django/contrib/sites/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,797 root INFO creating build/lib/django/contrib/sites/locale/th
2025-04-22 20:54:03,797 root INFO creating build/lib/django/contrib/sites/locale/th/LC_MESSAGES
2025-04-22 20:54:03,797 root INFO copying django/contrib/sites/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/th/LC_MESSAGES
2025-04-22 20:54:03,797 root INFO copying django/contrib/sites/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/th/LC_MESSAGES
2025-04-22 20:54:03,798 root INFO creating build/lib/django/contrib/sites/locale/tk
2025-04-22 20:54:03,798 root INFO creating build/lib/django/contrib/sites/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,798 root INFO copying django/contrib/sites/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,798 root INFO copying django/contrib/sites/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,798 root INFO creating build/lib/django/contrib/sites/locale/tr
2025-04-22 20:54:03,798 root INFO creating build/lib/django/contrib/sites/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,798 root INFO copying django/contrib/sites/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,798 root INFO copying django/contrib/sites/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,799 root INFO creating build/lib/django/contrib/sites/locale/tt
2025-04-22 20:54:03,799 root INFO creating build/lib/django/contrib/sites/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,799 root INFO copying django/contrib/sites/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,799 root INFO copying django/contrib/sites/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,799 root INFO creating build/lib/django/contrib/sites/locale/udm
2025-04-22 20:54:03,799 root INFO creating build/lib/django/contrib/sites/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,799 root INFO copying django/contrib/sites/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,799 root INFO copying django/contrib/sites/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,799 root INFO creating build/lib/django/contrib/sites/locale/uk
2025-04-22 20:54:03,800 root INFO creating build/lib/django/contrib/sites/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,800 root INFO copying django/contrib/sites/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,800 root INFO copying django/contrib/sites/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,800 root INFO creating build/lib/django/contrib/sites/locale/ur
2025-04-22 20:54:03,800 root INFO creating build/lib/django/contrib/sites/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,800 root INFO copying django/contrib/sites/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,800 root INFO copying django/contrib/sites/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,800 root INFO creating build/lib/django/contrib/sites/locale/uz
2025-04-22 20:54:03,800 root INFO creating build/lib/django/contrib/sites/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,801 root INFO copying django/contrib/sites/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,801 root INFO copying django/contrib/sites/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,801 root INFO creating build/lib/django/contrib/sites/locale/vi
2025-04-22 20:54:03,801 root INFO creating build/lib/django/contrib/sites/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,801 root INFO copying django/contrib/sites/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,801 root INFO copying django/contrib/sites/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,801 root INFO creating build/lib/django/contrib/sites/locale/zh_Hans
2025-04-22 20:54:03,801 root INFO creating build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:03,801 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 20:54:03,802 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 20:54:03,802 root INFO creating build/lib/django/contrib/sites/locale/zh_Hant
2025-04-22 20:54:03,802 root INFO creating build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:03,802 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 20:54:03,802 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 20:54:03,802 root INFO creating build/lib/django/contrib/sitemaps/templates
2025-04-22 20:54:03,802 root INFO copying django/contrib/sitemaps/templates/sitemap.xml -> build/lib/django/contrib/sitemaps/templates
2025-04-22 20:54:03,803 root INFO copying django/contrib/sitemaps/templates/sitemap_index.xml -> build/lib/django/contrib/sitemaps/templates
2025-04-22 20:54:03,803 root INFO creating build/lib/django/contrib/flatpages/locale
2025-04-22 20:54:03,803 root INFO creating build/lib/django/contrib/flatpages/locale/af
2025-04-22 20:54:03,803 root INFO creating build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES
2025-04-22 20:54:03,803 root INFO copying django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES
2025-04-22 20:54:03,803 root INFO copying django/contrib/flatpages/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES
2025-04-22 20:54:03,803 root INFO creating build/lib/django/contrib/flatpages/locale/ar
2025-04-22 20:54:03,803 root INFO creating build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,803 root INFO copying django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,804 root INFO copying django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,804 root INFO creating build/lib/django/contrib/flatpages/locale/ar_DZ
2025-04-22 20:54:03,804 root INFO creating build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:03,804 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 20:54:03,804 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 20:54:03,804 root INFO creating build/lib/django/contrib/flatpages/locale/ast
2025-04-22 20:54:03,804 root INFO creating build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,804 root INFO copying django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,804 root INFO copying django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,805 root INFO creating build/lib/django/contrib/flatpages/locale/az
2025-04-22 20:54:03,805 root INFO creating build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES
2025-04-22 20:54:03,805 root INFO copying django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES
2025-04-22 20:54:03,805 root INFO copying django/contrib/flatpages/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES
2025-04-22 20:54:03,805 root INFO creating build/lib/django/contrib/flatpages/locale/be
2025-04-22 20:54:03,805 root INFO creating build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES
2025-04-22 20:54:03,805 root INFO copying django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES
2025-04-22 20:54:03,805 root INFO copying django/contrib/flatpages/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES
2025-04-22 20:54:03,806 root INFO creating build/lib/django/contrib/flatpages/locale/bg
2025-04-22 20:54:03,806 root INFO creating build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,806 root INFO copying django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,806 root INFO copying django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,806 root INFO creating build/lib/django/contrib/flatpages/locale/bn
2025-04-22 20:54:03,806 root INFO creating build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,806 root INFO copying django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,806 root INFO copying django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,806 root INFO creating build/lib/django/contrib/flatpages/locale/br
2025-04-22 20:54:03,807 root INFO creating build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES
2025-04-22 20:54:03,807 root INFO copying django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES
2025-04-22 20:54:03,807 root INFO copying django/contrib/flatpages/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES
2025-04-22 20:54:03,807 root INFO creating build/lib/django/contrib/flatpages/locale/bs
2025-04-22 20:54:03,807 root INFO creating build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,807 root INFO copying django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,807 root INFO copying django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,807 root INFO creating build/lib/django/contrib/flatpages/locale/ca
2025-04-22 20:54:03,808 root INFO creating build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,808 root INFO copying django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,808 root INFO copying django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,808 root INFO creating build/lib/django/contrib/flatpages/locale/ckb
2025-04-22 20:54:03,808 root INFO creating build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,808 root INFO copying django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,808 root INFO copying django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,808 root INFO creating build/lib/django/contrib/flatpages/locale/cs
2025-04-22 20:54:03,808 root INFO creating build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,809 root INFO copying django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,809 root INFO copying django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,809 root INFO creating build/lib/django/contrib/flatpages/locale/cy
2025-04-22 20:54:03,809 root INFO creating build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,809 root INFO copying django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,809 root INFO copying django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,809 root INFO creating build/lib/django/contrib/flatpages/locale/da
2025-04-22 20:54:03,809 root INFO creating build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES
2025-04-22 20:54:03,810 root INFO copying django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES
2025-04-22 20:54:03,810 root INFO copying django/contrib/flatpages/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES
2025-04-22 20:54:03,810 root INFO creating build/lib/django/contrib/flatpages/locale/de
2025-04-22 20:54:03,810 root INFO creating build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES
2025-04-22 20:54:03,810 root INFO copying django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES
2025-04-22 20:54:03,810 root INFO copying django/contrib/flatpages/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES
2025-04-22 20:54:03,810 root INFO creating build/lib/django/contrib/flatpages/locale/dsb
2025-04-22 20:54:03,810 root INFO creating build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,810 root INFO copying django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,811 root INFO copying django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,811 root INFO creating build/lib/django/contrib/flatpages/locale/el
2025-04-22 20:54:03,811 root INFO creating build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES
2025-04-22 20:54:03,811 root INFO copying django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES
2025-04-22 20:54:03,811 root INFO copying django/contrib/flatpages/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES
2025-04-22 20:54:03,811 root INFO creating build/lib/django/contrib/flatpages/locale/en
2025-04-22 20:54:03,811 root INFO creating build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES
2025-04-22 20:54:03,811 root INFO copying django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES
2025-04-22 20:54:03,812 root INFO copying django/contrib/flatpages/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES
2025-04-22 20:54:03,812 root INFO creating build/lib/django/contrib/flatpages/locale/en_AU
2025-04-22 20:54:03,812 root INFO creating build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:03,812 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 20:54:03,812 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 20:54:03,812 root INFO creating build/lib/django/contrib/flatpages/locale/en_GB
2025-04-22 20:54:03,812 root INFO creating build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:03,812 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 20:54:03,813 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 20:54:03,813 root INFO creating build/lib/django/contrib/flatpages/locale/eo
2025-04-22 20:54:03,813 root INFO creating build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,813 root INFO copying django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,813 root INFO copying django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,813 root INFO creating build/lib/django/contrib/flatpages/locale/es
2025-04-22 20:54:03,813 root INFO creating build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES
2025-04-22 20:54:03,813 root INFO copying django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES
2025-04-22 20:54:03,813 root INFO copying django/contrib/flatpages/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES
2025-04-22 20:54:03,814 root INFO creating build/lib/django/contrib/flatpages/locale/es_AR
2025-04-22 20:54:03,814 root INFO creating build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:03,814 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 20:54:03,814 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 20:54:03,814 root INFO creating build/lib/django/contrib/flatpages/locale/es_CO
2025-04-22 20:54:03,814 root INFO creating build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:03,814 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 20:54:03,814 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 20:54:03,815 root INFO creating build/lib/django/contrib/flatpages/locale/es_MX
2025-04-22 20:54:03,815 root INFO creating build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:03,815 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 20:54:03,815 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 20:54:03,815 root INFO creating build/lib/django/contrib/flatpages/locale/es_VE
2025-04-22 20:54:03,815 root INFO creating build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:03,815 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 20:54:03,815 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 20:54:03,816 root INFO creating build/lib/django/contrib/flatpages/locale/et
2025-04-22 20:54:03,816 root INFO creating build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES
2025-04-22 20:54:03,816 root INFO copying django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES
2025-04-22 20:54:03,816 root INFO copying django/contrib/flatpages/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES
2025-04-22 20:54:03,816 root INFO creating build/lib/django/contrib/flatpages/locale/eu
2025-04-22 20:54:03,816 root INFO creating build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,816 root INFO copying django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,816 root INFO copying django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,817 root INFO creating build/lib/django/contrib/flatpages/locale/fa
2025-04-22 20:54:03,817 root INFO creating build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,817 root INFO copying django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,817 root INFO copying django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,817 root INFO creating build/lib/django/contrib/flatpages/locale/fi
2025-04-22 20:54:03,817 root INFO creating build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,817 root INFO copying django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,817 root INFO copying django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,817 root INFO creating build/lib/django/contrib/flatpages/locale/fr
2025-04-22 20:54:03,818 root INFO creating build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,818 root INFO copying django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,818 root INFO copying django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,818 root INFO creating build/lib/django/contrib/flatpages/locale/fy
2025-04-22 20:54:03,818 root INFO creating build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,818 root INFO copying django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,818 root INFO copying django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,818 root INFO creating build/lib/django/contrib/flatpages/locale/ga
2025-04-22 20:54:03,819 root INFO creating build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,819 root INFO copying django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,819 root INFO copying django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,819 root INFO creating build/lib/django/contrib/flatpages/locale/gd
2025-04-22 20:54:03,819 root INFO creating build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,819 root INFO copying django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,819 root INFO copying django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,819 root INFO creating build/lib/django/contrib/flatpages/locale/gl
2025-04-22 20:54:03,819 root INFO creating build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,820 root INFO copying django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,820 root INFO copying django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,820 root INFO creating build/lib/django/contrib/flatpages/locale/he
2025-04-22 20:54:03,820 root INFO creating build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES
2025-04-22 20:54:03,820 root INFO copying django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES
2025-04-22 20:54:03,820 root INFO copying django/contrib/flatpages/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES
2025-04-22 20:54:03,820 root INFO creating build/lib/django/contrib/flatpages/locale/hi
2025-04-22 20:54:03,820 root INFO creating build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,820 root INFO copying django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,821 root INFO copying django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,821 root INFO creating build/lib/django/contrib/flatpages/locale/hr
2025-04-22 20:54:03,821 root INFO creating build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,821 root INFO copying django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,821 root INFO copying django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,821 root INFO creating build/lib/django/contrib/flatpages/locale/hsb
2025-04-22 20:54:03,821 root INFO creating build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,821 root INFO copying django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,822 root INFO copying django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,822 root INFO creating build/lib/django/contrib/flatpages/locale/hu
2025-04-22 20:54:03,822 root INFO creating build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,822 root INFO copying django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,822 root INFO copying django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,822 root INFO creating build/lib/django/contrib/flatpages/locale/hy
2025-04-22 20:54:03,822 root INFO creating build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,823 root INFO copying django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,823 root INFO copying django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,823 root INFO creating build/lib/django/contrib/flatpages/locale/ia
2025-04-22 20:54:03,823 root INFO creating build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,823 root INFO copying django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,823 root INFO copying django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,823 root INFO creating build/lib/django/contrib/flatpages/locale/id
2025-04-22 20:54:03,823 root INFO creating build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES
2025-04-22 20:54:03,823 root INFO copying django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES
2025-04-22 20:54:03,824 root INFO copying django/contrib/flatpages/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES
2025-04-22 20:54:03,824 root INFO creating build/lib/django/contrib/flatpages/locale/io
2025-04-22 20:54:03,824 root INFO creating build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES
2025-04-22 20:54:03,824 root INFO copying django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES
2025-04-22 20:54:03,824 root INFO copying django/contrib/flatpages/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES
2025-04-22 20:54:03,824 root INFO creating build/lib/django/contrib/flatpages/locale/is
2025-04-22 20:54:03,824 root INFO creating build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES
2025-04-22 20:54:03,824 root INFO copying django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES
2025-04-22 20:54:03,825 root INFO copying django/contrib/flatpages/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES
2025-04-22 20:54:03,825 root INFO creating build/lib/django/contrib/flatpages/locale/it
2025-04-22 20:54:03,825 root INFO creating build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES
2025-04-22 20:54:03,825 root INFO copying django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES
2025-04-22 20:54:03,825 root INFO copying django/contrib/flatpages/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES
2025-04-22 20:54:03,825 root INFO creating build/lib/django/contrib/flatpages/locale/ja
2025-04-22 20:54:03,825 root INFO creating build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,825 root INFO copying django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,826 root INFO copying django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,826 root INFO creating build/lib/django/contrib/flatpages/locale/ka
2025-04-22 20:54:03,826 root INFO creating build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,826 root INFO copying django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,826 root INFO copying django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,826 root INFO creating build/lib/django/contrib/flatpages/locale/kk
2025-04-22 20:54:03,826 root INFO creating build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,826 root INFO copying django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,826 root INFO copying django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,827 root INFO creating build/lib/django/contrib/flatpages/locale/km
2025-04-22 20:54:03,827 root INFO creating build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES
2025-04-22 20:54:03,827 root INFO copying django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES
2025-04-22 20:54:03,827 root INFO copying django/contrib/flatpages/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES
2025-04-22 20:54:03,827 root INFO creating build/lib/django/contrib/flatpages/locale/kn
2025-04-22 20:54:03,827 root INFO creating build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,827 root INFO copying django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,827 root INFO copying django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,828 root INFO creating build/lib/django/contrib/flatpages/locale/ko
2025-04-22 20:54:03,828 root INFO creating build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,828 root INFO copying django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,828 root INFO copying django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,828 root INFO creating build/lib/django/contrib/flatpages/locale/ky
2025-04-22 20:54:03,828 root INFO creating build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,828 root INFO copying django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,828 root INFO copying django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,829 root INFO creating build/lib/django/contrib/flatpages/locale/lb
2025-04-22 20:54:03,829 root INFO creating build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,829 root INFO copying django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,829 root INFO copying django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,829 root INFO creating build/lib/django/contrib/flatpages/locale/lt
2025-04-22 20:54:03,829 root INFO creating build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,829 root INFO copying django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,829 root INFO copying django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,829 root INFO creating build/lib/django/contrib/flatpages/locale/lv
2025-04-22 20:54:03,830 root INFO creating build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,830 root INFO copying django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,830 root INFO copying django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,830 root INFO creating build/lib/django/contrib/flatpages/locale/mk
2025-04-22 20:54:03,830 root INFO creating build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,830 root INFO copying django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,830 root INFO copying django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,830 root INFO creating build/lib/django/contrib/flatpages/locale/ml
2025-04-22 20:54:03,831 root INFO creating build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,831 root INFO copying django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,831 root INFO copying django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,831 root INFO creating build/lib/django/contrib/flatpages/locale/mn
2025-04-22 20:54:03,831 root INFO creating build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,831 root INFO copying django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,831 root INFO copying django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,831 root INFO creating build/lib/django/contrib/flatpages/locale/mr
2025-04-22 20:54:03,832 root INFO creating build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,832 root INFO copying django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,832 root INFO copying django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,832 root INFO creating build/lib/django/contrib/flatpages/locale/ms
2025-04-22 20:54:03,832 root INFO creating build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,832 root INFO copying django/contrib/flatpages/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,832 root INFO copying django/contrib/flatpages/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,833 root INFO creating build/lib/django/contrib/flatpages/locale/my
2025-04-22 20:54:03,833 root INFO creating build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES
2025-04-22 20:54:03,833 root INFO copying django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES
2025-04-22 20:54:03,833 root INFO copying django/contrib/flatpages/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES
2025-04-22 20:54:03,833 root INFO creating build/lib/django/contrib/flatpages/locale/nb
2025-04-22 20:54:03,833 root INFO creating build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,833 root INFO copying django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,833 root INFO copying django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,833 root INFO creating build/lib/django/contrib/flatpages/locale/ne
2025-04-22 20:54:03,834 root INFO creating build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,834 root INFO copying django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,834 root INFO copying django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,834 root INFO creating build/lib/django/contrib/flatpages/locale/nl
2025-04-22 20:54:03,834 root INFO creating build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,834 root INFO copying django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,834 root INFO copying django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,834 root INFO creating build/lib/django/contrib/flatpages/locale/nn
2025-04-22 20:54:03,834 root INFO creating build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,835 root INFO copying django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,835 root INFO copying django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,835 root INFO creating build/lib/django/contrib/flatpages/locale/os
2025-04-22 20:54:03,835 root INFO creating build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES
2025-04-22 20:54:03,835 root INFO copying django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES
2025-04-22 20:54:03,835 root INFO copying django/contrib/flatpages/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES
2025-04-22 20:54:03,835 root INFO creating build/lib/django/contrib/flatpages/locale/pa
2025-04-22 20:54:03,835 root INFO creating build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,836 root INFO copying django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,836 root INFO copying django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,836 root INFO creating build/lib/django/contrib/flatpages/locale/pl
2025-04-22 20:54:03,836 root INFO creating build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,836 root INFO copying django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,836 root INFO copying django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,836 root INFO creating build/lib/django/contrib/flatpages/locale/pt
2025-04-22 20:54:03,836 root INFO creating build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,836 root INFO copying django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,837 root INFO copying django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,837 root INFO creating build/lib/django/contrib/flatpages/locale/pt_BR
2025-04-22 20:54:03,837 root INFO creating build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:03,837 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 20:54:03,837 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 20:54:03,837 root INFO creating build/lib/django/contrib/flatpages/locale/ro
2025-04-22 20:54:03,837 root INFO creating build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,837 root INFO copying django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,838 root INFO copying django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,838 root INFO creating build/lib/django/contrib/flatpages/locale/ru
2025-04-22 20:54:03,838 root INFO creating build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,838 root INFO copying django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,838 root INFO copying django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,838 root INFO creating build/lib/django/contrib/flatpages/locale/sk
2025-04-22 20:54:03,838 root INFO creating build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,838 root INFO copying django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,839 root INFO copying django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,839 root INFO creating build/lib/django/contrib/flatpages/locale/sl
2025-04-22 20:54:03,839 root INFO creating build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,839 root INFO copying django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,839 root INFO copying django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,839 root INFO creating build/lib/django/contrib/flatpages/locale/sq
2025-04-22 20:54:03,839 root INFO creating build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,839 root INFO copying django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,839 root INFO copying django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,840 root INFO creating build/lib/django/contrib/flatpages/locale/sr
2025-04-22 20:54:03,840 root INFO creating build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,840 root INFO copying django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,840 root INFO copying django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,840 root INFO creating build/lib/django/contrib/flatpages/locale/sr_Latn
2025-04-22 20:54:03,840 root INFO creating build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:03,840 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 20:54:03,840 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 20:54:03,841 root INFO creating build/lib/django/contrib/flatpages/locale/sv
2025-04-22 20:54:03,841 root INFO creating build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,841 root INFO copying django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,841 root INFO copying django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,841 root INFO creating build/lib/django/contrib/flatpages/locale/sw
2025-04-22 20:54:03,841 root INFO creating build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,841 root INFO copying django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,841 root INFO copying django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,842 root INFO creating build/lib/django/contrib/flatpages/locale/ta
2025-04-22 20:54:03,842 root INFO creating build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,842 root INFO copying django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,842 root INFO copying django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,842 root INFO creating build/lib/django/contrib/flatpages/locale/te
2025-04-22 20:54:03,842 root INFO creating build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES
2025-04-22 20:54:03,842 root INFO copying django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES
2025-04-22 20:54:03,842 root INFO copying django/contrib/flatpages/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES
2025-04-22 20:54:03,843 root INFO creating build/lib/django/contrib/flatpages/locale/tg
2025-04-22 20:54:03,843 root INFO creating build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,843 root INFO copying django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,843 root INFO copying django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,843 root INFO creating build/lib/django/contrib/flatpages/locale/th
2025-04-22 20:54:03,843 root INFO creating build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES
2025-04-22 20:54:03,843 root INFO copying django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES
2025-04-22 20:54:03,843 root INFO copying django/contrib/flatpages/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES
2025-04-22 20:54:03,843 root INFO creating build/lib/django/contrib/flatpages/locale/tk
2025-04-22 20:54:03,844 root INFO creating build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,844 root INFO copying django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,844 root INFO copying django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,844 root INFO creating build/lib/django/contrib/flatpages/locale/tr
2025-04-22 20:54:03,844 root INFO creating build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,844 root INFO copying django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,844 root INFO copying django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,844 root INFO creating build/lib/django/contrib/flatpages/locale/tt
2025-04-22 20:54:03,844 root INFO creating build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,845 root INFO copying django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,845 root INFO copying django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,845 root INFO creating build/lib/django/contrib/flatpages/locale/udm
2025-04-22 20:54:03,845 root INFO creating build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,845 root INFO copying django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,845 root INFO copying django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,845 root INFO creating build/lib/django/contrib/flatpages/locale/uk
2025-04-22 20:54:03,845 root INFO creating build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,846 root INFO copying django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,846 root INFO copying django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,846 root INFO creating build/lib/django/contrib/flatpages/locale/ur
2025-04-22 20:54:03,846 root INFO creating build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,846 root INFO copying django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,846 root INFO copying django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,846 root INFO creating build/lib/django/contrib/flatpages/locale/vi
2025-04-22 20:54:03,846 root INFO creating build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,847 root INFO copying django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,847 root INFO copying django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,847 root INFO creating build/lib/django/contrib/flatpages/locale/zh_Hans
2025-04-22 20:54:03,847 root INFO creating build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:03,847 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 20:54:03,847 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 20:54:03,847 root INFO creating build/lib/django/contrib/flatpages/locale/zh_Hant
2025-04-22 20:54:03,847 root INFO creating build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:03,848 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 20:54:03,848 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 20:54:03,848 root INFO creating build/lib/django/contrib/sessions/locale
2025-04-22 20:54:03,848 root INFO creating build/lib/django/contrib/sessions/locale/af
2025-04-22 20:54:03,848 root INFO creating build/lib/django/contrib/sessions/locale/af/LC_MESSAGES
2025-04-22 20:54:03,848 root INFO copying django/contrib/sessions/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/af/LC_MESSAGES
2025-04-22 20:54:03,848 root INFO copying django/contrib/sessions/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/af/LC_MESSAGES
2025-04-22 20:54:03,848 root INFO creating build/lib/django/contrib/sessions/locale/ar
2025-04-22 20:54:03,848 root INFO creating build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,849 root INFO copying django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,849 root INFO copying django/contrib/sessions/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,849 root INFO creating build/lib/django/contrib/sessions/locale/ar_DZ
2025-04-22 20:54:03,849 root INFO creating build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:03,849 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 20:54:03,849 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 20:54:03,849 root INFO creating build/lib/django/contrib/sessions/locale/ast
2025-04-22 20:54:03,849 root INFO creating build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,850 root INFO copying django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,850 root INFO copying django/contrib/sessions/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,850 root INFO creating build/lib/django/contrib/sessions/locale/az
2025-04-22 20:54:03,850 root INFO creating build/lib/django/contrib/sessions/locale/az/LC_MESSAGES
2025-04-22 20:54:03,850 root INFO copying django/contrib/sessions/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/az/LC_MESSAGES
2025-04-22 20:54:03,850 root INFO copying django/contrib/sessions/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/az/LC_MESSAGES
2025-04-22 20:54:03,850 root INFO creating build/lib/django/contrib/sessions/locale/be
2025-04-22 20:54:03,850 root INFO creating build/lib/django/contrib/sessions/locale/be/LC_MESSAGES
2025-04-22 20:54:03,850 root INFO copying django/contrib/sessions/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/be/LC_MESSAGES
2025-04-22 20:54:03,851 root INFO copying django/contrib/sessions/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/be/LC_MESSAGES
2025-04-22 20:54:03,851 root INFO creating build/lib/django/contrib/sessions/locale/bg
2025-04-22 20:54:03,851 root INFO creating build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,851 root INFO copying django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,851 root INFO copying django/contrib/sessions/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,851 root INFO creating build/lib/django/contrib/sessions/locale/bn
2025-04-22 20:54:03,851 root INFO creating build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,851 root INFO copying django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,852 root INFO copying django/contrib/sessions/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,852 root INFO creating build/lib/django/contrib/sessions/locale/br
2025-04-22 20:54:03,852 root INFO creating build/lib/django/contrib/sessions/locale/br/LC_MESSAGES
2025-04-22 20:54:03,852 root INFO copying django/contrib/sessions/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/br/LC_MESSAGES
2025-04-22 20:54:03,852 root INFO copying django/contrib/sessions/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/br/LC_MESSAGES
2025-04-22 20:54:03,852 root INFO creating build/lib/django/contrib/sessions/locale/bs
2025-04-22 20:54:03,852 root INFO creating build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,852 root INFO copying django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,853 root INFO copying django/contrib/sessions/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,853 root INFO creating build/lib/django/contrib/sessions/locale/ca
2025-04-22 20:54:03,853 root INFO creating build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,853 root INFO copying django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,853 root INFO copying django/contrib/sessions/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,853 root INFO creating build/lib/django/contrib/sessions/locale/ckb
2025-04-22 20:54:03,853 root INFO creating build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,853 root INFO copying django/contrib/sessions/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,854 root INFO copying django/contrib/sessions/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,854 root INFO creating build/lib/django/contrib/sessions/locale/cs
2025-04-22 20:54:03,854 root INFO creating build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,854 root INFO copying django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,854 root INFO copying django/contrib/sessions/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,854 root INFO creating build/lib/django/contrib/sessions/locale/cy
2025-04-22 20:54:03,854 root INFO creating build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,854 root INFO copying django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,854 root INFO copying django/contrib/sessions/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,855 root INFO creating build/lib/django/contrib/sessions/locale/da
2025-04-22 20:54:03,855 root INFO creating build/lib/django/contrib/sessions/locale/da/LC_MESSAGES
2025-04-22 20:54:03,855 root INFO copying django/contrib/sessions/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/da/LC_MESSAGES
2025-04-22 20:54:03,855 root INFO copying django/contrib/sessions/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/da/LC_MESSAGES
2025-04-22 20:54:03,855 root INFO creating build/lib/django/contrib/sessions/locale/de
2025-04-22 20:54:03,855 root INFO creating build/lib/django/contrib/sessions/locale/de/LC_MESSAGES
2025-04-22 20:54:03,855 root INFO copying django/contrib/sessions/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/de/LC_MESSAGES
2025-04-22 20:54:03,855 root INFO copying django/contrib/sessions/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/de/LC_MESSAGES
2025-04-22 20:54:03,856 root INFO creating build/lib/django/contrib/sessions/locale/dsb
2025-04-22 20:54:03,856 root INFO creating build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,856 root INFO copying django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,856 root INFO copying django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,856 root INFO creating build/lib/django/contrib/sessions/locale/el
2025-04-22 20:54:03,856 root INFO creating build/lib/django/contrib/sessions/locale/el/LC_MESSAGES
2025-04-22 20:54:03,856 root INFO copying django/contrib/sessions/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/el/LC_MESSAGES
2025-04-22 20:54:03,856 root INFO copying django/contrib/sessions/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/el/LC_MESSAGES
2025-04-22 20:54:03,857 root INFO creating build/lib/django/contrib/sessions/locale/en
2025-04-22 20:54:03,857 root INFO creating build/lib/django/contrib/sessions/locale/en/LC_MESSAGES
2025-04-22 20:54:03,857 root INFO copying django/contrib/sessions/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/en/LC_MESSAGES
2025-04-22 20:54:03,857 root INFO copying django/contrib/sessions/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/en/LC_MESSAGES
2025-04-22 20:54:03,857 root INFO creating build/lib/django/contrib/sessions/locale/en_AU
2025-04-22 20:54:03,857 root INFO creating build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:03,857 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 20:54:03,857 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 20:54:03,857 root INFO creating build/lib/django/contrib/sessions/locale/en_GB
2025-04-22 20:54:03,858 root INFO creating build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:03,858 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 20:54:03,858 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 20:54:03,858 root INFO creating build/lib/django/contrib/sessions/locale/eo
2025-04-22 20:54:03,858 root INFO creating build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,858 root INFO copying django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,858 root INFO copying django/contrib/sessions/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,858 root INFO creating build/lib/django/contrib/sessions/locale/es
2025-04-22 20:54:03,858 root INFO creating build/lib/django/contrib/sessions/locale/es/LC_MESSAGES
2025-04-22 20:54:03,859 root INFO copying django/contrib/sessions/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es/LC_MESSAGES
2025-04-22 20:54:03,859 root INFO copying django/contrib/sessions/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es/LC_MESSAGES
2025-04-22 20:54:03,859 root INFO creating build/lib/django/contrib/sessions/locale/es_AR
2025-04-22 20:54:03,859 root INFO creating build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:03,859 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 20:54:03,859 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 20:54:03,859 root INFO creating build/lib/django/contrib/sessions/locale/es_CO
2025-04-22 20:54:03,859 root INFO creating build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:03,860 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 20:54:03,860 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 20:54:03,860 root INFO creating build/lib/django/contrib/sessions/locale/es_MX
2025-04-22 20:54:03,860 root INFO creating build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:03,860 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 20:54:03,860 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 20:54:03,860 root INFO creating build/lib/django/contrib/sessions/locale/es_VE
2025-04-22 20:54:03,860 root INFO creating build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:03,860 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 20:54:03,861 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 20:54:03,861 root INFO creating build/lib/django/contrib/sessions/locale/et
2025-04-22 20:54:03,861 root INFO creating build/lib/django/contrib/sessions/locale/et/LC_MESSAGES
2025-04-22 20:54:03,861 root INFO copying django/contrib/sessions/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/et/LC_MESSAGES
2025-04-22 20:54:03,861 root INFO copying django/contrib/sessions/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/et/LC_MESSAGES
2025-04-22 20:54:03,861 root INFO creating build/lib/django/contrib/sessions/locale/eu
2025-04-22 20:54:03,861 root INFO creating build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,861 root INFO copying django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,862 root INFO copying django/contrib/sessions/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,862 root INFO creating build/lib/django/contrib/sessions/locale/fa
2025-04-22 20:54:03,862 root INFO creating build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,862 root INFO copying django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,862 root INFO copying django/contrib/sessions/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,862 root INFO creating build/lib/django/contrib/sessions/locale/fi
2025-04-22 20:54:03,862 root INFO creating build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,862 root INFO copying django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,863 root INFO copying django/contrib/sessions/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,863 root INFO creating build/lib/django/contrib/sessions/locale/fr
2025-04-22 20:54:03,863 root INFO creating build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,863 root INFO copying django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,863 root INFO copying django/contrib/sessions/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,863 root INFO creating build/lib/django/contrib/sessions/locale/fy
2025-04-22 20:54:03,863 root INFO creating build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,863 root INFO copying django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,864 root INFO copying django/contrib/sessions/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,864 root INFO creating build/lib/django/contrib/sessions/locale/ga
2025-04-22 20:54:03,864 root INFO creating build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,864 root INFO copying django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,864 root INFO copying django/contrib/sessions/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,864 root INFO creating build/lib/django/contrib/sessions/locale/gd
2025-04-22 20:54:03,864 root INFO creating build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,864 root INFO copying django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,865 root INFO copying django/contrib/sessions/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,865 root INFO creating build/lib/django/contrib/sessions/locale/gl
2025-04-22 20:54:03,865 root INFO creating build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,865 root INFO copying django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,865 root INFO copying django/contrib/sessions/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,865 root INFO creating build/lib/django/contrib/sessions/locale/he
2025-04-22 20:54:03,865 root INFO creating build/lib/django/contrib/sessions/locale/he/LC_MESSAGES
2025-04-22 20:54:03,865 root INFO copying django/contrib/sessions/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/he/LC_MESSAGES
2025-04-22 20:54:03,866 root INFO copying django/contrib/sessions/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/he/LC_MESSAGES
2025-04-22 20:54:03,866 root INFO creating build/lib/django/contrib/sessions/locale/hi
2025-04-22 20:54:03,866 root INFO creating build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,866 root INFO copying django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,866 root INFO copying django/contrib/sessions/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,866 root INFO creating build/lib/django/contrib/sessions/locale/hr
2025-04-22 20:54:03,866 root INFO creating build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,866 root INFO copying django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,866 root INFO copying django/contrib/sessions/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,867 root INFO creating build/lib/django/contrib/sessions/locale/hsb
2025-04-22 20:54:03,867 root INFO creating build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,867 root INFO copying django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,867 root INFO copying django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,867 root INFO creating build/lib/django/contrib/sessions/locale/hu
2025-04-22 20:54:03,867 root INFO creating build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,867 root INFO copying django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,867 root INFO copying django/contrib/sessions/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,868 root INFO creating build/lib/django/contrib/sessions/locale/hy
2025-04-22 20:54:03,868 root INFO creating build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,868 root INFO copying django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,868 root INFO copying django/contrib/sessions/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,868 root INFO creating build/lib/django/contrib/sessions/locale/ia
2025-04-22 20:54:03,868 root INFO creating build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,868 root INFO copying django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,868 root INFO copying django/contrib/sessions/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,869 root INFO creating build/lib/django/contrib/sessions/locale/id
2025-04-22 20:54:03,869 root INFO creating build/lib/django/contrib/sessions/locale/id/LC_MESSAGES
2025-04-22 20:54:03,869 root INFO copying django/contrib/sessions/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/id/LC_MESSAGES
2025-04-22 20:54:03,869 root INFO copying django/contrib/sessions/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/id/LC_MESSAGES
2025-04-22 20:54:03,869 root INFO creating build/lib/django/contrib/sessions/locale/io
2025-04-22 20:54:03,869 root INFO creating build/lib/django/contrib/sessions/locale/io/LC_MESSAGES
2025-04-22 20:54:03,869 root INFO copying django/contrib/sessions/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/io/LC_MESSAGES
2025-04-22 20:54:03,869 root INFO copying django/contrib/sessions/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/io/LC_MESSAGES
2025-04-22 20:54:03,870 root INFO creating build/lib/django/contrib/sessions/locale/is
2025-04-22 20:54:03,870 root INFO creating build/lib/django/contrib/sessions/locale/is/LC_MESSAGES
2025-04-22 20:54:03,870 root INFO copying django/contrib/sessions/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/is/LC_MESSAGES
2025-04-22 20:54:03,870 root INFO copying django/contrib/sessions/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/is/LC_MESSAGES
2025-04-22 20:54:03,870 root INFO creating build/lib/django/contrib/sessions/locale/it
2025-04-22 20:54:03,870 root INFO creating build/lib/django/contrib/sessions/locale/it/LC_MESSAGES
2025-04-22 20:54:03,870 root INFO copying django/contrib/sessions/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/it/LC_MESSAGES
2025-04-22 20:54:03,870 root INFO copying django/contrib/sessions/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/it/LC_MESSAGES
2025-04-22 20:54:03,870 root INFO creating build/lib/django/contrib/sessions/locale/ja
2025-04-22 20:54:03,871 root INFO creating build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,871 root INFO copying django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,871 root INFO copying django/contrib/sessions/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,871 root INFO creating build/lib/django/contrib/sessions/locale/ka
2025-04-22 20:54:03,871 root INFO creating build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,871 root INFO copying django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,871 root INFO copying django/contrib/sessions/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,871 root INFO creating build/lib/django/contrib/sessions/locale/kab
2025-04-22 20:54:03,872 root INFO creating build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,872 root INFO copying django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,872 root INFO copying django/contrib/sessions/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,872 root INFO creating build/lib/django/contrib/sessions/locale/kk
2025-04-22 20:54:03,872 root INFO creating build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,872 root INFO copying django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,872 root INFO copying django/contrib/sessions/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,873 root INFO creating build/lib/django/contrib/sessions/locale/km
2025-04-22 20:54:03,873 root INFO creating build/lib/django/contrib/sessions/locale/km/LC_MESSAGES
2025-04-22 20:54:03,873 root INFO copying django/contrib/sessions/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/km/LC_MESSAGES
2025-04-22 20:54:03,873 root INFO copying django/contrib/sessions/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/km/LC_MESSAGES
2025-04-22 20:54:03,873 root INFO creating build/lib/django/contrib/sessions/locale/kn
2025-04-22 20:54:03,873 root INFO creating build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,873 root INFO copying django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,873 root INFO copying django/contrib/sessions/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,874 root INFO creating build/lib/django/contrib/sessions/locale/ko
2025-04-22 20:54:03,874 root INFO creating build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,874 root INFO copying django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,874 root INFO copying django/contrib/sessions/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,874 root INFO creating build/lib/django/contrib/sessions/locale/ky
2025-04-22 20:54:03,874 root INFO creating build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,874 root INFO copying django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,874 root INFO copying django/contrib/sessions/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,875 root INFO creating build/lib/django/contrib/sessions/locale/lb
2025-04-22 20:54:03,875 root INFO creating build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,875 root INFO copying django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,875 root INFO copying django/contrib/sessions/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,875 root INFO creating build/lib/django/contrib/sessions/locale/lt
2025-04-22 20:54:03,875 root INFO creating build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,875 root INFO copying django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,875 root INFO copying django/contrib/sessions/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,876 root INFO creating build/lib/django/contrib/sessions/locale/lv
2025-04-22 20:54:03,876 root INFO creating build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,876 root INFO copying django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,876 root INFO copying django/contrib/sessions/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,876 root INFO creating build/lib/django/contrib/sessions/locale/mk
2025-04-22 20:54:03,876 root INFO creating build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,876 root INFO copying django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,876 root INFO copying django/contrib/sessions/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,877 root INFO creating build/lib/django/contrib/sessions/locale/ml
2025-04-22 20:54:03,877 root INFO creating build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,877 root INFO copying django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,877 root INFO copying django/contrib/sessions/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,877 root INFO creating build/lib/django/contrib/sessions/locale/mn
2025-04-22 20:54:03,877 root INFO creating build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,877 root INFO copying django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,877 root INFO copying django/contrib/sessions/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,877 root INFO creating build/lib/django/contrib/sessions/locale/mr
2025-04-22 20:54:03,878 root INFO creating build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,878 root INFO copying django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,878 root INFO copying django/contrib/sessions/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,878 root INFO creating build/lib/django/contrib/sessions/locale/ms
2025-04-22 20:54:03,878 root INFO creating build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,878 root INFO copying django/contrib/sessions/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,878 root INFO copying django/contrib/sessions/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,878 root INFO creating build/lib/django/contrib/sessions/locale/my
2025-04-22 20:54:03,879 root INFO creating build/lib/django/contrib/sessions/locale/my/LC_MESSAGES
2025-04-22 20:54:03,879 root INFO copying django/contrib/sessions/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/my/LC_MESSAGES
2025-04-22 20:54:03,879 root INFO copying django/contrib/sessions/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/my/LC_MESSAGES
2025-04-22 20:54:03,879 root INFO creating build/lib/django/contrib/sessions/locale/nb
2025-04-22 20:54:03,879 root INFO creating build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,879 root INFO copying django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,879 root INFO copying django/contrib/sessions/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,879 root INFO creating build/lib/django/contrib/sessions/locale/ne
2025-04-22 20:54:03,880 root INFO creating build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,880 root INFO copying django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,880 root INFO copying django/contrib/sessions/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,880 root INFO creating build/lib/django/contrib/sessions/locale/nl
2025-04-22 20:54:03,880 root INFO creating build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,880 root INFO copying django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,880 root INFO copying django/contrib/sessions/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,880 root INFO creating build/lib/django/contrib/sessions/locale/nn
2025-04-22 20:54:03,880 root INFO creating build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,881 root INFO copying django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,881 root INFO copying django/contrib/sessions/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,881 root INFO creating build/lib/django/contrib/sessions/locale/os
2025-04-22 20:54:03,881 root INFO creating build/lib/django/contrib/sessions/locale/os/LC_MESSAGES
2025-04-22 20:54:03,881 root INFO copying django/contrib/sessions/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/os/LC_MESSAGES
2025-04-22 20:54:03,881 root INFO copying django/contrib/sessions/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/os/LC_MESSAGES
2025-04-22 20:54:03,881 root INFO creating build/lib/django/contrib/sessions/locale/pa
2025-04-22 20:54:03,881 root INFO creating build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,882 root INFO copying django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,882 root INFO copying django/contrib/sessions/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,882 root INFO creating build/lib/django/contrib/sessions/locale/pl
2025-04-22 20:54:03,882 root INFO creating build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,882 root INFO copying django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,882 root INFO copying django/contrib/sessions/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,882 root INFO creating build/lib/django/contrib/sessions/locale/pt
2025-04-22 20:54:03,882 root INFO creating build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,883 root INFO copying django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,883 root INFO copying django/contrib/sessions/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,883 root INFO creating build/lib/django/contrib/sessions/locale/pt_BR
2025-04-22 20:54:03,883 root INFO creating build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:03,883 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 20:54:03,883 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 20:54:03,883 root INFO creating build/lib/django/contrib/sessions/locale/ro
2025-04-22 20:54:03,883 root INFO creating build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,884 root INFO copying django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,884 root INFO copying django/contrib/sessions/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,884 root INFO creating build/lib/django/contrib/sessions/locale/ru
2025-04-22 20:54:03,884 root INFO creating build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,884 root INFO copying django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,884 root INFO copying django/contrib/sessions/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,884 root INFO creating build/lib/django/contrib/sessions/locale/sk
2025-04-22 20:54:03,884 root INFO creating build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,884 root INFO copying django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,885 root INFO copying django/contrib/sessions/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,885 root INFO creating build/lib/django/contrib/sessions/locale/sl
2025-04-22 20:54:03,885 root INFO creating build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,885 root INFO copying django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,885 root INFO copying django/contrib/sessions/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,885 root INFO creating build/lib/django/contrib/sessions/locale/sq
2025-04-22 20:54:03,885 root INFO creating build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,885 root INFO copying django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,886 root INFO copying django/contrib/sessions/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,886 root INFO creating build/lib/django/contrib/sessions/locale/sr
2025-04-22 20:54:03,886 root INFO creating build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,886 root INFO copying django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,886 root INFO copying django/contrib/sessions/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,886 root INFO creating build/lib/django/contrib/sessions/locale/sr_Latn
2025-04-22 20:54:03,886 root INFO creating build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:03,886 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 20:54:03,887 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 20:54:03,887 root INFO creating build/lib/django/contrib/sessions/locale/sv
2025-04-22 20:54:03,887 root INFO creating build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,887 root INFO copying django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,887 root INFO copying django/contrib/sessions/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,887 root INFO creating build/lib/django/contrib/sessions/locale/sw
2025-04-22 20:54:03,887 root INFO creating build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,888 root INFO copying django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,888 root INFO copying django/contrib/sessions/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,888 root INFO creating build/lib/django/contrib/sessions/locale/ta
2025-04-22 20:54:03,888 root INFO creating build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,888 root INFO copying django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,888 root INFO copying django/contrib/sessions/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,888 root INFO creating build/lib/django/contrib/sessions/locale/te
2025-04-22 20:54:03,888 root INFO creating build/lib/django/contrib/sessions/locale/te/LC_MESSAGES
2025-04-22 20:54:03,889 root INFO copying django/contrib/sessions/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/te/LC_MESSAGES
2025-04-22 20:54:03,889 root INFO copying django/contrib/sessions/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/te/LC_MESSAGES
2025-04-22 20:54:03,889 root INFO creating build/lib/django/contrib/sessions/locale/tg
2025-04-22 20:54:03,889 root INFO creating build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,889 root INFO copying django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,889 root INFO copying django/contrib/sessions/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,889 root INFO creating build/lib/django/contrib/sessions/locale/th
2025-04-22 20:54:03,889 root INFO creating build/lib/django/contrib/sessions/locale/th/LC_MESSAGES
2025-04-22 20:54:03,890 root INFO copying django/contrib/sessions/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/th/LC_MESSAGES
2025-04-22 20:54:03,890 root INFO copying django/contrib/sessions/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/th/LC_MESSAGES
2025-04-22 20:54:03,890 root INFO creating build/lib/django/contrib/sessions/locale/tk
2025-04-22 20:54:03,890 root INFO creating build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,890 root INFO copying django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,890 root INFO copying django/contrib/sessions/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,890 root INFO creating build/lib/django/contrib/sessions/locale/tr
2025-04-22 20:54:03,890 root INFO creating build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,891 root INFO copying django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,891 root INFO copying django/contrib/sessions/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,891 root INFO creating build/lib/django/contrib/sessions/locale/tt
2025-04-22 20:54:03,891 root INFO creating build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,891 root INFO copying django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,891 root INFO copying django/contrib/sessions/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,891 root INFO creating build/lib/django/contrib/sessions/locale/udm
2025-04-22 20:54:03,891 root INFO creating build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,892 root INFO copying django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,892 root INFO copying django/contrib/sessions/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,892 root INFO creating build/lib/django/contrib/sessions/locale/uk
2025-04-22 20:54:03,892 root INFO creating build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,892 root INFO copying django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,892 root INFO copying django/contrib/sessions/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,892 root INFO creating build/lib/django/contrib/sessions/locale/ur
2025-04-22 20:54:03,892 root INFO creating build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,893 root INFO copying django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,893 root INFO copying django/contrib/sessions/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,893 root INFO creating build/lib/django/contrib/sessions/locale/uz
2025-04-22 20:54:03,893 root INFO creating build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,893 root INFO copying django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,893 root INFO copying django/contrib/sessions/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,893 root INFO creating build/lib/django/contrib/sessions/locale/vi
2025-04-22 20:54:03,893 root INFO creating build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,894 root INFO copying django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,894 root INFO copying django/contrib/sessions/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,894 root INFO creating build/lib/django/contrib/sessions/locale/zh_Hans
2025-04-22 20:54:03,894 root INFO creating build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:03,894 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 20:54:03,894 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 20:54:03,894 root INFO creating build/lib/django/contrib/sessions/locale/zh_Hant
2025-04-22 20:54:03,894 root INFO creating build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:03,894 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 20:54:03,895 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 20:54:03,895 root INFO creating build/lib/django/contrib/admindocs/locale
2025-04-22 20:54:03,895 root INFO creating build/lib/django/contrib/admindocs/locale/af
2025-04-22 20:54:03,895 root INFO creating build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES
2025-04-22 20:54:03,895 root INFO copying django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES
2025-04-22 20:54:03,895 root INFO copying django/contrib/admindocs/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES
2025-04-22 20:54:03,895 root INFO creating build/lib/django/contrib/admindocs/locale/ar
2025-04-22 20:54:03,895 root INFO creating build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,896 root INFO copying django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,896 root INFO copying django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,896 root INFO creating build/lib/django/contrib/admindocs/locale/ar_DZ
2025-04-22 20:54:03,896 root INFO creating build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:03,896 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 20:54:03,896 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 20:54:03,896 root INFO creating build/lib/django/contrib/admindocs/locale/ast
2025-04-22 20:54:03,897 root INFO creating build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,897 root INFO copying django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,897 root INFO copying django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,897 root INFO creating build/lib/django/contrib/admindocs/locale/az
2025-04-22 20:54:03,897 root INFO creating build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES
2025-04-22 20:54:03,897 root INFO copying django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES
2025-04-22 20:54:03,897 root INFO copying django/contrib/admindocs/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES
2025-04-22 20:54:03,897 root INFO creating build/lib/django/contrib/admindocs/locale/be
2025-04-22 20:54:03,897 root INFO creating build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES
2025-04-22 20:54:03,898 root INFO copying django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES
2025-04-22 20:54:03,898 root INFO copying django/contrib/admindocs/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES
2025-04-22 20:54:03,898 root INFO creating build/lib/django/contrib/admindocs/locale/bg
2025-04-22 20:54:03,898 root INFO creating build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,898 root INFO copying django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,898 root INFO copying django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,899 root INFO creating build/lib/django/contrib/admindocs/locale/bn
2025-04-22 20:54:03,899 root INFO creating build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,899 root INFO copying django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,899 root INFO copying django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,899 root INFO creating build/lib/django/contrib/admindocs/locale/br
2025-04-22 20:54:03,899 root INFO creating build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES
2025-04-22 20:54:03,899 root INFO copying django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES
2025-04-22 20:54:03,900 root INFO copying django/contrib/admindocs/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES
2025-04-22 20:54:03,900 root INFO creating build/lib/django/contrib/admindocs/locale/bs
2025-04-22 20:54:03,900 root INFO creating build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,900 root INFO copying django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,900 root INFO copying django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,900 root INFO creating build/lib/django/contrib/admindocs/locale/ca
2025-04-22 20:54:03,900 root INFO creating build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,900 root INFO copying django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,901 root INFO copying django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,901 root INFO creating build/lib/django/contrib/admindocs/locale/ckb
2025-04-22 20:54:03,901 root INFO creating build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,901 root INFO copying django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,901 root INFO copying django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,901 root INFO creating build/lib/django/contrib/admindocs/locale/cs
2025-04-22 20:54:03,901 root INFO creating build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,901 root INFO copying django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,902 root INFO copying django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,902 root INFO creating build/lib/django/contrib/admindocs/locale/cy
2025-04-22 20:54:03,902 root INFO creating build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,902 root INFO copying django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,902 root INFO copying django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,902 root INFO creating build/lib/django/contrib/admindocs/locale/da
2025-04-22 20:54:03,902 root INFO creating build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES
2025-04-22 20:54:03,902 root INFO copying django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES
2025-04-22 20:54:03,903 root INFO copying django/contrib/admindocs/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES
2025-04-22 20:54:03,903 root INFO creating build/lib/django/contrib/admindocs/locale/de
2025-04-22 20:54:03,903 root INFO creating build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES
2025-04-22 20:54:03,903 root INFO copying django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES
2025-04-22 20:54:03,903 root INFO copying django/contrib/admindocs/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES
2025-04-22 20:54:03,903 root INFO creating build/lib/django/contrib/admindocs/locale/dsb
2025-04-22 20:54:03,903 root INFO creating build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,903 root INFO copying django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,904 root INFO copying django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,904 root INFO creating build/lib/django/contrib/admindocs/locale/el
2025-04-22 20:54:03,904 root INFO creating build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES
2025-04-22 20:54:03,904 root INFO copying django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES
2025-04-22 20:54:03,904 root INFO copying django/contrib/admindocs/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES
2025-04-22 20:54:03,904 root INFO creating build/lib/django/contrib/admindocs/locale/en
2025-04-22 20:54:03,904 root INFO creating build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES
2025-04-22 20:54:03,905 root INFO copying django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES
2025-04-22 20:54:03,905 root INFO copying django/contrib/admindocs/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES
2025-04-22 20:54:03,905 root INFO creating build/lib/django/contrib/admindocs/locale/en_AU
2025-04-22 20:54:03,905 root INFO creating build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:03,905 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 20:54:03,905 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 20:54:03,905 root INFO creating build/lib/django/contrib/admindocs/locale/en_GB
2025-04-22 20:54:03,905 root INFO creating build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:03,906 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 20:54:03,906 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 20:54:03,906 root INFO creating build/lib/django/contrib/admindocs/locale/eo
2025-04-22 20:54:03,906 root INFO creating build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,906 root INFO copying django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,906 root INFO copying django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,906 root INFO creating build/lib/django/contrib/admindocs/locale/es
2025-04-22 20:54:03,906 root INFO creating build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES
2025-04-22 20:54:03,907 root INFO copying django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES
2025-04-22 20:54:03,907 root INFO copying django/contrib/admindocs/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES
2025-04-22 20:54:03,907 root INFO creating build/lib/django/contrib/admindocs/locale/es_AR
2025-04-22 20:54:03,907 root INFO creating build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:03,907 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 20:54:03,907 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 20:54:03,907 root INFO creating build/lib/django/contrib/admindocs/locale/es_CO
2025-04-22 20:54:03,907 root INFO creating build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:03,908 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 20:54:03,908 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 20:54:03,908 root INFO creating build/lib/django/contrib/admindocs/locale/es_MX
2025-04-22 20:54:03,908 root INFO creating build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:03,908 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 20:54:03,908 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 20:54:03,908 root INFO creating build/lib/django/contrib/admindocs/locale/es_VE
2025-04-22 20:54:03,908 root INFO creating build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:03,909 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 20:54:03,909 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 20:54:03,909 root INFO creating build/lib/django/contrib/admindocs/locale/et
2025-04-22 20:54:03,909 root INFO creating build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES
2025-04-22 20:54:03,909 root INFO copying django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES
2025-04-22 20:54:03,909 root INFO copying django/contrib/admindocs/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES
2025-04-22 20:54:03,909 root INFO creating build/lib/django/contrib/admindocs/locale/eu
2025-04-22 20:54:03,910 root INFO creating build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,910 root INFO copying django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,910 root INFO copying django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,910 root INFO creating build/lib/django/contrib/admindocs/locale/fa
2025-04-22 20:54:03,910 root INFO creating build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,910 root INFO copying django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,910 root INFO copying django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,911 root INFO creating build/lib/django/contrib/admindocs/locale/fi
2025-04-22 20:54:03,911 root INFO creating build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,911 root INFO copying django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,911 root INFO copying django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,911 root INFO creating build/lib/django/contrib/admindocs/locale/fr
2025-04-22 20:54:03,911 root INFO creating build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,911 root INFO copying django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,911 root INFO copying django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,912 root INFO creating build/lib/django/contrib/admindocs/locale/fy
2025-04-22 20:54:03,912 root INFO creating build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,912 root INFO copying django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,912 root INFO copying django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,912 root INFO creating build/lib/django/contrib/admindocs/locale/ga
2025-04-22 20:54:03,912 root INFO creating build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,912 root INFO copying django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,912 root INFO copying django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,913 root INFO creating build/lib/django/contrib/admindocs/locale/gd
2025-04-22 20:54:03,913 root INFO creating build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,913 root INFO copying django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,913 root INFO copying django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,913 root INFO creating build/lib/django/contrib/admindocs/locale/gl
2025-04-22 20:54:03,913 root INFO creating build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,913 root INFO copying django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,913 root INFO copying django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,914 root INFO creating build/lib/django/contrib/admindocs/locale/he
2025-04-22 20:54:03,914 root INFO creating build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES
2025-04-22 20:54:03,914 root INFO copying django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES
2025-04-22 20:54:03,914 root INFO copying django/contrib/admindocs/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES
2025-04-22 20:54:03,914 root INFO creating build/lib/django/contrib/admindocs/locale/hi
2025-04-22 20:54:03,914 root INFO creating build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,914 root INFO copying django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,914 root INFO copying django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES
2025-04-22 20:54:03,915 root INFO creating build/lib/django/contrib/admindocs/locale/hr
2025-04-22 20:54:03,915 root INFO creating build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,915 root INFO copying django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,915 root INFO copying django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,915 root INFO creating build/lib/django/contrib/admindocs/locale/hsb
2025-04-22 20:54:03,915 root INFO creating build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,915 root INFO copying django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,916 root INFO copying django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,916 root INFO creating build/lib/django/contrib/admindocs/locale/hu
2025-04-22 20:54:03,916 root INFO creating build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,916 root INFO copying django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,916 root INFO copying django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,916 root INFO creating build/lib/django/contrib/admindocs/locale/ia
2025-04-22 20:54:03,916 root INFO creating build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,916 root INFO copying django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,917 root INFO copying django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,917 root INFO creating build/lib/django/contrib/admindocs/locale/id
2025-04-22 20:54:03,917 root INFO creating build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES
2025-04-22 20:54:03,917 root INFO copying django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES
2025-04-22 20:54:03,917 root INFO copying django/contrib/admindocs/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES
2025-04-22 20:54:03,917 root INFO creating build/lib/django/contrib/admindocs/locale/io
2025-04-22 20:54:03,917 root INFO creating build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES
2025-04-22 20:54:03,917 root INFO copying django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES
2025-04-22 20:54:03,918 root INFO copying django/contrib/admindocs/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES
2025-04-22 20:54:03,918 root INFO creating build/lib/django/contrib/admindocs/locale/is
2025-04-22 20:54:03,918 root INFO creating build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES
2025-04-22 20:54:03,918 root INFO copying django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES
2025-04-22 20:54:03,918 root INFO copying django/contrib/admindocs/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES
2025-04-22 20:54:03,918 root INFO creating build/lib/django/contrib/admindocs/locale/it
2025-04-22 20:54:03,918 root INFO creating build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES
2025-04-22 20:54:03,918 root INFO copying django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES
2025-04-22 20:54:03,919 root INFO copying django/contrib/admindocs/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES
2025-04-22 20:54:03,919 root INFO creating build/lib/django/contrib/admindocs/locale/ja
2025-04-22 20:54:03,919 root INFO creating build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,919 root INFO copying django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,919 root INFO copying django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,919 root INFO creating build/lib/django/contrib/admindocs/locale/ka
2025-04-22 20:54:03,919 root INFO creating build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,919 root INFO copying django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,920 root INFO copying django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,920 root INFO creating build/lib/django/contrib/admindocs/locale/kab
2025-04-22 20:54:03,920 root INFO creating build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,920 root INFO copying django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,920 root INFO copying django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES
2025-04-22 20:54:03,920 root INFO creating build/lib/django/contrib/admindocs/locale/kk
2025-04-22 20:54:03,920 root INFO creating build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,920 root INFO copying django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,921 root INFO copying django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,921 root INFO creating build/lib/django/contrib/admindocs/locale/km
2025-04-22 20:54:03,921 root INFO creating build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES
2025-04-22 20:54:03,921 root INFO copying django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES
2025-04-22 20:54:03,921 root INFO copying django/contrib/admindocs/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES
2025-04-22 20:54:03,921 root INFO creating build/lib/django/contrib/admindocs/locale/kn
2025-04-22 20:54:03,921 root INFO creating build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,921 root INFO copying django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,922 root INFO copying django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES
2025-04-22 20:54:03,922 root INFO creating build/lib/django/contrib/admindocs/locale/ko
2025-04-22 20:54:03,922 root INFO creating build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,922 root INFO copying django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,922 root INFO copying django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,922 root INFO creating build/lib/django/contrib/admindocs/locale/ky
2025-04-22 20:54:03,922 root INFO creating build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,922 root INFO copying django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,923 root INFO copying django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,923 root INFO creating build/lib/django/contrib/admindocs/locale/lb
2025-04-22 20:54:03,923 root INFO creating build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,923 root INFO copying django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,923 root INFO copying django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES
2025-04-22 20:54:03,923 root INFO creating build/lib/django/contrib/admindocs/locale/lt
2025-04-22 20:54:03,923 root INFO creating build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,924 root INFO copying django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,924 root INFO copying django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,924 root INFO creating build/lib/django/contrib/admindocs/locale/lv
2025-04-22 20:54:03,924 root INFO creating build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,924 root INFO copying django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,924 root INFO copying django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,924 root INFO creating build/lib/django/contrib/admindocs/locale/mk
2025-04-22 20:54:03,924 root INFO creating build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,925 root INFO copying django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,925 root INFO copying django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,925 root INFO creating build/lib/django/contrib/admindocs/locale/ml
2025-04-22 20:54:03,925 root INFO creating build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,925 root INFO copying django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,925 root INFO copying django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,926 root INFO creating build/lib/django/contrib/admindocs/locale/mn
2025-04-22 20:54:03,926 root INFO creating build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,926 root INFO copying django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,926 root INFO copying django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,926 root INFO creating build/lib/django/contrib/admindocs/locale/mr
2025-04-22 20:54:03,926 root INFO creating build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,926 root INFO copying django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,927 root INFO copying django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES
2025-04-22 20:54:03,927 root INFO creating build/lib/django/contrib/admindocs/locale/ms
2025-04-22 20:54:03,927 root INFO creating build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,927 root INFO copying django/contrib/admindocs/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,927 root INFO copying django/contrib/admindocs/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,927 root INFO creating build/lib/django/contrib/admindocs/locale/my
2025-04-22 20:54:03,927 root INFO creating build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES
2025-04-22 20:54:03,927 root INFO copying django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES
2025-04-22 20:54:03,928 root INFO copying django/contrib/admindocs/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES
2025-04-22 20:54:03,928 root INFO creating build/lib/django/contrib/admindocs/locale/nb
2025-04-22 20:54:03,928 root INFO creating build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,928 root INFO copying django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,928 root INFO copying django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,928 root INFO creating build/lib/django/contrib/admindocs/locale/ne
2025-04-22 20:54:03,928 root INFO creating build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,928 root INFO copying django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,929 root INFO copying django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,929 root INFO creating build/lib/django/contrib/admindocs/locale/nl
2025-04-22 20:54:03,929 root INFO creating build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,929 root INFO copying django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,929 root INFO copying django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,929 root INFO creating build/lib/django/contrib/admindocs/locale/nn
2025-04-22 20:54:03,929 root INFO creating build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,929 root INFO copying django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,930 root INFO copying django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,930 root INFO creating build/lib/django/contrib/admindocs/locale/os
2025-04-22 20:54:03,930 root INFO creating build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES
2025-04-22 20:54:03,930 root INFO copying django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES
2025-04-22 20:54:03,930 root INFO copying django/contrib/admindocs/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES
2025-04-22 20:54:03,930 root INFO creating build/lib/django/contrib/admindocs/locale/pa
2025-04-22 20:54:03,930 root INFO creating build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,930 root INFO copying django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,931 root INFO copying django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES
2025-04-22 20:54:03,931 root INFO creating build/lib/django/contrib/admindocs/locale/pl
2025-04-22 20:54:03,931 root INFO creating build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,931 root INFO copying django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,931 root INFO copying django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,931 root INFO creating build/lib/django/contrib/admindocs/locale/pt
2025-04-22 20:54:03,931 root INFO creating build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,932 root INFO copying django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,932 root INFO copying django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,932 root INFO creating build/lib/django/contrib/admindocs/locale/pt_BR
2025-04-22 20:54:03,932 root INFO creating build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:03,932 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 20:54:03,932 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 20:54:03,932 root INFO creating build/lib/django/contrib/admindocs/locale/ro
2025-04-22 20:54:03,933 root INFO creating build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,933 root INFO copying django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,933 root INFO copying django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,933 root INFO creating build/lib/django/contrib/admindocs/locale/ru
2025-04-22 20:54:03,933 root INFO creating build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,933 root INFO copying django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,933 root INFO copying django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,934 root INFO creating build/lib/django/contrib/admindocs/locale/sk
2025-04-22 20:54:03,934 root INFO creating build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,934 root INFO copying django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,934 root INFO copying django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,934 root INFO creating build/lib/django/contrib/admindocs/locale/sl
2025-04-22 20:54:03,934 root INFO creating build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,934 root INFO copying django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,934 root INFO copying django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,935 root INFO creating build/lib/django/contrib/admindocs/locale/sq
2025-04-22 20:54:03,935 root INFO creating build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,935 root INFO copying django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,935 root INFO copying django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,935 root INFO creating build/lib/django/contrib/admindocs/locale/sr
2025-04-22 20:54:03,935 root INFO creating build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,935 root INFO copying django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,935 root INFO copying django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,936 root INFO creating build/lib/django/contrib/admindocs/locale/sr_Latn
2025-04-22 20:54:03,936 root INFO creating build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:03,936 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 20:54:03,936 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 20:54:03,936 root INFO creating build/lib/django/contrib/admindocs/locale/sv
2025-04-22 20:54:03,936 root INFO creating build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,936 root INFO copying django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,936 root INFO copying django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,937 root INFO creating build/lib/django/contrib/admindocs/locale/sw
2025-04-22 20:54:03,937 root INFO creating build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,937 root INFO copying django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,937 root INFO copying django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES
2025-04-22 20:54:03,937 root INFO creating build/lib/django/contrib/admindocs/locale/ta
2025-04-22 20:54:03,937 root INFO creating build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,937 root INFO copying django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,938 root INFO copying django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES
2025-04-22 20:54:03,938 root INFO creating build/lib/django/contrib/admindocs/locale/te
2025-04-22 20:54:03,938 root INFO creating build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES
2025-04-22 20:54:03,938 root INFO copying django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES
2025-04-22 20:54:03,938 root INFO copying django/contrib/admindocs/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES
2025-04-22 20:54:03,938 root INFO creating build/lib/django/contrib/admindocs/locale/tg
2025-04-22 20:54:03,938 root INFO creating build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,938 root INFO copying django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,939 root INFO copying django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,939 root INFO creating build/lib/django/contrib/admindocs/locale/th
2025-04-22 20:54:03,939 root INFO creating build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES
2025-04-22 20:54:03,939 root INFO copying django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES
2025-04-22 20:54:03,939 root INFO copying django/contrib/admindocs/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES
2025-04-22 20:54:03,939 root INFO creating build/lib/django/contrib/admindocs/locale/tr
2025-04-22 20:54:03,939 root INFO creating build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,939 root INFO copying django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,940 root INFO copying django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,940 root INFO creating build/lib/django/contrib/admindocs/locale/tt
2025-04-22 20:54:03,940 root INFO creating build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,940 root INFO copying django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,940 root INFO copying django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES
2025-04-22 20:54:03,940 root INFO creating build/lib/django/contrib/admindocs/locale/udm
2025-04-22 20:54:03,940 root INFO creating build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,940 root INFO copying django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,941 root INFO copying django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES
2025-04-22 20:54:03,941 root INFO creating build/lib/django/contrib/admindocs/locale/uk
2025-04-22 20:54:03,941 root INFO creating build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,941 root INFO copying django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,941 root INFO copying django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,941 root INFO creating build/lib/django/contrib/admindocs/locale/ur
2025-04-22 20:54:03,941 root INFO creating build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,942 root INFO copying django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,942 root INFO copying django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES
2025-04-22 20:54:03,942 root INFO creating build/lib/django/contrib/admindocs/locale/vi
2025-04-22 20:54:03,942 root INFO creating build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,942 root INFO copying django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,942 root INFO copying django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES
2025-04-22 20:54:03,942 root INFO creating build/lib/django/contrib/admindocs/locale/zh_Hans
2025-04-22 20:54:03,943 root INFO creating build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:03,943 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 20:54:03,943 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 20:54:03,943 root INFO creating build/lib/django/contrib/admindocs/locale/zh_Hant
2025-04-22 20:54:03,943 root INFO creating build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:03,943 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 20:54:03,943 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 20:54:03,943 root INFO creating build/lib/django/contrib/admindocs/templates
2025-04-22 20:54:03,944 root INFO creating build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:03,944 root INFO copying django/contrib/admindocs/templates/admin_doc/bookmarklets.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:03,944 root INFO copying django/contrib/admindocs/templates/admin_doc/index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:03,944 root INFO copying django/contrib/admindocs/templates/admin_doc/missing_docutils.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:03,944 root INFO copying django/contrib/admindocs/templates/admin_doc/model_detail.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:03,944 root INFO copying django/contrib/admindocs/templates/admin_doc/model_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:03,944 root INFO copying django/contrib/admindocs/templates/admin_doc/template_detail.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:03,945 root INFO copying django/contrib/admindocs/templates/admin_doc/template_filter_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:03,945 root INFO copying django/contrib/admindocs/templates/admin_doc/template_tag_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:03,945 root INFO copying django/contrib/admindocs/templates/admin_doc/view_detail.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:03,945 root INFO copying django/contrib/admindocs/templates/admin_doc/view_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:03,945 root INFO creating build/lib/django/contrib/postgres/jinja2
2025-04-22 20:54:03,945 root INFO creating build/lib/django/contrib/postgres/jinja2/postgres
2025-04-22 20:54:03,945 root INFO creating build/lib/django/contrib/postgres/jinja2/postgres/widgets
2025-04-22 20:54:03,946 root INFO copying django/contrib/postgres/jinja2/postgres/widgets/split_array.html -> build/lib/django/contrib/postgres/jinja2/postgres/widgets
2025-04-22 20:54:03,946 root INFO creating build/lib/django/contrib/postgres/locale
2025-04-22 20:54:03,946 root INFO creating build/lib/django/contrib/postgres/locale/af
2025-04-22 20:54:03,946 root INFO creating build/lib/django/contrib/postgres/locale/af/LC_MESSAGES
2025-04-22 20:54:03,946 root INFO copying django/contrib/postgres/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/af/LC_MESSAGES
2025-04-22 20:54:03,946 root INFO copying django/contrib/postgres/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/af/LC_MESSAGES
2025-04-22 20:54:03,946 root INFO creating build/lib/django/contrib/postgres/locale/ar
2025-04-22 20:54:03,946 root INFO creating build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,946 root INFO copying django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,947 root INFO copying django/contrib/postgres/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,947 root INFO creating build/lib/django/contrib/postgres/locale/ar_DZ
2025-04-22 20:54:03,947 root INFO creating build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:03,947 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 20:54:03,947 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 20:54:03,947 root INFO creating build/lib/django/contrib/postgres/locale/az
2025-04-22 20:54:03,947 root INFO creating build/lib/django/contrib/postgres/locale/az/LC_MESSAGES
2025-04-22 20:54:03,947 root INFO copying django/contrib/postgres/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/az/LC_MESSAGES
2025-04-22 20:54:03,948 root INFO copying django/contrib/postgres/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/az/LC_MESSAGES
2025-04-22 20:54:03,948 root INFO creating build/lib/django/contrib/postgres/locale/be
2025-04-22 20:54:03,948 root INFO creating build/lib/django/contrib/postgres/locale/be/LC_MESSAGES
2025-04-22 20:54:03,948 root INFO copying django/contrib/postgres/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/be/LC_MESSAGES
2025-04-22 20:54:03,948 root INFO copying django/contrib/postgres/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/be/LC_MESSAGES
2025-04-22 20:54:03,948 root INFO creating build/lib/django/contrib/postgres/locale/bg
2025-04-22 20:54:03,948 root INFO creating build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,948 root INFO copying django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,949 root INFO copying django/contrib/postgres/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,949 root INFO creating build/lib/django/contrib/postgres/locale/ca
2025-04-22 20:54:03,949 root INFO creating build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,949 root INFO copying django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,949 root INFO copying django/contrib/postgres/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,949 root INFO creating build/lib/django/contrib/postgres/locale/ckb
2025-04-22 20:54:03,949 root INFO creating build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,949 root INFO copying django/contrib/postgres/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,950 root INFO copying django/contrib/postgres/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,950 root INFO creating build/lib/django/contrib/postgres/locale/cs
2025-04-22 20:54:03,950 root INFO creating build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,950 root INFO copying django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,950 root INFO copying django/contrib/postgres/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,950 root INFO creating build/lib/django/contrib/postgres/locale/da
2025-04-22 20:54:03,950 root INFO creating build/lib/django/contrib/postgres/locale/da/LC_MESSAGES
2025-04-22 20:54:03,950 root INFO copying django/contrib/postgres/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/da/LC_MESSAGES
2025-04-22 20:54:03,951 root INFO copying django/contrib/postgres/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/da/LC_MESSAGES
2025-04-22 20:54:03,951 root INFO creating build/lib/django/contrib/postgres/locale/de
2025-04-22 20:54:03,951 root INFO creating build/lib/django/contrib/postgres/locale/de/LC_MESSAGES
2025-04-22 20:54:03,951 root INFO copying django/contrib/postgres/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/de/LC_MESSAGES
2025-04-22 20:54:03,951 root INFO copying django/contrib/postgres/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/de/LC_MESSAGES
2025-04-22 20:54:03,951 root INFO creating build/lib/django/contrib/postgres/locale/dsb
2025-04-22 20:54:03,951 root INFO creating build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,951 root INFO copying django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,952 root INFO copying django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,952 root INFO creating build/lib/django/contrib/postgres/locale/el
2025-04-22 20:54:03,952 root INFO creating build/lib/django/contrib/postgres/locale/el/LC_MESSAGES
2025-04-22 20:54:03,952 root INFO copying django/contrib/postgres/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/el/LC_MESSAGES
2025-04-22 20:54:03,952 root INFO copying django/contrib/postgres/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/el/LC_MESSAGES
2025-04-22 20:54:03,952 root INFO creating build/lib/django/contrib/postgres/locale/en
2025-04-22 20:54:03,952 root INFO creating build/lib/django/contrib/postgres/locale/en/LC_MESSAGES
2025-04-22 20:54:03,953 root INFO copying django/contrib/postgres/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/en/LC_MESSAGES
2025-04-22 20:54:03,953 root INFO copying django/contrib/postgres/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/en/LC_MESSAGES
2025-04-22 20:54:03,953 root INFO creating build/lib/django/contrib/postgres/locale/en_AU
2025-04-22 20:54:03,953 root INFO creating build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:03,953 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 20:54:03,953 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 20:54:03,953 root INFO creating build/lib/django/contrib/postgres/locale/eo
2025-04-22 20:54:03,953 root INFO creating build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,954 root INFO copying django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,954 root INFO copying django/contrib/postgres/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,954 root INFO creating build/lib/django/contrib/postgres/locale/es
2025-04-22 20:54:03,954 root INFO creating build/lib/django/contrib/postgres/locale/es/LC_MESSAGES
2025-04-22 20:54:03,954 root INFO copying django/contrib/postgres/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/es/LC_MESSAGES
2025-04-22 20:54:03,954 root INFO copying django/contrib/postgres/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/es/LC_MESSAGES
2025-04-22 20:54:03,954 root INFO creating build/lib/django/contrib/postgres/locale/es_AR
2025-04-22 20:54:03,954 root INFO creating build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:03,954 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 20:54:03,955 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 20:54:03,955 root INFO creating build/lib/django/contrib/postgres/locale/es_CO
2025-04-22 20:54:03,955 root INFO creating build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:03,955 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 20:54:03,955 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 20:54:03,955 root INFO creating build/lib/django/contrib/postgres/locale/es_MX
2025-04-22 20:54:03,955 root INFO creating build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:03,955 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 20:54:03,956 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 20:54:03,956 root INFO creating build/lib/django/contrib/postgres/locale/et
2025-04-22 20:54:03,956 root INFO creating build/lib/django/contrib/postgres/locale/et/LC_MESSAGES
2025-04-22 20:54:03,956 root INFO copying django/contrib/postgres/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/et/LC_MESSAGES
2025-04-22 20:54:03,956 root INFO copying django/contrib/postgres/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/et/LC_MESSAGES
2025-04-22 20:54:03,956 root INFO creating build/lib/django/contrib/postgres/locale/eu
2025-04-22 20:54:03,956 root INFO creating build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,956 root INFO copying django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,957 root INFO copying django/contrib/postgres/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,957 root INFO creating build/lib/django/contrib/postgres/locale/fa
2025-04-22 20:54:03,957 root INFO creating build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,957 root INFO copying django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,957 root INFO copying django/contrib/postgres/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,957 root INFO creating build/lib/django/contrib/postgres/locale/fi
2025-04-22 20:54:03,957 root INFO creating build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,957 root INFO copying django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,958 root INFO copying django/contrib/postgres/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,958 root INFO creating build/lib/django/contrib/postgres/locale/fr
2025-04-22 20:54:03,958 root INFO creating build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,958 root INFO copying django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,958 root INFO copying django/contrib/postgres/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,958 root INFO creating build/lib/django/contrib/postgres/locale/gd
2025-04-22 20:54:03,958 root INFO creating build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,958 root INFO copying django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,959 root INFO copying django/contrib/postgres/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,959 root INFO creating build/lib/django/contrib/postgres/locale/gl
2025-04-22 20:54:03,959 root INFO creating build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,959 root INFO copying django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,959 root INFO copying django/contrib/postgres/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,959 root INFO creating build/lib/django/contrib/postgres/locale/he
2025-04-22 20:54:03,959 root INFO creating build/lib/django/contrib/postgres/locale/he/LC_MESSAGES
2025-04-22 20:54:03,959 root INFO copying django/contrib/postgres/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/he/LC_MESSAGES
2025-04-22 20:54:03,960 root INFO copying django/contrib/postgres/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/he/LC_MESSAGES
2025-04-22 20:54:03,960 root INFO creating build/lib/django/contrib/postgres/locale/hr
2025-04-22 20:54:03,960 root INFO creating build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,960 root INFO copying django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,960 root INFO copying django/contrib/postgres/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES
2025-04-22 20:54:03,960 root INFO creating build/lib/django/contrib/postgres/locale/hsb
2025-04-22 20:54:03,960 root INFO creating build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,961 root INFO copying django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,961 root INFO copying django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES
2025-04-22 20:54:03,961 root INFO creating build/lib/django/contrib/postgres/locale/hu
2025-04-22 20:54:03,961 root INFO creating build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,961 root INFO copying django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,961 root INFO copying django/contrib/postgres/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES
2025-04-22 20:54:03,961 root INFO creating build/lib/django/contrib/postgres/locale/hy
2025-04-22 20:54:03,961 root INFO creating build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,962 root INFO copying django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,962 root INFO copying django/contrib/postgres/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES
2025-04-22 20:54:03,962 root INFO creating build/lib/django/contrib/postgres/locale/ia
2025-04-22 20:54:03,962 root INFO creating build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,962 root INFO copying django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,962 root INFO copying django/contrib/postgres/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES
2025-04-22 20:54:03,962 root INFO creating build/lib/django/contrib/postgres/locale/id
2025-04-22 20:54:03,962 root INFO creating build/lib/django/contrib/postgres/locale/id/LC_MESSAGES
2025-04-22 20:54:03,963 root INFO copying django/contrib/postgres/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/id/LC_MESSAGES
2025-04-22 20:54:03,963 root INFO copying django/contrib/postgres/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/id/LC_MESSAGES
2025-04-22 20:54:03,963 root INFO creating build/lib/django/contrib/postgres/locale/is
2025-04-22 20:54:03,963 root INFO creating build/lib/django/contrib/postgres/locale/is/LC_MESSAGES
2025-04-22 20:54:03,963 root INFO copying django/contrib/postgres/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/is/LC_MESSAGES
2025-04-22 20:54:03,963 root INFO copying django/contrib/postgres/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/is/LC_MESSAGES
2025-04-22 20:54:03,963 root INFO creating build/lib/django/contrib/postgres/locale/it
2025-04-22 20:54:03,964 root INFO creating build/lib/django/contrib/postgres/locale/it/LC_MESSAGES
2025-04-22 20:54:03,964 root INFO copying django/contrib/postgres/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/it/LC_MESSAGES
2025-04-22 20:54:03,964 root INFO copying django/contrib/postgres/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/it/LC_MESSAGES
2025-04-22 20:54:03,964 root INFO creating build/lib/django/contrib/postgres/locale/ja
2025-04-22 20:54:03,964 root INFO creating build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,964 root INFO copying django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,964 root INFO copying django/contrib/postgres/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES
2025-04-22 20:54:03,964 root INFO creating build/lib/django/contrib/postgres/locale/ka
2025-04-22 20:54:03,965 root INFO creating build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,965 root INFO copying django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,965 root INFO copying django/contrib/postgres/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES
2025-04-22 20:54:03,965 root INFO creating build/lib/django/contrib/postgres/locale/kk
2025-04-22 20:54:03,965 root INFO creating build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,965 root INFO copying django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,965 root INFO copying django/contrib/postgres/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES
2025-04-22 20:54:03,965 root INFO creating build/lib/django/contrib/postgres/locale/ko
2025-04-22 20:54:03,966 root INFO creating build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,966 root INFO copying django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,966 root INFO copying django/contrib/postgres/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES
2025-04-22 20:54:03,966 root INFO creating build/lib/django/contrib/postgres/locale/ky
2025-04-22 20:54:03,966 root INFO creating build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,966 root INFO copying django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,966 root INFO copying django/contrib/postgres/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES
2025-04-22 20:54:03,966 root INFO creating build/lib/django/contrib/postgres/locale/lt
2025-04-22 20:54:03,967 root INFO creating build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,967 root INFO copying django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,967 root INFO copying django/contrib/postgres/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES
2025-04-22 20:54:03,967 root INFO creating build/lib/django/contrib/postgres/locale/lv
2025-04-22 20:54:03,967 root INFO creating build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,967 root INFO copying django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,967 root INFO copying django/contrib/postgres/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES
2025-04-22 20:54:03,967 root INFO creating build/lib/django/contrib/postgres/locale/mk
2025-04-22 20:54:03,968 root INFO creating build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,968 root INFO copying django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,968 root INFO copying django/contrib/postgres/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES
2025-04-22 20:54:03,968 root INFO creating build/lib/django/contrib/postgres/locale/ml
2025-04-22 20:54:03,968 root INFO creating build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,968 root INFO copying django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,968 root INFO copying django/contrib/postgres/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES
2025-04-22 20:54:03,969 root INFO creating build/lib/django/contrib/postgres/locale/mn
2025-04-22 20:54:03,969 root INFO creating build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,969 root INFO copying django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,969 root INFO copying django/contrib/postgres/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES
2025-04-22 20:54:03,969 root INFO creating build/lib/django/contrib/postgres/locale/ms
2025-04-22 20:54:03,969 root INFO creating build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,969 root INFO copying django/contrib/postgres/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,969 root INFO copying django/contrib/postgres/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES
2025-04-22 20:54:03,970 root INFO creating build/lib/django/contrib/postgres/locale/nb
2025-04-22 20:54:03,970 root INFO creating build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,970 root INFO copying django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,970 root INFO copying django/contrib/postgres/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES
2025-04-22 20:54:03,970 root INFO creating build/lib/django/contrib/postgres/locale/ne
2025-04-22 20:54:03,970 root INFO creating build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,970 root INFO copying django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,970 root INFO copying django/contrib/postgres/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES
2025-04-22 20:54:03,971 root INFO creating build/lib/django/contrib/postgres/locale/nl
2025-04-22 20:54:03,971 root INFO creating build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,971 root INFO copying django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,971 root INFO copying django/contrib/postgres/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES
2025-04-22 20:54:03,971 root INFO creating build/lib/django/contrib/postgres/locale/nn
2025-04-22 20:54:03,971 root INFO creating build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,971 root INFO copying django/contrib/postgres/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,971 root INFO copying django/contrib/postgres/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES
2025-04-22 20:54:03,972 root INFO creating build/lib/django/contrib/postgres/locale/pl
2025-04-22 20:54:03,972 root INFO creating build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,972 root INFO copying django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,972 root INFO copying django/contrib/postgres/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES
2025-04-22 20:54:03,972 root INFO creating build/lib/django/contrib/postgres/locale/pt
2025-04-22 20:54:03,972 root INFO creating build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,972 root INFO copying django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,972 root INFO copying django/contrib/postgres/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES
2025-04-22 20:54:03,973 root INFO creating build/lib/django/contrib/postgres/locale/pt_BR
2025-04-22 20:54:03,973 root INFO creating build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:03,973 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 20:54:03,973 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 20:54:03,973 root INFO creating build/lib/django/contrib/postgres/locale/ro
2025-04-22 20:54:03,973 root INFO creating build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,973 root INFO copying django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,973 root INFO copying django/contrib/postgres/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES
2025-04-22 20:54:03,974 root INFO creating build/lib/django/contrib/postgres/locale/ru
2025-04-22 20:54:03,974 root INFO creating build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,974 root INFO copying django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,974 root INFO copying django/contrib/postgres/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES
2025-04-22 20:54:03,974 root INFO creating build/lib/django/contrib/postgres/locale/sk
2025-04-22 20:54:03,974 root INFO creating build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,974 root INFO copying django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,974 root INFO copying django/contrib/postgres/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES
2025-04-22 20:54:03,975 root INFO creating build/lib/django/contrib/postgres/locale/sl
2025-04-22 20:54:03,975 root INFO creating build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,975 root INFO copying django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,975 root INFO copying django/contrib/postgres/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES
2025-04-22 20:54:03,975 root INFO creating build/lib/django/contrib/postgres/locale/sq
2025-04-22 20:54:03,975 root INFO creating build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,975 root INFO copying django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,976 root INFO copying django/contrib/postgres/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES
2025-04-22 20:54:03,976 root INFO creating build/lib/django/contrib/postgres/locale/sr
2025-04-22 20:54:03,976 root INFO creating build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,976 root INFO copying django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,976 root INFO copying django/contrib/postgres/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES
2025-04-22 20:54:03,976 root INFO creating build/lib/django/contrib/postgres/locale/sr_Latn
2025-04-22 20:54:03,976 root INFO creating build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:03,976 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 20:54:03,976 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 20:54:03,977 root INFO creating build/lib/django/contrib/postgres/locale/sv
2025-04-22 20:54:03,977 root INFO creating build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,977 root INFO copying django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,977 root INFO copying django/contrib/postgres/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES
2025-04-22 20:54:03,977 root INFO creating build/lib/django/contrib/postgres/locale/tg
2025-04-22 20:54:03,977 root INFO creating build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,977 root INFO copying django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,977 root INFO copying django/contrib/postgres/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES
2025-04-22 20:54:03,978 root INFO creating build/lib/django/contrib/postgres/locale/tk
2025-04-22 20:54:03,978 root INFO creating build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,978 root INFO copying django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,978 root INFO copying django/contrib/postgres/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES
2025-04-22 20:54:03,978 root INFO creating build/lib/django/contrib/postgres/locale/tr
2025-04-22 20:54:03,978 root INFO creating build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,978 root INFO copying django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,979 root INFO copying django/contrib/postgres/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES
2025-04-22 20:54:03,979 root INFO creating build/lib/django/contrib/postgres/locale/uk
2025-04-22 20:54:03,979 root INFO creating build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,979 root INFO copying django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,979 root INFO copying django/contrib/postgres/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES
2025-04-22 20:54:03,979 root INFO creating build/lib/django/contrib/postgres/locale/uz
2025-04-22 20:54:03,979 root INFO creating build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,979 root INFO copying django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,980 root INFO copying django/contrib/postgres/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES
2025-04-22 20:54:03,980 root INFO creating build/lib/django/contrib/postgres/locale/zh_Hans
2025-04-22 20:54:03,980 root INFO creating build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:03,980 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 20:54:03,980 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 20:54:03,980 root INFO creating build/lib/django/contrib/postgres/locale/zh_Hant
2025-04-22 20:54:03,980 root INFO creating build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:03,980 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 20:54:03,981 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 20:54:03,981 root INFO creating build/lib/django/contrib/postgres/templates
2025-04-22 20:54:03,981 root INFO creating build/lib/django/contrib/postgres/templates/postgres
2025-04-22 20:54:03,981 root INFO creating build/lib/django/contrib/postgres/templates/postgres/widgets
2025-04-22 20:54:03,981 root INFO copying django/contrib/postgres/templates/postgres/widgets/split_array.html -> build/lib/django/contrib/postgres/templates/postgres/widgets
2025-04-22 20:54:03,981 root INFO creating build/lib/django/contrib/gis/locale
2025-04-22 20:54:03,981 root INFO creating build/lib/django/contrib/gis/locale/af
2025-04-22 20:54:03,981 root INFO creating build/lib/django/contrib/gis/locale/af/LC_MESSAGES
2025-04-22 20:54:03,981 root INFO copying django/contrib/gis/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/af/LC_MESSAGES
2025-04-22 20:54:03,982 root INFO copying django/contrib/gis/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/af/LC_MESSAGES
2025-04-22 20:54:03,982 root INFO creating build/lib/django/contrib/gis/locale/ar
2025-04-22 20:54:03,982 root INFO creating build/lib/django/contrib/gis/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,982 root INFO copying django/contrib/gis/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,982 root INFO copying django/contrib/gis/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ar/LC_MESSAGES
2025-04-22 20:54:03,982 root INFO creating build/lib/django/contrib/gis/locale/ar_DZ
2025-04-22 20:54:03,982 root INFO creating build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:03,982 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 20:54:03,983 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 20:54:03,983 root INFO creating build/lib/django/contrib/gis/locale/ast
2025-04-22 20:54:03,983 root INFO creating build/lib/django/contrib/gis/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,983 root INFO copying django/contrib/gis/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,983 root INFO copying django/contrib/gis/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ast/LC_MESSAGES
2025-04-22 20:54:03,983 root INFO creating build/lib/django/contrib/gis/locale/az
2025-04-22 20:54:03,983 root INFO creating build/lib/django/contrib/gis/locale/az/LC_MESSAGES
2025-04-22 20:54:03,983 root INFO copying django/contrib/gis/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/az/LC_MESSAGES
2025-04-22 20:54:03,983 root INFO copying django/contrib/gis/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/az/LC_MESSAGES
2025-04-22 20:54:03,984 root INFO creating build/lib/django/contrib/gis/locale/be
2025-04-22 20:54:03,984 root INFO creating build/lib/django/contrib/gis/locale/be/LC_MESSAGES
2025-04-22 20:54:03,984 root INFO copying django/contrib/gis/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/be/LC_MESSAGES
2025-04-22 20:54:03,984 root INFO copying django/contrib/gis/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/be/LC_MESSAGES
2025-04-22 20:54:03,984 root INFO creating build/lib/django/contrib/gis/locale/bg
2025-04-22 20:54:03,984 root INFO creating build/lib/django/contrib/gis/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,984 root INFO copying django/contrib/gis/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,984 root INFO copying django/contrib/gis/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/bg/LC_MESSAGES
2025-04-22 20:54:03,985 root INFO creating build/lib/django/contrib/gis/locale/bn
2025-04-22 20:54:03,985 root INFO creating build/lib/django/contrib/gis/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,985 root INFO copying django/contrib/gis/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,985 root INFO copying django/contrib/gis/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/bn/LC_MESSAGES
2025-04-22 20:54:03,985 root INFO creating build/lib/django/contrib/gis/locale/br
2025-04-22 20:54:03,985 root INFO creating build/lib/django/contrib/gis/locale/br/LC_MESSAGES
2025-04-22 20:54:03,985 root INFO copying django/contrib/gis/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/br/LC_MESSAGES
2025-04-22 20:54:03,986 root INFO copying django/contrib/gis/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/br/LC_MESSAGES
2025-04-22 20:54:03,986 root INFO creating build/lib/django/contrib/gis/locale/bs
2025-04-22 20:54:03,986 root INFO creating build/lib/django/contrib/gis/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,986 root INFO copying django/contrib/gis/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,986 root INFO copying django/contrib/gis/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/bs/LC_MESSAGES
2025-04-22 20:54:03,986 root INFO creating build/lib/django/contrib/gis/locale/ca
2025-04-22 20:54:03,986 root INFO creating build/lib/django/contrib/gis/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,986 root INFO copying django/contrib/gis/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,986 root INFO copying django/contrib/gis/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ca/LC_MESSAGES
2025-04-22 20:54:03,987 root INFO creating build/lib/django/contrib/gis/locale/ckb
2025-04-22 20:54:03,987 root INFO creating build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,987 root INFO copying django/contrib/gis/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,987 root INFO copying django/contrib/gis/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES
2025-04-22 20:54:03,987 root INFO creating build/lib/django/contrib/gis/locale/cs
2025-04-22 20:54:03,987 root INFO creating build/lib/django/contrib/gis/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,987 root INFO copying django/contrib/gis/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,987 root INFO copying django/contrib/gis/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/cs/LC_MESSAGES
2025-04-22 20:54:03,988 root INFO creating build/lib/django/contrib/gis/locale/cy
2025-04-22 20:54:03,988 root INFO creating build/lib/django/contrib/gis/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,988 root INFO copying django/contrib/gis/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,988 root INFO copying django/contrib/gis/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/cy/LC_MESSAGES
2025-04-22 20:54:03,988 root INFO creating build/lib/django/contrib/gis/locale/da
2025-04-22 20:54:03,988 root INFO creating build/lib/django/contrib/gis/locale/da/LC_MESSAGES
2025-04-22 20:54:03,988 root INFO copying django/contrib/gis/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/da/LC_MESSAGES
2025-04-22 20:54:03,988 root INFO copying django/contrib/gis/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/da/LC_MESSAGES
2025-04-22 20:54:03,989 root INFO creating build/lib/django/contrib/gis/locale/de
2025-04-22 20:54:03,989 root INFO creating build/lib/django/contrib/gis/locale/de/LC_MESSAGES
2025-04-22 20:54:03,989 root INFO copying django/contrib/gis/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/de/LC_MESSAGES
2025-04-22 20:54:03,989 root INFO copying django/contrib/gis/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/de/LC_MESSAGES
2025-04-22 20:54:03,989 root INFO creating build/lib/django/contrib/gis/locale/dsb
2025-04-22 20:54:03,989 root INFO creating build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,989 root INFO copying django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,989 root INFO copying django/contrib/gis/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES
2025-04-22 20:54:03,990 root INFO creating build/lib/django/contrib/gis/locale/el
2025-04-22 20:54:03,990 root INFO creating build/lib/django/contrib/gis/locale/el/LC_MESSAGES
2025-04-22 20:54:03,990 root INFO copying django/contrib/gis/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/el/LC_MESSAGES
2025-04-22 20:54:03,990 root INFO copying django/contrib/gis/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/el/LC_MESSAGES
2025-04-22 20:54:03,990 root INFO creating build/lib/django/contrib/gis/locale/en
2025-04-22 20:54:03,990 root INFO creating build/lib/django/contrib/gis/locale/en/LC_MESSAGES
2025-04-22 20:54:03,990 root INFO copying django/contrib/gis/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/en/LC_MESSAGES
2025-04-22 20:54:03,990 root INFO copying django/contrib/gis/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/en/LC_MESSAGES
2025-04-22 20:54:03,991 root INFO creating build/lib/django/contrib/gis/locale/en_AU
2025-04-22 20:54:03,991 root INFO creating build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:03,991 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 20:54:03,991 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 20:54:03,991 root INFO creating build/lib/django/contrib/gis/locale/en_GB
2025-04-22 20:54:03,991 root INFO creating build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:03,991 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 20:54:03,991 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 20:54:03,992 root INFO creating build/lib/django/contrib/gis/locale/eo
2025-04-22 20:54:03,992 root INFO creating build/lib/django/contrib/gis/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,992 root INFO copying django/contrib/gis/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,992 root INFO copying django/contrib/gis/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/eo/LC_MESSAGES
2025-04-22 20:54:03,992 root INFO creating build/lib/django/contrib/gis/locale/es
2025-04-22 20:54:03,992 root INFO creating build/lib/django/contrib/gis/locale/es/LC_MESSAGES
2025-04-22 20:54:03,992 root INFO copying django/contrib/gis/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es/LC_MESSAGES
2025-04-22 20:54:03,992 root INFO copying django/contrib/gis/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es/LC_MESSAGES
2025-04-22 20:54:03,993 root INFO creating build/lib/django/contrib/gis/locale/es_AR
2025-04-22 20:54:03,993 root INFO creating build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:03,993 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 20:54:03,993 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 20:54:03,993 root INFO creating build/lib/django/contrib/gis/locale/es_CO
2025-04-22 20:54:03,993 root INFO creating build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:03,993 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 20:54:03,993 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 20:54:03,993 root INFO creating build/lib/django/contrib/gis/locale/es_MX
2025-04-22 20:54:03,994 root INFO creating build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:03,994 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 20:54:03,994 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 20:54:03,994 root INFO creating build/lib/django/contrib/gis/locale/es_VE
2025-04-22 20:54:03,994 root INFO creating build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:03,994 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 20:54:03,994 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 20:54:03,994 root INFO creating build/lib/django/contrib/gis/locale/et
2025-04-22 20:54:03,995 root INFO creating build/lib/django/contrib/gis/locale/et/LC_MESSAGES
2025-04-22 20:54:03,995 root INFO copying django/contrib/gis/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/et/LC_MESSAGES
2025-04-22 20:54:03,995 root INFO copying django/contrib/gis/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/et/LC_MESSAGES
2025-04-22 20:54:03,995 root INFO creating build/lib/django/contrib/gis/locale/eu
2025-04-22 20:54:03,995 root INFO creating build/lib/django/contrib/gis/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,995 root INFO copying django/contrib/gis/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,995 root INFO copying django/contrib/gis/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/eu/LC_MESSAGES
2025-04-22 20:54:03,995 root INFO creating build/lib/django/contrib/gis/locale/fa
2025-04-22 20:54:03,996 root INFO creating build/lib/django/contrib/gis/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,996 root INFO copying django/contrib/gis/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,996 root INFO copying django/contrib/gis/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fa/LC_MESSAGES
2025-04-22 20:54:03,996 root INFO creating build/lib/django/contrib/gis/locale/fi
2025-04-22 20:54:03,996 root INFO creating build/lib/django/contrib/gis/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,996 root INFO copying django/contrib/gis/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,996 root INFO copying django/contrib/gis/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fi/LC_MESSAGES
2025-04-22 20:54:03,996 root INFO creating build/lib/django/contrib/gis/locale/fr
2025-04-22 20:54:03,996 root INFO creating build/lib/django/contrib/gis/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,997 root INFO copying django/contrib/gis/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,997 root INFO copying django/contrib/gis/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fr/LC_MESSAGES
2025-04-22 20:54:03,997 root INFO creating build/lib/django/contrib/gis/locale/fy
2025-04-22 20:54:03,997 root INFO creating build/lib/django/contrib/gis/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,997 root INFO copying django/contrib/gis/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,997 root INFO copying django/contrib/gis/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fy/LC_MESSAGES
2025-04-22 20:54:03,997 root INFO creating build/lib/django/contrib/gis/locale/ga
2025-04-22 20:54:03,997 root INFO creating build/lib/django/contrib/gis/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,998 root INFO copying django/contrib/gis/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,998 root INFO copying django/contrib/gis/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ga/LC_MESSAGES
2025-04-22 20:54:03,998 root INFO creating build/lib/django/contrib/gis/locale/gd
2025-04-22 20:54:03,998 root INFO creating build/lib/django/contrib/gis/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,998 root INFO copying django/contrib/gis/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,998 root INFO copying django/contrib/gis/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/gd/LC_MESSAGES
2025-04-22 20:54:03,998 root INFO creating build/lib/django/contrib/gis/locale/gl
2025-04-22 20:54:03,998 root INFO creating build/lib/django/contrib/gis/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,999 root INFO copying django/contrib/gis/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,999 root INFO copying django/contrib/gis/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/gl/LC_MESSAGES
2025-04-22 20:54:03,999 root INFO creating build/lib/django/contrib/gis/locale/he
2025-04-22 20:54:03,999 root INFO creating build/lib/django/contrib/gis/locale/he/LC_MESSAGES
2025-04-22 20:54:03,999 root INFO copying django/contrib/gis/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/he/LC_MESSAGES
2025-04-22 20:54:03,999 root INFO copying django/contrib/gis/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/he/LC_MESSAGES
2025-04-22 20:54:03,999 root INFO creating build/lib/django/contrib/gis/locale/hi
2025-04-22 20:54:03,999 root INFO creating build/lib/django/contrib/gis/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,000 root INFO copying django/contrib/gis/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,000 root INFO copying django/contrib/gis/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,000 root INFO creating build/lib/django/contrib/gis/locale/hr
2025-04-22 20:54:04,000 root INFO creating build/lib/django/contrib/gis/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,000 root INFO copying django/contrib/gis/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,000 root INFO copying django/contrib/gis/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,000 root INFO creating build/lib/django/contrib/gis/locale/hsb
2025-04-22 20:54:04,000 root INFO creating build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,000 root INFO copying django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,001 root INFO copying django/contrib/gis/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,001 root INFO creating build/lib/django/contrib/gis/locale/hu
2025-04-22 20:54:04,001 root INFO creating build/lib/django/contrib/gis/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,001 root INFO copying django/contrib/gis/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,001 root INFO copying django/contrib/gis/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,001 root INFO creating build/lib/django/contrib/gis/locale/hy
2025-04-22 20:54:04,001 root INFO creating build/lib/django/contrib/gis/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,001 root INFO copying django/contrib/gis/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,002 root INFO copying django/contrib/gis/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,002 root INFO creating build/lib/django/contrib/gis/locale/ia
2025-04-22 20:54:04,002 root INFO creating build/lib/django/contrib/gis/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,002 root INFO copying django/contrib/gis/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,002 root INFO copying django/contrib/gis/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,002 root INFO creating build/lib/django/contrib/gis/locale/id
2025-04-22 20:54:04,002 root INFO creating build/lib/django/contrib/gis/locale/id/LC_MESSAGES
2025-04-22 20:54:04,002 root INFO copying django/contrib/gis/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/id/LC_MESSAGES
2025-04-22 20:54:04,003 root INFO copying django/contrib/gis/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/id/LC_MESSAGES
2025-04-22 20:54:04,003 root INFO creating build/lib/django/contrib/gis/locale/io
2025-04-22 20:54:04,003 root INFO creating build/lib/django/contrib/gis/locale/io/LC_MESSAGES
2025-04-22 20:54:04,003 root INFO copying django/contrib/gis/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/io/LC_MESSAGES
2025-04-22 20:54:04,003 root INFO copying django/contrib/gis/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/io/LC_MESSAGES
2025-04-22 20:54:04,003 root INFO creating build/lib/django/contrib/gis/locale/is
2025-04-22 20:54:04,003 root INFO creating build/lib/django/contrib/gis/locale/is/LC_MESSAGES
2025-04-22 20:54:04,003 root INFO copying django/contrib/gis/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/is/LC_MESSAGES
2025-04-22 20:54:04,004 root INFO copying django/contrib/gis/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/is/LC_MESSAGES
2025-04-22 20:54:04,004 root INFO creating build/lib/django/contrib/gis/locale/it
2025-04-22 20:54:04,004 root INFO creating build/lib/django/contrib/gis/locale/it/LC_MESSAGES
2025-04-22 20:54:04,004 root INFO copying django/contrib/gis/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/it/LC_MESSAGES
2025-04-22 20:54:04,004 root INFO copying django/contrib/gis/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/it/LC_MESSAGES
2025-04-22 20:54:04,004 root INFO creating build/lib/django/contrib/gis/locale/ja
2025-04-22 20:54:04,004 root INFO creating build/lib/django/contrib/gis/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,004 root INFO copying django/contrib/gis/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,004 root INFO copying django/contrib/gis/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,005 root INFO creating build/lib/django/contrib/gis/locale/ka
2025-04-22 20:54:04,005 root INFO creating build/lib/django/contrib/gis/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,005 root INFO copying django/contrib/gis/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,005 root INFO copying django/contrib/gis/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,005 root INFO creating build/lib/django/contrib/gis/locale/kk
2025-04-22 20:54:04,005 root INFO creating build/lib/django/contrib/gis/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,005 root INFO copying django/contrib/gis/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,005 root INFO copying django/contrib/gis/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,006 root INFO creating build/lib/django/contrib/gis/locale/km
2025-04-22 20:54:04,006 root INFO creating build/lib/django/contrib/gis/locale/km/LC_MESSAGES
2025-04-22 20:54:04,006 root INFO copying django/contrib/gis/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/km/LC_MESSAGES
2025-04-22 20:54:04,006 root INFO copying django/contrib/gis/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/km/LC_MESSAGES
2025-04-22 20:54:04,006 root INFO creating build/lib/django/contrib/gis/locale/kn
2025-04-22 20:54:04,006 root INFO creating build/lib/django/contrib/gis/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,006 root INFO copying django/contrib/gis/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,006 root INFO copying django/contrib/gis/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,007 root INFO creating build/lib/django/contrib/gis/locale/ko
2025-04-22 20:54:04,007 root INFO creating build/lib/django/contrib/gis/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,007 root INFO copying django/contrib/gis/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,007 root INFO copying django/contrib/gis/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,007 root INFO creating build/lib/django/contrib/gis/locale/ky
2025-04-22 20:54:04,007 root INFO creating build/lib/django/contrib/gis/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,007 root INFO copying django/contrib/gis/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,007 root INFO copying django/contrib/gis/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,008 root INFO creating build/lib/django/contrib/gis/locale/lb
2025-04-22 20:54:04,008 root INFO creating build/lib/django/contrib/gis/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,008 root INFO copying django/contrib/gis/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,008 root INFO copying django/contrib/gis/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,008 root INFO creating build/lib/django/contrib/gis/locale/lt
2025-04-22 20:54:04,008 root INFO creating build/lib/django/contrib/gis/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,008 root INFO copying django/contrib/gis/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,009 root INFO copying django/contrib/gis/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,009 root INFO creating build/lib/django/contrib/gis/locale/lv
2025-04-22 20:54:04,009 root INFO creating build/lib/django/contrib/gis/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,009 root INFO copying django/contrib/gis/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,009 root INFO copying django/contrib/gis/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,009 root INFO creating build/lib/django/contrib/gis/locale/mk
2025-04-22 20:54:04,009 root INFO creating build/lib/django/contrib/gis/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,009 root INFO copying django/contrib/gis/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,010 root INFO copying django/contrib/gis/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,010 root INFO creating build/lib/django/contrib/gis/locale/ml
2025-04-22 20:54:04,010 root INFO creating build/lib/django/contrib/gis/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,010 root INFO copying django/contrib/gis/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,010 root INFO copying django/contrib/gis/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,010 root INFO creating build/lib/django/contrib/gis/locale/mn
2025-04-22 20:54:04,010 root INFO creating build/lib/django/contrib/gis/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,010 root INFO copying django/contrib/gis/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,011 root INFO copying django/contrib/gis/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,011 root INFO creating build/lib/django/contrib/gis/locale/mr
2025-04-22 20:54:04,011 root INFO creating build/lib/django/contrib/gis/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,011 root INFO copying django/contrib/gis/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,011 root INFO copying django/contrib/gis/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,011 root INFO creating build/lib/django/contrib/gis/locale/ms
2025-04-22 20:54:04,011 root INFO creating build/lib/django/contrib/gis/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,011 root INFO copying django/contrib/gis/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,011 root INFO copying django/contrib/gis/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,012 root INFO creating build/lib/django/contrib/gis/locale/my
2025-04-22 20:54:04,012 root INFO creating build/lib/django/contrib/gis/locale/my/LC_MESSAGES
2025-04-22 20:54:04,012 root INFO copying django/contrib/gis/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/my/LC_MESSAGES
2025-04-22 20:54:04,012 root INFO copying django/contrib/gis/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/my/LC_MESSAGES
2025-04-22 20:54:04,012 root INFO creating build/lib/django/contrib/gis/locale/nb
2025-04-22 20:54:04,012 root INFO creating build/lib/django/contrib/gis/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,012 root INFO copying django/contrib/gis/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,012 root INFO copying django/contrib/gis/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,013 root INFO creating build/lib/django/contrib/gis/locale/ne
2025-04-22 20:54:04,013 root INFO creating build/lib/django/contrib/gis/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,013 root INFO copying django/contrib/gis/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,013 root INFO copying django/contrib/gis/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,013 root INFO creating build/lib/django/contrib/gis/locale/nl
2025-04-22 20:54:04,013 root INFO creating build/lib/django/contrib/gis/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,013 root INFO copying django/contrib/gis/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,013 root INFO copying django/contrib/gis/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,014 root INFO creating build/lib/django/contrib/gis/locale/nn
2025-04-22 20:54:04,014 root INFO creating build/lib/django/contrib/gis/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,014 root INFO copying django/contrib/gis/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,014 root INFO copying django/contrib/gis/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,014 root INFO creating build/lib/django/contrib/gis/locale/os
2025-04-22 20:54:04,014 root INFO creating build/lib/django/contrib/gis/locale/os/LC_MESSAGES
2025-04-22 20:54:04,014 root INFO copying django/contrib/gis/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/os/LC_MESSAGES
2025-04-22 20:54:04,014 root INFO copying django/contrib/gis/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/os/LC_MESSAGES
2025-04-22 20:54:04,015 root INFO creating build/lib/django/contrib/gis/locale/pa
2025-04-22 20:54:04,015 root INFO creating build/lib/django/contrib/gis/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,015 root INFO copying django/contrib/gis/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,015 root INFO copying django/contrib/gis/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,015 root INFO creating build/lib/django/contrib/gis/locale/pl
2025-04-22 20:54:04,015 root INFO creating build/lib/django/contrib/gis/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,015 root INFO copying django/contrib/gis/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,015 root INFO copying django/contrib/gis/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,016 root INFO creating build/lib/django/contrib/gis/locale/pt
2025-04-22 20:54:04,016 root INFO creating build/lib/django/contrib/gis/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,016 root INFO copying django/contrib/gis/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,016 root INFO copying django/contrib/gis/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,016 root INFO creating build/lib/django/contrib/gis/locale/pt_BR
2025-04-22 20:54:04,016 root INFO creating build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,016 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 20:54:04,016 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 20:54:04,017 root INFO creating build/lib/django/contrib/gis/locale/ro
2025-04-22 20:54:04,017 root INFO creating build/lib/django/contrib/gis/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,017 root INFO copying django/contrib/gis/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,017 root INFO copying django/contrib/gis/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,017 root INFO creating build/lib/django/contrib/gis/locale/ru
2025-04-22 20:54:04,017 root INFO creating build/lib/django/contrib/gis/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,017 root INFO copying django/contrib/gis/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,017 root INFO copying django/contrib/gis/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,018 root INFO creating build/lib/django/contrib/gis/locale/sk
2025-04-22 20:54:04,018 root INFO creating build/lib/django/contrib/gis/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,018 root INFO copying django/contrib/gis/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,018 root INFO copying django/contrib/gis/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,018 root INFO creating build/lib/django/contrib/gis/locale/sl
2025-04-22 20:54:04,018 root INFO creating build/lib/django/contrib/gis/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,018 root INFO copying django/contrib/gis/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,018 root INFO copying django/contrib/gis/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,019 root INFO creating build/lib/django/contrib/gis/locale/sq
2025-04-22 20:54:04,019 root INFO creating build/lib/django/contrib/gis/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,019 root INFO copying django/contrib/gis/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,019 root INFO copying django/contrib/gis/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,019 root INFO creating build/lib/django/contrib/gis/locale/sr
2025-04-22 20:54:04,019 root INFO creating build/lib/django/contrib/gis/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,019 root INFO copying django/contrib/gis/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,019 root INFO copying django/contrib/gis/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,020 root INFO creating build/lib/django/contrib/gis/locale/sr_Latn
2025-04-22 20:54:04,020 root INFO creating build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,020 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 20:54:04,020 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 20:54:04,020 root INFO creating build/lib/django/contrib/gis/locale/sv
2025-04-22 20:54:04,020 root INFO creating build/lib/django/contrib/gis/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,020 root INFO copying django/contrib/gis/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,020 root INFO copying django/contrib/gis/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,021 root INFO creating build/lib/django/contrib/gis/locale/sw
2025-04-22 20:54:04,021 root INFO creating build/lib/django/contrib/gis/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,021 root INFO copying django/contrib/gis/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,021 root INFO copying django/contrib/gis/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,021 root INFO creating build/lib/django/contrib/gis/locale/ta
2025-04-22 20:54:04,021 root INFO creating build/lib/django/contrib/gis/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,021 root INFO copying django/contrib/gis/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,021 root INFO copying django/contrib/gis/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,022 root INFO creating build/lib/django/contrib/gis/locale/te
2025-04-22 20:54:04,022 root INFO creating build/lib/django/contrib/gis/locale/te/LC_MESSAGES
2025-04-22 20:54:04,022 root INFO copying django/contrib/gis/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/te/LC_MESSAGES
2025-04-22 20:54:04,022 root INFO copying django/contrib/gis/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/te/LC_MESSAGES
2025-04-22 20:54:04,022 root INFO creating build/lib/django/contrib/gis/locale/tg
2025-04-22 20:54:04,022 root INFO creating build/lib/django/contrib/gis/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,022 root INFO copying django/contrib/gis/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,022 root INFO copying django/contrib/gis/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,023 root INFO creating build/lib/django/contrib/gis/locale/th
2025-04-22 20:54:04,023 root INFO creating build/lib/django/contrib/gis/locale/th/LC_MESSAGES
2025-04-22 20:54:04,023 root INFO copying django/contrib/gis/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/th/LC_MESSAGES
2025-04-22 20:54:04,023 root INFO copying django/contrib/gis/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/th/LC_MESSAGES
2025-04-22 20:54:04,023 root INFO creating build/lib/django/contrib/gis/locale/tr
2025-04-22 20:54:04,023 root INFO creating build/lib/django/contrib/gis/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,023 root INFO copying django/contrib/gis/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,023 root INFO copying django/contrib/gis/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,024 root INFO creating build/lib/django/contrib/gis/locale/tt
2025-04-22 20:54:04,024 root INFO creating build/lib/django/contrib/gis/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,024 root INFO copying django/contrib/gis/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,024 root INFO copying django/contrib/gis/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,024 root INFO creating build/lib/django/contrib/gis/locale/udm
2025-04-22 20:54:04,024 root INFO creating build/lib/django/contrib/gis/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,024 root INFO copying django/contrib/gis/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,024 root INFO copying django/contrib/gis/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,024 root INFO creating build/lib/django/contrib/gis/locale/uk
2025-04-22 20:54:04,025 root INFO creating build/lib/django/contrib/gis/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,025 root INFO copying django/contrib/gis/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,025 root INFO copying django/contrib/gis/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,025 root INFO creating build/lib/django/contrib/gis/locale/ur
2025-04-22 20:54:04,025 root INFO creating build/lib/django/contrib/gis/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,025 root INFO copying django/contrib/gis/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,025 root INFO copying django/contrib/gis/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,026 root INFO creating build/lib/django/contrib/gis/locale/vi
2025-04-22 20:54:04,026 root INFO creating build/lib/django/contrib/gis/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,026 root INFO copying django/contrib/gis/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,026 root INFO copying django/contrib/gis/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,026 root INFO creating build/lib/django/contrib/gis/locale/zh_Hans
2025-04-22 20:54:04,026 root INFO creating build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,026 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 20:54:04,026 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 20:54:04,026 root INFO creating build/lib/django/contrib/gis/locale/zh_Hant
2025-04-22 20:54:04,027 root INFO creating build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,027 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 20:54:04,027 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 20:54:04,027 root INFO creating build/lib/django/contrib/gis/static
2025-04-22 20:54:04,027 root INFO creating build/lib/django/contrib/gis/static/gis
2025-04-22 20:54:04,027 root INFO creating build/lib/django/contrib/gis/static/gis/css
2025-04-22 20:54:04,027 root INFO copying django/contrib/gis/static/gis/css/ol3.css -> build/lib/django/contrib/gis/static/gis/css
2025-04-22 20:54:04,027 root INFO creating build/lib/django/contrib/gis/static/gis/img
2025-04-22 20:54:04,027 root INFO copying django/contrib/gis/static/gis/img/draw_line_off.svg -> build/lib/django/contrib/gis/static/gis/img
2025-04-22 20:54:04,028 root INFO copying django/contrib/gis/static/gis/img/draw_line_on.svg -> build/lib/django/contrib/gis/static/gis/img
2025-04-22 20:54:04,028 root INFO copying django/contrib/gis/static/gis/img/draw_point_off.svg -> build/lib/django/contrib/gis/static/gis/img
2025-04-22 20:54:04,028 root INFO copying django/contrib/gis/static/gis/img/draw_point_on.svg -> build/lib/django/contrib/gis/static/gis/img
2025-04-22 20:54:04,028 root INFO copying django/contrib/gis/static/gis/img/draw_polygon_off.svg -> build/lib/django/contrib/gis/static/gis/img
2025-04-22 20:54:04,028 root INFO copying django/contrib/gis/static/gis/img/draw_polygon_on.svg -> build/lib/django/contrib/gis/static/gis/img
2025-04-22 20:54:04,028 root INFO creating build/lib/django/contrib/gis/static/gis/js
2025-04-22 20:54:04,029 root INFO copying django/contrib/gis/static/gis/js/OLMapWidget.js -> build/lib/django/contrib/gis/static/gis/js
2025-04-22 20:54:04,029 root INFO creating build/lib/django/contrib/gis/templates
2025-04-22 20:54:04,029 root INFO creating build/lib/django/contrib/gis/templates/gis
2025-04-22 20:54:04,029 root INFO copying django/contrib/gis/templates/gis/openlayers-osm.html -> build/lib/django/contrib/gis/templates/gis
2025-04-22 20:54:04,029 root INFO copying django/contrib/gis/templates/gis/openlayers.html -> build/lib/django/contrib/gis/templates/gis
2025-04-22 20:54:04,029 root INFO creating build/lib/django/contrib/gis/templates/gis/admin
2025-04-22 20:54:04,029 root INFO copying django/contrib/gis/templates/gis/admin/openlayers.html -> build/lib/django/contrib/gis/templates/gis/admin
2025-04-22 20:54:04,030 root INFO copying django/contrib/gis/templates/gis/admin/openlayers.js -> build/lib/django/contrib/gis/templates/gis/admin
2025-04-22 20:54:04,030 root INFO copying django/contrib/gis/templates/gis/admin/osm.html -> build/lib/django/contrib/gis/templates/gis/admin
2025-04-22 20:54:04,030 root INFO copying django/contrib/gis/templates/gis/admin/osm.js -> build/lib/django/contrib/gis/templates/gis/admin
2025-04-22 20:54:04,030 root INFO creating build/lib/django/contrib/gis/templates/gis/kml
2025-04-22 20:54:04,030 root INFO copying django/contrib/gis/templates/gis/kml/base.kml -> build/lib/django/contrib/gis/templates/gis/kml
2025-04-22 20:54:04,030 root INFO copying django/contrib/gis/templates/gis/kml/placemarks.kml -> build/lib/django/contrib/gis/templates/gis/kml
2025-04-22 20:54:04,030 root INFO creating build/lib/django/contrib/admin/locale
2025-04-22 20:54:04,031 root INFO creating build/lib/django/contrib/admin/locale/af
2025-04-22 20:54:04,031 root INFO creating build/lib/django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 20:54:04,031 root INFO copying django/contrib/admin/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 20:54:04,031 root INFO copying django/contrib/admin/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 20:54:04,031 root INFO copying django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 20:54:04,031 root INFO copying django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 20:54:04,031 root INFO creating build/lib/django/contrib/admin/locale/am
2025-04-22 20:54:04,032 root INFO creating build/lib/django/contrib/admin/locale/am/LC_MESSAGES
2025-04-22 20:54:04,032 root INFO copying django/contrib/admin/locale/am/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/am/LC_MESSAGES
2025-04-22 20:54:04,032 root INFO copying django/contrib/admin/locale/am/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/am/LC_MESSAGES
2025-04-22 20:54:04,032 root INFO creating build/lib/django/contrib/admin/locale/ar
2025-04-22 20:54:04,032 root INFO creating build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,032 root INFO copying django/contrib/admin/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,032 root INFO copying django/contrib/admin/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,033 root INFO copying django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,033 root INFO copying django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,033 root INFO creating build/lib/django/contrib/admin/locale/ar_DZ
2025-04-22 20:54:04,033 root INFO creating build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,033 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 20:54:04,033 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 20:54:04,033 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 20:54:04,034 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 20:54:04,034 root INFO creating build/lib/django/contrib/admin/locale/ast
2025-04-22 20:54:04,034 root INFO creating build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,034 root INFO copying django/contrib/admin/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,034 root INFO copying django/contrib/admin/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,034 root INFO copying django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,035 root INFO copying django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,035 root INFO creating build/lib/django/contrib/admin/locale/az
2025-04-22 20:54:04,035 root INFO creating build/lib/django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 20:54:04,035 root INFO copying django/contrib/admin/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 20:54:04,035 root INFO copying django/contrib/admin/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 20:54:04,035 root INFO copying django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 20:54:04,035 root INFO copying django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 20:54:04,036 root INFO creating build/lib/django/contrib/admin/locale/be
2025-04-22 20:54:04,036 root INFO creating build/lib/django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 20:54:04,036 root INFO copying django/contrib/admin/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 20:54:04,036 root INFO copying django/contrib/admin/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 20:54:04,036 root INFO copying django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 20:54:04,036 root INFO copying django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 20:54:04,037 root INFO creating build/lib/django/contrib/admin/locale/bg
2025-04-22 20:54:04,037 root INFO creating build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,037 root INFO copying django/contrib/admin/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,037 root INFO copying django/contrib/admin/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,037 root INFO copying django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,037 root INFO copying django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,037 root INFO creating build/lib/django/contrib/admin/locale/bn
2025-04-22 20:54:04,038 root INFO creating build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,038 root INFO copying django/contrib/admin/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,038 root INFO copying django/contrib/admin/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,038 root INFO copying django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,038 root INFO copying django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,038 root INFO creating build/lib/django/contrib/admin/locale/br
2025-04-22 20:54:04,039 root INFO creating build/lib/django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 20:54:04,039 root INFO copying django/contrib/admin/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 20:54:04,039 root INFO copying django/contrib/admin/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 20:54:04,039 root INFO copying django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 20:54:04,039 root INFO copying django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 20:54:04,039 root INFO creating build/lib/django/contrib/admin/locale/bs
2025-04-22 20:54:04,039 root INFO creating build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,039 root INFO copying django/contrib/admin/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,040 root INFO copying django/contrib/admin/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,040 root INFO copying django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,040 root INFO copying django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,040 root INFO creating build/lib/django/contrib/admin/locale/ca
2025-04-22 20:54:04,040 root INFO creating build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,040 root INFO copying django/contrib/admin/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,040 root INFO copying django/contrib/admin/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,041 root INFO copying django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,041 root INFO copying django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,041 root INFO creating build/lib/django/contrib/admin/locale/ckb
2025-04-22 20:54:04,041 root INFO creating build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,041 root INFO copying django/contrib/admin/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,041 root INFO copying django/contrib/admin/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,042 root INFO copying django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,042 root INFO copying django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,042 root INFO creating build/lib/django/contrib/admin/locale/cs
2025-04-22 20:54:04,042 root INFO creating build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,042 root INFO copying django/contrib/admin/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,042 root INFO copying django/contrib/admin/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,042 root INFO copying django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,043 root INFO copying django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,043 root INFO creating build/lib/django/contrib/admin/locale/cy
2025-04-22 20:54:04,043 root INFO creating build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,043 root INFO copying django/contrib/admin/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,043 root INFO copying django/contrib/admin/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,043 root INFO copying django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,044 root INFO copying django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,044 root INFO creating build/lib/django/contrib/admin/locale/da
2025-04-22 20:54:04,044 root INFO creating build/lib/django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 20:54:04,044 root INFO copying django/contrib/admin/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 20:54:04,044 root INFO copying django/contrib/admin/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 20:54:04,044 root INFO copying django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 20:54:04,044 root INFO copying django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 20:54:04,045 root INFO creating build/lib/django/contrib/admin/locale/de
2025-04-22 20:54:04,045 root INFO creating build/lib/django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 20:54:04,045 root INFO copying django/contrib/admin/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 20:54:04,045 root INFO copying django/contrib/admin/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 20:54:04,045 root INFO copying django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 20:54:04,045 root INFO copying django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 20:54:04,045 root INFO creating build/lib/django/contrib/admin/locale/dsb
2025-04-22 20:54:04,046 root INFO creating build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,046 root INFO copying django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,046 root INFO copying django/contrib/admin/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,046 root INFO copying django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,046 root INFO copying django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,046 root INFO creating build/lib/django/contrib/admin/locale/el
2025-04-22 20:54:04,046 root INFO creating build/lib/django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 20:54:04,046 root INFO copying django/contrib/admin/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 20:54:04,047 root INFO copying django/contrib/admin/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 20:54:04,047 root INFO copying django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 20:54:04,047 root INFO copying django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 20:54:04,047 root INFO creating build/lib/django/contrib/admin/locale/en
2025-04-22 20:54:04,047 root INFO creating build/lib/django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 20:54:04,047 root INFO copying django/contrib/admin/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 20:54:04,048 root INFO copying django/contrib/admin/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 20:54:04,048 root INFO copying django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 20:54:04,048 root INFO copying django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 20:54:04,048 root INFO creating build/lib/django/contrib/admin/locale/en_AU
2025-04-22 20:54:04,048 root INFO creating build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,048 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 20:54:04,048 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 20:54:04,049 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 20:54:04,049 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 20:54:04,049 root INFO creating build/lib/django/contrib/admin/locale/en_GB
2025-04-22 20:54:04,049 root INFO creating build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,049 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 20:54:04,049 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 20:54:04,049 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 20:54:04,050 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 20:54:04,050 root INFO creating build/lib/django/contrib/admin/locale/eo
2025-04-22 20:54:04,050 root INFO creating build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,050 root INFO copying django/contrib/admin/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,050 root INFO copying django/contrib/admin/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,050 root INFO copying django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,050 root INFO copying django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,051 root INFO creating build/lib/django/contrib/admin/locale/es
2025-04-22 20:54:04,051 root INFO creating build/lib/django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 20:54:04,051 root INFO copying django/contrib/admin/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 20:54:04,051 root INFO copying django/contrib/admin/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 20:54:04,051 root INFO copying django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 20:54:04,051 root INFO copying django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 20:54:04,051 root INFO creating build/lib/django/contrib/admin/locale/es_AR
2025-04-22 20:54:04,052 root INFO creating build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,052 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 20:54:04,052 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 20:54:04,052 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 20:54:04,052 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 20:54:04,052 root INFO creating build/lib/django/contrib/admin/locale/es_CO
2025-04-22 20:54:04,052 root INFO creating build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,053 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 20:54:04,053 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 20:54:04,053 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 20:54:04,053 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 20:54:04,053 root INFO creating build/lib/django/contrib/admin/locale/es_MX
2025-04-22 20:54:04,053 root INFO creating build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,053 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 20:54:04,054 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 20:54:04,054 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 20:54:04,054 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 20:54:04,054 root INFO creating build/lib/django/contrib/admin/locale/es_VE
2025-04-22 20:54:04,054 root INFO creating build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,054 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 20:54:04,054 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 20:54:04,055 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 20:54:04,055 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 20:54:04,055 root INFO creating build/lib/django/contrib/admin/locale/et
2025-04-22 20:54:04,055 root INFO creating build/lib/django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 20:54:04,055 root INFO copying django/contrib/admin/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 20:54:04,055 root INFO copying django/contrib/admin/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 20:54:04,056 root INFO copying django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 20:54:04,056 root INFO copying django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 20:54:04,056 root INFO creating build/lib/django/contrib/admin/locale/eu
2025-04-22 20:54:04,056 root INFO creating build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,056 root INFO copying django/contrib/admin/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,056 root INFO copying django/contrib/admin/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,056 root INFO copying django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,057 root INFO copying django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,057 root INFO creating build/lib/django/contrib/admin/locale/fa
2025-04-22 20:54:04,057 root INFO creating build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,057 root INFO copying django/contrib/admin/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,057 root INFO copying django/contrib/admin/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,057 root INFO copying django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,057 root INFO copying django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,058 root INFO creating build/lib/django/contrib/admin/locale/fi
2025-04-22 20:54:04,058 root INFO creating build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,058 root INFO copying django/contrib/admin/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,058 root INFO copying django/contrib/admin/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,058 root INFO copying django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,059 root INFO copying django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,059 root INFO creating build/lib/django/contrib/admin/locale/fr
2025-04-22 20:54:04,059 root INFO creating build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,059 root INFO copying django/contrib/admin/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,059 root INFO copying django/contrib/admin/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,059 root INFO copying django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,059 root INFO copying django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,060 root INFO creating build/lib/django/contrib/admin/locale/fy
2025-04-22 20:54:04,060 root INFO creating build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,060 root INFO copying django/contrib/admin/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,060 root INFO copying django/contrib/admin/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,060 root INFO copying django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,060 root INFO copying django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,060 root INFO creating build/lib/django/contrib/admin/locale/ga
2025-04-22 20:54:04,061 root INFO creating build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,061 root INFO copying django/contrib/admin/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,061 root INFO copying django/contrib/admin/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,061 root INFO copying django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,061 root INFO copying django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,061 root INFO creating build/lib/django/contrib/admin/locale/gd
2025-04-22 20:54:04,061 root INFO creating build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,062 root INFO copying django/contrib/admin/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,062 root INFO copying django/contrib/admin/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,062 root INFO copying django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,062 root INFO copying django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,062 root INFO creating build/lib/django/contrib/admin/locale/gl
2025-04-22 20:54:04,062 root INFO creating build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,062 root INFO copying django/contrib/admin/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,063 root INFO copying django/contrib/admin/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,063 root INFO copying django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,063 root INFO copying django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,063 root INFO creating build/lib/django/contrib/admin/locale/he
2025-04-22 20:54:04,063 root INFO creating build/lib/django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 20:54:04,063 root INFO copying django/contrib/admin/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 20:54:04,063 root INFO copying django/contrib/admin/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 20:54:04,064 root INFO copying django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 20:54:04,064 root INFO copying django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 20:54:04,064 root INFO creating build/lib/django/contrib/admin/locale/hi
2025-04-22 20:54:04,064 root INFO creating build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,064 root INFO copying django/contrib/admin/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,064 root INFO copying django/contrib/admin/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,064 root INFO copying django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,065 root INFO copying django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,065 root INFO creating build/lib/django/contrib/admin/locale/hr
2025-04-22 20:54:04,065 root INFO creating build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,065 root INFO copying django/contrib/admin/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,065 root INFO copying django/contrib/admin/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,065 root INFO copying django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,066 root INFO copying django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,066 root INFO creating build/lib/django/contrib/admin/locale/hsb
2025-04-22 20:54:04,066 root INFO creating build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,066 root INFO copying django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,066 root INFO copying django/contrib/admin/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,066 root INFO copying django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,066 root INFO copying django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,067 root INFO creating build/lib/django/contrib/admin/locale/hu
2025-04-22 20:54:04,067 root INFO creating build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,067 root INFO copying django/contrib/admin/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,067 root INFO copying django/contrib/admin/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,067 root INFO copying django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,067 root INFO copying django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,067 root INFO creating build/lib/django/contrib/admin/locale/hy
2025-04-22 20:54:04,067 root INFO creating build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,068 root INFO copying django/contrib/admin/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,068 root INFO copying django/contrib/admin/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,068 root INFO copying django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,068 root INFO copying django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,068 root INFO creating build/lib/django/contrib/admin/locale/ia
2025-04-22 20:54:04,068 root INFO creating build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,069 root INFO copying django/contrib/admin/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,069 root INFO copying django/contrib/admin/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,069 root INFO copying django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,069 root INFO copying django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,069 root INFO creating build/lib/django/contrib/admin/locale/id
2025-04-22 20:54:04,069 root INFO creating build/lib/django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 20:54:04,069 root INFO copying django/contrib/admin/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 20:54:04,070 root INFO copying django/contrib/admin/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 20:54:04,070 root INFO copying django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 20:54:04,070 root INFO copying django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 20:54:04,070 root INFO creating build/lib/django/contrib/admin/locale/io
2025-04-22 20:54:04,070 root INFO creating build/lib/django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 20:54:04,070 root INFO copying django/contrib/admin/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 20:54:04,070 root INFO copying django/contrib/admin/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 20:54:04,071 root INFO copying django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 20:54:04,071 root INFO copying django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 20:54:04,071 root INFO creating build/lib/django/contrib/admin/locale/is
2025-04-22 20:54:04,071 root INFO creating build/lib/django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 20:54:04,071 root INFO copying django/contrib/admin/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 20:54:04,071 root INFO copying django/contrib/admin/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 20:54:04,072 root INFO copying django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 20:54:04,072 root INFO copying django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 20:54:04,072 root INFO creating build/lib/django/contrib/admin/locale/it
2025-04-22 20:54:04,072 root INFO creating build/lib/django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 20:54:04,072 root INFO copying django/contrib/admin/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 20:54:04,072 root INFO copying django/contrib/admin/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 20:54:04,072 root INFO copying django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 20:54:04,073 root INFO copying django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 20:54:04,073 root INFO creating build/lib/django/contrib/admin/locale/ja
2025-04-22 20:54:04,073 root INFO creating build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,073 root INFO copying django/contrib/admin/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,073 root INFO copying django/contrib/admin/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,073 root INFO copying django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,073 root INFO copying django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,074 root INFO creating build/lib/django/contrib/admin/locale/ka
2025-04-22 20:54:04,074 root INFO creating build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,074 root INFO copying django/contrib/admin/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,074 root INFO copying django/contrib/admin/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,074 root INFO copying django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,074 root INFO copying django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,074 root INFO creating build/lib/django/contrib/admin/locale/kab
2025-04-22 20:54:04,075 root INFO creating build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,075 root INFO copying django/contrib/admin/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,075 root INFO copying django/contrib/admin/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,075 root INFO copying django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,075 root INFO copying django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,075 root INFO creating build/lib/django/contrib/admin/locale/kk
2025-04-22 20:54:04,075 root INFO creating build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,075 root INFO copying django/contrib/admin/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,076 root INFO copying django/contrib/admin/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,076 root INFO copying django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,076 root INFO copying django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,076 root INFO creating build/lib/django/contrib/admin/locale/km
2025-04-22 20:54:04,076 root INFO creating build/lib/django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 20:54:04,076 root INFO copying django/contrib/admin/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 20:54:04,077 root INFO copying django/contrib/admin/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 20:54:04,077 root INFO copying django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 20:54:04,077 root INFO copying django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 20:54:04,077 root INFO creating build/lib/django/contrib/admin/locale/kn
2025-04-22 20:54:04,077 root INFO creating build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,077 root INFO copying django/contrib/admin/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,077 root INFO copying django/contrib/admin/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,078 root INFO copying django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,078 root INFO copying django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,078 root INFO creating build/lib/django/contrib/admin/locale/ko
2025-04-22 20:54:04,078 root INFO creating build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,078 root INFO copying django/contrib/admin/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,078 root INFO copying django/contrib/admin/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,079 root INFO copying django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,079 root INFO copying django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,079 root INFO creating build/lib/django/contrib/admin/locale/ky
2025-04-22 20:54:04,079 root INFO creating build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,079 root INFO copying django/contrib/admin/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,079 root INFO copying django/contrib/admin/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,079 root INFO copying django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,080 root INFO copying django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,080 root INFO creating build/lib/django/contrib/admin/locale/lb
2025-04-22 20:54:04,080 root INFO creating build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,080 root INFO copying django/contrib/admin/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,080 root INFO copying django/contrib/admin/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,080 root INFO copying django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,080 root INFO copying django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,081 root INFO creating build/lib/django/contrib/admin/locale/lt
2025-04-22 20:54:04,081 root INFO creating build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,081 root INFO copying django/contrib/admin/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,081 root INFO copying django/contrib/admin/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,081 root INFO copying django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,081 root INFO copying django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,081 root INFO creating build/lib/django/contrib/admin/locale/lv
2025-04-22 20:54:04,082 root INFO creating build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,082 root INFO copying django/contrib/admin/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,082 root INFO copying django/contrib/admin/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,082 root INFO copying django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,082 root INFO copying django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,082 root INFO creating build/lib/django/contrib/admin/locale/mk
2025-04-22 20:54:04,082 root INFO creating build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,083 root INFO copying django/contrib/admin/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,083 root INFO copying django/contrib/admin/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,083 root INFO copying django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,083 root INFO copying django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,083 root INFO creating build/lib/django/contrib/admin/locale/ml
2025-04-22 20:54:04,083 root INFO creating build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,083 root INFO copying django/contrib/admin/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,084 root INFO copying django/contrib/admin/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,084 root INFO copying django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,084 root INFO copying django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,084 root INFO creating build/lib/django/contrib/admin/locale/mn
2025-04-22 20:54:04,084 root INFO creating build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,084 root INFO copying django/contrib/admin/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,085 root INFO copying django/contrib/admin/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,085 root INFO copying django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,085 root INFO copying django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,085 root INFO creating build/lib/django/contrib/admin/locale/mr
2025-04-22 20:54:04,085 root INFO creating build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,085 root INFO copying django/contrib/admin/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,086 root INFO copying django/contrib/admin/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,086 root INFO copying django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,086 root INFO copying django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,086 root INFO creating build/lib/django/contrib/admin/locale/ms
2025-04-22 20:54:04,086 root INFO creating build/lib/django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,086 root INFO copying django/contrib/admin/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,086 root INFO copying django/contrib/admin/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,087 root INFO copying django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,087 root INFO copying django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,087 root INFO creating build/lib/django/contrib/admin/locale/my
2025-04-22 20:54:04,087 root INFO creating build/lib/django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 20:54:04,087 root INFO copying django/contrib/admin/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 20:54:04,087 root INFO copying django/contrib/admin/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 20:54:04,087 root INFO copying django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 20:54:04,088 root INFO copying django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 20:54:04,088 root INFO creating build/lib/django/contrib/admin/locale/nb
2025-04-22 20:54:04,088 root INFO creating build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,088 root INFO copying django/contrib/admin/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,088 root INFO copying django/contrib/admin/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,088 root INFO copying django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,089 root INFO copying django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,089 root INFO creating build/lib/django/contrib/admin/locale/ne
2025-04-22 20:54:04,089 root INFO creating build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,089 root INFO copying django/contrib/admin/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,089 root INFO copying django/contrib/admin/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,089 root INFO copying django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,089 root INFO copying django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,090 root INFO creating build/lib/django/contrib/admin/locale/nl
2025-04-22 20:54:04,090 root INFO creating build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,090 root INFO copying django/contrib/admin/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,090 root INFO copying django/contrib/admin/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,090 root INFO copying django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,090 root INFO copying django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,090 root INFO creating build/lib/django/contrib/admin/locale/nn
2025-04-22 20:54:04,091 root INFO creating build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,091 root INFO copying django/contrib/admin/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,091 root INFO copying django/contrib/admin/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,091 root INFO copying django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,091 root INFO copying django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,091 root INFO creating build/lib/django/contrib/admin/locale/os
2025-04-22 20:54:04,091 root INFO creating build/lib/django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 20:54:04,091 root INFO copying django/contrib/admin/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 20:54:04,092 root INFO copying django/contrib/admin/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 20:54:04,092 root INFO copying django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 20:54:04,092 root INFO copying django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 20:54:04,092 root INFO creating build/lib/django/contrib/admin/locale/pa
2025-04-22 20:54:04,092 root INFO creating build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,092 root INFO copying django/contrib/admin/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,093 root INFO copying django/contrib/admin/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,093 root INFO copying django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,093 root INFO copying django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,093 root INFO creating build/lib/django/contrib/admin/locale/pl
2025-04-22 20:54:04,093 root INFO creating build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,093 root INFO copying django/contrib/admin/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,093 root INFO copying django/contrib/admin/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,094 root INFO copying django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,094 root INFO copying django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,094 root INFO creating build/lib/django/contrib/admin/locale/pt
2025-04-22 20:54:04,094 root INFO creating build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,094 root INFO copying django/contrib/admin/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,094 root INFO copying django/contrib/admin/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,095 root INFO copying django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,095 root INFO copying django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,095 root INFO creating build/lib/django/contrib/admin/locale/pt_BR
2025-04-22 20:54:04,095 root INFO creating build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,095 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 20:54:04,095 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 20:54:04,095 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 20:54:04,096 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 20:54:04,096 root INFO creating build/lib/django/contrib/admin/locale/ro
2025-04-22 20:54:04,096 root INFO creating build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,096 root INFO copying django/contrib/admin/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,096 root INFO copying django/contrib/admin/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,096 root INFO copying django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,097 root INFO copying django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,097 root INFO creating build/lib/django/contrib/admin/locale/ru
2025-04-22 20:54:04,097 root INFO creating build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,097 root INFO copying django/contrib/admin/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,097 root INFO copying django/contrib/admin/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,097 root INFO copying django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,097 root INFO copying django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,098 root INFO creating build/lib/django/contrib/admin/locale/sk
2025-04-22 20:54:04,098 root INFO creating build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,098 root INFO copying django/contrib/admin/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,098 root INFO copying django/contrib/admin/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,098 root INFO copying django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,098 root INFO copying django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,099 root INFO creating build/lib/django/contrib/admin/locale/sl
2025-04-22 20:54:04,099 root INFO creating build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,099 root INFO copying django/contrib/admin/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,099 root INFO copying django/contrib/admin/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,099 root INFO copying django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,099 root INFO copying django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,099 root INFO creating build/lib/django/contrib/admin/locale/sq
2025-04-22 20:54:04,099 root INFO creating build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,100 root INFO copying django/contrib/admin/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,100 root INFO copying django/contrib/admin/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,100 root INFO copying django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,100 root INFO copying django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,100 root INFO creating build/lib/django/contrib/admin/locale/sr
2025-04-22 20:54:04,100 root INFO creating build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,100 root INFO copying django/contrib/admin/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,101 root INFO copying django/contrib/admin/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,101 root INFO copying django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,101 root INFO copying django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,101 root INFO creating build/lib/django/contrib/admin/locale/sr_Latn
2025-04-22 20:54:04,101 root INFO creating build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,101 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 20:54:04,102 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 20:54:04,102 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 20:54:04,102 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 20:54:04,102 root INFO creating build/lib/django/contrib/admin/locale/sv
2025-04-22 20:54:04,102 root INFO creating build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,102 root INFO copying django/contrib/admin/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,103 root INFO copying django/contrib/admin/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,103 root INFO copying django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,103 root INFO copying django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,103 root INFO creating build/lib/django/contrib/admin/locale/sw
2025-04-22 20:54:04,103 root INFO creating build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,103 root INFO copying django/contrib/admin/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,103 root INFO copying django/contrib/admin/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,104 root INFO copying django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,104 root INFO copying django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,104 root INFO creating build/lib/django/contrib/admin/locale/ta
2025-04-22 20:54:04,104 root INFO creating build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,104 root INFO copying django/contrib/admin/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,104 root INFO copying django/contrib/admin/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,104 root INFO copying django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,105 root INFO copying django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,105 root INFO creating build/lib/django/contrib/admin/locale/te
2025-04-22 20:54:04,105 root INFO creating build/lib/django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 20:54:04,105 root INFO copying django/contrib/admin/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 20:54:04,105 root INFO copying django/contrib/admin/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 20:54:04,105 root INFO copying django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 20:54:04,105 root INFO copying django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 20:54:04,106 root INFO creating build/lib/django/contrib/admin/locale/tg
2025-04-22 20:54:04,106 root INFO creating build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,106 root INFO copying django/contrib/admin/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,106 root INFO copying django/contrib/admin/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,106 root INFO copying django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,106 root INFO copying django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,106 root INFO creating build/lib/django/contrib/admin/locale/th
2025-04-22 20:54:04,107 root INFO creating build/lib/django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 20:54:04,107 root INFO copying django/contrib/admin/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 20:54:04,107 root INFO copying django/contrib/admin/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 20:54:04,107 root INFO copying django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 20:54:04,107 root INFO copying django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 20:54:04,107 root INFO creating build/lib/django/contrib/admin/locale/tk
2025-04-22 20:54:04,107 root INFO creating build/lib/django/contrib/admin/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,108 root INFO copying django/contrib/admin/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,108 root INFO copying django/contrib/admin/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,108 root INFO creating build/lib/django/contrib/admin/locale/tr
2025-04-22 20:54:04,108 root INFO creating build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,108 root INFO copying django/contrib/admin/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,108 root INFO copying django/contrib/admin/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,108 root INFO copying django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,109 root INFO copying django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,109 root INFO creating build/lib/django/contrib/admin/locale/tt
2025-04-22 20:54:04,109 root INFO creating build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,109 root INFO copying django/contrib/admin/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,109 root INFO copying django/contrib/admin/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,109 root INFO copying django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,110 root INFO copying django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,110 root INFO creating build/lib/django/contrib/admin/locale/udm
2025-04-22 20:54:04,110 root INFO creating build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,110 root INFO copying django/contrib/admin/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,110 root INFO copying django/contrib/admin/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,110 root INFO copying django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,110 root INFO copying django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,111 root INFO creating build/lib/django/contrib/admin/locale/uk
2025-04-22 20:54:04,111 root INFO creating build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,111 root INFO copying django/contrib/admin/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,111 root INFO copying django/contrib/admin/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,111 root INFO copying django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,111 root INFO copying django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,111 root INFO creating build/lib/django/contrib/admin/locale/ur
2025-04-22 20:54:04,112 root INFO creating build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,112 root INFO copying django/contrib/admin/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,112 root INFO copying django/contrib/admin/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,112 root INFO copying django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,112 root INFO copying django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,112 root INFO creating build/lib/django/contrib/admin/locale/uz
2025-04-22 20:54:04,112 root INFO creating build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,113 root INFO copying django/contrib/admin/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,113 root INFO copying django/contrib/admin/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,113 root INFO copying django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,113 root INFO copying django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,113 root INFO creating build/lib/django/contrib/admin/locale/vi
2025-04-22 20:54:04,113 root INFO creating build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,113 root INFO copying django/contrib/admin/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,114 root INFO copying django/contrib/admin/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,114 root INFO copying django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,114 root INFO copying django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,114 root INFO creating build/lib/django/contrib/admin/locale/zh_Hans
2025-04-22 20:54:04,114 root INFO creating build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,114 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 20:54:04,114 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 20:54:04,115 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 20:54:04,115 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 20:54:04,115 root INFO creating build/lib/django/contrib/admin/locale/zh_Hant
2025-04-22 20:54:04,115 root INFO creating build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,115 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 20:54:04,115 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 20:54:04,116 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 20:54:04,116 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 20:54:04,116 root INFO creating build/lib/django/contrib/admin/static
2025-04-22 20:54:04,116 root INFO creating build/lib/django/contrib/admin/static/admin
2025-04-22 20:54:04,116 root INFO creating build/lib/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,116 root INFO copying django/contrib/admin/static/admin/css/autocomplete.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,116 root INFO copying django/contrib/admin/static/admin/css/base.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,116 root INFO copying django/contrib/admin/static/admin/css/changelists.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,117 root INFO copying django/contrib/admin/static/admin/css/dark_mode.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,117 root INFO copying django/contrib/admin/static/admin/css/dashboard.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,117 root INFO copying django/contrib/admin/static/admin/css/forms.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,117 root INFO copying django/contrib/admin/static/admin/css/login.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,117 root INFO copying django/contrib/admin/static/admin/css/nav_sidebar.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,117 root INFO copying django/contrib/admin/static/admin/css/responsive.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,118 root INFO copying django/contrib/admin/static/admin/css/responsive_rtl.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,118 root INFO copying django/contrib/admin/static/admin/css/rtl.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,118 root INFO copying django/contrib/admin/static/admin/css/widgets.css -> build/lib/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,118 root INFO creating build/lib/django/contrib/admin/static/admin/css/vendor
2025-04-22 20:54:04,118 root INFO creating build/lib/django/contrib/admin/static/admin/css/vendor/select2
2025-04-22 20:54:04,118 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 20:54:04,119 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 20:54:04,119 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 20:54:04,119 root INFO creating build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,119 root INFO copying django/contrib/admin/static/admin/img/LICENSE -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,119 root INFO copying django/contrib/admin/static/admin/img/README.txt -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,119 root INFO copying django/contrib/admin/static/admin/img/calendar-icons.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,120 root INFO copying django/contrib/admin/static/admin/img/icon-addlink.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,120 root INFO copying django/contrib/admin/static/admin/img/icon-alert.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,120 root INFO copying django/contrib/admin/static/admin/img/icon-calendar.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,120 root INFO copying django/contrib/admin/static/admin/img/icon-changelink.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,120 root INFO copying django/contrib/admin/static/admin/img/icon-clock.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,120 root INFO copying django/contrib/admin/static/admin/img/icon-deletelink.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,120 root INFO copying django/contrib/admin/static/admin/img/icon-no.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,121 root INFO copying django/contrib/admin/static/admin/img/icon-unknown-alt.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,121 root INFO copying django/contrib/admin/static/admin/img/icon-unknown.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,121 root INFO copying django/contrib/admin/static/admin/img/icon-viewlink.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,121 root INFO copying django/contrib/admin/static/admin/img/icon-yes.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,121 root INFO copying django/contrib/admin/static/admin/img/inline-delete.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,121 root INFO copying django/contrib/admin/static/admin/img/search.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,122 root INFO copying django/contrib/admin/static/admin/img/selector-icons.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,122 root INFO copying django/contrib/admin/static/admin/img/sorting-icons.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,122 root INFO copying django/contrib/admin/static/admin/img/tooltag-add.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,122 root INFO copying django/contrib/admin/static/admin/img/tooltag-arrowright.svg -> build/lib/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,122 root INFO creating build/lib/django/contrib/admin/static/admin/img/gis
2025-04-22 20:54:04,122 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 20:54:04,122 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 20:54:04,123 root INFO creating build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,123 root INFO copying django/contrib/admin/static/admin/js/SelectBox.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,123 root INFO copying django/contrib/admin/static/admin/js/SelectFilter2.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,123 root INFO copying django/contrib/admin/static/admin/js/actions.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,123 root INFO copying django/contrib/admin/static/admin/js/autocomplete.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,123 root INFO copying django/contrib/admin/static/admin/js/calendar.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,124 root INFO copying django/contrib/admin/static/admin/js/cancel.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,124 root INFO copying django/contrib/admin/static/admin/js/change_form.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,124 root INFO copying django/contrib/admin/static/admin/js/collapse.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,124 root INFO copying django/contrib/admin/static/admin/js/core.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,124 root INFO copying django/contrib/admin/static/admin/js/filters.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,124 root INFO copying django/contrib/admin/static/admin/js/inlines.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,124 root INFO copying django/contrib/admin/static/admin/js/jquery.init.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,125 root INFO copying django/contrib/admin/static/admin/js/nav_sidebar.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,125 root INFO copying django/contrib/admin/static/admin/js/popup_response.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,125 root INFO copying django/contrib/admin/static/admin/js/prepopulate.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,125 root INFO copying django/contrib/admin/static/admin/js/prepopulate_init.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,125 root INFO copying django/contrib/admin/static/admin/js/theme.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,125 root INFO copying django/contrib/admin/static/admin/js/urlify.js -> build/lib/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,126 root INFO creating build/lib/django/contrib/admin/static/admin/js/admin
2025-04-22 20:54:04,126 root INFO copying django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js -> build/lib/django/contrib/admin/static/admin/js/admin
2025-04-22 20:54:04,126 root INFO copying django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js -> build/lib/django/contrib/admin/static/admin/js/admin
2025-04-22 20:54:04,126 root INFO creating build/lib/django/contrib/admin/static/admin/js/vendor
2025-04-22 20:54:04,126 root INFO creating build/lib/django/contrib/admin/static/admin/js/vendor/jquery
2025-04-22 20:54:04,126 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 20:54:04,126 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 20:54:04,127 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 20:54:04,127 root INFO creating build/lib/django/contrib/admin/static/admin/js/vendor/select2
2025-04-22 20:54:04,127 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 20:54:04,127 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 20:54:04,128 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 20:54:04,128 root INFO creating build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,128 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 20:54:04,129 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 20:54:04,129 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 20:54:04,129 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 20:54:04,129 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 20:54:04,129 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 20:54:04,129 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 20:54:04,129 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 20:54:04,130 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 20:54:04,130 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 20:54:04,130 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 20:54:04,130 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 20:54:04,130 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 20:54:04,130 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 20:54:04,131 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 20:54:04,131 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 20:54:04,131 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 20:54:04,131 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 20:54:04,131 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 20:54:04,131 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 20:54:04,131 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 20:54:04,132 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 20:54:04,132 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 20:54:04,132 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 20:54:04,132 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 20:54:04,132 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 20:54:04,132 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 20:54:04,133 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 20:54:04,133 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 20:54:04,133 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 20:54:04,133 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 20:54:04,133 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 20:54:04,133 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 20:54:04,133 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 20:54:04,134 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 20:54:04,134 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 20:54:04,134 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 20:54:04,134 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 20:54:04,134 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 20:54:04,134 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 20:54:04,135 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 20:54:04,135 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 20:54:04,135 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 20:54:04,135 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 20:54:04,135 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 20:54:04,135 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 20:54:04,135 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 20:54:04,136 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 20:54:04,136 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 20:54:04,136 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 20:54:04,136 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 20:54:04,136 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 20:54:04,136 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 20:54:04,137 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 20:54:04,137 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 20:54:04,137 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 20:54:04,137 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 20:54:04,137 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 20:54:04,137 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 20:54:04,137 root INFO creating build/lib/django/contrib/admin/static/admin/js/vendor/xregexp
2025-04-22 20:54:04,138 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 20:54:04,138 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 20:54:04,138 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 20:54:04,139 root INFO creating build/lib/django/contrib/admin/templates
2025-04-22 20:54:04,139 root INFO creating build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,139 root INFO copying django/contrib/admin/templates/admin/404.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,139 root INFO copying django/contrib/admin/templates/admin/500.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,139 root INFO copying django/contrib/admin/templates/admin/actions.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,139 root INFO copying django/contrib/admin/templates/admin/app_index.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,140 root INFO copying django/contrib/admin/templates/admin/app_list.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,140 root INFO copying django/contrib/admin/templates/admin/base.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,140 root INFO copying django/contrib/admin/templates/admin/base_site.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,140 root INFO copying django/contrib/admin/templates/admin/change_form.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,140 root INFO copying django/contrib/admin/templates/admin/change_form_object_tools.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,140 root INFO copying django/contrib/admin/templates/admin/change_list.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,140 root INFO copying django/contrib/admin/templates/admin/change_list_object_tools.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,141 root INFO copying django/contrib/admin/templates/admin/change_list_results.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,141 root INFO copying django/contrib/admin/templates/admin/color_theme_toggle.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,141 root INFO copying django/contrib/admin/templates/admin/date_hierarchy.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,141 root INFO copying django/contrib/admin/templates/admin/delete_confirmation.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,141 root INFO copying django/contrib/admin/templates/admin/delete_selected_confirmation.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,141 root INFO copying django/contrib/admin/templates/admin/filter.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,142 root INFO copying django/contrib/admin/templates/admin/index.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,142 root INFO copying django/contrib/admin/templates/admin/invalid_setup.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,142 root INFO copying django/contrib/admin/templates/admin/login.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,142 root INFO copying django/contrib/admin/templates/admin/nav_sidebar.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,142 root INFO copying django/contrib/admin/templates/admin/object_history.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,142 root INFO copying django/contrib/admin/templates/admin/pagination.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,142 root INFO copying django/contrib/admin/templates/admin/popup_response.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,143 root INFO copying django/contrib/admin/templates/admin/prepopulated_fields_js.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,143 root INFO copying django/contrib/admin/templates/admin/search_form.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,143 root INFO copying django/contrib/admin/templates/admin/submit_line.html -> build/lib/django/contrib/admin/templates/admin
2025-04-22 20:54:04,143 root INFO creating build/lib/django/contrib/admin/templates/admin/auth
2025-04-22 20:54:04,143 root INFO creating build/lib/django/contrib/admin/templates/admin/auth/user
2025-04-22 20:54:04,143 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 20:54:04,143 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 20:54:04,144 root INFO creating build/lib/django/contrib/admin/templates/admin/edit_inline
2025-04-22 20:54:04,144 root INFO copying django/contrib/admin/templates/admin/edit_inline/stacked.html -> build/lib/django/contrib/admin/templates/admin/edit_inline
2025-04-22 20:54:04,144 root INFO copying django/contrib/admin/templates/admin/edit_inline/tabular.html -> build/lib/django/contrib/admin/templates/admin/edit_inline
2025-04-22 20:54:04,144 root INFO creating build/lib/django/contrib/admin/templates/admin/includes
2025-04-22 20:54:04,144 root INFO copying django/contrib/admin/templates/admin/includes/fieldset.html -> build/lib/django/contrib/admin/templates/admin/includes
2025-04-22 20:54:04,144 root INFO copying django/contrib/admin/templates/admin/includes/object_delete_summary.html -> build/lib/django/contrib/admin/templates/admin/includes
2025-04-22 20:54:04,144 root INFO creating build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:04,144 root INFO copying django/contrib/admin/templates/admin/widgets/clearable_file_input.html -> build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:04,145 root INFO copying django/contrib/admin/templates/admin/widgets/date.html -> build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:04,145 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 20:54:04,145 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 20:54:04,145 root INFO copying django/contrib/admin/templates/admin/widgets/radio.html -> build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:04,145 root INFO copying django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html -> build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:04,146 root INFO copying django/contrib/admin/templates/admin/widgets/split_datetime.html -> build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:04,146 root INFO copying django/contrib/admin/templates/admin/widgets/time.html -> build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:04,146 root INFO copying django/contrib/admin/templates/admin/widgets/url.html -> build/lib/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:04,146 root INFO creating build/lib/django/contrib/admin/templates/registration
2025-04-22 20:54:04,146 root INFO copying django/contrib/admin/templates/registration/logged_out.html -> build/lib/django/contrib/admin/templates/registration
2025-04-22 20:54:04,146 root INFO copying django/contrib/admin/templates/registration/password_change_done.html -> build/lib/django/contrib/admin/templates/registration
2025-04-22 20:54:04,146 root INFO copying django/contrib/admin/templates/registration/password_change_form.html -> build/lib/django/contrib/admin/templates/registration
2025-04-22 20:54:04,147 root INFO copying django/contrib/admin/templates/registration/password_reset_complete.html -> build/lib/django/contrib/admin/templates/registration
2025-04-22 20:54:04,147 root INFO copying django/contrib/admin/templates/registration/password_reset_confirm.html -> build/lib/django/contrib/admin/templates/registration
2025-04-22 20:54:04,147 root INFO copying django/contrib/admin/templates/registration/password_reset_done.html -> build/lib/django/contrib/admin/templates/registration
2025-04-22 20:54:04,147 root INFO copying django/contrib/admin/templates/registration/password_reset_email.html -> build/lib/django/contrib/admin/templates/registration
2025-04-22 20:54:04,147 root INFO copying django/contrib/admin/templates/registration/password_reset_form.html -> build/lib/django/contrib/admin/templates/registration
2025-04-22 20:54:04,147 root INFO creating build/lib/django/contrib/humanize/locale
2025-04-22 20:54:04,147 root INFO creating build/lib/django/contrib/humanize/locale/af
2025-04-22 20:54:04,147 root INFO creating build/lib/django/contrib/humanize/locale/af/LC_MESSAGES
2025-04-22 20:54:04,148 root INFO copying django/contrib/humanize/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/af/LC_MESSAGES
2025-04-22 20:54:04,148 root INFO copying django/contrib/humanize/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/af/LC_MESSAGES
2025-04-22 20:54:04,148 root INFO creating build/lib/django/contrib/humanize/locale/ar
2025-04-22 20:54:04,148 root INFO creating build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,148 root INFO copying django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,148 root INFO copying django/contrib/humanize/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,148 root INFO creating build/lib/django/contrib/humanize/locale/ar_DZ
2025-04-22 20:54:04,149 root INFO creating build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,149 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 20:54:04,149 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 20:54:04,149 root INFO creating build/lib/django/contrib/humanize/locale/ast
2025-04-22 20:54:04,149 root INFO creating build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,149 root INFO copying django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,149 root INFO copying django/contrib/humanize/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,149 root INFO creating build/lib/django/contrib/humanize/locale/az
2025-04-22 20:54:04,150 root INFO creating build/lib/django/contrib/humanize/locale/az/LC_MESSAGES
2025-04-22 20:54:04,150 root INFO copying django/contrib/humanize/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/az/LC_MESSAGES
2025-04-22 20:54:04,150 root INFO copying django/contrib/humanize/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/az/LC_MESSAGES
2025-04-22 20:54:04,150 root INFO creating build/lib/django/contrib/humanize/locale/be
2025-04-22 20:54:04,150 root INFO creating build/lib/django/contrib/humanize/locale/be/LC_MESSAGES
2025-04-22 20:54:04,150 root INFO copying django/contrib/humanize/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/be/LC_MESSAGES
2025-04-22 20:54:04,150 root INFO copying django/contrib/humanize/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/be/LC_MESSAGES
2025-04-22 20:54:04,151 root INFO creating build/lib/django/contrib/humanize/locale/bg
2025-04-22 20:54:04,151 root INFO creating build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,151 root INFO copying django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,151 root INFO copying django/contrib/humanize/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,151 root INFO creating build/lib/django/contrib/humanize/locale/bn
2025-04-22 20:54:04,151 root INFO creating build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,151 root INFO copying django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,151 root INFO copying django/contrib/humanize/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,152 root INFO creating build/lib/django/contrib/humanize/locale/br
2025-04-22 20:54:04,152 root INFO creating build/lib/django/contrib/humanize/locale/br/LC_MESSAGES
2025-04-22 20:54:04,152 root INFO copying django/contrib/humanize/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/br/LC_MESSAGES
2025-04-22 20:54:04,152 root INFO copying django/contrib/humanize/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/br/LC_MESSAGES
2025-04-22 20:54:04,152 root INFO creating build/lib/django/contrib/humanize/locale/bs
2025-04-22 20:54:04,152 root INFO creating build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,152 root INFO copying django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,152 root INFO copying django/contrib/humanize/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,153 root INFO creating build/lib/django/contrib/humanize/locale/ca
2025-04-22 20:54:04,153 root INFO creating build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,153 root INFO copying django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,153 root INFO copying django/contrib/humanize/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,153 root INFO creating build/lib/django/contrib/humanize/locale/ckb
2025-04-22 20:54:04,153 root INFO creating build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,153 root INFO copying django/contrib/humanize/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,153 root INFO copying django/contrib/humanize/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,154 root INFO creating build/lib/django/contrib/humanize/locale/cs
2025-04-22 20:54:04,154 root INFO creating build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,154 root INFO copying django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,154 root INFO copying django/contrib/humanize/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,154 root INFO creating build/lib/django/contrib/humanize/locale/cy
2025-04-22 20:54:04,154 root INFO creating build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,154 root INFO copying django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,155 root INFO copying django/contrib/humanize/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,155 root INFO creating build/lib/django/contrib/humanize/locale/da
2025-04-22 20:54:04,155 root INFO creating build/lib/django/contrib/humanize/locale/da/LC_MESSAGES
2025-04-22 20:54:04,155 root INFO copying django/contrib/humanize/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/da/LC_MESSAGES
2025-04-22 20:54:04,155 root INFO copying django/contrib/humanize/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/da/LC_MESSAGES
2025-04-22 20:54:04,155 root INFO creating build/lib/django/contrib/humanize/locale/de
2025-04-22 20:54:04,155 root INFO creating build/lib/django/contrib/humanize/locale/de/LC_MESSAGES
2025-04-22 20:54:04,155 root INFO copying django/contrib/humanize/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/de/LC_MESSAGES
2025-04-22 20:54:04,156 root INFO copying django/contrib/humanize/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/de/LC_MESSAGES
2025-04-22 20:54:04,156 root INFO creating build/lib/django/contrib/humanize/locale/dsb
2025-04-22 20:54:04,156 root INFO creating build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,156 root INFO copying django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,156 root INFO copying django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,156 root INFO creating build/lib/django/contrib/humanize/locale/el
2025-04-22 20:54:04,156 root INFO creating build/lib/django/contrib/humanize/locale/el/LC_MESSAGES
2025-04-22 20:54:04,156 root INFO copying django/contrib/humanize/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/el/LC_MESSAGES
2025-04-22 20:54:04,157 root INFO copying django/contrib/humanize/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/el/LC_MESSAGES
2025-04-22 20:54:04,157 root INFO creating build/lib/django/contrib/humanize/locale/en
2025-04-22 20:54:04,157 root INFO creating build/lib/django/contrib/humanize/locale/en/LC_MESSAGES
2025-04-22 20:54:04,157 root INFO copying django/contrib/humanize/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/en/LC_MESSAGES
2025-04-22 20:54:04,157 root INFO copying django/contrib/humanize/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/en/LC_MESSAGES
2025-04-22 20:54:04,157 root INFO creating build/lib/django/contrib/humanize/locale/en_AU
2025-04-22 20:54:04,157 root INFO creating build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,157 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 20:54:04,158 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 20:54:04,158 root INFO creating build/lib/django/contrib/humanize/locale/en_GB
2025-04-22 20:54:04,158 root INFO creating build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,158 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 20:54:04,158 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 20:54:04,159 root INFO creating build/lib/django/contrib/humanize/locale/eo
2025-04-22 20:54:04,159 root INFO creating build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,159 root INFO copying django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,159 root INFO copying django/contrib/humanize/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,159 root INFO creating build/lib/django/contrib/humanize/locale/es
2025-04-22 20:54:04,159 root INFO creating build/lib/django/contrib/humanize/locale/es/LC_MESSAGES
2025-04-22 20:54:04,159 root INFO copying django/contrib/humanize/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es/LC_MESSAGES
2025-04-22 20:54:04,159 root INFO copying django/contrib/humanize/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es/LC_MESSAGES
2025-04-22 20:54:04,160 root INFO creating build/lib/django/contrib/humanize/locale/es_AR
2025-04-22 20:54:04,160 root INFO creating build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,160 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 20:54:04,160 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 20:54:04,160 root INFO creating build/lib/django/contrib/humanize/locale/es_CO
2025-04-22 20:54:04,160 root INFO creating build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,160 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 20:54:04,160 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 20:54:04,161 root INFO creating build/lib/django/contrib/humanize/locale/es_MX
2025-04-22 20:54:04,161 root INFO creating build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,161 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 20:54:04,161 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 20:54:04,161 root INFO creating build/lib/django/contrib/humanize/locale/es_VE
2025-04-22 20:54:04,161 root INFO creating build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,161 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 20:54:04,161 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 20:54:04,161 root INFO creating build/lib/django/contrib/humanize/locale/et
2025-04-22 20:54:04,162 root INFO creating build/lib/django/contrib/humanize/locale/et/LC_MESSAGES
2025-04-22 20:54:04,162 root INFO copying django/contrib/humanize/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/et/LC_MESSAGES
2025-04-22 20:54:04,162 root INFO copying django/contrib/humanize/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/et/LC_MESSAGES
2025-04-22 20:54:04,162 root INFO creating build/lib/django/contrib/humanize/locale/eu
2025-04-22 20:54:04,162 root INFO creating build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,162 root INFO copying django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,162 root INFO copying django/contrib/humanize/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,163 root INFO creating build/lib/django/contrib/humanize/locale/fa
2025-04-22 20:54:04,163 root INFO creating build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,163 root INFO copying django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,163 root INFO copying django/contrib/humanize/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,163 root INFO creating build/lib/django/contrib/humanize/locale/fi
2025-04-22 20:54:04,163 root INFO creating build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,163 root INFO copying django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,163 root INFO copying django/contrib/humanize/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,164 root INFO creating build/lib/django/contrib/humanize/locale/fr
2025-04-22 20:54:04,164 root INFO creating build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,164 root INFO copying django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,164 root INFO copying django/contrib/humanize/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,164 root INFO creating build/lib/django/contrib/humanize/locale/fy
2025-04-22 20:54:04,164 root INFO creating build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,164 root INFO copying django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,164 root INFO copying django/contrib/humanize/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,165 root INFO creating build/lib/django/contrib/humanize/locale/ga
2025-04-22 20:54:04,165 root INFO creating build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,165 root INFO copying django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,165 root INFO copying django/contrib/humanize/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,165 root INFO creating build/lib/django/contrib/humanize/locale/gd
2025-04-22 20:54:04,165 root INFO creating build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,165 root INFO copying django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,165 root INFO copying django/contrib/humanize/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,166 root INFO creating build/lib/django/contrib/humanize/locale/gl
2025-04-22 20:54:04,166 root INFO creating build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,166 root INFO copying django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,166 root INFO copying django/contrib/humanize/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,166 root INFO creating build/lib/django/contrib/humanize/locale/he
2025-04-22 20:54:04,166 root INFO creating build/lib/django/contrib/humanize/locale/he/LC_MESSAGES
2025-04-22 20:54:04,166 root INFO copying django/contrib/humanize/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/he/LC_MESSAGES
2025-04-22 20:54:04,166 root INFO copying django/contrib/humanize/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/he/LC_MESSAGES
2025-04-22 20:54:04,167 root INFO creating build/lib/django/contrib/humanize/locale/hi
2025-04-22 20:54:04,167 root INFO creating build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,167 root INFO copying django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,167 root INFO copying django/contrib/humanize/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,167 root INFO creating build/lib/django/contrib/humanize/locale/hr
2025-04-22 20:54:04,167 root INFO creating build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,167 root INFO copying django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,167 root INFO copying django/contrib/humanize/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,168 root INFO creating build/lib/django/contrib/humanize/locale/hsb
2025-04-22 20:54:04,168 root INFO creating build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,168 root INFO copying django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,168 root INFO copying django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,168 root INFO creating build/lib/django/contrib/humanize/locale/hu
2025-04-22 20:54:04,168 root INFO creating build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,168 root INFO copying django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,168 root INFO copying django/contrib/humanize/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,169 root INFO creating build/lib/django/contrib/humanize/locale/hy
2025-04-22 20:54:04,169 root INFO creating build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,169 root INFO copying django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,169 root INFO copying django/contrib/humanize/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,169 root INFO creating build/lib/django/contrib/humanize/locale/ia
2025-04-22 20:54:04,169 root INFO creating build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,169 root INFO copying django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,170 root INFO copying django/contrib/humanize/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,170 root INFO creating build/lib/django/contrib/humanize/locale/id
2025-04-22 20:54:04,170 root INFO creating build/lib/django/contrib/humanize/locale/id/LC_MESSAGES
2025-04-22 20:54:04,170 root INFO copying django/contrib/humanize/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/id/LC_MESSAGES
2025-04-22 20:54:04,170 root INFO copying django/contrib/humanize/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/id/LC_MESSAGES
2025-04-22 20:54:04,170 root INFO creating build/lib/django/contrib/humanize/locale/io
2025-04-22 20:54:04,170 root INFO creating build/lib/django/contrib/humanize/locale/io/LC_MESSAGES
2025-04-22 20:54:04,170 root INFO copying django/contrib/humanize/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/io/LC_MESSAGES
2025-04-22 20:54:04,171 root INFO copying django/contrib/humanize/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/io/LC_MESSAGES
2025-04-22 20:54:04,171 root INFO creating build/lib/django/contrib/humanize/locale/is
2025-04-22 20:54:04,171 root INFO creating build/lib/django/contrib/humanize/locale/is/LC_MESSAGES
2025-04-22 20:54:04,171 root INFO copying django/contrib/humanize/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/is/LC_MESSAGES
2025-04-22 20:54:04,171 root INFO copying django/contrib/humanize/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/is/LC_MESSAGES
2025-04-22 20:54:04,171 root INFO creating build/lib/django/contrib/humanize/locale/it
2025-04-22 20:54:04,171 root INFO creating build/lib/django/contrib/humanize/locale/it/LC_MESSAGES
2025-04-22 20:54:04,171 root INFO copying django/contrib/humanize/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/it/LC_MESSAGES
2025-04-22 20:54:04,172 root INFO copying django/contrib/humanize/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/it/LC_MESSAGES
2025-04-22 20:54:04,172 root INFO creating build/lib/django/contrib/humanize/locale/ja
2025-04-22 20:54:04,172 root INFO creating build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,172 root INFO copying django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,172 root INFO copying django/contrib/humanize/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,172 root INFO creating build/lib/django/contrib/humanize/locale/ka
2025-04-22 20:54:04,172 root INFO creating build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,172 root INFO copying django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,173 root INFO copying django/contrib/humanize/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,173 root INFO creating build/lib/django/contrib/humanize/locale/kk
2025-04-22 20:54:04,173 root INFO creating build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,173 root INFO copying django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,173 root INFO copying django/contrib/humanize/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,173 root INFO creating build/lib/django/contrib/humanize/locale/km
2025-04-22 20:54:04,173 root INFO creating build/lib/django/contrib/humanize/locale/km/LC_MESSAGES
2025-04-22 20:54:04,173 root INFO copying django/contrib/humanize/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/km/LC_MESSAGES
2025-04-22 20:54:04,174 root INFO copying django/contrib/humanize/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/km/LC_MESSAGES
2025-04-22 20:54:04,174 root INFO creating build/lib/django/contrib/humanize/locale/kn
2025-04-22 20:54:04,174 root INFO creating build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,174 root INFO copying django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,174 root INFO copying django/contrib/humanize/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,174 root INFO creating build/lib/django/contrib/humanize/locale/ko
2025-04-22 20:54:04,174 root INFO creating build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,174 root INFO copying django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,175 root INFO copying django/contrib/humanize/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,175 root INFO creating build/lib/django/contrib/humanize/locale/ky
2025-04-22 20:54:04,175 root INFO creating build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,175 root INFO copying django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,175 root INFO copying django/contrib/humanize/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,175 root INFO creating build/lib/django/contrib/humanize/locale/lb
2025-04-22 20:54:04,175 root INFO creating build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,176 root INFO copying django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,176 root INFO copying django/contrib/humanize/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,176 root INFO creating build/lib/django/contrib/humanize/locale/lt
2025-04-22 20:54:04,176 root INFO creating build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,176 root INFO copying django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,176 root INFO copying django/contrib/humanize/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,176 root INFO creating build/lib/django/contrib/humanize/locale/lv
2025-04-22 20:54:04,176 root INFO creating build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,177 root INFO copying django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,177 root INFO copying django/contrib/humanize/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,177 root INFO creating build/lib/django/contrib/humanize/locale/mk
2025-04-22 20:54:04,177 root INFO creating build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,177 root INFO copying django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,177 root INFO copying django/contrib/humanize/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,177 root INFO creating build/lib/django/contrib/humanize/locale/ml
2025-04-22 20:54:04,178 root INFO creating build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,178 root INFO copying django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,178 root INFO copying django/contrib/humanize/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,178 root INFO creating build/lib/django/contrib/humanize/locale/mn
2025-04-22 20:54:04,178 root INFO creating build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,178 root INFO copying django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,178 root INFO copying django/contrib/humanize/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,179 root INFO creating build/lib/django/contrib/humanize/locale/mr
2025-04-22 20:54:04,179 root INFO creating build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,179 root INFO copying django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,179 root INFO copying django/contrib/humanize/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,179 root INFO creating build/lib/django/contrib/humanize/locale/ms
2025-04-22 20:54:04,179 root INFO creating build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,179 root INFO copying django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,179 root INFO copying django/contrib/humanize/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,180 root INFO creating build/lib/django/contrib/humanize/locale/my
2025-04-22 20:54:04,180 root INFO creating build/lib/django/contrib/humanize/locale/my/LC_MESSAGES
2025-04-22 20:54:04,180 root INFO copying django/contrib/humanize/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/my/LC_MESSAGES
2025-04-22 20:54:04,180 root INFO copying django/contrib/humanize/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/my/LC_MESSAGES
2025-04-22 20:54:04,180 root INFO creating build/lib/django/contrib/humanize/locale/nb
2025-04-22 20:54:04,180 root INFO creating build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,180 root INFO copying django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,180 root INFO copying django/contrib/humanize/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,181 root INFO creating build/lib/django/contrib/humanize/locale/ne
2025-04-22 20:54:04,181 root INFO creating build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,181 root INFO copying django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,181 root INFO copying django/contrib/humanize/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,181 root INFO creating build/lib/django/contrib/humanize/locale/nl
2025-04-22 20:54:04,181 root INFO creating build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,181 root INFO copying django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,182 root INFO copying django/contrib/humanize/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,182 root INFO creating build/lib/django/contrib/humanize/locale/nn
2025-04-22 20:54:04,182 root INFO creating build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,182 root INFO copying django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,182 root INFO copying django/contrib/humanize/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,182 root INFO creating build/lib/django/contrib/humanize/locale/os
2025-04-22 20:54:04,182 root INFO creating build/lib/django/contrib/humanize/locale/os/LC_MESSAGES
2025-04-22 20:54:04,182 root INFO copying django/contrib/humanize/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/os/LC_MESSAGES
2025-04-22 20:54:04,183 root INFO copying django/contrib/humanize/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/os/LC_MESSAGES
2025-04-22 20:54:04,183 root INFO creating build/lib/django/contrib/humanize/locale/pa
2025-04-22 20:54:04,183 root INFO creating build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,183 root INFO copying django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,183 root INFO copying django/contrib/humanize/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,183 root INFO creating build/lib/django/contrib/humanize/locale/pl
2025-04-22 20:54:04,183 root INFO creating build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,183 root INFO copying django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,184 root INFO copying django/contrib/humanize/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,184 root INFO creating build/lib/django/contrib/humanize/locale/pt
2025-04-22 20:54:04,184 root INFO creating build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,184 root INFO copying django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,184 root INFO copying django/contrib/humanize/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,184 root INFO creating build/lib/django/contrib/humanize/locale/pt_BR
2025-04-22 20:54:04,184 root INFO creating build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,184 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 20:54:04,185 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 20:54:04,185 root INFO creating build/lib/django/contrib/humanize/locale/ro
2025-04-22 20:54:04,185 root INFO creating build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,185 root INFO copying django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,185 root INFO copying django/contrib/humanize/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,186 root INFO creating build/lib/django/contrib/humanize/locale/ru
2025-04-22 20:54:04,186 root INFO creating build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,186 root INFO copying django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,186 root INFO copying django/contrib/humanize/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,186 root INFO creating build/lib/django/contrib/humanize/locale/sk
2025-04-22 20:54:04,186 root INFO creating build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,186 root INFO copying django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,186 root INFO copying django/contrib/humanize/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,187 root INFO creating build/lib/django/contrib/humanize/locale/sl
2025-04-22 20:54:04,187 root INFO creating build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,187 root INFO copying django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,187 root INFO copying django/contrib/humanize/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,187 root INFO creating build/lib/django/contrib/humanize/locale/sq
2025-04-22 20:54:04,187 root INFO creating build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,187 root INFO copying django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,187 root INFO copying django/contrib/humanize/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,188 root INFO creating build/lib/django/contrib/humanize/locale/sr
2025-04-22 20:54:04,188 root INFO creating build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,188 root INFO copying django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,188 root INFO copying django/contrib/humanize/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,188 root INFO creating build/lib/django/contrib/humanize/locale/sr_Latn
2025-04-22 20:54:04,188 root INFO creating build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,188 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 20:54:04,189 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 20:54:04,189 root INFO creating build/lib/django/contrib/humanize/locale/sv
2025-04-22 20:54:04,189 root INFO creating build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,189 root INFO copying django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,189 root INFO copying django/contrib/humanize/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,189 root INFO creating build/lib/django/contrib/humanize/locale/sw
2025-04-22 20:54:04,189 root INFO creating build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,189 root INFO copying django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,190 root INFO copying django/contrib/humanize/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,190 root INFO creating build/lib/django/contrib/humanize/locale/ta
2025-04-22 20:54:04,190 root INFO creating build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,190 root INFO copying django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,190 root INFO copying django/contrib/humanize/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,190 root INFO creating build/lib/django/contrib/humanize/locale/te
2025-04-22 20:54:04,190 root INFO creating build/lib/django/contrib/humanize/locale/te/LC_MESSAGES
2025-04-22 20:54:04,190 root INFO copying django/contrib/humanize/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/te/LC_MESSAGES
2025-04-22 20:54:04,191 root INFO copying django/contrib/humanize/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/te/LC_MESSAGES
2025-04-22 20:54:04,191 root INFO creating build/lib/django/contrib/humanize/locale/tg
2025-04-22 20:54:04,191 root INFO creating build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,191 root INFO copying django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,191 root INFO copying django/contrib/humanize/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,191 root INFO creating build/lib/django/contrib/humanize/locale/th
2025-04-22 20:54:04,191 root INFO creating build/lib/django/contrib/humanize/locale/th/LC_MESSAGES
2025-04-22 20:54:04,191 root INFO copying django/contrib/humanize/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/th/LC_MESSAGES
2025-04-22 20:54:04,192 root INFO copying django/contrib/humanize/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/th/LC_MESSAGES
2025-04-22 20:54:04,192 root INFO creating build/lib/django/contrib/humanize/locale/tk
2025-04-22 20:54:04,192 root INFO creating build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,192 root INFO copying django/contrib/humanize/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,192 root INFO copying django/contrib/humanize/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,192 root INFO creating build/lib/django/contrib/humanize/locale/tr
2025-04-22 20:54:04,192 root INFO creating build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,192 root INFO copying django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,193 root INFO copying django/contrib/humanize/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,193 root INFO creating build/lib/django/contrib/humanize/locale/tt
2025-04-22 20:54:04,193 root INFO creating build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,193 root INFO copying django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,193 root INFO copying django/contrib/humanize/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,193 root INFO creating build/lib/django/contrib/humanize/locale/udm
2025-04-22 20:54:04,193 root INFO creating build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,193 root INFO copying django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,194 root INFO copying django/contrib/humanize/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,194 root INFO creating build/lib/django/contrib/humanize/locale/uk
2025-04-22 20:54:04,194 root INFO creating build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,194 root INFO copying django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,194 root INFO copying django/contrib/humanize/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,194 root INFO creating build/lib/django/contrib/humanize/locale/ur
2025-04-22 20:54:04,194 root INFO creating build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,195 root INFO copying django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,195 root INFO copying django/contrib/humanize/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,195 root INFO creating build/lib/django/contrib/humanize/locale/uz
2025-04-22 20:54:04,195 root INFO creating build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,195 root INFO copying django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,195 root INFO copying django/contrib/humanize/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,195 root INFO creating build/lib/django/contrib/humanize/locale/vi
2025-04-22 20:54:04,195 root INFO creating build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,196 root INFO copying django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,196 root INFO copying django/contrib/humanize/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,196 root INFO creating build/lib/django/contrib/humanize/locale/zh_Hans
2025-04-22 20:54:04,196 root INFO creating build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,196 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 20:54:04,196 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 20:54:04,196 root INFO creating build/lib/django/contrib/humanize/locale/zh_Hant
2025-04-22 20:54:04,196 root INFO creating build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,197 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 20:54:04,197 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 20:54:04,198 root INFO copying django/contrib/gis/geos/LICENSE -> build/lib/django/contrib/gis/geos
2025-04-22 20:54:04,198 root INFO copying django/contrib/gis/gdal/LICENSE -> build/lib/django/contrib/gis/gdal
2025-04-22 20:54:04,218 root INFO installing to build/bdist.linux-aarch64/wheel
2025-04-22 20:54:04,218 root INFO running install
2025-04-22 20:54:04,226 root INFO running install_lib
2025-04-22 20:54:04,228 root INFO creating build/bdist.linux-aarch64
2025-04-22 20:54:04,228 root INFO creating build/bdist.linux-aarch64/wheel
2025-04-22 20:54:04,228 root INFO creating build/bdist.linux-aarch64/wheel/django
2025-04-22 20:54:04,228 root INFO copying build/lib/django/__init__.py -> build/bdist.linux-aarch64/wheel/django
2025-04-22 20:54:04,228 root INFO creating build/bdist.linux-aarch64/wheel/django/db
2025-04-22 20:54:04,228 root INFO copying build/lib/django/db/__init__.py -> build/bdist.linux-aarch64/wheel/django/db
2025-04-22 20:54:04,229 root INFO creating build/bdist.linux-aarch64/wheel/django/db/models
2025-04-22 20:54:04,229 root INFO copying build/lib/django/db/models/__init__.py -> build/bdist.linux-aarch64/wheel/django/db/models
2025-04-22 20:54:04,229 root INFO copying build/lib/django/db/models/options.py -> build/bdist.linux-aarch64/wheel/django/db/models
2025-04-22 20:54:04,229 root INFO copying build/lib/django/db/models/enums.py -> build/bdist.linux-aarch64/wheel/django/db/models
2025-04-22 20:54:04,229 root INFO copying build/lib/django/db/models/signals.py -> build/bdist.linux-aarch64/wheel/django/db/models
2025-04-22 20:54:04,229 root INFO copying build/lib/django/db/models/query.py -> build/bdist.linux-aarch64/wheel/django/db/models
2025-04-22 20:54:04,230 root INFO copying build/lib/django/db/models/lookups.py -> build/bdist.linux-aarch64/wheel/django/db/models
2025-04-22 20:54:04,230 root INFO copying build/lib/django/db/models/manager.py -> build/bdist.linux-aarch64/wheel/django/db/models
2025-04-22 20:54:04,230 root INFO creating build/bdist.linux-aarch64/wheel/django/db/models/functions
2025-04-22 20:54:04,230 root INFO copying build/lib/django/db/models/functions/__init__.py -> build/bdist.linux-aarch64/wheel/django/db/models/functions
2025-04-22 20:54:04,230 root INFO copying build/lib/django/db/models/functions/datetime.py -> build/bdist.linux-aarch64/wheel/django/db/models/functions
2025-04-22 20:54:04,230 root INFO copying build/lib/django/db/models/functions/window.py -> build/bdist.linux-aarch64/wheel/django/db/models/functions
2025-04-22 20:54:04,231 root INFO copying build/lib/django/db/models/functions/comparison.py -> build/bdist.linux-aarch64/wheel/django/db/models/functions
2025-04-22 20:54:04,231 root INFO copying build/lib/django/db/models/functions/math.py -> build/bdist.linux-aarch64/wheel/django/db/models/functions
2025-04-22 20:54:04,231 root INFO copying build/lib/django/db/models/functions/text.py -> build/bdist.linux-aarch64/wheel/django/db/models/functions
2025-04-22 20:54:04,231 root INFO copying build/lib/django/db/models/functions/mixins.py -> build/bdist.linux-aarch64/wheel/django/db/models/functions
2025-04-22 20:54:04,231 root INFO creating build/bdist.linux-aarch64/wheel/django/db/models/sql
2025-04-22 20:54:04,231 root INFO copying build/lib/django/db/models/sql/__init__.py -> build/bdist.linux-aarch64/wheel/django/db/models/sql
2025-04-22 20:54:04,232 root INFO copying build/lib/django/db/models/sql/query.py -> build/bdist.linux-aarch64/wheel/django/db/models/sql
2025-04-22 20:54:04,232 root INFO copying build/lib/django/db/models/sql/compiler.py -> build/bdist.linux-aarch64/wheel/django/db/models/sql
2025-04-22 20:54:04,232 root INFO copying build/lib/django/db/models/sql/subqueries.py -> build/bdist.linux-aarch64/wheel/django/db/models/sql
2025-04-22 20:54:04,232 root INFO copying build/lib/django/db/models/sql/datastructures.py -> build/bdist.linux-aarch64/wheel/django/db/models/sql
2025-04-22 20:54:04,232 root INFO copying build/lib/django/db/models/sql/where.py -> build/bdist.linux-aarch64/wheel/django/db/models/sql
2025-04-22 20:54:04,233 root INFO copying build/lib/django/db/models/sql/constants.py -> build/bdist.linux-aarch64/wheel/django/db/models/sql
2025-04-22 20:54:04,233 root INFO copying build/lib/django/db/models/indexes.py -> build/bdist.linux-aarch64/wheel/django/db/models
2025-04-22 20:54:04,233 root INFO copying build/lib/django/db/models/utils.py -> build/bdist.linux-aarch64/wheel/django/db/models
2025-04-22 20:54:04,233 root INFO creating build/bdist.linux-aarch64/wheel/django/db/models/fields
2025-04-22 20:54:04,233 root INFO copying build/lib/django/db/models/fields/__init__.py -> build/bdist.linux-aarch64/wheel/django/db/models/fields
2025-04-22 20:54:04,234 root INFO copying build/lib/django/db/models/fields/related_descriptors.py -> build/bdist.linux-aarch64/wheel/django/db/models/fields
2025-04-22 20:54:04,234 root INFO copying build/lib/django/db/models/fields/json.py -> build/bdist.linux-aarch64/wheel/django/db/models/fields
2025-04-22 20:54:04,234 root INFO copying build/lib/django/db/models/fields/related_lookups.py -> build/bdist.linux-aarch64/wheel/django/db/models/fields
2025-04-22 20:54:04,234 root INFO copying build/lib/django/db/models/fields/proxy.py -> build/bdist.linux-aarch64/wheel/django/db/models/fields
2025-04-22 20:54:04,234 root INFO copying build/lib/django/db/models/fields/reverse_related.py -> build/bdist.linux-aarch64/wheel/django/db/models/fields
2025-04-22 20:54:04,234 root INFO copying build/lib/django/db/models/fields/files.py -> build/bdist.linux-aarch64/wheel/django/db/models/fields
2025-04-22 20:54:04,235 root INFO copying build/lib/django/db/models/fields/related.py -> build/bdist.linux-aarch64/wheel/django/db/models/fields
2025-04-22 20:54:04,235 root INFO copying build/lib/django/db/models/fields/mixins.py -> build/bdist.linux-aarch64/wheel/django/db/models/fields
2025-04-22 20:54:04,235 root INFO copying build/lib/django/db/models/deletion.py -> build/bdist.linux-aarch64/wheel/django/db/models
2025-04-22 20:54:04,235 root INFO copying build/lib/django/db/models/expressions.py -> build/bdist.linux-aarch64/wheel/django/db/models
2025-04-22 20:54:04,235 root INFO copying build/lib/django/db/models/constraints.py -> build/bdist.linux-aarch64/wheel/django/db/models
2025-04-22 20:54:04,236 root INFO copying build/lib/django/db/models/query_utils.py -> build/bdist.linux-aarch64/wheel/django/db/models
2025-04-22 20:54:04,236 root INFO copying build/lib/django/db/models/constants.py -> build/bdist.linux-aarch64/wheel/django/db/models
2025-04-22 20:54:04,236 root INFO copying build/lib/django/db/models/base.py -> build/bdist.linux-aarch64/wheel/django/db/models
2025-04-22 20:54:04,236 root INFO copying build/lib/django/db/models/aggregates.py -> build/bdist.linux-aarch64/wheel/django/db/models
2025-04-22 20:54:04,236 root INFO creating build/bdist.linux-aarch64/wheel/django/db/migrations
2025-04-22 20:54:04,237 root INFO copying build/lib/django/db/migrations/__init__.py -> build/bdist.linux-aarch64/wheel/django/db/migrations
2025-04-22 20:54:04,237 root INFO copying build/lib/django/db/migrations/state.py -> build/bdist.linux-aarch64/wheel/django/db/migrations
2025-04-22 20:54:04,237 root INFO copying build/lib/django/db/migrations/graph.py -> build/bdist.linux-aarch64/wheel/django/db/migrations
2025-04-22 20:54:04,237 root INFO copying build/lib/django/db/migrations/writer.py -> build/bdist.linux-aarch64/wheel/django/db/migrations
2025-04-22 20:54:04,237 root INFO copying build/lib/django/db/migrations/serializer.py -> build/bdist.linux-aarch64/wheel/django/db/migrations
2025-04-22 20:54:04,237 root INFO copying build/lib/django/db/migrations/loader.py -> build/bdist.linux-aarch64/wheel/django/db/migrations
2025-04-22 20:54:04,237 root INFO copying build/lib/django/db/migrations/executor.py -> build/bdist.linux-aarch64/wheel/django/db/migrations
2025-04-22 20:54:04,238 root INFO copying build/lib/django/db/migrations/exceptions.py -> build/bdist.linux-aarch64/wheel/django/db/migrations
2025-04-22 20:54:04,238 root INFO copying build/lib/django/db/migrations/optimizer.py -> build/bdist.linux-aarch64/wheel/django/db/migrations
2025-04-22 20:54:04,238 root INFO copying build/lib/django/db/migrations/utils.py -> build/bdist.linux-aarch64/wheel/django/db/migrations
2025-04-22 20:54:04,238 root INFO copying build/lib/django/db/migrations/recorder.py -> build/bdist.linux-aarch64/wheel/django/db/migrations
2025-04-22 20:54:04,238 root INFO copying build/lib/django/db/migrations/migration.py -> build/bdist.linux-aarch64/wheel/django/db/migrations
2025-04-22 20:54:04,239 root INFO copying build/lib/django/db/migrations/autodetector.py -> build/bdist.linux-aarch64/wheel/django/db/migrations
2025-04-22 20:54:04,239 root INFO copying build/lib/django/db/migrations/questioner.py -> build/bdist.linux-aarch64/wheel/django/db/migrations
2025-04-22 20:54:04,239 root INFO creating build/bdist.linux-aarch64/wheel/django/db/migrations/operations
2025-04-22 20:54:04,239 root INFO copying build/lib/django/db/migrations/operations/__init__.py -> build/bdist.linux-aarch64/wheel/django/db/migrations/operations
2025-04-22 20:54:04,239 root INFO copying build/lib/django/db/migrations/operations/models.py -> build/bdist.linux-aarch64/wheel/django/db/migrations/operations
2025-04-22 20:54:04,240 root INFO copying build/lib/django/db/migrations/operations/fields.py -> build/bdist.linux-aarch64/wheel/django/db/migrations/operations
2025-04-22 20:54:04,240 root INFO copying build/lib/django/db/migrations/operations/special.py -> build/bdist.linux-aarch64/wheel/django/db/migrations/operations
2025-04-22 20:54:04,240 root INFO copying build/lib/django/db/migrations/operations/base.py -> build/bdist.linux-aarch64/wheel/django/db/migrations/operations
2025-04-22 20:54:04,240 root INFO copying build/lib/django/db/utils.py -> build/bdist.linux-aarch64/wheel/django/db
2025-04-22 20:54:04,240 root INFO copying build/lib/django/db/transaction.py -> build/bdist.linux-aarch64/wheel/django/db
2025-04-22 20:54:04,240 root INFO creating build/bdist.linux-aarch64/wheel/django/db/backends
2025-04-22 20:54:04,241 root INFO copying build/lib/django/db/backends/__init__.py -> build/bdist.linux-aarch64/wheel/django/db/backends
2025-04-22 20:54:04,241 root INFO copying build/lib/django/db/backends/signals.py -> build/bdist.linux-aarch64/wheel/django/db/backends
2025-04-22 20:54:04,241 root INFO creating build/bdist.linux-aarch64/wheel/django/db/backends/base
2025-04-22 20:54:04,241 root INFO copying build/lib/django/db/backends/base/__init__.py -> build/bdist.linux-aarch64/wheel/django/db/backends/base
2025-04-22 20:54:04,241 root INFO copying build/lib/django/db/backends/base/schema.py -> build/bdist.linux-aarch64/wheel/django/db/backends/base
2025-04-22 20:54:04,241 root INFO copying build/lib/django/db/backends/base/features.py -> build/bdist.linux-aarch64/wheel/django/db/backends/base
2025-04-22 20:54:04,242 root INFO copying build/lib/django/db/backends/base/operations.py -> build/bdist.linux-aarch64/wheel/django/db/backends/base
2025-04-22 20:54:04,242 root INFO copying build/lib/django/db/backends/base/validation.py -> build/bdist.linux-aarch64/wheel/django/db/backends/base
2025-04-22 20:54:04,242 root INFO copying build/lib/django/db/backends/base/creation.py -> build/bdist.linux-aarch64/wheel/django/db/backends/base
2025-04-22 20:54:04,242 root INFO copying build/lib/django/db/backends/base/introspection.py -> build/bdist.linux-aarch64/wheel/django/db/backends/base
2025-04-22 20:54:04,242 root INFO copying build/lib/django/db/backends/base/base.py -> build/bdist.linux-aarch64/wheel/django/db/backends/base
2025-04-22 20:54:04,242 root INFO copying build/lib/django/db/backends/base/client.py -> build/bdist.linux-aarch64/wheel/django/db/backends/base
2025-04-22 20:54:04,243 root INFO copying build/lib/django/db/backends/ddl_references.py -> build/bdist.linux-aarch64/wheel/django/db/backends
2025-04-22 20:54:04,243 root INFO copying build/lib/django/db/backends/utils.py -> build/bdist.linux-aarch64/wheel/django/db/backends
2025-04-22 20:54:04,243 root INFO creating build/bdist.linux-aarch64/wheel/django/db/backends/postgresql
2025-04-22 20:54:04,243 root INFO copying build/lib/django/db/backends/postgresql/__init__.py -> build/bdist.linux-aarch64/wheel/django/db/backends/postgresql
2025-04-22 20:54:04,243 root INFO copying build/lib/django/db/backends/postgresql/schema.py -> build/bdist.linux-aarch64/wheel/django/db/backends/postgresql
2025-04-22 20:54:04,243 root INFO copying build/lib/django/db/backends/postgresql/features.py -> build/bdist.linux-aarch64/wheel/django/db/backends/postgresql
2025-04-22 20:54:04,243 root INFO copying build/lib/django/db/backends/postgresql/operations.py -> build/bdist.linux-aarch64/wheel/django/db/backends/postgresql
2025-04-22 20:54:04,244 root INFO copying build/lib/django/db/backends/postgresql/psycopg_any.py -> build/bdist.linux-aarch64/wheel/django/db/backends/postgresql
2025-04-22 20:54:04,244 root INFO copying build/lib/django/db/backends/postgresql/creation.py -> build/bdist.linux-aarch64/wheel/django/db/backends/postgresql
2025-04-22 20:54:04,244 root INFO copying build/lib/django/db/backends/postgresql/introspection.py -> build/bdist.linux-aarch64/wheel/django/db/backends/postgresql
2025-04-22 20:54:04,244 root INFO copying build/lib/django/db/backends/postgresql/base.py -> build/bdist.linux-aarch64/wheel/django/db/backends/postgresql
2025-04-22 20:54:04,244 root INFO copying build/lib/django/db/backends/postgresql/client.py -> build/bdist.linux-aarch64/wheel/django/db/backends/postgresql
2025-04-22 20:54:04,244 root INFO creating build/bdist.linux-aarch64/wheel/django/db/backends/dummy
2025-04-22 20:54:04,244 root INFO copying build/lib/django/db/backends/dummy/__init__.py -> build/bdist.linux-aarch64/wheel/django/db/backends/dummy
2025-04-22 20:54:04,245 root INFO copying build/lib/django/db/backends/dummy/features.py -> build/bdist.linux-aarch64/wheel/django/db/backends/dummy
2025-04-22 20:54:04,245 root INFO copying build/lib/django/db/backends/dummy/base.py -> build/bdist.linux-aarch64/wheel/django/db/backends/dummy
2025-04-22 20:54:04,245 root INFO creating build/bdist.linux-aarch64/wheel/django/db/backends/sqlite3
2025-04-22 20:54:04,245 root INFO copying build/lib/django/db/backends/sqlite3/__init__.py -> build/bdist.linux-aarch64/wheel/django/db/backends/sqlite3
2025-04-22 20:54:04,245 root INFO copying build/lib/django/db/backends/sqlite3/schema.py -> build/bdist.linux-aarch64/wheel/django/db/backends/sqlite3
2025-04-22 20:54:04,245 root INFO copying build/lib/django/db/backends/sqlite3/features.py -> build/bdist.linux-aarch64/wheel/django/db/backends/sqlite3
2025-04-22 20:54:04,246 root INFO copying build/lib/django/db/backends/sqlite3/operations.py -> build/bdist.linux-aarch64/wheel/django/db/backends/sqlite3
2025-04-22 20:54:04,246 root INFO copying build/lib/django/db/backends/sqlite3/creation.py -> build/bdist.linux-aarch64/wheel/django/db/backends/sqlite3
2025-04-22 20:54:04,246 root INFO copying build/lib/django/db/backends/sqlite3/introspection.py -> build/bdist.linux-aarch64/wheel/django/db/backends/sqlite3
2025-04-22 20:54:04,246 root INFO copying build/lib/django/db/backends/sqlite3/_functions.py -> build/bdist.linux-aarch64/wheel/django/db/backends/sqlite3
2025-04-22 20:54:04,246 root INFO copying build/lib/django/db/backends/sqlite3/base.py -> build/bdist.linux-aarch64/wheel/django/db/backends/sqlite3
2025-04-22 20:54:04,246 root INFO copying build/lib/django/db/backends/sqlite3/client.py -> build/bdist.linux-aarch64/wheel/django/db/backends/sqlite3
2025-04-22 20:54:04,247 root INFO creating build/bdist.linux-aarch64/wheel/django/db/backends/oracle
2025-04-22 20:54:04,247 root INFO copying build/lib/django/db/backends/oracle/__init__.py -> build/bdist.linux-aarch64/wheel/django/db/backends/oracle
2025-04-22 20:54:04,247 root INFO copying build/lib/django/db/backends/oracle/functions.py -> build/bdist.linux-aarch64/wheel/django/db/backends/oracle
2025-04-22 20:54:04,247 root INFO copying build/lib/django/db/backends/oracle/schema.py -> build/bdist.linux-aarch64/wheel/django/db/backends/oracle
2025-04-22 20:54:04,247 root INFO copying build/lib/django/db/backends/oracle/features.py -> build/bdist.linux-aarch64/wheel/django/db/backends/oracle
2025-04-22 20:54:04,247 root INFO copying build/lib/django/db/backends/oracle/operations.py -> build/bdist.linux-aarch64/wheel/django/db/backends/oracle
2025-04-22 20:54:04,247 root INFO copying build/lib/django/db/backends/oracle/utils.py -> build/bdist.linux-aarch64/wheel/django/db/backends/oracle
2025-04-22 20:54:04,248 root INFO copying build/lib/django/db/backends/oracle/validation.py -> build/bdist.linux-aarch64/wheel/django/db/backends/oracle
2025-04-22 20:54:04,248 root INFO copying build/lib/django/db/backends/oracle/creation.py -> build/bdist.linux-aarch64/wheel/django/db/backends/oracle
2025-04-22 20:54:04,248 root INFO copying build/lib/django/db/backends/oracle/introspection.py -> build/bdist.linux-aarch64/wheel/django/db/backends/oracle
2025-04-22 20:54:04,248 root INFO copying build/lib/django/db/backends/oracle/base.py -> build/bdist.linux-aarch64/wheel/django/db/backends/oracle
2025-04-22 20:54:04,248 root INFO copying build/lib/django/db/backends/oracle/client.py -> build/bdist.linux-aarch64/wheel/django/db/backends/oracle
2025-04-22 20:54:04,248 root INFO creating build/bdist.linux-aarch64/wheel/django/db/backends/mysql
2025-04-22 20:54:04,249 root INFO copying build/lib/django/db/backends/mysql/__init__.py -> build/bdist.linux-aarch64/wheel/django/db/backends/mysql
2025-04-22 20:54:04,249 root INFO copying build/lib/django/db/backends/mysql/compiler.py -> build/bdist.linux-aarch64/wheel/django/db/backends/mysql
2025-04-22 20:54:04,249 root INFO copying build/lib/django/db/backends/mysql/schema.py -> build/bdist.linux-aarch64/wheel/django/db/backends/mysql
2025-04-22 20:54:04,249 root INFO copying build/lib/django/db/backends/mysql/features.py -> build/bdist.linux-aarch64/wheel/django/db/backends/mysql
2025-04-22 20:54:04,249 root INFO copying build/lib/django/db/backends/mysql/operations.py -> build/bdist.linux-aarch64/wheel/django/db/backends/mysql
2025-04-22 20:54:04,249 root INFO copying build/lib/django/db/backends/mysql/validation.py -> build/bdist.linux-aarch64/wheel/django/db/backends/mysql
2025-04-22 20:54:04,249 root INFO copying build/lib/django/db/backends/mysql/creation.py -> build/bdist.linux-aarch64/wheel/django/db/backends/mysql
2025-04-22 20:54:04,250 root INFO copying build/lib/django/db/backends/mysql/introspection.py -> build/bdist.linux-aarch64/wheel/django/db/backends/mysql
2025-04-22 20:54:04,250 root INFO copying build/lib/django/db/backends/mysql/base.py -> build/bdist.linux-aarch64/wheel/django/db/backends/mysql
2025-04-22 20:54:04,250 root INFO copying build/lib/django/db/backends/mysql/client.py -> build/bdist.linux-aarch64/wheel/django/db/backends/mysql
2025-04-22 20:54:04,250 root INFO creating build/bdist.linux-aarch64/wheel/django/views
2025-04-22 20:54:04,250 root INFO copying build/lib/django/views/__init__.py -> build/bdist.linux-aarch64/wheel/django/views
2025-04-22 20:54:04,250 root INFO copying build/lib/django/views/i18n.py -> build/bdist.linux-aarch64/wheel/django/views
2025-04-22 20:54:04,250 root INFO copying build/lib/django/views/defaults.py -> build/bdist.linux-aarch64/wheel/django/views
2025-04-22 20:54:04,251 root INFO creating build/bdist.linux-aarch64/wheel/django/views/generic
2025-04-22 20:54:04,251 root INFO copying build/lib/django/views/generic/__init__.py -> build/bdist.linux-aarch64/wheel/django/views/generic
2025-04-22 20:54:04,251 root INFO copying build/lib/django/views/generic/list.py -> build/bdist.linux-aarch64/wheel/django/views/generic
2025-04-22 20:54:04,251 root INFO copying build/lib/django/views/generic/detail.py -> build/bdist.linux-aarch64/wheel/django/views/generic
2025-04-22 20:54:04,251 root INFO copying build/lib/django/views/generic/base.py -> build/bdist.linux-aarch64/wheel/django/views/generic
2025-04-22 20:54:04,251 root INFO copying build/lib/django/views/generic/dates.py -> build/bdist.linux-aarch64/wheel/django/views/generic
2025-04-22 20:54:04,252 root INFO copying build/lib/django/views/generic/edit.py -> build/bdist.linux-aarch64/wheel/django/views/generic
2025-04-22 20:54:04,252 root INFO copying build/lib/django/views/csrf.py -> build/bdist.linux-aarch64/wheel/django/views
2025-04-22 20:54:04,252 root INFO creating build/bdist.linux-aarch64/wheel/django/views/templates
2025-04-22 20:54:04,252 root INFO copying build/lib/django/views/templates/technical_500.html -> build/bdist.linux-aarch64/wheel/django/views/templates
2025-04-22 20:54:04,252 root INFO copying build/lib/django/views/templates/technical_500.txt -> build/bdist.linux-aarch64/wheel/django/views/templates
2025-04-22 20:54:04,252 root INFO copying build/lib/django/views/templates/technical_404.html -> build/bdist.linux-aarch64/wheel/django/views/templates
2025-04-22 20:54:04,253 root INFO copying build/lib/django/views/templates/default_urlconf.html -> build/bdist.linux-aarch64/wheel/django/views/templates
2025-04-22 20:54:04,253 root INFO creating build/bdist.linux-aarch64/wheel/django/views/decorators
2025-04-22 20:54:04,253 root INFO copying build/lib/django/views/decorators/__init__.py -> build/bdist.linux-aarch64/wheel/django/views/decorators
2025-04-22 20:54:04,253 root INFO copying build/lib/django/views/decorators/cache.py -> build/bdist.linux-aarch64/wheel/django/views/decorators
2025-04-22 20:54:04,253 root INFO copying build/lib/django/views/decorators/http.py -> build/bdist.linux-aarch64/wheel/django/views/decorators
2025-04-22 20:54:04,253 root INFO copying build/lib/django/views/decorators/vary.py -> build/bdist.linux-aarch64/wheel/django/views/decorators
2025-04-22 20:54:04,253 root INFO copying build/lib/django/views/decorators/gzip.py -> build/bdist.linux-aarch64/wheel/django/views/decorators
2025-04-22 20:54:04,254 root INFO copying build/lib/django/views/decorators/csrf.py -> build/bdist.linux-aarch64/wheel/django/views/decorators
2025-04-22 20:54:04,254 root INFO copying build/lib/django/views/decorators/clickjacking.py -> build/bdist.linux-aarch64/wheel/django/views/decorators
2025-04-22 20:54:04,254 root INFO copying build/lib/django/views/decorators/debug.py -> build/bdist.linux-aarch64/wheel/django/views/decorators
2025-04-22 20:54:04,254 root INFO copying build/lib/django/views/decorators/common.py -> build/bdist.linux-aarch64/wheel/django/views/decorators
2025-04-22 20:54:04,254 root INFO copying build/lib/django/views/static.py -> build/bdist.linux-aarch64/wheel/django/views
2025-04-22 20:54:04,254 root INFO copying build/lib/django/views/debug.py -> build/bdist.linux-aarch64/wheel/django/views
2025-04-22 20:54:04,255 root INFO creating build/bdist.linux-aarch64/wheel/django/middleware
2025-04-22 20:54:04,255 root INFO copying build/lib/django/middleware/__init__.py -> build/bdist.linux-aarch64/wheel/django/middleware
2025-04-22 20:54:04,255 root INFO copying build/lib/django/middleware/locale.py -> build/bdist.linux-aarch64/wheel/django/middleware
2025-04-22 20:54:04,255 root INFO copying build/lib/django/middleware/cache.py -> build/bdist.linux-aarch64/wheel/django/middleware
2025-04-22 20:54:04,255 root INFO copying build/lib/django/middleware/http.py -> build/bdist.linux-aarch64/wheel/django/middleware
2025-04-22 20:54:04,255 root INFO copying build/lib/django/middleware/security.py -> build/bdist.linux-aarch64/wheel/django/middleware
2025-04-22 20:54:04,255 root INFO copying build/lib/django/middleware/gzip.py -> build/bdist.linux-aarch64/wheel/django/middleware
2025-04-22 20:54:04,256 root INFO copying build/lib/django/middleware/csrf.py -> build/bdist.linux-aarch64/wheel/django/middleware
2025-04-22 20:54:04,256 root INFO copying build/lib/django/middleware/clickjacking.py -> build/bdist.linux-aarch64/wheel/django/middleware
2025-04-22 20:54:04,256 root INFO copying build/lib/django/middleware/common.py -> build/bdist.linux-aarch64/wheel/django/middleware
2025-04-22 20:54:04,256 root INFO creating build/bdist.linux-aarch64/wheel/django/http
2025-04-22 20:54:04,256 root INFO copying build/lib/django/http/__init__.py -> build/bdist.linux-aarch64/wheel/django/http
2025-04-22 20:54:04,256 root INFO copying build/lib/django/http/response.py -> build/bdist.linux-aarch64/wheel/django/http
2025-04-22 20:54:04,256 root INFO copying build/lib/django/http/multipartparser.py -> build/bdist.linux-aarch64/wheel/django/http
2025-04-22 20:54:04,257 root INFO copying build/lib/django/http/cookie.py -> build/bdist.linux-aarch64/wheel/django/http
2025-04-22 20:54:04,257 root INFO copying build/lib/django/http/request.py -> build/bdist.linux-aarch64/wheel/django/http
2025-04-22 20:54:04,257 root INFO creating build/bdist.linux-aarch64/wheel/django/dispatch
2025-04-22 20:54:04,257 root INFO copying build/lib/django/dispatch/__init__.py -> build/bdist.linux-aarch64/wheel/django/dispatch
2025-04-22 20:54:04,257 root INFO copying build/lib/django/dispatch/dispatcher.py -> build/bdist.linux-aarch64/wheel/django/dispatch
2025-04-22 20:54:04,257 root INFO copying build/lib/django/dispatch/license.txt -> build/bdist.linux-aarch64/wheel/django/dispatch
2025-04-22 20:54:04,258 root INFO creating build/bdist.linux-aarch64/wheel/django/urls
2025-04-22 20:54:04,258 root INFO copying build/lib/django/urls/__init__.py -> build/bdist.linux-aarch64/wheel/django/urls
2025-04-22 20:54:04,258 root INFO copying build/lib/django/urls/converters.py -> build/bdist.linux-aarch64/wheel/django/urls
2025-04-22 20:54:04,258 root INFO copying build/lib/django/urls/exceptions.py -> build/bdist.linux-aarch64/wheel/django/urls
2025-04-22 20:54:04,258 root INFO copying build/lib/django/urls/conf.py -> build/bdist.linux-aarch64/wheel/django/urls
2025-04-22 20:54:04,258 root INFO copying build/lib/django/urls/utils.py -> build/bdist.linux-aarch64/wheel/django/urls
2025-04-22 20:54:04,259 root INFO copying build/lib/django/urls/resolvers.py -> build/bdist.linux-aarch64/wheel/django/urls
2025-04-22 20:54:04,259 root INFO copying build/lib/django/urls/base.py -> build/bdist.linux-aarch64/wheel/django/urls
2025-04-22 20:54:04,259 root INFO creating build/bdist.linux-aarch64/wheel/django/template
2025-04-22 20:54:04,259 root INFO copying build/lib/django/template/__init__.py -> build/bdist.linux-aarch64/wheel/django/template
2025-04-22 20:54:04,259 root INFO copying build/lib/django/template/library.py -> build/bdist.linux-aarch64/wheel/django/template
2025-04-22 20:54:04,259 root INFO copying build/lib/django/template/engine.py -> build/bdist.linux-aarch64/wheel/django/template
2025-04-22 20:54:04,260 root INFO copying build/lib/django/template/response.py -> build/bdist.linux-aarch64/wheel/django/template
2025-04-22 20:54:04,260 root INFO copying build/lib/django/template/loader_tags.py -> build/bdist.linux-aarch64/wheel/django/template
2025-04-22 20:54:04,260 root INFO copying build/lib/django/template/loader.py -> build/bdist.linux-aarch64/wheel/django/template
2025-04-22 20:54:04,260 root INFO copying build/lib/django/template/autoreload.py -> build/bdist.linux-aarch64/wheel/django/template
2025-04-22 20:54:04,260 root INFO copying build/lib/django/template/exceptions.py -> build/bdist.linux-aarch64/wheel/django/template
2025-04-22 20:54:04,260 root INFO copying build/lib/django/template/smartif.py -> build/bdist.linux-aarch64/wheel/django/template
2025-04-22 20:54:04,260 root INFO copying build/lib/django/template/defaulttags.py -> build/bdist.linux-aarch64/wheel/django/template
2025-04-22 20:54:04,261 root INFO copying build/lib/django/template/context.py -> build/bdist.linux-aarch64/wheel/django/template
2025-04-22 20:54:04,261 root INFO copying build/lib/django/template/utils.py -> build/bdist.linux-aarch64/wheel/django/template
2025-04-22 20:54:04,261 root INFO copying build/lib/django/template/defaultfilters.py -> build/bdist.linux-aarch64/wheel/django/template
2025-04-22 20:54:04,261 root INFO creating build/bdist.linux-aarch64/wheel/django/template/loaders
2025-04-22 20:54:04,261 root INFO copying build/lib/django/template/loaders/__init__.py -> build/bdist.linux-aarch64/wheel/django/template/loaders
2025-04-22 20:54:04,261 root INFO copying build/lib/django/template/loaders/locmem.py -> build/bdist.linux-aarch64/wheel/django/template/loaders
2025-04-22 20:54:04,262 root INFO copying build/lib/django/template/loaders/cached.py -> build/bdist.linux-aarch64/wheel/django/template/loaders
2025-04-22 20:54:04,262 root INFO copying build/lib/django/template/loaders/app_directories.py -> build/bdist.linux-aarch64/wheel/django/template/loaders
2025-04-22 20:54:04,262 root INFO copying build/lib/django/template/loaders/filesystem.py -> build/bdist.linux-aarch64/wheel/django/template/loaders
2025-04-22 20:54:04,262 root INFO copying build/lib/django/template/loaders/base.py -> build/bdist.linux-aarch64/wheel/django/template/loaders
2025-04-22 20:54:04,262 root INFO copying build/lib/django/template/context_processors.py -> build/bdist.linux-aarch64/wheel/django/template
2025-04-22 20:54:04,262 root INFO creating build/bdist.linux-aarch64/wheel/django/template/backends
2025-04-22 20:54:04,262 root INFO copying build/lib/django/template/backends/__init__.py -> build/bdist.linux-aarch64/wheel/django/template/backends
2025-04-22 20:54:04,263 root INFO copying build/lib/django/template/backends/jinja2.py -> build/bdist.linux-aarch64/wheel/django/template/backends
2025-04-22 20:54:04,263 root INFO copying build/lib/django/template/backends/utils.py -> build/bdist.linux-aarch64/wheel/django/template/backends
2025-04-22 20:54:04,263 root INFO copying build/lib/django/template/backends/django.py -> build/bdist.linux-aarch64/wheel/django/template/backends
2025-04-22 20:54:04,263 root INFO copying build/lib/django/template/backends/base.py -> build/bdist.linux-aarch64/wheel/django/template/backends
2025-04-22 20:54:04,263 root INFO copying build/lib/django/template/backends/dummy.py -> build/bdist.linux-aarch64/wheel/django/template/backends
2025-04-22 20:54:04,263 root INFO copying build/lib/django/template/base.py -> build/bdist.linux-aarch64/wheel/django/template
2025-04-22 20:54:04,263 root INFO creating build/bdist.linux-aarch64/wheel/django/conf
2025-04-22 20:54:04,264 root INFO copying build/lib/django/conf/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf
2025-04-22 20:54:04,264 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/urls
2025-04-22 20:54:04,264 root INFO copying build/lib/django/conf/urls/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/urls
2025-04-22 20:54:04,264 root INFO copying build/lib/django/conf/urls/i18n.py -> build/bdist.linux-aarch64/wheel/django/conf/urls
2025-04-22 20:54:04,264 root INFO copying build/lib/django/conf/urls/static.py -> build/bdist.linux-aarch64/wheel/django/conf/urls
2025-04-22 20:54:04,264 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale
2025-04-22 20:54:04,264 root INFO copying build/lib/django/conf/locale/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale
2025-04-22 20:54:04,265 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/lv
2025-04-22 20:54:04,265 root INFO copying build/lib/django/conf/locale/lv/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/lv
2025-04-22 20:54:04,265 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,265 root INFO copying build/lib/django/conf/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,265 root INFO copying build/lib/django/conf/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,266 root INFO copying build/lib/django/conf/locale/lv/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/lv
2025-04-22 20:54:04,266 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/es_PR
2025-04-22 20:54:04,266 root INFO copying build/lib/django/conf/locale/es_PR/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_PR
2025-04-22 20:54:04,266 root INFO copying build/lib/django/conf/locale/es_PR/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_PR
2025-04-22 20:54:04,266 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/sw
2025-04-22 20:54:04,266 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,266 root INFO copying build/lib/django/conf/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,267 root INFO copying build/lib/django/conf/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,267 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/en_AU
2025-04-22 20:54:04,267 root INFO copying build/lib/django/conf/locale/en_AU/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/en_AU
2025-04-22 20:54:04,267 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,267 root INFO copying build/lib/django/conf/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,267 root INFO copying build/lib/django/conf/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,268 root INFO copying build/lib/django/conf/locale/en_AU/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/en_AU
2025-04-22 20:54:04,268 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/mr
2025-04-22 20:54:04,268 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,268 root INFO copying build/lib/django/conf/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,268 root INFO copying build/lib/django/conf/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,268 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/de_CH
2025-04-22 20:54:04,268 root INFO copying build/lib/django/conf/locale/de_CH/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/de_CH
2025-04-22 20:54:04,269 root INFO copying build/lib/django/conf/locale/de_CH/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/de_CH
2025-04-22 20:54:04,269 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/lb
2025-04-22 20:54:04,269 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,269 root INFO copying build/lib/django/conf/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,269 root INFO copying build/lib/django/conf/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,269 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ca
2025-04-22 20:54:04,269 root INFO copying build/lib/django/conf/locale/ca/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ca
2025-04-22 20:54:04,270 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,270 root INFO copying build/lib/django/conf/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,270 root INFO copying build/lib/django/conf/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,270 root INFO copying build/lib/django/conf/locale/ca/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ca
2025-04-22 20:54:04,270 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/en_GB
2025-04-22 20:54:04,270 root INFO copying build/lib/django/conf/locale/en_GB/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/en_GB
2025-04-22 20:54:04,271 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,271 root INFO copying build/lib/django/conf/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,271 root INFO copying build/lib/django/conf/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,271 root INFO copying build/lib/django/conf/locale/en_GB/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/en_GB
2025-04-22 20:54:04,271 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/el
2025-04-22 20:54:04,271 root INFO copying build/lib/django/conf/locale/el/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/el
2025-04-22 20:54:04,271 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/el/LC_MESSAGES
2025-04-22 20:54:04,272 root INFO copying build/lib/django/conf/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/el/LC_MESSAGES
2025-04-22 20:54:04,272 root INFO copying build/lib/django/conf/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/el/LC_MESSAGES
2025-04-22 20:54:04,272 root INFO copying build/lib/django/conf/locale/el/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/el
2025-04-22 20:54:04,272 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/es_VE
2025-04-22 20:54:04,272 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,272 root INFO copying build/lib/django/conf/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,273 root INFO copying build/lib/django/conf/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,273 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/af
2025-04-22 20:54:04,273 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/af/LC_MESSAGES
2025-04-22 20:54:04,273 root INFO copying build/lib/django/conf/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/af/LC_MESSAGES
2025-04-22 20:54:04,273 root INFO copying build/lib/django/conf/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/af/LC_MESSAGES
2025-04-22 20:54:04,273 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/en
2025-04-22 20:54:04,274 root INFO copying build/lib/django/conf/locale/en/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/en
2025-04-22 20:54:04,274 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/en/LC_MESSAGES
2025-04-22 20:54:04,274 root INFO copying build/lib/django/conf/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/en/LC_MESSAGES
2025-04-22 20:54:04,274 root INFO copying build/lib/django/conf/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/en/LC_MESSAGES
2025-04-22 20:54:04,274 root INFO copying build/lib/django/conf/locale/en/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/en
2025-04-22 20:54:04,274 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/dsb
2025-04-22 20:54:04,274 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,275 root INFO copying build/lib/django/conf/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,275 root INFO copying build/lib/django/conf/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,275 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/et
2025-04-22 20:54:04,275 root INFO copying build/lib/django/conf/locale/et/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/et
2025-04-22 20:54:04,275 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/et/LC_MESSAGES
2025-04-22 20:54:04,275 root INFO copying build/lib/django/conf/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/et/LC_MESSAGES
2025-04-22 20:54:04,276 root INFO copying build/lib/django/conf/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/et/LC_MESSAGES
2025-04-22 20:54:04,276 root INFO copying build/lib/django/conf/locale/et/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/et
2025-04-22 20:54:04,276 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/nn
2025-04-22 20:54:04,276 root INFO copying build/lib/django/conf/locale/nn/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/nn
2025-04-22 20:54:04,276 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,276 root INFO copying build/lib/django/conf/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,277 root INFO copying build/lib/django/conf/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,277 root INFO copying build/lib/django/conf/locale/nn/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/nn
2025-04-22 20:54:04,277 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/cy
2025-04-22 20:54:04,277 root INFO copying build/lib/django/conf/locale/cy/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/cy
2025-04-22 20:54:04,277 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,277 root INFO copying build/lib/django/conf/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,277 root INFO copying build/lib/django/conf/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,278 root INFO copying build/lib/django/conf/locale/cy/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/cy
2025-04-22 20:54:04,278 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ko
2025-04-22 20:54:04,278 root INFO copying build/lib/django/conf/locale/ko/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ko
2025-04-22 20:54:04,278 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,278 root INFO copying build/lib/django/conf/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,278 root INFO copying build/lib/django/conf/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,279 root INFO copying build/lib/django/conf/locale/ko/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ko
2025-04-22 20:54:04,279 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/is
2025-04-22 20:54:04,279 root INFO copying build/lib/django/conf/locale/is/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/is
2025-04-22 20:54:04,279 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/is/LC_MESSAGES
2025-04-22 20:54:04,279 root INFO copying build/lib/django/conf/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/is/LC_MESSAGES
2025-04-22 20:54:04,279 root INFO copying build/lib/django/conf/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/is/LC_MESSAGES
2025-04-22 20:54:04,279 root INFO copying build/lib/django/conf/locale/is/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/is
2025-04-22 20:54:04,280 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/pa
2025-04-22 20:54:04,280 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,280 root INFO copying build/lib/django/conf/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,280 root INFO copying build/lib/django/conf/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,280 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/tt
2025-04-22 20:54:04,280 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,280 root INFO copying build/lib/django/conf/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,281 root INFO copying build/lib/django/conf/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,281 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ne
2025-04-22 20:54:04,281 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,281 root INFO copying build/lib/django/conf/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,281 root INFO copying build/lib/django/conf/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,281 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/sr_Latn
2025-04-22 20:54:04,282 root INFO copying build/lib/django/conf/locale/sr_Latn/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/sr_Latn
2025-04-22 20:54:04,282 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,282 root INFO copying build/lib/django/conf/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,282 root INFO copying build/lib/django/conf/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,282 root INFO copying build/lib/django/conf/locale/sr_Latn/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/sr_Latn
2025-04-22 20:54:04,282 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/fy
2025-04-22 20:54:04,282 root INFO copying build/lib/django/conf/locale/fy/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/fy
2025-04-22 20:54:04,283 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,283 root INFO copying build/lib/django/conf/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,283 root INFO copying build/lib/django/conf/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,283 root INFO copying build/lib/django/conf/locale/fy/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/fy
2025-04-22 20:54:04,283 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/bg
2025-04-22 20:54:04,283 root INFO copying build/lib/django/conf/locale/bg/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/bg
2025-04-22 20:54:04,283 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,284 root INFO copying build/lib/django/conf/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,284 root INFO copying build/lib/django/conf/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,284 root INFO copying build/lib/django/conf/locale/bg/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/bg
2025-04-22 20:54:04,284 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ga
2025-04-22 20:54:04,284 root INFO copying build/lib/django/conf/locale/ga/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ga
2025-04-22 20:54:04,284 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,285 root INFO copying build/lib/django/conf/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,285 root INFO copying build/lib/django/conf/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,285 root INFO copying build/lib/django/conf/locale/ga/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ga
2025-04-22 20:54:04,285 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/gl
2025-04-22 20:54:04,285 root INFO copying build/lib/django/conf/locale/gl/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/gl
2025-04-22 20:54:04,285 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,286 root INFO copying build/lib/django/conf/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,286 root INFO copying build/lib/django/conf/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,286 root INFO copying build/lib/django/conf/locale/gl/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/gl
2025-04-22 20:54:04,286 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ig
2025-04-22 20:54:04,286 root INFO copying build/lib/django/conf/locale/ig/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ig
2025-04-22 20:54:04,286 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ig/LC_MESSAGES
2025-04-22 20:54:04,286 root INFO copying build/lib/django/conf/locale/ig/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ig/LC_MESSAGES
2025-04-22 20:54:04,287 root INFO copying build/lib/django/conf/locale/ig/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ig/LC_MESSAGES
2025-04-22 20:54:04,287 root INFO copying build/lib/django/conf/locale/ig/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ig
2025-04-22 20:54:04,287 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/uk
2025-04-22 20:54:04,287 root INFO copying build/lib/django/conf/locale/uk/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/uk
2025-04-22 20:54:04,287 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,287 root INFO copying build/lib/django/conf/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,288 root INFO copying build/lib/django/conf/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,288 root INFO copying build/lib/django/conf/locale/uk/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/uk
2025-04-22 20:54:04,288 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/uz
2025-04-22 20:54:04,288 root INFO copying build/lib/django/conf/locale/uz/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/uz
2025-04-22 20:54:04,288 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,288 root INFO copying build/lib/django/conf/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,289 root INFO copying build/lib/django/conf/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,289 root INFO copying build/lib/django/conf/locale/uz/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/uz
2025-04-22 20:54:04,289 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/kn
2025-04-22 20:54:04,289 root INFO copying build/lib/django/conf/locale/kn/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/kn
2025-04-22 20:54:04,289 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,289 root INFO copying build/lib/django/conf/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,290 root INFO copying build/lib/django/conf/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,290 root INFO copying build/lib/django/conf/locale/kn/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/kn
2025-04-22 20:54:04,290 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ja
2025-04-22 20:54:04,290 root INFO copying build/lib/django/conf/locale/ja/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ja
2025-04-22 20:54:04,290 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,290 root INFO copying build/lib/django/conf/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,290 root INFO copying build/lib/django/conf/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,291 root INFO copying build/lib/django/conf/locale/ja/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ja
2025-04-22 20:54:04,291 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/cs
2025-04-22 20:54:04,291 root INFO copying build/lib/django/conf/locale/cs/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/cs
2025-04-22 20:54:04,291 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,291 root INFO copying build/lib/django/conf/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,291 root INFO copying build/lib/django/conf/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,292 root INFO copying build/lib/django/conf/locale/cs/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/cs
2025-04-22 20:54:04,292 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/os
2025-04-22 20:54:04,292 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/os/LC_MESSAGES
2025-04-22 20:54:04,292 root INFO copying build/lib/django/conf/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/os/LC_MESSAGES
2025-04-22 20:54:04,292 root INFO copying build/lib/django/conf/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/os/LC_MESSAGES
2025-04-22 20:54:04,292 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/tr
2025-04-22 20:54:04,293 root INFO copying build/lib/django/conf/locale/tr/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/tr
2025-04-22 20:54:04,293 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,293 root INFO copying build/lib/django/conf/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,293 root INFO copying build/lib/django/conf/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,293 root INFO copying build/lib/django/conf/locale/tr/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/tr
2025-04-22 20:54:04,293 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/io
2025-04-22 20:54:04,294 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/io/LC_MESSAGES
2025-04-22 20:54:04,294 root INFO copying build/lib/django/conf/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/io/LC_MESSAGES
2025-04-22 20:54:04,294 root INFO copying build/lib/django/conf/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/io/LC_MESSAGES
2025-04-22 20:54:04,294 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/sl
2025-04-22 20:54:04,294 root INFO copying build/lib/django/conf/locale/sl/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/sl
2025-04-22 20:54:04,294 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,294 root INFO copying build/lib/django/conf/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,295 root INFO copying build/lib/django/conf/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,295 root INFO copying build/lib/django/conf/locale/sl/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/sl
2025-04-22 20:54:04,295 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/sq
2025-04-22 20:54:04,295 root INFO copying build/lib/django/conf/locale/sq/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/sq
2025-04-22 20:54:04,295 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,295 root INFO copying build/lib/django/conf/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,296 root INFO copying build/lib/django/conf/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,296 root INFO copying build/lib/django/conf/locale/sq/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/sq
2025-04-22 20:54:04,296 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/az
2025-04-22 20:54:04,296 root INFO copying build/lib/django/conf/locale/az/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/az
2025-04-22 20:54:04,296 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/az/LC_MESSAGES
2025-04-22 20:54:04,296 root INFO copying build/lib/django/conf/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/az/LC_MESSAGES
2025-04-22 20:54:04,296 root INFO copying build/lib/django/conf/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/az/LC_MESSAGES
2025-04-22 20:54:04,297 root INFO copying build/lib/django/conf/locale/az/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/az
2025-04-22 20:54:04,297 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/eo
2025-04-22 20:54:04,297 root INFO copying build/lib/django/conf/locale/eo/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/eo
2025-04-22 20:54:04,297 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,297 root INFO copying build/lib/django/conf/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,297 root INFO copying build/lib/django/conf/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,298 root INFO copying build/lib/django/conf/locale/eo/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/eo
2025-04-22 20:54:04,298 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/pt_BR
2025-04-22 20:54:04,298 root INFO copying build/lib/django/conf/locale/pt_BR/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/pt_BR
2025-04-22 20:54:04,298 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,298 root INFO copying build/lib/django/conf/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,298 root INFO copying build/lib/django/conf/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,299 root INFO copying build/lib/django/conf/locale/pt_BR/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/pt_BR
2025-04-22 20:54:04,299 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/pl
2025-04-22 20:54:04,299 root INFO copying build/lib/django/conf/locale/pl/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/pl
2025-04-22 20:54:04,299 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,299 root INFO copying build/lib/django/conf/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,299 root INFO copying build/lib/django/conf/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,300 root INFO copying build/lib/django/conf/locale/pl/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/pl
2025-04-22 20:54:04,300 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/gd
2025-04-22 20:54:04,300 root INFO copying build/lib/django/conf/locale/gd/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/gd
2025-04-22 20:54:04,300 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,300 root INFO copying build/lib/django/conf/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,300 root INFO copying build/lib/django/conf/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,301 root INFO copying build/lib/django/conf/locale/gd/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/gd
2025-04-22 20:54:04,301 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/hr
2025-04-22 20:54:04,301 root INFO copying build/lib/django/conf/locale/hr/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/hr
2025-04-22 20:54:04,301 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,301 root INFO copying build/lib/django/conf/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,301 root INFO copying build/lib/django/conf/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,301 root INFO copying build/lib/django/conf/locale/hr/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/hr
2025-04-22 20:54:04,302 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ru
2025-04-22 20:54:04,302 root INFO copying build/lib/django/conf/locale/ru/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ru
2025-04-22 20:54:04,302 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,302 root INFO copying build/lib/django/conf/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,302 root INFO copying build/lib/django/conf/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,303 root INFO copying build/lib/django/conf/locale/ru/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ru
2025-04-22 20:54:04,303 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/es
2025-04-22 20:54:04,303 root INFO copying build/lib/django/conf/locale/es/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/es
2025-04-22 20:54:04,303 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/es/LC_MESSAGES
2025-04-22 20:54:04,303 root INFO copying build/lib/django/conf/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/es/LC_MESSAGES
2025-04-22 20:54:04,303 root INFO copying build/lib/django/conf/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/es/LC_MESSAGES
2025-04-22 20:54:04,303 root INFO copying build/lib/django/conf/locale/es/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/es
2025-04-22 20:54:04,304 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/id
2025-04-22 20:54:04,304 root INFO copying build/lib/django/conf/locale/id/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/id
2025-04-22 20:54:04,304 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/id/LC_MESSAGES
2025-04-22 20:54:04,304 root INFO copying build/lib/django/conf/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/id/LC_MESSAGES
2025-04-22 20:54:04,304 root INFO copying build/lib/django/conf/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/id/LC_MESSAGES
2025-04-22 20:54:04,304 root INFO copying build/lib/django/conf/locale/id/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/id
2025-04-22 20:54:04,305 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/fi
2025-04-22 20:54:04,305 root INFO copying build/lib/django/conf/locale/fi/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/fi
2025-04-22 20:54:04,305 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,305 root INFO copying build/lib/django/conf/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,305 root INFO copying build/lib/django/conf/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,305 root INFO copying build/lib/django/conf/locale/fi/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/fi
2025-04-22 20:54:04,306 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/mk
2025-04-22 20:54:04,306 root INFO copying build/lib/django/conf/locale/mk/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/mk
2025-04-22 20:54:04,306 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,306 root INFO copying build/lib/django/conf/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,306 root INFO copying build/lib/django/conf/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,306 root INFO copying build/lib/django/conf/locale/mk/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/mk
2025-04-22 20:54:04,307 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/hi
2025-04-22 20:54:04,307 root INFO copying build/lib/django/conf/locale/hi/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/hi
2025-04-22 20:54:04,307 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,307 root INFO copying build/lib/django/conf/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,307 root INFO copying build/lib/django/conf/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,307 root INFO copying build/lib/django/conf/locale/hi/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/hi
2025-04-22 20:54:04,307 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/kab
2025-04-22 20:54:04,308 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,308 root INFO copying build/lib/django/conf/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,308 root INFO copying build/lib/django/conf/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,308 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/hsb
2025-04-22 20:54:04,308 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,308 root INFO copying build/lib/django/conf/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,308 root INFO copying build/lib/django/conf/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,309 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/sk
2025-04-22 20:54:04,309 root INFO copying build/lib/django/conf/locale/sk/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/sk
2025-04-22 20:54:04,309 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,309 root INFO copying build/lib/django/conf/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,309 root INFO copying build/lib/django/conf/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,309 root INFO copying build/lib/django/conf/locale/sk/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/sk
2025-04-22 20:54:04,310 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/lt
2025-04-22 20:54:04,310 root INFO copying build/lib/django/conf/locale/lt/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/lt
2025-04-22 20:54:04,310 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,310 root INFO copying build/lib/django/conf/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,310 root INFO copying build/lib/django/conf/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,310 root INFO copying build/lib/django/conf/locale/lt/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/lt
2025-04-22 20:54:04,311 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/de
2025-04-22 20:54:04,311 root INFO copying build/lib/django/conf/locale/de/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/de
2025-04-22 20:54:04,311 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/de/LC_MESSAGES
2025-04-22 20:54:04,311 root INFO copying build/lib/django/conf/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/de/LC_MESSAGES
2025-04-22 20:54:04,311 root INFO copying build/lib/django/conf/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/de/LC_MESSAGES
2025-04-22 20:54:04,311 root INFO copying build/lib/django/conf/locale/de/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/de
2025-04-22 20:54:04,312 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/it
2025-04-22 20:54:04,312 root INFO copying build/lib/django/conf/locale/it/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/it
2025-04-22 20:54:04,312 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/it/LC_MESSAGES
2025-04-22 20:54:04,312 root INFO copying build/lib/django/conf/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/it/LC_MESSAGES
2025-04-22 20:54:04,312 root INFO copying build/lib/django/conf/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/it/LC_MESSAGES
2025-04-22 20:54:04,313 root INFO copying build/lib/django/conf/locale/it/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/it
2025-04-22 20:54:04,313 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/my
2025-04-22 20:54:04,313 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/my/LC_MESSAGES
2025-04-22 20:54:04,313 root INFO copying build/lib/django/conf/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/my/LC_MESSAGES
2025-04-22 20:54:04,313 root INFO copying build/lib/django/conf/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/my/LC_MESSAGES
2025-04-22 20:54:04,313 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/sr
2025-04-22 20:54:04,313 root INFO copying build/lib/django/conf/locale/sr/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/sr
2025-04-22 20:54:04,314 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,314 root INFO copying build/lib/django/conf/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,314 root INFO copying build/lib/django/conf/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,314 root INFO copying build/lib/django/conf/locale/sr/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/sr
2025-04-22 20:54:04,314 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/bs
2025-04-22 20:54:04,314 root INFO copying build/lib/django/conf/locale/bs/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/bs
2025-04-22 20:54:04,315 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,315 root INFO copying build/lib/django/conf/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,315 root INFO copying build/lib/django/conf/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,315 root INFO copying build/lib/django/conf/locale/bs/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/bs
2025-04-22 20:54:04,315 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/es_NI
2025-04-22 20:54:04,315 root INFO copying build/lib/django/conf/locale/es_NI/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_NI
2025-04-22 20:54:04,315 root INFO copying build/lib/django/conf/locale/es_NI/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_NI
2025-04-22 20:54:04,316 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ro
2025-04-22 20:54:04,316 root INFO copying build/lib/django/conf/locale/ro/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ro
2025-04-22 20:54:04,316 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,316 root INFO copying build/lib/django/conf/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,316 root INFO copying build/lib/django/conf/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,316 root INFO copying build/lib/django/conf/locale/ro/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ro
2025-04-22 20:54:04,317 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ky
2025-04-22 20:54:04,317 root INFO copying build/lib/django/conf/locale/ky/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ky
2025-04-22 20:54:04,317 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,317 root INFO copying build/lib/django/conf/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,317 root INFO copying build/lib/django/conf/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,317 root INFO copying build/lib/django/conf/locale/ky/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ky
2025-04-22 20:54:04,317 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/fr
2025-04-22 20:54:04,318 root INFO copying build/lib/django/conf/locale/fr/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/fr
2025-04-22 20:54:04,318 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,318 root INFO copying build/lib/django/conf/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,318 root INFO copying build/lib/django/conf/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,318 root INFO copying build/lib/django/conf/locale/fr/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/fr
2025-04-22 20:54:04,318 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ar
2025-04-22 20:54:04,318 root INFO copying build/lib/django/conf/locale/ar/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ar
2025-04-22 20:54:04,319 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,319 root INFO copying build/lib/django/conf/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,319 root INFO copying build/lib/django/conf/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,319 root INFO copying build/lib/django/conf/locale/ar/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ar
2025-04-22 20:54:04,319 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/hy
2025-04-22 20:54:04,319 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,320 root INFO copying build/lib/django/conf/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,320 root INFO copying build/lib/django/conf/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,320 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/es_AR
2025-04-22 20:54:04,320 root INFO copying build/lib/django/conf/locale/es_AR/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_AR
2025-04-22 20:54:04,320 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,320 root INFO copying build/lib/django/conf/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,321 root INFO copying build/lib/django/conf/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,321 root INFO copying build/lib/django/conf/locale/es_AR/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_AR
2025-04-22 20:54:04,321 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/vi
2025-04-22 20:54:04,321 root INFO copying build/lib/django/conf/locale/vi/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/vi
2025-04-22 20:54:04,321 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,321 root INFO copying build/lib/django/conf/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,322 root INFO copying build/lib/django/conf/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,322 root INFO copying build/lib/django/conf/locale/vi/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/vi
2025-04-22 20:54:04,322 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ckb
2025-04-22 20:54:04,322 root INFO copying build/lib/django/conf/locale/ckb/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ckb
2025-04-22 20:54:04,322 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,322 root INFO copying build/lib/django/conf/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,323 root INFO copying build/lib/django/conf/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,323 root INFO copying build/lib/django/conf/locale/ckb/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ckb
2025-04-22 20:54:04,323 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/sv
2025-04-22 20:54:04,323 root INFO copying build/lib/django/conf/locale/sv/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/sv
2025-04-22 20:54:04,323 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,323 root INFO copying build/lib/django/conf/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,323 root INFO copying build/lib/django/conf/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,324 root INFO copying build/lib/django/conf/locale/sv/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/sv
2025-04-22 20:54:04,324 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/zh_Hant
2025-04-22 20:54:04,324 root INFO copying build/lib/django/conf/locale/zh_Hant/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/zh_Hant
2025-04-22 20:54:04,324 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,324 root INFO copying build/lib/django/conf/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,324 root INFO copying build/lib/django/conf/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,325 root INFO copying build/lib/django/conf/locale/zh_Hant/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/zh_Hant
2025-04-22 20:54:04,325 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/kk
2025-04-22 20:54:04,325 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,325 root INFO copying build/lib/django/conf/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,325 root INFO copying build/lib/django/conf/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,325 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/es_CO
2025-04-22 20:54:04,326 root INFO copying build/lib/django/conf/locale/es_CO/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_CO
2025-04-22 20:54:04,326 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,326 root INFO copying build/lib/django/conf/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,326 root INFO copying build/lib/django/conf/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,326 root INFO copying build/lib/django/conf/locale/es_CO/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_CO
2025-04-22 20:54:04,326 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/be
2025-04-22 20:54:04,327 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/be/LC_MESSAGES
2025-04-22 20:54:04,327 root INFO copying build/lib/django/conf/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/be/LC_MESSAGES
2025-04-22 20:54:04,327 root INFO copying build/lib/django/conf/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/be/LC_MESSAGES
2025-04-22 20:54:04,327 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/udm
2025-04-22 20:54:04,327 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,327 root INFO copying build/lib/django/conf/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,327 root INFO copying build/lib/django/conf/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,328 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ml
2025-04-22 20:54:04,328 root INFO copying build/lib/django/conf/locale/ml/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ml
2025-04-22 20:54:04,328 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,328 root INFO copying build/lib/django/conf/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,328 root INFO copying build/lib/django/conf/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,328 root INFO copying build/lib/django/conf/locale/ml/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ml
2025-04-22 20:54:04,329 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ar_DZ
2025-04-22 20:54:04,329 root INFO copying build/lib/django/conf/locale/ar_DZ/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ar_DZ
2025-04-22 20:54:04,329 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,329 root INFO copying build/lib/django/conf/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,329 root INFO copying build/lib/django/conf/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,329 root INFO copying build/lib/django/conf/locale/ar_DZ/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ar_DZ
2025-04-22 20:54:04,330 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ms
2025-04-22 20:54:04,330 root INFO copying build/lib/django/conf/locale/ms/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ms
2025-04-22 20:54:04,330 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,330 root INFO copying build/lib/django/conf/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,330 root INFO copying build/lib/django/conf/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,330 root INFO copying build/lib/django/conf/locale/ms/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ms
2025-04-22 20:54:04,331 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ast
2025-04-22 20:54:04,331 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,331 root INFO copying build/lib/django/conf/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,331 root INFO copying build/lib/django/conf/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,331 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/zh_Hans
2025-04-22 20:54:04,331 root INFO copying build/lib/django/conf/locale/zh_Hans/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/zh_Hans
2025-04-22 20:54:04,332 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,332 root INFO copying build/lib/django/conf/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,332 root INFO copying build/lib/django/conf/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,332 root INFO copying build/lib/django/conf/locale/zh_Hans/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/zh_Hans
2025-04-22 20:54:04,332 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ur
2025-04-22 20:54:04,332 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,332 root INFO copying build/lib/django/conf/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,333 root INFO copying build/lib/django/conf/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,333 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ia
2025-04-22 20:54:04,333 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,333 root INFO copying build/lib/django/conf/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,333 root INFO copying build/lib/django/conf/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,333 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/hu
2025-04-22 20:54:04,334 root INFO copying build/lib/django/conf/locale/hu/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/hu
2025-04-22 20:54:04,334 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,334 root INFO copying build/lib/django/conf/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,334 root INFO copying build/lib/django/conf/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,334 root INFO copying build/lib/django/conf/locale/hu/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/hu
2025-04-22 20:54:04,334 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ta
2025-04-22 20:54:04,334 root INFO copying build/lib/django/conf/locale/ta/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ta
2025-04-22 20:54:04,335 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,335 root INFO copying build/lib/django/conf/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,335 root INFO copying build/lib/django/conf/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,335 root INFO copying build/lib/django/conf/locale/ta/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ta
2025-04-22 20:54:04,335 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/eu
2025-04-22 20:54:04,336 root INFO copying build/lib/django/conf/locale/eu/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/eu
2025-04-22 20:54:04,336 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,336 root INFO copying build/lib/django/conf/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,336 root INFO copying build/lib/django/conf/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,336 root INFO copying build/lib/django/conf/locale/eu/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/eu
2025-04-22 20:54:04,336 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/es_MX
2025-04-22 20:54:04,336 root INFO copying build/lib/django/conf/locale/es_MX/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_MX
2025-04-22 20:54:04,337 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,337 root INFO copying build/lib/django/conf/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,337 root INFO copying build/lib/django/conf/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,337 root INFO copying build/lib/django/conf/locale/es_MX/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/es_MX
2025-04-22 20:54:04,337 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/tk
2025-04-22 20:54:04,337 root INFO copying build/lib/django/conf/locale/tk/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/tk
2025-04-22 20:54:04,338 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,338 root INFO copying build/lib/django/conf/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,338 root INFO copying build/lib/django/conf/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,338 root INFO copying build/lib/django/conf/locale/tk/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/tk
2025-04-22 20:54:04,338 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/th
2025-04-22 20:54:04,338 root INFO copying build/lib/django/conf/locale/th/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/th
2025-04-22 20:54:04,338 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/th/LC_MESSAGES
2025-04-22 20:54:04,339 root INFO copying build/lib/django/conf/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/th/LC_MESSAGES
2025-04-22 20:54:04,339 root INFO copying build/lib/django/conf/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/th/LC_MESSAGES
2025-04-22 20:54:04,339 root INFO copying build/lib/django/conf/locale/th/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/th
2025-04-22 20:54:04,339 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/nb
2025-04-22 20:54:04,339 root INFO copying build/lib/django/conf/locale/nb/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/nb
2025-04-22 20:54:04,339 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,339 root INFO copying build/lib/django/conf/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,340 root INFO copying build/lib/django/conf/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,340 root INFO copying build/lib/django/conf/locale/nb/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/nb
2025-04-22 20:54:04,340 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/mn
2025-04-22 20:54:04,340 root INFO copying build/lib/django/conf/locale/mn/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/mn
2025-04-22 20:54:04,340 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,340 root INFO copying build/lib/django/conf/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,341 root INFO copying build/lib/django/conf/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,341 root INFO copying build/lib/django/conf/locale/mn/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/mn
2025-04-22 20:54:04,341 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ka
2025-04-22 20:54:04,341 root INFO copying build/lib/django/conf/locale/ka/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ka
2025-04-22 20:54:04,341 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,341 root INFO copying build/lib/django/conf/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,342 root INFO copying build/lib/django/conf/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,342 root INFO copying build/lib/django/conf/locale/ka/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/ka
2025-04-22 20:54:04,342 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/nl
2025-04-22 20:54:04,342 root INFO copying build/lib/django/conf/locale/nl/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/nl
2025-04-22 20:54:04,342 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,342 root INFO copying build/lib/django/conf/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,342 root INFO copying build/lib/django/conf/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,343 root INFO copying build/lib/django/conf/locale/nl/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/nl
2025-04-22 20:54:04,343 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/te
2025-04-22 20:54:04,343 root INFO copying build/lib/django/conf/locale/te/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/te
2025-04-22 20:54:04,343 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/te/LC_MESSAGES
2025-04-22 20:54:04,343 root INFO copying build/lib/django/conf/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/te/LC_MESSAGES
2025-04-22 20:54:04,343 root INFO copying build/lib/django/conf/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/te/LC_MESSAGES
2025-04-22 20:54:04,344 root INFO copying build/lib/django/conf/locale/te/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/te
2025-04-22 20:54:04,344 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/pt
2025-04-22 20:54:04,344 root INFO copying build/lib/django/conf/locale/pt/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/pt
2025-04-22 20:54:04,344 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,344 root INFO copying build/lib/django/conf/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,344 root INFO copying build/lib/django/conf/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,344 root INFO copying build/lib/django/conf/locale/pt/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/pt
2025-04-22 20:54:04,345 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/bn
2025-04-22 20:54:04,345 root INFO copying build/lib/django/conf/locale/bn/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/bn
2025-04-22 20:54:04,345 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,345 root INFO copying build/lib/django/conf/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,345 root INFO copying build/lib/django/conf/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,345 root INFO copying build/lib/django/conf/locale/bn/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/bn
2025-04-22 20:54:04,346 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/he
2025-04-22 20:54:04,346 root INFO copying build/lib/django/conf/locale/he/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/he
2025-04-22 20:54:04,346 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/he/LC_MESSAGES
2025-04-22 20:54:04,346 root INFO copying build/lib/django/conf/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/he/LC_MESSAGES
2025-04-22 20:54:04,346 root INFO copying build/lib/django/conf/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/he/LC_MESSAGES
2025-04-22 20:54:04,346 root INFO copying build/lib/django/conf/locale/he/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/he
2025-04-22 20:54:04,346 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/br
2025-04-22 20:54:04,347 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/br/LC_MESSAGES
2025-04-22 20:54:04,347 root INFO copying build/lib/django/conf/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/br/LC_MESSAGES
2025-04-22 20:54:04,347 root INFO copying build/lib/django/conf/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/br/LC_MESSAGES
2025-04-22 20:54:04,347 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/fa
2025-04-22 20:54:04,347 root INFO copying build/lib/django/conf/locale/fa/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/fa
2025-04-22 20:54:04,347 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,347 root INFO copying build/lib/django/conf/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,348 root INFO copying build/lib/django/conf/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,348 root INFO copying build/lib/django/conf/locale/fa/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/fa
2025-04-22 20:54:04,348 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/tg
2025-04-22 20:54:04,348 root INFO copying build/lib/django/conf/locale/tg/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/tg
2025-04-22 20:54:04,348 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,348 root INFO copying build/lib/django/conf/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,349 root INFO copying build/lib/django/conf/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,349 root INFO copying build/lib/django/conf/locale/tg/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/tg
2025-04-22 20:54:04,349 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/km
2025-04-22 20:54:04,349 root INFO copying build/lib/django/conf/locale/km/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/km
2025-04-22 20:54:04,349 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/km/LC_MESSAGES
2025-04-22 20:54:04,349 root INFO copying build/lib/django/conf/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/km/LC_MESSAGES
2025-04-22 20:54:04,350 root INFO copying build/lib/django/conf/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/km/LC_MESSAGES
2025-04-22 20:54:04,350 root INFO copying build/lib/django/conf/locale/km/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/km
2025-04-22 20:54:04,350 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/da
2025-04-22 20:54:04,350 root INFO copying build/lib/django/conf/locale/da/__init__.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/da
2025-04-22 20:54:04,350 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/locale/da/LC_MESSAGES
2025-04-22 20:54:04,350 root INFO copying build/lib/django/conf/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/conf/locale/da/LC_MESSAGES
2025-04-22 20:54:04,350 root INFO copying build/lib/django/conf/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/conf/locale/da/LC_MESSAGES
2025-04-22 20:54:04,351 root INFO copying build/lib/django/conf/locale/da/formats.py -> build/bdist.linux-aarch64/wheel/django/conf/locale/da
2025-04-22 20:54:04,351 root INFO copying build/lib/django/conf/global_settings.py -> build/bdist.linux-aarch64/wheel/django/conf
2025-04-22 20:54:04,351 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/app_template
2025-04-22 20:54:04,351 root INFO copying build/lib/django/conf/app_template/apps.py-tpl -> build/bdist.linux-aarch64/wheel/django/conf/app_template
2025-04-22 20:54:04,351 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/app_template/migrations
2025-04-22 20:54:04,351 root INFO copying build/lib/django/conf/app_template/migrations/__init__.py-tpl -> build/bdist.linux-aarch64/wheel/django/conf/app_template/migrations
2025-04-22 20:54:04,352 root INFO copying build/lib/django/conf/app_template/views.py-tpl -> build/bdist.linux-aarch64/wheel/django/conf/app_template
2025-04-22 20:54:04,352 root INFO copying build/lib/django/conf/app_template/__init__.py-tpl -> build/bdist.linux-aarch64/wheel/django/conf/app_template
2025-04-22 20:54:04,352 root INFO copying build/lib/django/conf/app_template/admin.py-tpl -> build/bdist.linux-aarch64/wheel/django/conf/app_template
2025-04-22 20:54:04,352 root INFO copying build/lib/django/conf/app_template/tests.py-tpl -> build/bdist.linux-aarch64/wheel/django/conf/app_template
2025-04-22 20:54:04,352 root INFO copying build/lib/django/conf/app_template/models.py-tpl -> build/bdist.linux-aarch64/wheel/django/conf/app_template
2025-04-22 20:54:04,352 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/project_template
2025-04-22 20:54:04,352 root INFO creating build/bdist.linux-aarch64/wheel/django/conf/project_template/project_name
2025-04-22 20:54:04,352 root INFO copying build/lib/django/conf/project_template/project_name/asgi.py-tpl -> build/bdist.linux-aarch64/wheel/django/conf/project_template/project_name
2025-04-22 20:54:04,353 root INFO copying build/lib/django/conf/project_template/project_name/urls.py-tpl -> build/bdist.linux-aarch64/wheel/django/conf/project_template/project_name
2025-04-22 20:54:04,353 root INFO copying build/lib/django/conf/project_template/project_name/settings.py-tpl -> build/bdist.linux-aarch64/wheel/django/conf/project_template/project_name
2025-04-22 20:54:04,353 root INFO copying build/lib/django/conf/project_template/project_name/wsgi.py-tpl -> build/bdist.linux-aarch64/wheel/django/conf/project_template/project_name
2025-04-22 20:54:04,353 root INFO copying build/lib/django/conf/project_template/project_name/__init__.py-tpl -> build/bdist.linux-aarch64/wheel/django/conf/project_template/project_name
2025-04-22 20:54:04,353 root INFO copying build/lib/django/conf/project_template/manage.py-tpl -> build/bdist.linux-aarch64/wheel/django/conf/project_template
2025-04-22 20:54:04,353 root INFO creating build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,354 root INFO copying build/lib/django/utils/datetime_safe.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,354 root INFO copying build/lib/django/utils/__init__.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,354 root INFO copying build/lib/django/utils/itercompat.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,354 root INFO copying build/lib/django/utils/functional.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,354 root INFO copying build/lib/django/utils/hashable.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,354 root INFO creating build/bdist.linux-aarch64/wheel/django/utils/translation
2025-04-22 20:54:04,354 root INFO copying build/lib/django/utils/translation/__init__.py -> build/bdist.linux-aarch64/wheel/django/utils/translation
2025-04-22 20:54:04,355 root INFO copying build/lib/django/utils/translation/template.py -> build/bdist.linux-aarch64/wheel/django/utils/translation
2025-04-22 20:54:04,355 root INFO copying build/lib/django/utils/translation/reloader.py -> build/bdist.linux-aarch64/wheel/django/utils/translation
2025-04-22 20:54:04,355 root INFO copying build/lib/django/utils/translation/trans_null.py -> build/bdist.linux-aarch64/wheel/django/utils/translation
2025-04-22 20:54:04,355 root INFO copying build/lib/django/utils/translation/trans_real.py -> build/bdist.linux-aarch64/wheel/django/utils/translation
2025-04-22 20:54:04,355 root INFO copying build/lib/django/utils/log.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,356 root INFO copying build/lib/django/utils/_os.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,356 root INFO copying build/lib/django/utils/dateparse.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,356 root INFO copying build/lib/django/utils/decorators.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,356 root INFO copying build/lib/django/utils/topological_sort.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,356 root INFO copying build/lib/django/utils/deprecation.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,356 root INFO copying build/lib/django/utils/formats.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,356 root INFO copying build/lib/django/utils/autoreload.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,357 root INFO copying build/lib/django/utils/timezone.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,357 root INFO copying build/lib/django/utils/timesince.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,357 root INFO copying build/lib/django/utils/cache.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,357 root INFO copying build/lib/django/utils/version.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,357 root INFO copying build/lib/django/utils/datastructures.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,358 root INFO copying build/lib/django/utils/dateformat.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,358 root INFO copying build/lib/django/utils/html.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,358 root INFO copying build/lib/django/utils/termcolors.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,358 root INFO copying build/lib/django/utils/tree.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,358 root INFO copying build/lib/django/utils/http.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,358 root INFO copying build/lib/django/utils/ipv6.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,359 root INFO copying build/lib/django/utils/asyncio.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,359 root INFO copying build/lib/django/utils/connection.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,359 root INFO copying build/lib/django/utils/lorem_ipsum.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,359 root INFO copying build/lib/django/utils/baseconv.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,359 root INFO copying build/lib/django/utils/numberformat.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,359 root INFO copying build/lib/django/utils/inspect.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,359 root INFO copying build/lib/django/utils/feedgenerator.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,360 root INFO copying build/lib/django/utils/duration.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,360 root INFO copying build/lib/django/utils/deconstruct.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,360 root INFO copying build/lib/django/utils/safestring.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,360 root INFO copying build/lib/django/utils/module_loading.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,360 root INFO copying build/lib/django/utils/archive.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,360 root INFO copying build/lib/django/utils/crypto.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,361 root INFO copying build/lib/django/utils/regex_helper.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,361 root INFO copying build/lib/django/utils/dates.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,361 root INFO copying build/lib/django/utils/xmlutils.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,361 root INFO copying build/lib/django/utils/encoding.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,361 root INFO copying build/lib/django/utils/jslex.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,361 root INFO copying build/lib/django/utils/text.py -> build/bdist.linux-aarch64/wheel/django/utils
2025-04-22 20:54:04,362 root INFO creating build/bdist.linux-aarch64/wheel/django/templatetags
2025-04-22 20:54:04,362 root INFO copying build/lib/django/templatetags/__init__.py -> build/bdist.linux-aarch64/wheel/django/templatetags
2025-04-22 20:54:04,362 root INFO copying build/lib/django/templatetags/tz.py -> build/bdist.linux-aarch64/wheel/django/templatetags
2025-04-22 20:54:04,362 root INFO copying build/lib/django/templatetags/i18n.py -> build/bdist.linux-aarch64/wheel/django/templatetags
2025-04-22 20:54:04,362 root INFO copying build/lib/django/templatetags/cache.py -> build/bdist.linux-aarch64/wheel/django/templatetags
2025-04-22 20:54:04,362 root INFO copying build/lib/django/templatetags/static.py -> build/bdist.linux-aarch64/wheel/django/templatetags
2025-04-22 20:54:04,363 root INFO copying build/lib/django/templatetags/l10n.py -> build/bdist.linux-aarch64/wheel/django/templatetags
2025-04-22 20:54:04,363 root INFO copying build/lib/django/__main__.py -> build/bdist.linux-aarch64/wheel/django
2025-04-22 20:54:04,363 root INFO creating build/bdist.linux-aarch64/wheel/django/test
2025-04-22 20:54:04,363 root INFO copying build/lib/django/test/__init__.py -> build/bdist.linux-aarch64/wheel/django/test
2025-04-22 20:54:04,363 root INFO copying build/lib/django/test/signals.py -> build/bdist.linux-aarch64/wheel/django/test
2025-04-22 20:54:04,363 root INFO copying build/lib/django/test/selenium.py -> build/bdist.linux-aarch64/wheel/django/test
2025-04-22 20:54:04,363 root INFO copying build/lib/django/test/testcases.py -> build/bdist.linux-aarch64/wheel/django/test
2025-04-22 20:54:04,364 root INFO copying build/lib/django/test/html.py -> build/bdist.linux-aarch64/wheel/django/test
2025-04-22 20:54:04,364 root INFO copying build/lib/django/test/utils.py -> build/bdist.linux-aarch64/wheel/django/test
2025-04-22 20:54:04,364 root INFO copying build/lib/django/test/runner.py -> build/bdist.linux-aarch64/wheel/django/test
2025-04-22 20:54:04,364 root INFO copying build/lib/django/test/client.py -> build/bdist.linux-aarch64/wheel/django/test
2025-04-22 20:54:04,365 root INFO copying build/lib/django/shortcuts.py -> build/bdist.linux-aarch64/wheel/django
2025-04-22 20:54:04,365 root INFO creating build/bdist.linux-aarch64/wheel/django/core
2025-04-22 20:54:04,365 root INFO copying build/lib/django/core/__init__.py -> build/bdist.linux-aarch64/wheel/django/core
2025-04-22 20:54:04,365 root INFO copying build/lib/django/core/signals.py -> build/bdist.linux-aarch64/wheel/django/core
2025-04-22 20:54:04,365 root INFO creating build/bdist.linux-aarch64/wheel/django/core/files
2025-04-22 20:54:04,366 root INFO copying build/lib/django/core/files/__init__.py -> build/bdist.linux-aarch64/wheel/django/core/files
2025-04-22 20:54:04,366 root INFO copying build/lib/django/core/files/uploadhandler.py -> build/bdist.linux-aarch64/wheel/django/core/files
2025-04-22 20:54:04,366 root INFO creating build/bdist.linux-aarch64/wheel/django/core/files/storage
2025-04-22 20:54:04,366 root INFO copying build/lib/django/core/files/storage/__init__.py -> build/bdist.linux-aarch64/wheel/django/core/files/storage
2025-04-22 20:54:04,366 root INFO copying build/lib/django/core/files/storage/handler.py -> build/bdist.linux-aarch64/wheel/django/core/files/storage
2025-04-22 20:54:04,366 root INFO copying build/lib/django/core/files/storage/memory.py -> build/bdist.linux-aarch64/wheel/django/core/files/storage
2025-04-22 20:54:04,366 root INFO copying build/lib/django/core/files/storage/filesystem.py -> build/bdist.linux-aarch64/wheel/django/core/files/storage
2025-04-22 20:54:04,367 root INFO copying build/lib/django/core/files/storage/base.py -> build/bdist.linux-aarch64/wheel/django/core/files/storage
2025-04-22 20:54:04,367 root INFO copying build/lib/django/core/files/storage/mixins.py -> build/bdist.linux-aarch64/wheel/django/core/files/storage
2025-04-22 20:54:04,367 root INFO copying build/lib/django/core/files/uploadedfile.py -> build/bdist.linux-aarch64/wheel/django/core/files
2025-04-22 20:54:04,367 root INFO copying build/lib/django/core/files/utils.py -> build/bdist.linux-aarch64/wheel/django/core/files
2025-04-22 20:54:04,367 root INFO copying build/lib/django/core/files/temp.py -> build/bdist.linux-aarch64/wheel/django/core/files
2025-04-22 20:54:04,367 root INFO copying build/lib/django/core/files/move.py -> build/bdist.linux-aarch64/wheel/django/core/files
2025-04-22 20:54:04,367 root INFO copying build/lib/django/core/files/locks.py -> build/bdist.linux-aarch64/wheel/django/core/files
2025-04-22 20:54:04,368 root INFO copying build/lib/django/core/files/base.py -> build/bdist.linux-aarch64/wheel/django/core/files
2025-04-22 20:54:04,368 root INFO copying build/lib/django/core/files/images.py -> build/bdist.linux-aarch64/wheel/django/core/files
2025-04-22 20:54:04,368 root INFO creating build/bdist.linux-aarch64/wheel/django/core/handlers
2025-04-22 20:54:04,368 root INFO copying build/lib/django/core/handlers/__init__.py -> build/bdist.linux-aarch64/wheel/django/core/handlers
2025-04-22 20:54:04,368 root INFO copying build/lib/django/core/handlers/asgi.py -> build/bdist.linux-aarch64/wheel/django/core/handlers
2025-04-22 20:54:04,368 root INFO copying build/lib/django/core/handlers/exception.py -> build/bdist.linux-aarch64/wheel/django/core/handlers
2025-04-22 20:54:04,369 root INFO copying build/lib/django/core/handlers/wsgi.py -> build/bdist.linux-aarch64/wheel/django/core/handlers
2025-04-22 20:54:04,369 root INFO copying build/lib/django/core/handlers/base.py -> build/bdist.linux-aarch64/wheel/django/core/handlers
2025-04-22 20:54:04,369 root INFO copying build/lib/django/core/asgi.py -> build/bdist.linux-aarch64/wheel/django/core
2025-04-22 20:54:04,369 root INFO copying build/lib/django/core/validators.py -> build/bdist.linux-aarch64/wheel/django/core
2025-04-22 20:54:04,369 root INFO copying build/lib/django/core/exceptions.py -> build/bdist.linux-aarch64/wheel/django/core
2025-04-22 20:54:04,369 root INFO creating build/bdist.linux-aarch64/wheel/django/core/servers
2025-04-22 20:54:04,369 root INFO copying build/lib/django/core/servers/__init__.py -> build/bdist.linux-aarch64/wheel/django/core/servers
2025-04-22 20:54:04,370 root INFO copying build/lib/django/core/servers/basehttp.py -> build/bdist.linux-aarch64/wheel/django/core/servers
2025-04-22 20:54:04,370 root INFO creating build/bdist.linux-aarch64/wheel/django/core/mail
2025-04-22 20:54:04,370 root INFO copying build/lib/django/core/mail/__init__.py -> build/bdist.linux-aarch64/wheel/django/core/mail
2025-04-22 20:54:04,370 root INFO copying build/lib/django/core/mail/utils.py -> build/bdist.linux-aarch64/wheel/django/core/mail
2025-04-22 20:54:04,370 root INFO copying build/lib/django/core/mail/message.py -> build/bdist.linux-aarch64/wheel/django/core/mail
2025-04-22 20:54:04,370 root INFO creating build/bdist.linux-aarch64/wheel/django/core/mail/backends
2025-04-22 20:54:04,370 root INFO copying build/lib/django/core/mail/backends/__init__.py -> build/bdist.linux-aarch64/wheel/django/core/mail/backends
2025-04-22 20:54:04,371 root INFO copying build/lib/django/core/mail/backends/locmem.py -> build/bdist.linux-aarch64/wheel/django/core/mail/backends
2025-04-22 20:54:04,371 root INFO copying build/lib/django/core/mail/backends/base.py -> build/bdist.linux-aarch64/wheel/django/core/mail/backends
2025-04-22 20:54:04,371 root INFO copying build/lib/django/core/mail/backends/console.py -> build/bdist.linux-aarch64/wheel/django/core/mail/backends
2025-04-22 20:54:04,371 root INFO copying build/lib/django/core/mail/backends/dummy.py -> build/bdist.linux-aarch64/wheel/django/core/mail/backends
2025-04-22 20:54:04,371 root INFO copying build/lib/django/core/mail/backends/smtp.py -> build/bdist.linux-aarch64/wheel/django/core/mail/backends
2025-04-22 20:54:04,371 root INFO copying build/lib/django/core/mail/backends/filebased.py -> build/bdist.linux-aarch64/wheel/django/core/mail/backends
2025-04-22 20:54:04,372 root INFO creating build/bdist.linux-aarch64/wheel/django/core/cache
2025-04-22 20:54:04,372 root INFO copying build/lib/django/core/cache/__init__.py -> build/bdist.linux-aarch64/wheel/django/core/cache
2025-04-22 20:54:04,372 root INFO copying build/lib/django/core/cache/utils.py -> build/bdist.linux-aarch64/wheel/django/core/cache
2025-04-22 20:54:04,372 root INFO creating build/bdist.linux-aarch64/wheel/django/core/cache/backends
2025-04-22 20:54:04,372 root INFO copying build/lib/django/core/cache/backends/__init__.py -> build/bdist.linux-aarch64/wheel/django/core/cache/backends
2025-04-22 20:54:04,372 root INFO copying build/lib/django/core/cache/backends/locmem.py -> build/bdist.linux-aarch64/wheel/django/core/cache/backends
2025-04-22 20:54:04,372 root INFO copying build/lib/django/core/cache/backends/db.py -> build/bdist.linux-aarch64/wheel/django/core/cache/backends
2025-04-22 20:54:04,373 root INFO copying build/lib/django/core/cache/backends/memcached.py -> build/bdist.linux-aarch64/wheel/django/core/cache/backends
2025-04-22 20:54:04,373 root INFO copying build/lib/django/core/cache/backends/redis.py -> build/bdist.linux-aarch64/wheel/django/core/cache/backends
2025-04-22 20:54:04,373 root INFO copying build/lib/django/core/cache/backends/base.py -> build/bdist.linux-aarch64/wheel/django/core/cache/backends
2025-04-22 20:54:04,373 root INFO copying build/lib/django/core/cache/backends/dummy.py -> build/bdist.linux-aarch64/wheel/django/core/cache/backends
2025-04-22 20:54:04,373 root INFO copying build/lib/django/core/cache/backends/filebased.py -> build/bdist.linux-aarch64/wheel/django/core/cache/backends
2025-04-22 20:54:04,373 root INFO copying build/lib/django/core/paginator.py -> build/bdist.linux-aarch64/wheel/django/core
2025-04-22 20:54:04,374 root INFO creating build/bdist.linux-aarch64/wheel/django/core/management
2025-04-22 20:54:04,374 root INFO copying build/lib/django/core/management/__init__.py -> build/bdist.linux-aarch64/wheel/django/core/management
2025-04-22 20:54:04,374 root INFO copying build/lib/django/core/management/color.py -> build/bdist.linux-aarch64/wheel/django/core/management
2025-04-22 20:54:04,374 root INFO copying build/lib/django/core/management/utils.py -> build/bdist.linux-aarch64/wheel/django/core/management
2025-04-22 20:54:04,374 root INFO copying build/lib/django/core/management/sql.py -> build/bdist.linux-aarch64/wheel/django/core/management
2025-04-22 20:54:04,374 root INFO creating build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,374 root INFO copying build/lib/django/core/management/commands/__init__.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,375 root INFO copying build/lib/django/core/management/commands/sqlmigrate.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,375 root INFO copying build/lib/django/core/management/commands/startapp.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,375 root INFO copying build/lib/django/core/management/commands/showmigrations.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,375 root INFO copying build/lib/django/core/management/commands/optimizemigration.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,375 root INFO copying build/lib/django/core/management/commands/dumpdata.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,375 root INFO copying build/lib/django/core/management/commands/migrate.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,375 root INFO copying build/lib/django/core/management/commands/shell.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,376 root INFO copying build/lib/django/core/management/commands/loaddata.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,376 root INFO copying build/lib/django/core/management/commands/createcachetable.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,376 root INFO copying build/lib/django/core/management/commands/dbshell.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,376 root INFO copying build/lib/django/core/management/commands/inspectdb.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,376 root INFO copying build/lib/django/core/management/commands/compilemessages.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,376 root INFO copying build/lib/django/core/management/commands/startproject.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,376 root INFO copying build/lib/django/core/management/commands/testserver.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,377 root INFO copying build/lib/django/core/management/commands/flush.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,377 root INFO copying build/lib/django/core/management/commands/diffsettings.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,377 root INFO copying build/lib/django/core/management/commands/sqlflush.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,377 root INFO copying build/lib/django/core/management/commands/makemigrations.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,377 root INFO copying build/lib/django/core/management/commands/sqlsequencereset.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,377 root INFO copying build/lib/django/core/management/commands/makemessages.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,378 root INFO copying build/lib/django/core/management/commands/runserver.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,378 root INFO copying build/lib/django/core/management/commands/check.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,378 root INFO copying build/lib/django/core/management/commands/sendtestemail.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,378 root INFO copying build/lib/django/core/management/commands/squashmigrations.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,378 root INFO copying build/lib/django/core/management/commands/test.py -> build/bdist.linux-aarch64/wheel/django/core/management/commands
2025-04-22 20:54:04,378 root INFO copying build/lib/django/core/management/templates.py -> build/bdist.linux-aarch64/wheel/django/core/management
2025-04-22 20:54:04,378 root INFO copying build/lib/django/core/management/base.py -> build/bdist.linux-aarch64/wheel/django/core/management
2025-04-22 20:54:04,379 root INFO copying build/lib/django/core/wsgi.py -> build/bdist.linux-aarch64/wheel/django/core
2025-04-22 20:54:04,379 root INFO creating build/bdist.linux-aarch64/wheel/django/core/serializers
2025-04-22 20:54:04,379 root INFO copying build/lib/django/core/serializers/python.py -> build/bdist.linux-aarch64/wheel/django/core/serializers
2025-04-22 20:54:04,379 root INFO copying build/lib/django/core/serializers/__init__.py -> build/bdist.linux-aarch64/wheel/django/core/serializers
2025-04-22 20:54:04,379 root INFO copying build/lib/django/core/serializers/xml_serializer.py -> build/bdist.linux-aarch64/wheel/django/core/serializers
2025-04-22 20:54:04,379 root INFO copying build/lib/django/core/serializers/jsonl.py -> build/bdist.linux-aarch64/wheel/django/core/serializers
2025-04-22 20:54:04,380 root INFO copying build/lib/django/core/serializers/json.py -> build/bdist.linux-aarch64/wheel/django/core/serializers
2025-04-22 20:54:04,380 root INFO copying build/lib/django/core/serializers/pyyaml.py -> build/bdist.linux-aarch64/wheel/django/core/serializers
2025-04-22 20:54:04,380 root INFO copying build/lib/django/core/serializers/base.py -> build/bdist.linux-aarch64/wheel/django/core/serializers
2025-04-22 20:54:04,380 root INFO creating build/bdist.linux-aarch64/wheel/django/core/checks
2025-04-22 20:54:04,380 root INFO copying build/lib/django/core/checks/__init__.py -> build/bdist.linux-aarch64/wheel/django/core/checks
2025-04-22 20:54:04,380 root INFO copying build/lib/django/core/checks/registry.py -> build/bdist.linux-aarch64/wheel/django/core/checks
2025-04-22 20:54:04,380 root INFO copying build/lib/django/core/checks/database.py -> build/bdist.linux-aarch64/wheel/django/core/checks
2025-04-22 20:54:04,381 root INFO copying build/lib/django/core/checks/messages.py -> build/bdist.linux-aarch64/wheel/django/core/checks
2025-04-22 20:54:04,381 root INFO copying build/lib/django/core/checks/urls.py -> build/bdist.linux-aarch64/wheel/django/core/checks
2025-04-22 20:54:04,381 root INFO creating build/bdist.linux-aarch64/wheel/django/core/checks/compatibility
2025-04-22 20:54:04,381 root INFO copying build/lib/django/core/checks/compatibility/__init__.py -> build/bdist.linux-aarch64/wheel/django/core/checks/compatibility
2025-04-22 20:54:04,381 root INFO copying build/lib/django/core/checks/compatibility/django_4_0.py -> build/bdist.linux-aarch64/wheel/django/core/checks/compatibility
2025-04-22 20:54:04,381 root INFO creating build/bdist.linux-aarch64/wheel/django/core/checks/security
2025-04-22 20:54:04,381 root INFO copying build/lib/django/core/checks/security/__init__.py -> build/bdist.linux-aarch64/wheel/django/core/checks/security
2025-04-22 20:54:04,382 root INFO copying build/lib/django/core/checks/security/sessions.py -> build/bdist.linux-aarch64/wheel/django/core/checks/security
2025-04-22 20:54:04,382 root INFO copying build/lib/django/core/checks/security/csrf.py -> build/bdist.linux-aarch64/wheel/django/core/checks/security
2025-04-22 20:54:04,382 root INFO copying build/lib/django/core/checks/security/base.py -> build/bdist.linux-aarch64/wheel/django/core/checks/security
2025-04-22 20:54:04,382 root INFO copying build/lib/django/core/checks/model_checks.py -> build/bdist.linux-aarch64/wheel/django/core/checks
2025-04-22 20:54:04,382 root INFO copying build/lib/django/core/checks/caches.py -> build/bdist.linux-aarch64/wheel/django/core/checks
2025-04-22 20:54:04,382 root INFO copying build/lib/django/core/checks/translation.py -> build/bdist.linux-aarch64/wheel/django/core/checks
2025-04-22 20:54:04,383 root INFO copying build/lib/django/core/checks/templates.py -> build/bdist.linux-aarch64/wheel/django/core/checks
2025-04-22 20:54:04,383 root INFO copying build/lib/django/core/checks/async_checks.py -> build/bdist.linux-aarch64/wheel/django/core/checks
2025-04-22 20:54:04,383 root INFO copying build/lib/django/core/checks/files.py -> build/bdist.linux-aarch64/wheel/django/core/checks
2025-04-22 20:54:04,383 root INFO copying build/lib/django/core/signing.py -> build/bdist.linux-aarch64/wheel/django/core
2025-04-22 20:54:04,383 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib
2025-04-22 20:54:04,383 root INFO copying build/lib/django/contrib/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib
2025-04-22 20:54:04,383 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,384 root INFO copying build/lib/django/contrib/auth/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,384 root INFO copying build/lib/django/contrib/auth/hashers.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,384 root INFO copying build/lib/django/contrib/auth/signals.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,384 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/handlers
2025-04-22 20:54:04,384 root INFO copying build/lib/django/contrib/auth/handlers/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/handlers
2025-04-22 20:54:04,384 root INFO copying build/lib/django/contrib/auth/handlers/modwsgi.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/handlers
2025-04-22 20:54:04,385 root INFO copying build/lib/django/contrib/auth/middleware.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,385 root INFO copying build/lib/django/contrib/auth/views.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,385 root INFO copying build/lib/django/contrib/auth/forms.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,385 root INFO copying build/lib/django/contrib/auth/validators.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,385 root INFO copying build/lib/django/contrib/auth/decorators.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,385 root INFO copying build/lib/django/contrib/auth/models.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,386 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/migrations
2025-04-22 20:54:04,386 root INFO copying build/lib/django/contrib/auth/migrations/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/migrations
2025-04-22 20:54:04,386 root INFO copying build/lib/django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/migrations
2025-04-22 20:54:04,386 root INFO copying build/lib/django/contrib/auth/migrations/0002_alter_permission_name_max_length.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/migrations
2025-04-22 20:54:04,386 root INFO copying build/lib/django/contrib/auth/migrations/0008_alter_user_username_max_length.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/migrations
2025-04-22 20:54:04,386 root INFO copying build/lib/django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/migrations
2025-04-22 20:54:04,386 root INFO copying build/lib/django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/migrations
2025-04-22 20:54:04,387 root INFO copying build/lib/django/contrib/auth/migrations/0006_require_contenttypes_0002.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/migrations
2025-04-22 20:54:04,387 root INFO copying build/lib/django/contrib/auth/migrations/0011_update_proxy_permissions.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/migrations
2025-04-22 20:54:04,387 root INFO copying build/lib/django/contrib/auth/migrations/0005_alter_user_last_login_null.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/migrations
2025-04-22 20:54:04,387 root INFO copying build/lib/django/contrib/auth/migrations/0001_initial.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/migrations
2025-04-22 20:54:04,387 root INFO copying build/lib/django/contrib/auth/migrations/0010_alter_group_name_max_length.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/migrations
2025-04-22 20:54:04,387 root INFO copying build/lib/django/contrib/auth/migrations/0003_alter_user_email_max_length.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/migrations
2025-04-22 20:54:04,387 root INFO copying build/lib/django/contrib/auth/migrations/0004_alter_user_username_opts.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/migrations
2025-04-22 20:54:04,388 root INFO copying build/lib/django/contrib/auth/backends.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,388 root INFO copying build/lib/django/contrib/auth/apps.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,388 root INFO copying build/lib/django/contrib/auth/urls.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,388 root INFO copying build/lib/django/contrib/auth/admin.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,388 root INFO copying build/lib/django/contrib/auth/common-passwords.txt.gz -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,389 root INFO copying build/lib/django/contrib/auth/checks.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,389 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/management
2025-04-22 20:54:04,389 root INFO copying build/lib/django/contrib/auth/management/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/management
2025-04-22 20:54:04,389 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/management/commands
2025-04-22 20:54:04,389 root INFO copying build/lib/django/contrib/auth/management/commands/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/management/commands
2025-04-22 20:54:04,389 root INFO copying build/lib/django/contrib/auth/management/commands/createsuperuser.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/management/commands
2025-04-22 20:54:04,389 root INFO copying build/lib/django/contrib/auth/management/commands/changepassword.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth/management/commands
2025-04-22 20:54:04,390 root INFO copying build/lib/django/contrib/auth/context_processors.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,390 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale
2025-04-22 20:54:04,390 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/lv
2025-04-22 20:54:04,390 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,390 root INFO copying build/lib/django/contrib/auth/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,390 root INFO copying build/lib/django/contrib/auth/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,391 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sw
2025-04-22 20:54:04,391 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,391 root INFO copying build/lib/django/contrib/auth/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,391 root INFO copying build/lib/django/contrib/auth/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,391 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/en_AU
2025-04-22 20:54:04,391 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,391 root INFO copying build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,392 root INFO copying build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,392 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/mr
2025-04-22 20:54:04,392 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,392 root INFO copying build/lib/django/contrib/auth/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,392 root INFO copying build/lib/django/contrib/auth/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,392 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/lb
2025-04-22 20:54:04,392 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,392 root INFO copying build/lib/django/contrib/auth/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,393 root INFO copying build/lib/django/contrib/auth/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,393 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ca
2025-04-22 20:54:04,393 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,393 root INFO copying build/lib/django/contrib/auth/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,393 root INFO copying build/lib/django/contrib/auth/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,393 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/en_GB
2025-04-22 20:54:04,394 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,394 root INFO copying build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,394 root INFO copying build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,394 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/el
2025-04-22 20:54:04,394 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/el/LC_MESSAGES
2025-04-22 20:54:04,394 root INFO copying build/lib/django/contrib/auth/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/el/LC_MESSAGES
2025-04-22 20:54:04,394 root INFO copying build/lib/django/contrib/auth/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/el/LC_MESSAGES
2025-04-22 20:54:04,395 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es_VE
2025-04-22 20:54:04,395 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,395 root INFO copying build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,395 root INFO copying build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,395 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/af
2025-04-22 20:54:04,395 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/af/LC_MESSAGES
2025-04-22 20:54:04,395 root INFO copying build/lib/django/contrib/auth/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/af/LC_MESSAGES
2025-04-22 20:54:04,396 root INFO copying build/lib/django/contrib/auth/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/af/LC_MESSAGES
2025-04-22 20:54:04,396 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/en
2025-04-22 20:54:04,396 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/en/LC_MESSAGES
2025-04-22 20:54:04,396 root INFO copying build/lib/django/contrib/auth/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/en/LC_MESSAGES
2025-04-22 20:54:04,396 root INFO copying build/lib/django/contrib/auth/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/en/LC_MESSAGES
2025-04-22 20:54:04,396 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/dsb
2025-04-22 20:54:04,396 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,396 root INFO copying build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,397 root INFO copying build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,397 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/et
2025-04-22 20:54:04,397 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/et/LC_MESSAGES
2025-04-22 20:54:04,397 root INFO copying build/lib/django/contrib/auth/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/et/LC_MESSAGES
2025-04-22 20:54:04,397 root INFO copying build/lib/django/contrib/auth/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/et/LC_MESSAGES
2025-04-22 20:54:04,397 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/nn
2025-04-22 20:54:04,397 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,398 root INFO copying build/lib/django/contrib/auth/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,398 root INFO copying build/lib/django/contrib/auth/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,398 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/cy
2025-04-22 20:54:04,398 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,398 root INFO copying build/lib/django/contrib/auth/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,398 root INFO copying build/lib/django/contrib/auth/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,399 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ko
2025-04-22 20:54:04,399 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,399 root INFO copying build/lib/django/contrib/auth/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,399 root INFO copying build/lib/django/contrib/auth/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,399 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/is
2025-04-22 20:54:04,399 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/is/LC_MESSAGES
2025-04-22 20:54:04,399 root INFO copying build/lib/django/contrib/auth/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/is/LC_MESSAGES
2025-04-22 20:54:04,399 root INFO copying build/lib/django/contrib/auth/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/is/LC_MESSAGES
2025-04-22 20:54:04,400 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/pa
2025-04-22 20:54:04,400 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,400 root INFO copying build/lib/django/contrib/auth/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,400 root INFO copying build/lib/django/contrib/auth/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,400 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/tt
2025-04-22 20:54:04,400 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,400 root INFO copying build/lib/django/contrib/auth/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,401 root INFO copying build/lib/django/contrib/auth/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,401 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ne
2025-04-22 20:54:04,401 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,401 root INFO copying build/lib/django/contrib/auth/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,401 root INFO copying build/lib/django/contrib/auth/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,401 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sr_Latn
2025-04-22 20:54:04,401 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,402 root INFO copying build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,402 root INFO copying build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,402 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/fy
2025-04-22 20:54:04,402 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,402 root INFO copying build/lib/django/contrib/auth/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,402 root INFO copying build/lib/django/contrib/auth/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,402 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/bg
2025-04-22 20:54:04,403 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,403 root INFO copying build/lib/django/contrib/auth/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,403 root INFO copying build/lib/django/contrib/auth/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,403 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ga
2025-04-22 20:54:04,403 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,403 root INFO copying build/lib/django/contrib/auth/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,403 root INFO copying build/lib/django/contrib/auth/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,404 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/gl
2025-04-22 20:54:04,404 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,404 root INFO copying build/lib/django/contrib/auth/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,404 root INFO copying build/lib/django/contrib/auth/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,404 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/uk
2025-04-22 20:54:04,404 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,404 root INFO copying build/lib/django/contrib/auth/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,405 root INFO copying build/lib/django/contrib/auth/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,405 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/uz
2025-04-22 20:54:04,405 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,405 root INFO copying build/lib/django/contrib/auth/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,405 root INFO copying build/lib/django/contrib/auth/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,405 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/kn
2025-04-22 20:54:04,406 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,406 root INFO copying build/lib/django/contrib/auth/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,406 root INFO copying build/lib/django/contrib/auth/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,406 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ja
2025-04-22 20:54:04,406 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,406 root INFO copying build/lib/django/contrib/auth/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,406 root INFO copying build/lib/django/contrib/auth/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,407 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/cs
2025-04-22 20:54:04,407 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,407 root INFO copying build/lib/django/contrib/auth/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,407 root INFO copying build/lib/django/contrib/auth/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,407 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/os
2025-04-22 20:54:04,407 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/os/LC_MESSAGES
2025-04-22 20:54:04,407 root INFO copying build/lib/django/contrib/auth/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/os/LC_MESSAGES
2025-04-22 20:54:04,408 root INFO copying build/lib/django/contrib/auth/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/os/LC_MESSAGES
2025-04-22 20:54:04,408 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/tr
2025-04-22 20:54:04,408 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,408 root INFO copying build/lib/django/contrib/auth/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,408 root INFO copying build/lib/django/contrib/auth/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,409 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/io
2025-04-22 20:54:04,409 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/io/LC_MESSAGES
2025-04-22 20:54:04,409 root INFO copying build/lib/django/contrib/auth/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/io/LC_MESSAGES
2025-04-22 20:54:04,409 root INFO copying build/lib/django/contrib/auth/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/io/LC_MESSAGES
2025-04-22 20:54:04,409 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sl
2025-04-22 20:54:04,409 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,409 root INFO copying build/lib/django/contrib/auth/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,409 root INFO copying build/lib/django/contrib/auth/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,410 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sq
2025-04-22 20:54:04,410 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,410 root INFO copying build/lib/django/contrib/auth/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,410 root INFO copying build/lib/django/contrib/auth/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,410 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/az
2025-04-22 20:54:04,410 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/az/LC_MESSAGES
2025-04-22 20:54:04,410 root INFO copying build/lib/django/contrib/auth/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/az/LC_MESSAGES
2025-04-22 20:54:04,411 root INFO copying build/lib/django/contrib/auth/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/az/LC_MESSAGES
2025-04-22 20:54:04,411 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/eo
2025-04-22 20:54:04,411 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,411 root INFO copying build/lib/django/contrib/auth/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,411 root INFO copying build/lib/django/contrib/auth/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,411 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/pt_BR
2025-04-22 20:54:04,411 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,412 root INFO copying build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,412 root INFO copying build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,412 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/pl
2025-04-22 20:54:04,412 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,412 root INFO copying build/lib/django/contrib/auth/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,412 root INFO copying build/lib/django/contrib/auth/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,413 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/gd
2025-04-22 20:54:04,413 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,413 root INFO copying build/lib/django/contrib/auth/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,413 root INFO copying build/lib/django/contrib/auth/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,413 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hr
2025-04-22 20:54:04,413 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,413 root INFO copying build/lib/django/contrib/auth/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,413 root INFO copying build/lib/django/contrib/auth/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,414 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ru
2025-04-22 20:54:04,414 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,414 root INFO copying build/lib/django/contrib/auth/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,414 root INFO copying build/lib/django/contrib/auth/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,414 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es
2025-04-22 20:54:04,414 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es/LC_MESSAGES
2025-04-22 20:54:04,414 root INFO copying build/lib/django/contrib/auth/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es/LC_MESSAGES
2025-04-22 20:54:04,415 root INFO copying build/lib/django/contrib/auth/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es/LC_MESSAGES
2025-04-22 20:54:04,415 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/id
2025-04-22 20:54:04,415 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/id/LC_MESSAGES
2025-04-22 20:54:04,415 root INFO copying build/lib/django/contrib/auth/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/id/LC_MESSAGES
2025-04-22 20:54:04,415 root INFO copying build/lib/django/contrib/auth/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/id/LC_MESSAGES
2025-04-22 20:54:04,415 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/fi
2025-04-22 20:54:04,416 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,416 root INFO copying build/lib/django/contrib/auth/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,416 root INFO copying build/lib/django/contrib/auth/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,416 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/mk
2025-04-22 20:54:04,416 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,416 root INFO copying build/lib/django/contrib/auth/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,416 root INFO copying build/lib/django/contrib/auth/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,417 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hi
2025-04-22 20:54:04,417 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,417 root INFO copying build/lib/django/contrib/auth/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,417 root INFO copying build/lib/django/contrib/auth/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,417 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/kab
2025-04-22 20:54:04,417 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,417 root INFO copying build/lib/django/contrib/auth/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,417 root INFO copying build/lib/django/contrib/auth/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,418 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hsb
2025-04-22 20:54:04,418 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,418 root INFO copying build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,418 root INFO copying build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,418 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sk
2025-04-22 20:54:04,418 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,418 root INFO copying build/lib/django/contrib/auth/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,419 root INFO copying build/lib/django/contrib/auth/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,419 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/lt
2025-04-22 20:54:04,419 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,419 root INFO copying build/lib/django/contrib/auth/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,419 root INFO copying build/lib/django/contrib/auth/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,419 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/de
2025-04-22 20:54:04,420 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/de/LC_MESSAGES
2025-04-22 20:54:04,420 root INFO copying build/lib/django/contrib/auth/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/de/LC_MESSAGES
2025-04-22 20:54:04,420 root INFO copying build/lib/django/contrib/auth/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/de/LC_MESSAGES
2025-04-22 20:54:04,420 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/it
2025-04-22 20:54:04,420 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/it/LC_MESSAGES
2025-04-22 20:54:04,420 root INFO copying build/lib/django/contrib/auth/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/it/LC_MESSAGES
2025-04-22 20:54:04,420 root INFO copying build/lib/django/contrib/auth/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/it/LC_MESSAGES
2025-04-22 20:54:04,421 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/my
2025-04-22 20:54:04,421 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/my/LC_MESSAGES
2025-04-22 20:54:04,421 root INFO copying build/lib/django/contrib/auth/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/my/LC_MESSAGES
2025-04-22 20:54:04,421 root INFO copying build/lib/django/contrib/auth/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/my/LC_MESSAGES
2025-04-22 20:54:04,421 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sr
2025-04-22 20:54:04,421 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,421 root INFO copying build/lib/django/contrib/auth/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,421 root INFO copying build/lib/django/contrib/auth/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,422 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/bs
2025-04-22 20:54:04,422 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,422 root INFO copying build/lib/django/contrib/auth/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,422 root INFO copying build/lib/django/contrib/auth/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,422 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ro
2025-04-22 20:54:04,422 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,422 root INFO copying build/lib/django/contrib/auth/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,423 root INFO copying build/lib/django/contrib/auth/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,423 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ky
2025-04-22 20:54:04,423 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,423 root INFO copying build/lib/django/contrib/auth/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,423 root INFO copying build/lib/django/contrib/auth/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,423 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/fr
2025-04-22 20:54:04,423 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,424 root INFO copying build/lib/django/contrib/auth/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,424 root INFO copying build/lib/django/contrib/auth/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,424 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ar
2025-04-22 20:54:04,424 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,424 root INFO copying build/lib/django/contrib/auth/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,424 root INFO copying build/lib/django/contrib/auth/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,425 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hy
2025-04-22 20:54:04,425 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,425 root INFO copying build/lib/django/contrib/auth/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,425 root INFO copying build/lib/django/contrib/auth/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,425 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es_AR
2025-04-22 20:54:04,425 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,425 root INFO copying build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,426 root INFO copying build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,426 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/vi
2025-04-22 20:54:04,426 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,426 root INFO copying build/lib/django/contrib/auth/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,426 root INFO copying build/lib/django/contrib/auth/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,426 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ckb
2025-04-22 20:54:04,427 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,427 root INFO copying build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,427 root INFO copying build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,427 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sv
2025-04-22 20:54:04,427 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,427 root INFO copying build/lib/django/contrib/auth/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,427 root INFO copying build/lib/django/contrib/auth/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,428 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/zh_Hant
2025-04-22 20:54:04,428 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,428 root INFO copying build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,428 root INFO copying build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,428 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/kk
2025-04-22 20:54:04,428 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,428 root INFO copying build/lib/django/contrib/auth/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,429 root INFO copying build/lib/django/contrib/auth/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,429 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es_CO
2025-04-22 20:54:04,429 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,429 root INFO copying build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,429 root INFO copying build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,429 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/be
2025-04-22 20:54:04,429 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/be/LC_MESSAGES
2025-04-22 20:54:04,430 root INFO copying build/lib/django/contrib/auth/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/be/LC_MESSAGES
2025-04-22 20:54:04,430 root INFO copying build/lib/django/contrib/auth/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/be/LC_MESSAGES
2025-04-22 20:54:04,430 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/udm
2025-04-22 20:54:04,430 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,430 root INFO copying build/lib/django/contrib/auth/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,430 root INFO copying build/lib/django/contrib/auth/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,430 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ml
2025-04-22 20:54:04,431 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,431 root INFO copying build/lib/django/contrib/auth/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,431 root INFO copying build/lib/django/contrib/auth/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,431 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ar_DZ
2025-04-22 20:54:04,431 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,431 root INFO copying build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,432 root INFO copying build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,432 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ms
2025-04-22 20:54:04,432 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,432 root INFO copying build/lib/django/contrib/auth/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,432 root INFO copying build/lib/django/contrib/auth/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,432 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ast
2025-04-22 20:54:04,433 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,433 root INFO copying build/lib/django/contrib/auth/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,433 root INFO copying build/lib/django/contrib/auth/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,433 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/zh_Hans
2025-04-22 20:54:04,433 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,433 root INFO copying build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,433 root INFO copying build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,434 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ur
2025-04-22 20:54:04,434 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,434 root INFO copying build/lib/django/contrib/auth/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,434 root INFO copying build/lib/django/contrib/auth/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,434 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ia
2025-04-22 20:54:04,434 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,434 root INFO copying build/lib/django/contrib/auth/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,434 root INFO copying build/lib/django/contrib/auth/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,435 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hu
2025-04-22 20:54:04,435 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,435 root INFO copying build/lib/django/contrib/auth/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,435 root INFO copying build/lib/django/contrib/auth/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,435 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ta
2025-04-22 20:54:04,435 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,435 root INFO copying build/lib/django/contrib/auth/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,436 root INFO copying build/lib/django/contrib/auth/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,436 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/eu
2025-04-22 20:54:04,436 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,436 root INFO copying build/lib/django/contrib/auth/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,436 root INFO copying build/lib/django/contrib/auth/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,436 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es_MX
2025-04-22 20:54:04,436 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,437 root INFO copying build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,437 root INFO copying build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,437 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/tk
2025-04-22 20:54:04,437 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,437 root INFO copying build/lib/django/contrib/auth/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,437 root INFO copying build/lib/django/contrib/auth/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,438 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/th
2025-04-22 20:54:04,438 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/th/LC_MESSAGES
2025-04-22 20:54:04,438 root INFO copying build/lib/django/contrib/auth/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/th/LC_MESSAGES
2025-04-22 20:54:04,438 root INFO copying build/lib/django/contrib/auth/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/th/LC_MESSAGES
2025-04-22 20:54:04,438 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/nb
2025-04-22 20:54:04,438 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,438 root INFO copying build/lib/django/contrib/auth/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,439 root INFO copying build/lib/django/contrib/auth/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,439 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/mn
2025-04-22 20:54:04,439 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,439 root INFO copying build/lib/django/contrib/auth/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,439 root INFO copying build/lib/django/contrib/auth/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,439 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ka
2025-04-22 20:54:04,439 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,440 root INFO copying build/lib/django/contrib/auth/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,440 root INFO copying build/lib/django/contrib/auth/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,440 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/nl
2025-04-22 20:54:04,440 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,440 root INFO copying build/lib/django/contrib/auth/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,440 root INFO copying build/lib/django/contrib/auth/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,441 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/te
2025-04-22 20:54:04,441 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/te/LC_MESSAGES
2025-04-22 20:54:04,441 root INFO copying build/lib/django/contrib/auth/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/te/LC_MESSAGES
2025-04-22 20:54:04,441 root INFO copying build/lib/django/contrib/auth/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/te/LC_MESSAGES
2025-04-22 20:54:04,441 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/pt
2025-04-22 20:54:04,441 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,441 root INFO copying build/lib/django/contrib/auth/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,442 root INFO copying build/lib/django/contrib/auth/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,442 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/bn
2025-04-22 20:54:04,442 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,442 root INFO copying build/lib/django/contrib/auth/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,442 root INFO copying build/lib/django/contrib/auth/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,443 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/he
2025-04-22 20:54:04,443 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/he/LC_MESSAGES
2025-04-22 20:54:04,443 root INFO copying build/lib/django/contrib/auth/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/he/LC_MESSAGES
2025-04-22 20:54:04,443 root INFO copying build/lib/django/contrib/auth/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/he/LC_MESSAGES
2025-04-22 20:54:04,443 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/br
2025-04-22 20:54:04,443 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/br/LC_MESSAGES
2025-04-22 20:54:04,443 root INFO copying build/lib/django/contrib/auth/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/br/LC_MESSAGES
2025-04-22 20:54:04,444 root INFO copying build/lib/django/contrib/auth/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/br/LC_MESSAGES
2025-04-22 20:54:04,444 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/fa
2025-04-22 20:54:04,444 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,444 root INFO copying build/lib/django/contrib/auth/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,444 root INFO copying build/lib/django/contrib/auth/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,444 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/tg
2025-04-22 20:54:04,445 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,445 root INFO copying build/lib/django/contrib/auth/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,445 root INFO copying build/lib/django/contrib/auth/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,445 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/km
2025-04-22 20:54:04,445 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/km/LC_MESSAGES
2025-04-22 20:54:04,445 root INFO copying build/lib/django/contrib/auth/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/km/LC_MESSAGES
2025-04-22 20:54:04,445 root INFO copying build/lib/django/contrib/auth/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/km/LC_MESSAGES
2025-04-22 20:54:04,446 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/da
2025-04-22 20:54:04,446 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/da/LC_MESSAGES
2025-04-22 20:54:04,446 root INFO copying build/lib/django/contrib/auth/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/da/LC_MESSAGES
2025-04-22 20:54:04,446 root INFO copying build/lib/django/contrib/auth/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/auth/locale/da/LC_MESSAGES
2025-04-22 20:54:04,446 root INFO copying build/lib/django/contrib/auth/tokens.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,446 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/templates
2025-04-22 20:54:04,447 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/templates/auth
2025-04-22 20:54:04,447 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/templates/auth/widgets
2025-04-22 20:54:04,447 root INFO copying build/lib/django/contrib/auth/templates/auth/widgets/read_only_password_hash.html -> build/bdist.linux-aarch64/wheel/django/contrib/auth/templates/auth/widgets
2025-04-22 20:54:04,447 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/auth/templates/registration
2025-04-22 20:54:04,447 root INFO copying build/lib/django/contrib/auth/templates/registration/password_reset_subject.txt -> build/bdist.linux-aarch64/wheel/django/contrib/auth/templates/registration
2025-04-22 20:54:04,447 root INFO copying build/lib/django/contrib/auth/base_user.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,447 root INFO copying build/lib/django/contrib/auth/password_validation.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,447 root INFO copying build/lib/django/contrib/auth/mixins.py -> build/bdist.linux-aarch64/wheel/django/contrib/auth
2025-04-22 20:54:04,448 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes
2025-04-22 20:54:04,448 root INFO copying build/lib/django/contrib/contenttypes/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes
2025-04-22 20:54:04,448 root INFO copying build/lib/django/contrib/contenttypes/views.py -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes
2025-04-22 20:54:04,448 root INFO copying build/lib/django/contrib/contenttypes/forms.py -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes
2025-04-22 20:54:04,448 root INFO copying build/lib/django/contrib/contenttypes/models.py -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes
2025-04-22 20:54:04,448 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/migrations
2025-04-22 20:54:04,449 root INFO copying build/lib/django/contrib/contenttypes/migrations/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/migrations
2025-04-22 20:54:04,449 root INFO copying build/lib/django/contrib/contenttypes/migrations/0001_initial.py -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/migrations
2025-04-22 20:54:04,449 root INFO copying build/lib/django/contrib/contenttypes/migrations/0002_remove_content_type_name.py -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/migrations
2025-04-22 20:54:04,449 root INFO copying build/lib/django/contrib/contenttypes/apps.py -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes
2025-04-22 20:54:04,449 root INFO copying build/lib/django/contrib/contenttypes/admin.py -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes
2025-04-22 20:54:04,449 root INFO copying build/lib/django/contrib/contenttypes/checks.py -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes
2025-04-22 20:54:04,449 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/management
2025-04-22 20:54:04,450 root INFO copying build/lib/django/contrib/contenttypes/management/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/management
2025-04-22 20:54:04,450 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/management/commands
2025-04-22 20:54:04,450 root INFO copying build/lib/django/contrib/contenttypes/management/commands/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/management/commands
2025-04-22 20:54:04,450 root INFO copying build/lib/django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/management/commands
2025-04-22 20:54:04,450 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale
2025-04-22 20:54:04,450 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/lv
2025-04-22 20:54:04,450 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,451 root INFO copying build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,451 root INFO copying build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,451 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sw
2025-04-22 20:54:04,451 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,451 root INFO copying build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,451 root INFO copying build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,451 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/en_AU
2025-04-22 20:54:04,452 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,452 root INFO copying build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,452 root INFO copying build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,452 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/mr
2025-04-22 20:54:04,452 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,452 root INFO copying build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,452 root INFO copying build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,453 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/lb
2025-04-22 20:54:04,453 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,453 root INFO copying build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,453 root INFO copying build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,453 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ca
2025-04-22 20:54:04,453 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,453 root INFO copying build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,454 root INFO copying build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,454 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/en_GB
2025-04-22 20:54:04,454 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,454 root INFO copying build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,454 root INFO copying build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,454 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/el
2025-04-22 20:54:04,454 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/el/LC_MESSAGES
2025-04-22 20:54:04,454 root INFO copying build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/el/LC_MESSAGES
2025-04-22 20:54:04,455 root INFO copying build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/el/LC_MESSAGES
2025-04-22 20:54:04,455 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es_VE
2025-04-22 20:54:04,455 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,455 root INFO copying build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,455 root INFO copying build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,455 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/af
2025-04-22 20:54:04,455 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/af/LC_MESSAGES
2025-04-22 20:54:04,456 root INFO copying build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/af/LC_MESSAGES
2025-04-22 20:54:04,456 root INFO copying build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/af/LC_MESSAGES
2025-04-22 20:54:04,456 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/en
2025-04-22 20:54:04,456 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/en/LC_MESSAGES
2025-04-22 20:54:04,456 root INFO copying build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/en/LC_MESSAGES
2025-04-22 20:54:04,456 root INFO copying build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/en/LC_MESSAGES
2025-04-22 20:54:04,456 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/dsb
2025-04-22 20:54:04,457 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,457 root INFO copying build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,457 root INFO copying build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,457 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/et
2025-04-22 20:54:04,457 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/et/LC_MESSAGES
2025-04-22 20:54:04,457 root INFO copying build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/et/LC_MESSAGES
2025-04-22 20:54:04,457 root INFO copying build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/et/LC_MESSAGES
2025-04-22 20:54:04,458 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/nn
2025-04-22 20:54:04,458 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,458 root INFO copying build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,458 root INFO copying build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,458 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/cy
2025-04-22 20:54:04,458 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,458 root INFO copying build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,458 root INFO copying build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,459 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ko
2025-04-22 20:54:04,459 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,459 root INFO copying build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,459 root INFO copying build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,459 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/is
2025-04-22 20:54:04,459 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/is/LC_MESSAGES
2025-04-22 20:54:04,459 root INFO copying build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/is/LC_MESSAGES
2025-04-22 20:54:04,460 root INFO copying build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/is/LC_MESSAGES
2025-04-22 20:54:04,460 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/pa
2025-04-22 20:54:04,460 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,460 root INFO copying build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,460 root INFO copying build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,460 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/tt
2025-04-22 20:54:04,460 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,461 root INFO copying build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,461 root INFO copying build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,461 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ne
2025-04-22 20:54:04,461 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,461 root INFO copying build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,461 root INFO copying build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,461 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sr_Latn
2025-04-22 20:54:04,462 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,462 root INFO copying build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,462 root INFO copying build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,462 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/fy
2025-04-22 20:54:04,462 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,462 root INFO copying build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,463 root INFO copying build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,463 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/bg
2025-04-22 20:54:04,463 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,463 root INFO copying build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,463 root INFO copying build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,463 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ga
2025-04-22 20:54:04,463 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,464 root INFO copying build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,464 root INFO copying build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,464 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/gl
2025-04-22 20:54:04,464 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,464 root INFO copying build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,464 root INFO copying build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,464 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/uk
2025-04-22 20:54:04,465 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,465 root INFO copying build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,465 root INFO copying build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,465 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/kn
2025-04-22 20:54:04,465 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,465 root INFO copying build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,465 root INFO copying build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,466 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ja
2025-04-22 20:54:04,466 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,466 root INFO copying build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,466 root INFO copying build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,466 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/cs
2025-04-22 20:54:04,466 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,466 root INFO copying build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,466 root INFO copying build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,467 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/os
2025-04-22 20:54:04,467 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/os/LC_MESSAGES
2025-04-22 20:54:04,467 root INFO copying build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/os/LC_MESSAGES
2025-04-22 20:54:04,467 root INFO copying build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/os/LC_MESSAGES
2025-04-22 20:54:04,467 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/tr
2025-04-22 20:54:04,467 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,467 root INFO copying build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,468 root INFO copying build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,468 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/io
2025-04-22 20:54:04,468 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/io/LC_MESSAGES
2025-04-22 20:54:04,468 root INFO copying build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/io/LC_MESSAGES
2025-04-22 20:54:04,468 root INFO copying build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/io/LC_MESSAGES
2025-04-22 20:54:04,468 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sl
2025-04-22 20:54:04,468 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,469 root INFO copying build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,469 root INFO copying build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,469 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sq
2025-04-22 20:54:04,469 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,469 root INFO copying build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,469 root INFO copying build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,469 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/az
2025-04-22 20:54:04,470 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/az/LC_MESSAGES
2025-04-22 20:54:04,470 root INFO copying build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/az/LC_MESSAGES
2025-04-22 20:54:04,470 root INFO copying build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/az/LC_MESSAGES
2025-04-22 20:54:04,470 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/eo
2025-04-22 20:54:04,470 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,470 root INFO copying build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,470 root INFO copying build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,471 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/pt_BR
2025-04-22 20:54:04,471 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,471 root INFO copying build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,471 root INFO copying build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,471 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/pl
2025-04-22 20:54:04,471 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,471 root INFO copying build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,471 root INFO copying build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,472 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/gd
2025-04-22 20:54:04,472 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,472 root INFO copying build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,472 root INFO copying build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,472 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hr
2025-04-22 20:54:04,472 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,472 root INFO copying build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,473 root INFO copying build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,473 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ru
2025-04-22 20:54:04,473 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,473 root INFO copying build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,473 root INFO copying build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,473 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es
2025-04-22 20:54:04,473 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es/LC_MESSAGES
2025-04-22 20:54:04,474 root INFO copying build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es/LC_MESSAGES
2025-04-22 20:54:04,474 root INFO copying build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es/LC_MESSAGES
2025-04-22 20:54:04,474 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/id
2025-04-22 20:54:04,474 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/id/LC_MESSAGES
2025-04-22 20:54:04,474 root INFO copying build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/id/LC_MESSAGES
2025-04-22 20:54:04,474 root INFO copying build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/id/LC_MESSAGES
2025-04-22 20:54:04,474 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/fi
2025-04-22 20:54:04,475 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,475 root INFO copying build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,475 root INFO copying build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,475 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/mk
2025-04-22 20:54:04,475 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,475 root INFO copying build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,475 root INFO copying build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,476 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hi
2025-04-22 20:54:04,476 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,476 root INFO copying build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,476 root INFO copying build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,476 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hsb
2025-04-22 20:54:04,476 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,476 root INFO copying build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,477 root INFO copying build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,477 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sk
2025-04-22 20:54:04,477 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,477 root INFO copying build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,477 root INFO copying build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,477 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/lt
2025-04-22 20:54:04,477 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,478 root INFO copying build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,478 root INFO copying build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,478 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/de
2025-04-22 20:54:04,478 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/de/LC_MESSAGES
2025-04-22 20:54:04,478 root INFO copying build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/de/LC_MESSAGES
2025-04-22 20:54:04,478 root INFO copying build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/de/LC_MESSAGES
2025-04-22 20:54:04,478 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/it
2025-04-22 20:54:04,479 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/it/LC_MESSAGES
2025-04-22 20:54:04,479 root INFO copying build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/it/LC_MESSAGES
2025-04-22 20:54:04,479 root INFO copying build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/it/LC_MESSAGES
2025-04-22 20:54:04,479 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/my
2025-04-22 20:54:04,479 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/my/LC_MESSAGES
2025-04-22 20:54:04,479 root INFO copying build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/my/LC_MESSAGES
2025-04-22 20:54:04,479 root INFO copying build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/my/LC_MESSAGES
2025-04-22 20:54:04,480 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sr
2025-04-22 20:54:04,480 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,480 root INFO copying build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,480 root INFO copying build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,480 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/bs
2025-04-22 20:54:04,480 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,480 root INFO copying build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,480 root INFO copying build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,481 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ro
2025-04-22 20:54:04,481 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,481 root INFO copying build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,481 root INFO copying build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,481 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ky
2025-04-22 20:54:04,481 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,481 root INFO copying build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,482 root INFO copying build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,482 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/fr
2025-04-22 20:54:04,482 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,482 root INFO copying build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,482 root INFO copying build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,483 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ar
2025-04-22 20:54:04,483 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,483 root INFO copying build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,483 root INFO copying build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,483 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hy
2025-04-22 20:54:04,483 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,483 root INFO copying build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,484 root INFO copying build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,484 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es_AR
2025-04-22 20:54:04,484 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,484 root INFO copying build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,484 root INFO copying build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,484 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/vi
2025-04-22 20:54:04,484 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,484 root INFO copying build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,485 root INFO copying build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,485 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ckb
2025-04-22 20:54:04,485 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,485 root INFO copying build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,485 root INFO copying build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,485 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sv
2025-04-22 20:54:04,486 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,486 root INFO copying build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,486 root INFO copying build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,486 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/zh_Hant
2025-04-22 20:54:04,486 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,486 root INFO copying build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,486 root INFO copying build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,487 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/kk
2025-04-22 20:54:04,487 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,487 root INFO copying build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,487 root INFO copying build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,487 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es_CO
2025-04-22 20:54:04,487 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,487 root INFO copying build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,487 root INFO copying build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,488 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/be
2025-04-22 20:54:04,488 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/be/LC_MESSAGES
2025-04-22 20:54:04,488 root INFO copying build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/be/LC_MESSAGES
2025-04-22 20:54:04,488 root INFO copying build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/be/LC_MESSAGES
2025-04-22 20:54:04,488 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/udm
2025-04-22 20:54:04,488 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,488 root INFO copying build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,489 root INFO copying build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,489 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ml
2025-04-22 20:54:04,489 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,489 root INFO copying build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,489 root INFO copying build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,489 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ar_DZ
2025-04-22 20:54:04,489 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,490 root INFO copying build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,490 root INFO copying build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,490 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ms
2025-04-22 20:54:04,490 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,490 root INFO copying build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,490 root INFO copying build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,490 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ast
2025-04-22 20:54:04,491 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,491 root INFO copying build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,491 root INFO copying build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,491 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/zh_Hans
2025-04-22 20:54:04,491 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,491 root INFO copying build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,491 root INFO copying build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,492 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ur
2025-04-22 20:54:04,492 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,492 root INFO copying build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,492 root INFO copying build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,492 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ia
2025-04-22 20:54:04,492 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,492 root INFO copying build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,492 root INFO copying build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,493 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hu
2025-04-22 20:54:04,493 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,493 root INFO copying build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,493 root INFO copying build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,493 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ta
2025-04-22 20:54:04,493 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,493 root INFO copying build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,494 root INFO copying build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,494 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/eu
2025-04-22 20:54:04,494 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,494 root INFO copying build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,494 root INFO copying build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,494 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es_MX
2025-04-22 20:54:04,494 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,495 root INFO copying build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,495 root INFO copying build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,495 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/tk
2025-04-22 20:54:04,495 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,495 root INFO copying build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,495 root INFO copying build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,496 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/th
2025-04-22 20:54:04,496 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/th/LC_MESSAGES
2025-04-22 20:54:04,496 root INFO copying build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/th/LC_MESSAGES
2025-04-22 20:54:04,496 root INFO copying build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/th/LC_MESSAGES
2025-04-22 20:54:04,496 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/nb
2025-04-22 20:54:04,496 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,496 root INFO copying build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,496 root INFO copying build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,497 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/mn
2025-04-22 20:54:04,497 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,497 root INFO copying build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,497 root INFO copying build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,497 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ka
2025-04-22 20:54:04,497 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,497 root INFO copying build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,498 root INFO copying build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,498 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/nl
2025-04-22 20:54:04,498 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,498 root INFO copying build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,498 root INFO copying build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,498 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/te
2025-04-22 20:54:04,498 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/te/LC_MESSAGES
2025-04-22 20:54:04,499 root INFO copying build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/te/LC_MESSAGES
2025-04-22 20:54:04,499 root INFO copying build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/te/LC_MESSAGES
2025-04-22 20:54:04,499 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/pt
2025-04-22 20:54:04,499 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,499 root INFO copying build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,499 root INFO copying build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,499 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/bn
2025-04-22 20:54:04,500 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,500 root INFO copying build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,500 root INFO copying build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,500 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/he
2025-04-22 20:54:04,500 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/he/LC_MESSAGES
2025-04-22 20:54:04,500 root INFO copying build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/he/LC_MESSAGES
2025-04-22 20:54:04,500 root INFO copying build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/he/LC_MESSAGES
2025-04-22 20:54:04,501 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/br
2025-04-22 20:54:04,501 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/br/LC_MESSAGES
2025-04-22 20:54:04,501 root INFO copying build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/br/LC_MESSAGES
2025-04-22 20:54:04,501 root INFO copying build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/br/LC_MESSAGES
2025-04-22 20:54:04,501 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/fa
2025-04-22 20:54:04,501 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,501 root INFO copying build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,502 root INFO copying build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,502 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/tg
2025-04-22 20:54:04,502 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,502 root INFO copying build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,502 root INFO copying build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,502 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/km
2025-04-22 20:54:04,502 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/km/LC_MESSAGES
2025-04-22 20:54:04,503 root INFO copying build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/km/LC_MESSAGES
2025-04-22 20:54:04,503 root INFO copying build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/km/LC_MESSAGES
2025-04-22 20:54:04,503 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/da
2025-04-22 20:54:04,503 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/da/LC_MESSAGES
2025-04-22 20:54:04,503 root INFO copying build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/da/LC_MESSAGES
2025-04-22 20:54:04,503 root INFO copying build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes/locale/da/LC_MESSAGES
2025-04-22 20:54:04,503 root INFO copying build/lib/django/contrib/contenttypes/fields.py -> build/bdist.linux-aarch64/wheel/django/contrib/contenttypes
2025-04-22 20:54:04,504 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects
2025-04-22 20:54:04,504 root INFO copying build/lib/django/contrib/redirects/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/redirects
2025-04-22 20:54:04,504 root INFO copying build/lib/django/contrib/redirects/middleware.py -> build/bdist.linux-aarch64/wheel/django/contrib/redirects
2025-04-22 20:54:04,504 root INFO copying build/lib/django/contrib/redirects/models.py -> build/bdist.linux-aarch64/wheel/django/contrib/redirects
2025-04-22 20:54:04,504 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/migrations
2025-04-22 20:54:04,504 root INFO copying build/lib/django/contrib/redirects/migrations/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/migrations
2025-04-22 20:54:04,504 root INFO copying build/lib/django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/migrations
2025-04-22 20:54:04,505 root INFO copying build/lib/django/contrib/redirects/migrations/0001_initial.py -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/migrations
2025-04-22 20:54:04,505 root INFO copying build/lib/django/contrib/redirects/apps.py -> build/bdist.linux-aarch64/wheel/django/contrib/redirects
2025-04-22 20:54:04,505 root INFO copying build/lib/django/contrib/redirects/admin.py -> build/bdist.linux-aarch64/wheel/django/contrib/redirects
2025-04-22 20:54:04,505 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale
2025-04-22 20:54:04,505 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/lv
2025-04-22 20:54:04,506 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,506 root INFO copying build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,506 root INFO copying build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,506 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sw
2025-04-22 20:54:04,506 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,506 root INFO copying build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,506 root INFO copying build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,506 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/en_AU
2025-04-22 20:54:04,507 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,507 root INFO copying build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,507 root INFO copying build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,507 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/mr
2025-04-22 20:54:04,507 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,507 root INFO copying build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,507 root INFO copying build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,508 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/lb
2025-04-22 20:54:04,508 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,508 root INFO copying build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,508 root INFO copying build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,508 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ca
2025-04-22 20:54:04,508 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,508 root INFO copying build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,509 root INFO copying build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,509 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/en_GB
2025-04-22 20:54:04,509 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,509 root INFO copying build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,509 root INFO copying build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,509 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/el
2025-04-22 20:54:04,509 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/el/LC_MESSAGES
2025-04-22 20:54:04,509 root INFO copying build/lib/django/contrib/redirects/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/el/LC_MESSAGES
2025-04-22 20:54:04,510 root INFO copying build/lib/django/contrib/redirects/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/el/LC_MESSAGES
2025-04-22 20:54:04,510 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es_VE
2025-04-22 20:54:04,510 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,510 root INFO copying build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,510 root INFO copying build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,510 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/af
2025-04-22 20:54:04,510 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/af/LC_MESSAGES
2025-04-22 20:54:04,511 root INFO copying build/lib/django/contrib/redirects/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/af/LC_MESSAGES
2025-04-22 20:54:04,511 root INFO copying build/lib/django/contrib/redirects/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/af/LC_MESSAGES
2025-04-22 20:54:04,511 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/en
2025-04-22 20:54:04,511 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/en/LC_MESSAGES
2025-04-22 20:54:04,511 root INFO copying build/lib/django/contrib/redirects/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/en/LC_MESSAGES
2025-04-22 20:54:04,511 root INFO copying build/lib/django/contrib/redirects/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/en/LC_MESSAGES
2025-04-22 20:54:04,511 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/dsb
2025-04-22 20:54:04,512 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,512 root INFO copying build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,512 root INFO copying build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,512 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/et
2025-04-22 20:54:04,512 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/et/LC_MESSAGES
2025-04-22 20:54:04,512 root INFO copying build/lib/django/contrib/redirects/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/et/LC_MESSAGES
2025-04-22 20:54:04,512 root INFO copying build/lib/django/contrib/redirects/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/et/LC_MESSAGES
2025-04-22 20:54:04,513 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/nn
2025-04-22 20:54:04,513 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,513 root INFO copying build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,513 root INFO copying build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,513 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/cy
2025-04-22 20:54:04,513 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,513 root INFO copying build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,513 root INFO copying build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,514 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ko
2025-04-22 20:54:04,514 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,514 root INFO copying build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,514 root INFO copying build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,514 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/is
2025-04-22 20:54:04,514 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/is/LC_MESSAGES
2025-04-22 20:54:04,514 root INFO copying build/lib/django/contrib/redirects/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/is/LC_MESSAGES
2025-04-22 20:54:04,515 root INFO copying build/lib/django/contrib/redirects/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/is/LC_MESSAGES
2025-04-22 20:54:04,515 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/pa
2025-04-22 20:54:04,515 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,515 root INFO copying build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,515 root INFO copying build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,515 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/tt
2025-04-22 20:54:04,515 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,516 root INFO copying build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,516 root INFO copying build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,516 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ne
2025-04-22 20:54:04,516 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,516 root INFO copying build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,516 root INFO copying build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,516 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sr_Latn
2025-04-22 20:54:04,517 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,517 root INFO copying build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,517 root INFO copying build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,517 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/fy
2025-04-22 20:54:04,517 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,517 root INFO copying build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,517 root INFO copying build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,518 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/bg
2025-04-22 20:54:04,518 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,518 root INFO copying build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,518 root INFO copying build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,518 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ga
2025-04-22 20:54:04,518 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,518 root INFO copying build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,519 root INFO copying build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,519 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/gl
2025-04-22 20:54:04,519 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,519 root INFO copying build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,519 root INFO copying build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,519 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/uk
2025-04-22 20:54:04,519 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,520 root INFO copying build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,520 root INFO copying build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,520 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/uz
2025-04-22 20:54:04,520 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,520 root INFO copying build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,520 root INFO copying build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,520 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/kn
2025-04-22 20:54:04,521 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,521 root INFO copying build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,521 root INFO copying build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,521 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ja
2025-04-22 20:54:04,521 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,521 root INFO copying build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,521 root INFO copying build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,521 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/cs
2025-04-22 20:54:04,522 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,522 root INFO copying build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,522 root INFO copying build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,522 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/os
2025-04-22 20:54:04,522 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/os/LC_MESSAGES
2025-04-22 20:54:04,522 root INFO copying build/lib/django/contrib/redirects/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/os/LC_MESSAGES
2025-04-22 20:54:04,522 root INFO copying build/lib/django/contrib/redirects/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/os/LC_MESSAGES
2025-04-22 20:54:04,523 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/tr
2025-04-22 20:54:04,523 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,523 root INFO copying build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,523 root INFO copying build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,523 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/io
2025-04-22 20:54:04,523 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/io/LC_MESSAGES
2025-04-22 20:54:04,523 root INFO copying build/lib/django/contrib/redirects/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/io/LC_MESSAGES
2025-04-22 20:54:04,524 root INFO copying build/lib/django/contrib/redirects/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/io/LC_MESSAGES
2025-04-22 20:54:04,524 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sl
2025-04-22 20:54:04,524 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,524 root INFO copying build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,524 root INFO copying build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,524 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sq
2025-04-22 20:54:04,524 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,524 root INFO copying build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,525 root INFO copying build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,525 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/az
2025-04-22 20:54:04,525 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/az/LC_MESSAGES
2025-04-22 20:54:04,525 root INFO copying build/lib/django/contrib/redirects/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/az/LC_MESSAGES
2025-04-22 20:54:04,525 root INFO copying build/lib/django/contrib/redirects/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/az/LC_MESSAGES
2025-04-22 20:54:04,525 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/eo
2025-04-22 20:54:04,526 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,526 root INFO copying build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,526 root INFO copying build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,526 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/pt_BR
2025-04-22 20:54:04,526 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,526 root INFO copying build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,526 root INFO copying build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,527 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/pl
2025-04-22 20:54:04,527 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,527 root INFO copying build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,527 root INFO copying build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,527 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/gd
2025-04-22 20:54:04,527 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,527 root INFO copying build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,527 root INFO copying build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,528 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hr
2025-04-22 20:54:04,528 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,528 root INFO copying build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,528 root INFO copying build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,528 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ru
2025-04-22 20:54:04,528 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,528 root INFO copying build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,529 root INFO copying build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,529 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es
2025-04-22 20:54:04,529 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es/LC_MESSAGES
2025-04-22 20:54:04,529 root INFO copying build/lib/django/contrib/redirects/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es/LC_MESSAGES
2025-04-22 20:54:04,529 root INFO copying build/lib/django/contrib/redirects/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es/LC_MESSAGES
2025-04-22 20:54:04,529 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/id
2025-04-22 20:54:04,529 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/id/LC_MESSAGES
2025-04-22 20:54:04,530 root INFO copying build/lib/django/contrib/redirects/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/id/LC_MESSAGES
2025-04-22 20:54:04,530 root INFO copying build/lib/django/contrib/redirects/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/id/LC_MESSAGES
2025-04-22 20:54:04,530 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/fi
2025-04-22 20:54:04,530 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,530 root INFO copying build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,530 root INFO copying build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,530 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/mk
2025-04-22 20:54:04,530 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,531 root INFO copying build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,531 root INFO copying build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,531 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hi
2025-04-22 20:54:04,531 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,531 root INFO copying build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,531 root INFO copying build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,531 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/kab
2025-04-22 20:54:04,532 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,532 root INFO copying build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,532 root INFO copying build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,532 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hsb
2025-04-22 20:54:04,532 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,532 root INFO copying build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,533 root INFO copying build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,533 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sk
2025-04-22 20:54:04,533 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,533 root INFO copying build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,533 root INFO copying build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,533 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/lt
2025-04-22 20:54:04,533 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,533 root INFO copying build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,534 root INFO copying build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,534 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/de
2025-04-22 20:54:04,534 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/de/LC_MESSAGES
2025-04-22 20:54:04,534 root INFO copying build/lib/django/contrib/redirects/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/de/LC_MESSAGES
2025-04-22 20:54:04,534 root INFO copying build/lib/django/contrib/redirects/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/de/LC_MESSAGES
2025-04-22 20:54:04,534 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/it
2025-04-22 20:54:04,534 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/it/LC_MESSAGES
2025-04-22 20:54:04,535 root INFO copying build/lib/django/contrib/redirects/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/it/LC_MESSAGES
2025-04-22 20:54:04,535 root INFO copying build/lib/django/contrib/redirects/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/it/LC_MESSAGES
2025-04-22 20:54:04,535 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/my
2025-04-22 20:54:04,535 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/my/LC_MESSAGES
2025-04-22 20:54:04,535 root INFO copying build/lib/django/contrib/redirects/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/my/LC_MESSAGES
2025-04-22 20:54:04,535 root INFO copying build/lib/django/contrib/redirects/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/my/LC_MESSAGES
2025-04-22 20:54:04,535 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sr
2025-04-22 20:54:04,536 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,536 root INFO copying build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,536 root INFO copying build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,536 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/bs
2025-04-22 20:54:04,536 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,536 root INFO copying build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,536 root INFO copying build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,536 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ro
2025-04-22 20:54:04,537 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,537 root INFO copying build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,537 root INFO copying build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,537 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ky
2025-04-22 20:54:04,537 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,537 root INFO copying build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,537 root INFO copying build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,538 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/fr
2025-04-22 20:54:04,538 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,538 root INFO copying build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,538 root INFO copying build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,538 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ar
2025-04-22 20:54:04,538 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,538 root INFO copying build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,538 root INFO copying build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,539 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hy
2025-04-22 20:54:04,539 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,539 root INFO copying build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,539 root INFO copying build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,539 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es_AR
2025-04-22 20:54:04,539 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,539 root INFO copying build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,540 root INFO copying build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,540 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/vi
2025-04-22 20:54:04,540 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,540 root INFO copying build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,540 root INFO copying build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,540 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ckb
2025-04-22 20:54:04,540 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,541 root INFO copying build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,541 root INFO copying build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,541 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sv
2025-04-22 20:54:04,541 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,541 root INFO copying build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,541 root INFO copying build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,541 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/zh_Hant
2025-04-22 20:54:04,542 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,542 root INFO copying build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,542 root INFO copying build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,542 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/kk
2025-04-22 20:54:04,542 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,542 root INFO copying build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,542 root INFO copying build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,543 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es_CO
2025-04-22 20:54:04,543 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,543 root INFO copying build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,543 root INFO copying build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,543 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/be
2025-04-22 20:54:04,543 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/be/LC_MESSAGES
2025-04-22 20:54:04,543 root INFO copying build/lib/django/contrib/redirects/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/be/LC_MESSAGES
2025-04-22 20:54:04,543 root INFO copying build/lib/django/contrib/redirects/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/be/LC_MESSAGES
2025-04-22 20:54:04,544 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/udm
2025-04-22 20:54:04,544 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,544 root INFO copying build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,544 root INFO copying build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,544 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ml
2025-04-22 20:54:04,544 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,544 root INFO copying build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,545 root INFO copying build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,545 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ar_DZ
2025-04-22 20:54:04,545 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,545 root INFO copying build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,545 root INFO copying build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,545 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ms
2025-04-22 20:54:04,545 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,545 root INFO copying build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,546 root INFO copying build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,546 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ast
2025-04-22 20:54:04,546 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,546 root INFO copying build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,546 root INFO copying build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,546 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/zh_Hans
2025-04-22 20:54:04,546 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,547 root INFO copying build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,547 root INFO copying build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,547 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ur
2025-04-22 20:54:04,547 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,547 root INFO copying build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,547 root INFO copying build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,547 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ia
2025-04-22 20:54:04,548 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,548 root INFO copying build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,548 root INFO copying build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,548 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hu
2025-04-22 20:54:04,548 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,548 root INFO copying build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,548 root INFO copying build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,549 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ta
2025-04-22 20:54:04,549 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,549 root INFO copying build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,549 root INFO copying build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,549 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/eu
2025-04-22 20:54:04,549 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,549 root INFO copying build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,549 root INFO copying build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,550 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es_MX
2025-04-22 20:54:04,550 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,550 root INFO copying build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,550 root INFO copying build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,550 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/tk
2025-04-22 20:54:04,550 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,550 root INFO copying build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,551 root INFO copying build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,551 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/th
2025-04-22 20:54:04,551 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/th/LC_MESSAGES
2025-04-22 20:54:04,551 root INFO copying build/lib/django/contrib/redirects/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/th/LC_MESSAGES
2025-04-22 20:54:04,551 root INFO copying build/lib/django/contrib/redirects/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/th/LC_MESSAGES
2025-04-22 20:54:04,551 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/nb
2025-04-22 20:54:04,551 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,551 root INFO copying build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,552 root INFO copying build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,552 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/mn
2025-04-22 20:54:04,552 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,552 root INFO copying build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,552 root INFO copying build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,552 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ka
2025-04-22 20:54:04,552 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,553 root INFO copying build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,553 root INFO copying build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,553 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/nl
2025-04-22 20:54:04,553 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,553 root INFO copying build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,553 root INFO copying build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,553 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/te
2025-04-22 20:54:04,554 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/te/LC_MESSAGES
2025-04-22 20:54:04,554 root INFO copying build/lib/django/contrib/redirects/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/te/LC_MESSAGES
2025-04-22 20:54:04,554 root INFO copying build/lib/django/contrib/redirects/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/te/LC_MESSAGES
2025-04-22 20:54:04,554 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/pt
2025-04-22 20:54:04,554 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,554 root INFO copying build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,554 root INFO copying build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,554 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/bn
2025-04-22 20:54:04,555 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,555 root INFO copying build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,555 root INFO copying build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,555 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/he
2025-04-22 20:54:04,555 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/he/LC_MESSAGES
2025-04-22 20:54:04,555 root INFO copying build/lib/django/contrib/redirects/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/he/LC_MESSAGES
2025-04-22 20:54:04,555 root INFO copying build/lib/django/contrib/redirects/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/he/LC_MESSAGES
2025-04-22 20:54:04,556 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/br
2025-04-22 20:54:04,556 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/br/LC_MESSAGES
2025-04-22 20:54:04,556 root INFO copying build/lib/django/contrib/redirects/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/br/LC_MESSAGES
2025-04-22 20:54:04,556 root INFO copying build/lib/django/contrib/redirects/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/br/LC_MESSAGES
2025-04-22 20:54:04,556 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/fa
2025-04-22 20:54:04,556 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,556 root INFO copying build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,557 root INFO copying build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,557 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/tg
2025-04-22 20:54:04,557 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,557 root INFO copying build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,557 root INFO copying build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,557 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/km
2025-04-22 20:54:04,557 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/km/LC_MESSAGES
2025-04-22 20:54:04,557 root INFO copying build/lib/django/contrib/redirects/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/km/LC_MESSAGES
2025-04-22 20:54:04,558 root INFO copying build/lib/django/contrib/redirects/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/km/LC_MESSAGES
2025-04-22 20:54:04,558 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/da
2025-04-22 20:54:04,558 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/da/LC_MESSAGES
2025-04-22 20:54:04,558 root INFO copying build/lib/django/contrib/redirects/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/da/LC_MESSAGES
2025-04-22 20:54:04,558 root INFO copying build/lib/django/contrib/redirects/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/redirects/locale/da/LC_MESSAGES
2025-04-22 20:54:04,559 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/messages
2025-04-22 20:54:04,559 root INFO copying build/lib/django/contrib/messages/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/messages
2025-04-22 20:54:04,559 root INFO copying build/lib/django/contrib/messages/middleware.py -> build/bdist.linux-aarch64/wheel/django/contrib/messages
2025-04-22 20:54:04,559 root INFO copying build/lib/django/contrib/messages/views.py -> build/bdist.linux-aarch64/wheel/django/contrib/messages
2025-04-22 20:54:04,559 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/messages/storage
2025-04-22 20:54:04,559 root INFO copying build/lib/django/contrib/messages/storage/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/messages/storage
2025-04-22 20:54:04,559 root INFO copying build/lib/django/contrib/messages/storage/session.py -> build/bdist.linux-aarch64/wheel/django/contrib/messages/storage
2025-04-22 20:54:04,560 root INFO copying build/lib/django/contrib/messages/storage/cookie.py -> build/bdist.linux-aarch64/wheel/django/contrib/messages/storage
2025-04-22 20:54:04,560 root INFO copying build/lib/django/contrib/messages/storage/fallback.py -> build/bdist.linux-aarch64/wheel/django/contrib/messages/storage
2025-04-22 20:54:04,560 root INFO copying build/lib/django/contrib/messages/storage/base.py -> build/bdist.linux-aarch64/wheel/django/contrib/messages/storage
2025-04-22 20:54:04,560 root INFO copying build/lib/django/contrib/messages/apps.py -> build/bdist.linux-aarch64/wheel/django/contrib/messages
2025-04-22 20:54:04,560 root INFO copying build/lib/django/contrib/messages/utils.py -> build/bdist.linux-aarch64/wheel/django/contrib/messages
2025-04-22 20:54:04,560 root INFO copying build/lib/django/contrib/messages/api.py -> build/bdist.linux-aarch64/wheel/django/contrib/messages
2025-04-22 20:54:04,560 root INFO copying build/lib/django/contrib/messages/context_processors.py -> build/bdist.linux-aarch64/wheel/django/contrib/messages
2025-04-22 20:54:04,560 root INFO copying build/lib/django/contrib/messages/constants.py -> build/bdist.linux-aarch64/wheel/django/contrib/messages
2025-04-22 20:54:04,561 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites
2025-04-22 20:54:04,561 root INFO copying build/lib/django/contrib/sites/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/sites
2025-04-22 20:54:04,561 root INFO copying build/lib/django/contrib/sites/managers.py -> build/bdist.linux-aarch64/wheel/django/contrib/sites
2025-04-22 20:54:04,561 root INFO copying build/lib/django/contrib/sites/middleware.py -> build/bdist.linux-aarch64/wheel/django/contrib/sites
2025-04-22 20:54:04,561 root INFO copying build/lib/django/contrib/sites/models.py -> build/bdist.linux-aarch64/wheel/django/contrib/sites
2025-04-22 20:54:04,561 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/migrations
2025-04-22 20:54:04,562 root INFO copying build/lib/django/contrib/sites/migrations/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/sites/migrations
2025-04-22 20:54:04,562 root INFO copying build/lib/django/contrib/sites/migrations/0001_initial.py -> build/bdist.linux-aarch64/wheel/django/contrib/sites/migrations
2025-04-22 20:54:04,562 root INFO copying build/lib/django/contrib/sites/migrations/0002_alter_domain_unique.py -> build/bdist.linux-aarch64/wheel/django/contrib/sites/migrations
2025-04-22 20:54:04,562 root INFO copying build/lib/django/contrib/sites/apps.py -> build/bdist.linux-aarch64/wheel/django/contrib/sites
2025-04-22 20:54:04,562 root INFO copying build/lib/django/contrib/sites/admin.py -> build/bdist.linux-aarch64/wheel/django/contrib/sites
2025-04-22 20:54:04,562 root INFO copying build/lib/django/contrib/sites/checks.py -> build/bdist.linux-aarch64/wheel/django/contrib/sites
2025-04-22 20:54:04,562 root INFO copying build/lib/django/contrib/sites/management.py -> build/bdist.linux-aarch64/wheel/django/contrib/sites
2025-04-22 20:54:04,562 root INFO copying build/lib/django/contrib/sites/requests.py -> build/bdist.linux-aarch64/wheel/django/contrib/sites
2025-04-22 20:54:04,563 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale
2025-04-22 20:54:04,563 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/lv
2025-04-22 20:54:04,563 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,563 root INFO copying build/lib/django/contrib/sites/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,563 root INFO copying build/lib/django/contrib/sites/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,563 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sw
2025-04-22 20:54:04,563 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,564 root INFO copying build/lib/django/contrib/sites/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,564 root INFO copying build/lib/django/contrib/sites/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,564 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/en_AU
2025-04-22 20:54:04,564 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,564 root INFO copying build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,564 root INFO copying build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,564 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/mr
2025-04-22 20:54:04,565 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,565 root INFO copying build/lib/django/contrib/sites/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,565 root INFO copying build/lib/django/contrib/sites/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,565 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/lb
2025-04-22 20:54:04,565 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,565 root INFO copying build/lib/django/contrib/sites/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,565 root INFO copying build/lib/django/contrib/sites/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,566 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ca
2025-04-22 20:54:04,566 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,566 root INFO copying build/lib/django/contrib/sites/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,566 root INFO copying build/lib/django/contrib/sites/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,566 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/en_GB
2025-04-22 20:54:04,566 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,566 root INFO copying build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,566 root INFO copying build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,567 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/el
2025-04-22 20:54:04,567 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/el/LC_MESSAGES
2025-04-22 20:54:04,567 root INFO copying build/lib/django/contrib/sites/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/el/LC_MESSAGES
2025-04-22 20:54:04,567 root INFO copying build/lib/django/contrib/sites/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/el/LC_MESSAGES
2025-04-22 20:54:04,567 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es_VE
2025-04-22 20:54:04,567 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,567 root INFO copying build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,567 root INFO copying build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,568 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/af
2025-04-22 20:54:04,568 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/af/LC_MESSAGES
2025-04-22 20:54:04,568 root INFO copying build/lib/django/contrib/sites/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/af/LC_MESSAGES
2025-04-22 20:54:04,568 root INFO copying build/lib/django/contrib/sites/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/af/LC_MESSAGES
2025-04-22 20:54:04,568 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/en
2025-04-22 20:54:04,568 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/en/LC_MESSAGES
2025-04-22 20:54:04,568 root INFO copying build/lib/django/contrib/sites/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/en/LC_MESSAGES
2025-04-22 20:54:04,569 root INFO copying build/lib/django/contrib/sites/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/en/LC_MESSAGES
2025-04-22 20:54:04,569 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/dsb
2025-04-22 20:54:04,569 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,569 root INFO copying build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,569 root INFO copying build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,569 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/et
2025-04-22 20:54:04,569 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/et/LC_MESSAGES
2025-04-22 20:54:04,570 root INFO copying build/lib/django/contrib/sites/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/et/LC_MESSAGES
2025-04-22 20:54:04,570 root INFO copying build/lib/django/contrib/sites/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/et/LC_MESSAGES
2025-04-22 20:54:04,570 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/nn
2025-04-22 20:54:04,570 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,570 root INFO copying build/lib/django/contrib/sites/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,570 root INFO copying build/lib/django/contrib/sites/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,570 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/cy
2025-04-22 20:54:04,571 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,571 root INFO copying build/lib/django/contrib/sites/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,571 root INFO copying build/lib/django/contrib/sites/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,571 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ko
2025-04-22 20:54:04,571 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,571 root INFO copying build/lib/django/contrib/sites/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,571 root INFO copying build/lib/django/contrib/sites/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,572 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/is
2025-04-22 20:54:04,572 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/is/LC_MESSAGES
2025-04-22 20:54:04,572 root INFO copying build/lib/django/contrib/sites/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/is/LC_MESSAGES
2025-04-22 20:54:04,572 root INFO copying build/lib/django/contrib/sites/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/is/LC_MESSAGES
2025-04-22 20:54:04,572 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/pa
2025-04-22 20:54:04,572 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,572 root INFO copying build/lib/django/contrib/sites/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,572 root INFO copying build/lib/django/contrib/sites/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,573 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/tt
2025-04-22 20:54:04,573 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,573 root INFO copying build/lib/django/contrib/sites/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,573 root INFO copying build/lib/django/contrib/sites/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,573 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ne
2025-04-22 20:54:04,573 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,573 root INFO copying build/lib/django/contrib/sites/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,574 root INFO copying build/lib/django/contrib/sites/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,574 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sr_Latn
2025-04-22 20:54:04,574 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,574 root INFO copying build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,574 root INFO copying build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,574 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/fy
2025-04-22 20:54:04,574 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,575 root INFO copying build/lib/django/contrib/sites/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,575 root INFO copying build/lib/django/contrib/sites/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,575 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/bg
2025-04-22 20:54:04,575 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,575 root INFO copying build/lib/django/contrib/sites/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,575 root INFO copying build/lib/django/contrib/sites/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,575 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ga
2025-04-22 20:54:04,576 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,576 root INFO copying build/lib/django/contrib/sites/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,576 root INFO copying build/lib/django/contrib/sites/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,576 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/gl
2025-04-22 20:54:04,576 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,576 root INFO copying build/lib/django/contrib/sites/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,576 root INFO copying build/lib/django/contrib/sites/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,577 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/uk
2025-04-22 20:54:04,577 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,577 root INFO copying build/lib/django/contrib/sites/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,577 root INFO copying build/lib/django/contrib/sites/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,577 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/uz
2025-04-22 20:54:04,577 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,577 root INFO copying build/lib/django/contrib/sites/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,577 root INFO copying build/lib/django/contrib/sites/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,578 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/kn
2025-04-22 20:54:04,578 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,578 root INFO copying build/lib/django/contrib/sites/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,578 root INFO copying build/lib/django/contrib/sites/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,578 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ja
2025-04-22 20:54:04,578 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,578 root INFO copying build/lib/django/contrib/sites/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,579 root INFO copying build/lib/django/contrib/sites/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,579 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/cs
2025-04-22 20:54:04,579 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,579 root INFO copying build/lib/django/contrib/sites/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,579 root INFO copying build/lib/django/contrib/sites/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,579 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/os
2025-04-22 20:54:04,579 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/os/LC_MESSAGES
2025-04-22 20:54:04,580 root INFO copying build/lib/django/contrib/sites/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/os/LC_MESSAGES
2025-04-22 20:54:04,580 root INFO copying build/lib/django/contrib/sites/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/os/LC_MESSAGES
2025-04-22 20:54:04,580 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/tr
2025-04-22 20:54:04,580 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,580 root INFO copying build/lib/django/contrib/sites/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,580 root INFO copying build/lib/django/contrib/sites/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,580 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/io
2025-04-22 20:54:04,581 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/io/LC_MESSAGES
2025-04-22 20:54:04,581 root INFO copying build/lib/django/contrib/sites/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/io/LC_MESSAGES
2025-04-22 20:54:04,581 root INFO copying build/lib/django/contrib/sites/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/io/LC_MESSAGES
2025-04-22 20:54:04,581 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sl
2025-04-22 20:54:04,581 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,581 root INFO copying build/lib/django/contrib/sites/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,581 root INFO copying build/lib/django/contrib/sites/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,582 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sq
2025-04-22 20:54:04,582 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,582 root INFO copying build/lib/django/contrib/sites/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,582 root INFO copying build/lib/django/contrib/sites/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,582 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/az
2025-04-22 20:54:04,582 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/az/LC_MESSAGES
2025-04-22 20:54:04,582 root INFO copying build/lib/django/contrib/sites/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/az/LC_MESSAGES
2025-04-22 20:54:04,583 root INFO copying build/lib/django/contrib/sites/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/az/LC_MESSAGES
2025-04-22 20:54:04,583 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/eo
2025-04-22 20:54:04,583 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,583 root INFO copying build/lib/django/contrib/sites/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,583 root INFO copying build/lib/django/contrib/sites/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,583 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/pt_BR
2025-04-22 20:54:04,583 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,583 root INFO copying build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,584 root INFO copying build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,584 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/pl
2025-04-22 20:54:04,584 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,584 root INFO copying build/lib/django/contrib/sites/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,584 root INFO copying build/lib/django/contrib/sites/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,584 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/gd
2025-04-22 20:54:04,584 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,585 root INFO copying build/lib/django/contrib/sites/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,585 root INFO copying build/lib/django/contrib/sites/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,585 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hr
2025-04-22 20:54:04,585 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,585 root INFO copying build/lib/django/contrib/sites/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,585 root INFO copying build/lib/django/contrib/sites/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,586 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ru
2025-04-22 20:54:04,586 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,586 root INFO copying build/lib/django/contrib/sites/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,586 root INFO copying build/lib/django/contrib/sites/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,586 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es
2025-04-22 20:54:04,586 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es/LC_MESSAGES
2025-04-22 20:54:04,586 root INFO copying build/lib/django/contrib/sites/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es/LC_MESSAGES
2025-04-22 20:54:04,587 root INFO copying build/lib/django/contrib/sites/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es/LC_MESSAGES
2025-04-22 20:54:04,587 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/id
2025-04-22 20:54:04,587 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/id/LC_MESSAGES
2025-04-22 20:54:04,587 root INFO copying build/lib/django/contrib/sites/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/id/LC_MESSAGES
2025-04-22 20:54:04,587 root INFO copying build/lib/django/contrib/sites/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/id/LC_MESSAGES
2025-04-22 20:54:04,587 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/fi
2025-04-22 20:54:04,587 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,587 root INFO copying build/lib/django/contrib/sites/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,588 root INFO copying build/lib/django/contrib/sites/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,588 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/mk
2025-04-22 20:54:04,588 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,588 root INFO copying build/lib/django/contrib/sites/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,588 root INFO copying build/lib/django/contrib/sites/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,588 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hi
2025-04-22 20:54:04,589 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,589 root INFO copying build/lib/django/contrib/sites/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,589 root INFO copying build/lib/django/contrib/sites/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,589 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/kab
2025-04-22 20:54:04,589 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,589 root INFO copying build/lib/django/contrib/sites/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,589 root INFO copying build/lib/django/contrib/sites/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,590 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hsb
2025-04-22 20:54:04,590 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,590 root INFO copying build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,590 root INFO copying build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,590 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sk
2025-04-22 20:54:04,590 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,590 root INFO copying build/lib/django/contrib/sites/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,590 root INFO copying build/lib/django/contrib/sites/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,591 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/lt
2025-04-22 20:54:04,591 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,591 root INFO copying build/lib/django/contrib/sites/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,591 root INFO copying build/lib/django/contrib/sites/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,591 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/de
2025-04-22 20:54:04,591 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/de/LC_MESSAGES
2025-04-22 20:54:04,591 root INFO copying build/lib/django/contrib/sites/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/de/LC_MESSAGES
2025-04-22 20:54:04,592 root INFO copying build/lib/django/contrib/sites/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/de/LC_MESSAGES
2025-04-22 20:54:04,592 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/it
2025-04-22 20:54:04,592 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/it/LC_MESSAGES
2025-04-22 20:54:04,592 root INFO copying build/lib/django/contrib/sites/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/it/LC_MESSAGES
2025-04-22 20:54:04,592 root INFO copying build/lib/django/contrib/sites/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/it/LC_MESSAGES
2025-04-22 20:54:04,592 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/my
2025-04-22 20:54:04,592 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/my/LC_MESSAGES
2025-04-22 20:54:04,592 root INFO copying build/lib/django/contrib/sites/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/my/LC_MESSAGES
2025-04-22 20:54:04,593 root INFO copying build/lib/django/contrib/sites/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/my/LC_MESSAGES
2025-04-22 20:54:04,593 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sr
2025-04-22 20:54:04,593 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,593 root INFO copying build/lib/django/contrib/sites/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,593 root INFO copying build/lib/django/contrib/sites/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,593 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/bs
2025-04-22 20:54:04,593 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,594 root INFO copying build/lib/django/contrib/sites/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,594 root INFO copying build/lib/django/contrib/sites/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,594 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ro
2025-04-22 20:54:04,594 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,594 root INFO copying build/lib/django/contrib/sites/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,594 root INFO copying build/lib/django/contrib/sites/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,594 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ky
2025-04-22 20:54:04,595 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,595 root INFO copying build/lib/django/contrib/sites/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,595 root INFO copying build/lib/django/contrib/sites/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,595 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/fr
2025-04-22 20:54:04,595 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,595 root INFO copying build/lib/django/contrib/sites/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,595 root INFO copying build/lib/django/contrib/sites/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,596 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ar
2025-04-22 20:54:04,596 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,596 root INFO copying build/lib/django/contrib/sites/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,596 root INFO copying build/lib/django/contrib/sites/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,596 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hy
2025-04-22 20:54:04,596 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,596 root INFO copying build/lib/django/contrib/sites/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,597 root INFO copying build/lib/django/contrib/sites/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,597 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es_AR
2025-04-22 20:54:04,597 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,597 root INFO copying build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,597 root INFO copying build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,597 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/vi
2025-04-22 20:54:04,597 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,598 root INFO copying build/lib/django/contrib/sites/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,598 root INFO copying build/lib/django/contrib/sites/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,598 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ckb
2025-04-22 20:54:04,598 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,598 root INFO copying build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,598 root INFO copying build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,598 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sv
2025-04-22 20:54:04,599 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,599 root INFO copying build/lib/django/contrib/sites/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,599 root INFO copying build/lib/django/contrib/sites/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,599 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/zh_Hant
2025-04-22 20:54:04,599 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,599 root INFO copying build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,599 root INFO copying build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,600 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/kk
2025-04-22 20:54:04,600 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,600 root INFO copying build/lib/django/contrib/sites/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,600 root INFO copying build/lib/django/contrib/sites/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,600 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es_CO
2025-04-22 20:54:04,600 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,600 root INFO copying build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,600 root INFO copying build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,601 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/be
2025-04-22 20:54:04,601 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/be/LC_MESSAGES
2025-04-22 20:54:04,601 root INFO copying build/lib/django/contrib/sites/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/be/LC_MESSAGES
2025-04-22 20:54:04,601 root INFO copying build/lib/django/contrib/sites/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/be/LC_MESSAGES
2025-04-22 20:54:04,601 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/udm
2025-04-22 20:54:04,601 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,601 root INFO copying build/lib/django/contrib/sites/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,602 root INFO copying build/lib/django/contrib/sites/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,602 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ml
2025-04-22 20:54:04,602 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,602 root INFO copying build/lib/django/contrib/sites/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,602 root INFO copying build/lib/django/contrib/sites/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,602 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ar_DZ
2025-04-22 20:54:04,602 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,603 root INFO copying build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,603 root INFO copying build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,603 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ms
2025-04-22 20:54:04,603 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,603 root INFO copying build/lib/django/contrib/sites/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,603 root INFO copying build/lib/django/contrib/sites/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,603 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ast
2025-04-22 20:54:04,604 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,604 root INFO copying build/lib/django/contrib/sites/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,604 root INFO copying build/lib/django/contrib/sites/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,604 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/zh_Hans
2025-04-22 20:54:04,604 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,604 root INFO copying build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,604 root INFO copying build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,605 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ur
2025-04-22 20:54:04,605 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,605 root INFO copying build/lib/django/contrib/sites/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,605 root INFO copying build/lib/django/contrib/sites/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,605 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ia
2025-04-22 20:54:04,605 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,605 root INFO copying build/lib/django/contrib/sites/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,605 root INFO copying build/lib/django/contrib/sites/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,606 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hu
2025-04-22 20:54:04,606 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,606 root INFO copying build/lib/django/contrib/sites/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,606 root INFO copying build/lib/django/contrib/sites/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,606 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ta
2025-04-22 20:54:04,606 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,606 root INFO copying build/lib/django/contrib/sites/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,607 root INFO copying build/lib/django/contrib/sites/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,607 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/eu
2025-04-22 20:54:04,607 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,607 root INFO copying build/lib/django/contrib/sites/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,607 root INFO copying build/lib/django/contrib/sites/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,607 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es_MX
2025-04-22 20:54:04,607 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,607 root INFO copying build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,608 root INFO copying build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,608 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/tk
2025-04-22 20:54:04,608 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,608 root INFO copying build/lib/django/contrib/sites/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,608 root INFO copying build/lib/django/contrib/sites/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,609 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/th
2025-04-22 20:54:04,609 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/th/LC_MESSAGES
2025-04-22 20:54:04,609 root INFO copying build/lib/django/contrib/sites/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/th/LC_MESSAGES
2025-04-22 20:54:04,609 root INFO copying build/lib/django/contrib/sites/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/th/LC_MESSAGES
2025-04-22 20:54:04,609 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/nb
2025-04-22 20:54:04,609 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,609 root INFO copying build/lib/django/contrib/sites/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,609 root INFO copying build/lib/django/contrib/sites/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,610 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/mn
2025-04-22 20:54:04,610 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,610 root INFO copying build/lib/django/contrib/sites/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,610 root INFO copying build/lib/django/contrib/sites/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,610 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ka
2025-04-22 20:54:04,610 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,610 root INFO copying build/lib/django/contrib/sites/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,611 root INFO copying build/lib/django/contrib/sites/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,611 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/nl
2025-04-22 20:54:04,611 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,611 root INFO copying build/lib/django/contrib/sites/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,611 root INFO copying build/lib/django/contrib/sites/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,611 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/te
2025-04-22 20:54:04,611 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/te/LC_MESSAGES
2025-04-22 20:54:04,612 root INFO copying build/lib/django/contrib/sites/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/te/LC_MESSAGES
2025-04-22 20:54:04,612 root INFO copying build/lib/django/contrib/sites/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/te/LC_MESSAGES
2025-04-22 20:54:04,612 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/pt
2025-04-22 20:54:04,612 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,612 root INFO copying build/lib/django/contrib/sites/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,612 root INFO copying build/lib/django/contrib/sites/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,612 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/bn
2025-04-22 20:54:04,613 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,613 root INFO copying build/lib/django/contrib/sites/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,613 root INFO copying build/lib/django/contrib/sites/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,613 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/he
2025-04-22 20:54:04,613 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/he/LC_MESSAGES
2025-04-22 20:54:04,613 root INFO copying build/lib/django/contrib/sites/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/he/LC_MESSAGES
2025-04-22 20:54:04,613 root INFO copying build/lib/django/contrib/sites/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/he/LC_MESSAGES
2025-04-22 20:54:04,614 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/br
2025-04-22 20:54:04,614 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/br/LC_MESSAGES
2025-04-22 20:54:04,614 root INFO copying build/lib/django/contrib/sites/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/br/LC_MESSAGES
2025-04-22 20:54:04,614 root INFO copying build/lib/django/contrib/sites/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/br/LC_MESSAGES
2025-04-22 20:54:04,614 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/fa
2025-04-22 20:54:04,614 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,614 root INFO copying build/lib/django/contrib/sites/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,614 root INFO copying build/lib/django/contrib/sites/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,615 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/tg
2025-04-22 20:54:04,615 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,615 root INFO copying build/lib/django/contrib/sites/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,615 root INFO copying build/lib/django/contrib/sites/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,615 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/km
2025-04-22 20:54:04,615 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/km/LC_MESSAGES
2025-04-22 20:54:04,615 root INFO copying build/lib/django/contrib/sites/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/km/LC_MESSAGES
2025-04-22 20:54:04,616 root INFO copying build/lib/django/contrib/sites/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/km/LC_MESSAGES
2025-04-22 20:54:04,616 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/da
2025-04-22 20:54:04,616 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/da/LC_MESSAGES
2025-04-22 20:54:04,616 root INFO copying build/lib/django/contrib/sites/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/da/LC_MESSAGES
2025-04-22 20:54:04,616 root INFO copying build/lib/django/contrib/sites/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sites/locale/da/LC_MESSAGES
2025-04-22 20:54:04,616 root INFO copying build/lib/django/contrib/sites/shortcuts.py -> build/bdist.linux-aarch64/wheel/django/contrib/sites
2025-04-22 20:54:04,616 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sitemaps
2025-04-22 20:54:04,617 root INFO copying build/lib/django/contrib/sitemaps/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/sitemaps
2025-04-22 20:54:04,617 root INFO copying build/lib/django/contrib/sitemaps/views.py -> build/bdist.linux-aarch64/wheel/django/contrib/sitemaps
2025-04-22 20:54:04,617 root INFO copying build/lib/django/contrib/sitemaps/apps.py -> build/bdist.linux-aarch64/wheel/django/contrib/sitemaps
2025-04-22 20:54:04,617 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sitemaps/management
2025-04-22 20:54:04,617 root INFO copying build/lib/django/contrib/sitemaps/management/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/sitemaps/management
2025-04-22 20:54:04,617 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sitemaps/management/commands
2025-04-22 20:54:04,617 root INFO copying build/lib/django/contrib/sitemaps/management/commands/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/sitemaps/management/commands
2025-04-22 20:54:04,618 root INFO copying build/lib/django/contrib/sitemaps/management/commands/ping_google.py -> build/bdist.linux-aarch64/wheel/django/contrib/sitemaps/management/commands
2025-04-22 20:54:04,618 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sitemaps/templates
2025-04-22 20:54:04,618 root INFO copying build/lib/django/contrib/sitemaps/templates/sitemap.xml -> build/bdist.linux-aarch64/wheel/django/contrib/sitemaps/templates
2025-04-22 20:54:04,618 root INFO copying build/lib/django/contrib/sitemaps/templates/sitemap_index.xml -> build/bdist.linux-aarch64/wheel/django/contrib/sitemaps/templates
2025-04-22 20:54:04,618 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages
2025-04-22 20:54:04,618 root INFO copying build/lib/django/contrib/flatpages/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages
2025-04-22 20:54:04,618 root INFO copying build/lib/django/contrib/flatpages/middleware.py -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages
2025-04-22 20:54:04,619 root INFO copying build/lib/django/contrib/flatpages/views.py -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages
2025-04-22 20:54:04,619 root INFO copying build/lib/django/contrib/flatpages/forms.py -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages
2025-04-22 20:54:04,619 root INFO copying build/lib/django/contrib/flatpages/models.py -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages
2025-04-22 20:54:04,619 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/migrations
2025-04-22 20:54:04,619 root INFO copying build/lib/django/contrib/flatpages/migrations/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/migrations
2025-04-22 20:54:04,619 root INFO copying build/lib/django/contrib/flatpages/migrations/0001_initial.py -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/migrations
2025-04-22 20:54:04,619 root INFO copying build/lib/django/contrib/flatpages/apps.py -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages
2025-04-22 20:54:04,620 root INFO copying build/lib/django/contrib/flatpages/urls.py -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages
2025-04-22 20:54:04,620 root INFO copying build/lib/django/contrib/flatpages/admin.py -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages
2025-04-22 20:54:04,620 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/templatetags
2025-04-22 20:54:04,620 root INFO copying build/lib/django/contrib/flatpages/templatetags/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/templatetags
2025-04-22 20:54:04,620 root INFO copying build/lib/django/contrib/flatpages/templatetags/flatpages.py -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/templatetags
2025-04-22 20:54:04,620 root INFO copying build/lib/django/contrib/flatpages/sitemaps.py -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages
2025-04-22 20:54:04,621 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale
2025-04-22 20:54:04,621 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/lv
2025-04-22 20:54:04,621 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,621 root INFO copying build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,621 root INFO copying build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,621 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sw
2025-04-22 20:54:04,621 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,621 root INFO copying build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,622 root INFO copying build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,622 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/en_AU
2025-04-22 20:54:04,622 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,622 root INFO copying build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,622 root INFO copying build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,622 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/mr
2025-04-22 20:54:04,622 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,623 root INFO copying build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,623 root INFO copying build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,623 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/lb
2025-04-22 20:54:04,623 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,623 root INFO copying build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,623 root INFO copying build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,623 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ca
2025-04-22 20:54:04,624 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,624 root INFO copying build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,624 root INFO copying build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,624 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/en_GB
2025-04-22 20:54:04,624 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,624 root INFO copying build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,624 root INFO copying build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,625 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/el
2025-04-22 20:54:04,625 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/el/LC_MESSAGES
2025-04-22 20:54:04,625 root INFO copying build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/el/LC_MESSAGES
2025-04-22 20:54:04,625 root INFO copying build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/el/LC_MESSAGES
2025-04-22 20:54:04,625 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es_VE
2025-04-22 20:54:04,625 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,625 root INFO copying build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,626 root INFO copying build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,626 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/af
2025-04-22 20:54:04,626 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/af/LC_MESSAGES
2025-04-22 20:54:04,626 root INFO copying build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/af/LC_MESSAGES
2025-04-22 20:54:04,626 root INFO copying build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/af/LC_MESSAGES
2025-04-22 20:54:04,626 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/en
2025-04-22 20:54:04,626 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/en/LC_MESSAGES
2025-04-22 20:54:04,626 root INFO copying build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/en/LC_MESSAGES
2025-04-22 20:54:04,627 root INFO copying build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/en/LC_MESSAGES
2025-04-22 20:54:04,627 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/dsb
2025-04-22 20:54:04,627 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,627 root INFO copying build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,627 root INFO copying build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,627 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/et
2025-04-22 20:54:04,627 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/et/LC_MESSAGES
2025-04-22 20:54:04,628 root INFO copying build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/et/LC_MESSAGES
2025-04-22 20:54:04,628 root INFO copying build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/et/LC_MESSAGES
2025-04-22 20:54:04,628 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/nn
2025-04-22 20:54:04,628 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,628 root INFO copying build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,628 root INFO copying build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,628 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/cy
2025-04-22 20:54:04,629 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,629 root INFO copying build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,629 root INFO copying build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,629 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ko
2025-04-22 20:54:04,629 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,629 root INFO copying build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,629 root INFO copying build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,630 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/is
2025-04-22 20:54:04,630 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/is/LC_MESSAGES
2025-04-22 20:54:04,630 root INFO copying build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/is/LC_MESSAGES
2025-04-22 20:54:04,630 root INFO copying build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/is/LC_MESSAGES
2025-04-22 20:54:04,630 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/pa
2025-04-22 20:54:04,630 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,630 root INFO copying build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,630 root INFO copying build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,631 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/tt
2025-04-22 20:54:04,631 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,631 root INFO copying build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,631 root INFO copying build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,631 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ne
2025-04-22 20:54:04,631 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,631 root INFO copying build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,632 root INFO copying build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,632 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sr_Latn
2025-04-22 20:54:04,632 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,632 root INFO copying build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,632 root INFO copying build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,633 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/fy
2025-04-22 20:54:04,633 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,633 root INFO copying build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,633 root INFO copying build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,633 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/bg
2025-04-22 20:54:04,633 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,633 root INFO copying build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,633 root INFO copying build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,634 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ga
2025-04-22 20:54:04,634 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,634 root INFO copying build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,634 root INFO copying build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,634 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/gl
2025-04-22 20:54:04,634 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,634 root INFO copying build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,634 root INFO copying build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,635 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/uk
2025-04-22 20:54:04,635 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,635 root INFO copying build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,635 root INFO copying build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,635 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/kn
2025-04-22 20:54:04,635 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,635 root INFO copying build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,636 root INFO copying build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,636 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ja
2025-04-22 20:54:04,636 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,636 root INFO copying build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,636 root INFO copying build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,636 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/cs
2025-04-22 20:54:04,636 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,637 root INFO copying build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,637 root INFO copying build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,637 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/os
2025-04-22 20:54:04,637 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/os/LC_MESSAGES
2025-04-22 20:54:04,637 root INFO copying build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/os/LC_MESSAGES
2025-04-22 20:54:04,637 root INFO copying build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/os/LC_MESSAGES
2025-04-22 20:54:04,637 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/tr
2025-04-22 20:54:04,638 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,638 root INFO copying build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,638 root INFO copying build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,638 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/io
2025-04-22 20:54:04,638 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/io/LC_MESSAGES
2025-04-22 20:54:04,638 root INFO copying build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/io/LC_MESSAGES
2025-04-22 20:54:04,638 root INFO copying build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/io/LC_MESSAGES
2025-04-22 20:54:04,639 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sl
2025-04-22 20:54:04,639 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,639 root INFO copying build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,639 root INFO copying build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,639 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sq
2025-04-22 20:54:04,639 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,639 root INFO copying build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,640 root INFO copying build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,640 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/az
2025-04-22 20:54:04,640 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/az/LC_MESSAGES
2025-04-22 20:54:04,640 root INFO copying build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/az/LC_MESSAGES
2025-04-22 20:54:04,640 root INFO copying build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/az/LC_MESSAGES
2025-04-22 20:54:04,640 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/eo
2025-04-22 20:54:04,640 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,640 root INFO copying build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,641 root INFO copying build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,641 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/pt_BR
2025-04-22 20:54:04,641 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,641 root INFO copying build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,641 root INFO copying build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,641 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/pl
2025-04-22 20:54:04,641 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,642 root INFO copying build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,642 root INFO copying build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,642 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/gd
2025-04-22 20:54:04,642 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,642 root INFO copying build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,642 root INFO copying build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,642 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hr
2025-04-22 20:54:04,643 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,643 root INFO copying build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,643 root INFO copying build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,643 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ru
2025-04-22 20:54:04,643 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,643 root INFO copying build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,643 root INFO copying build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,644 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es
2025-04-22 20:54:04,644 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es/LC_MESSAGES
2025-04-22 20:54:04,644 root INFO copying build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es/LC_MESSAGES
2025-04-22 20:54:04,644 root INFO copying build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es/LC_MESSAGES
2025-04-22 20:54:04,644 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/id
2025-04-22 20:54:04,644 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/id/LC_MESSAGES
2025-04-22 20:54:04,644 root INFO copying build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/id/LC_MESSAGES
2025-04-22 20:54:04,644 root INFO copying build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/id/LC_MESSAGES
2025-04-22 20:54:04,645 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/fi
2025-04-22 20:54:04,645 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,645 root INFO copying build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,645 root INFO copying build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,645 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/mk
2025-04-22 20:54:04,645 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,645 root INFO copying build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,646 root INFO copying build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,646 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hi
2025-04-22 20:54:04,646 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,646 root INFO copying build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,646 root INFO copying build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,646 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hsb
2025-04-22 20:54:04,646 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,647 root INFO copying build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,647 root INFO copying build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,647 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sk
2025-04-22 20:54:04,647 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,647 root INFO copying build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,647 root INFO copying build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,647 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/lt
2025-04-22 20:54:04,648 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,648 root INFO copying build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,648 root INFO copying build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,648 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/de
2025-04-22 20:54:04,648 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/de/LC_MESSAGES
2025-04-22 20:54:04,648 root INFO copying build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/de/LC_MESSAGES
2025-04-22 20:54:04,648 root INFO copying build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/de/LC_MESSAGES
2025-04-22 20:54:04,649 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/it
2025-04-22 20:54:04,649 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/it/LC_MESSAGES
2025-04-22 20:54:04,649 root INFO copying build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/it/LC_MESSAGES
2025-04-22 20:54:04,649 root INFO copying build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/it/LC_MESSAGES
2025-04-22 20:54:04,649 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/my
2025-04-22 20:54:04,649 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/my/LC_MESSAGES
2025-04-22 20:54:04,649 root INFO copying build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/my/LC_MESSAGES
2025-04-22 20:54:04,650 root INFO copying build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/my/LC_MESSAGES
2025-04-22 20:54:04,650 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sr
2025-04-22 20:54:04,650 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,650 root INFO copying build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,650 root INFO copying build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,650 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/bs
2025-04-22 20:54:04,650 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,651 root INFO copying build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,651 root INFO copying build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,651 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ro
2025-04-22 20:54:04,651 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,651 root INFO copying build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,651 root INFO copying build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,651 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ky
2025-04-22 20:54:04,652 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,652 root INFO copying build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,652 root INFO copying build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,652 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/fr
2025-04-22 20:54:04,652 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,652 root INFO copying build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,652 root INFO copying build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,653 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ar
2025-04-22 20:54:04,653 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,653 root INFO copying build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,653 root INFO copying build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,653 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hy
2025-04-22 20:54:04,653 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,653 root INFO copying build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,653 root INFO copying build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,654 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es_AR
2025-04-22 20:54:04,654 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,654 root INFO copying build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,654 root INFO copying build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,654 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/vi
2025-04-22 20:54:04,654 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,654 root INFO copying build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,655 root INFO copying build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,655 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ckb
2025-04-22 20:54:04,655 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,655 root INFO copying build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,655 root INFO copying build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,655 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sv
2025-04-22 20:54:04,656 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,656 root INFO copying build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,656 root INFO copying build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,656 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/zh_Hant
2025-04-22 20:54:04,656 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,656 root INFO copying build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,656 root INFO copying build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,657 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/kk
2025-04-22 20:54:04,657 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,657 root INFO copying build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,657 root INFO copying build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,657 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es_CO
2025-04-22 20:54:04,657 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,657 root INFO copying build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,658 root INFO copying build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,658 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/be
2025-04-22 20:54:04,658 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/be/LC_MESSAGES
2025-04-22 20:54:04,658 root INFO copying build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/be/LC_MESSAGES
2025-04-22 20:54:04,658 root INFO copying build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/be/LC_MESSAGES
2025-04-22 20:54:04,658 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/udm
2025-04-22 20:54:04,658 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,659 root INFO copying build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,659 root INFO copying build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,659 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ml
2025-04-22 20:54:04,659 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,659 root INFO copying build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,659 root INFO copying build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,659 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ar_DZ
2025-04-22 20:54:04,660 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,660 root INFO copying build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,660 root INFO copying build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,660 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ms
2025-04-22 20:54:04,660 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,660 root INFO copying build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,660 root INFO copying build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,661 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ast
2025-04-22 20:54:04,661 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,661 root INFO copying build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,661 root INFO copying build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,661 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/zh_Hans
2025-04-22 20:54:04,661 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,661 root INFO copying build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,662 root INFO copying build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,662 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ur
2025-04-22 20:54:04,662 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,662 root INFO copying build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,662 root INFO copying build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,662 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ia
2025-04-22 20:54:04,662 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,662 root INFO copying build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,663 root INFO copying build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,663 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hu
2025-04-22 20:54:04,663 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,663 root INFO copying build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,663 root INFO copying build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,663 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ta
2025-04-22 20:54:04,664 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,664 root INFO copying build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,664 root INFO copying build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,664 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/eu
2025-04-22 20:54:04,664 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,664 root INFO copying build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,664 root INFO copying build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,665 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es_MX
2025-04-22 20:54:04,665 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,665 root INFO copying build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,665 root INFO copying build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,665 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/tk
2025-04-22 20:54:04,665 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,665 root INFO copying build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,665 root INFO copying build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,666 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/th
2025-04-22 20:54:04,666 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/th/LC_MESSAGES
2025-04-22 20:54:04,666 root INFO copying build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/th/LC_MESSAGES
2025-04-22 20:54:04,666 root INFO copying build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/th/LC_MESSAGES
2025-04-22 20:54:04,666 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/nb
2025-04-22 20:54:04,666 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,666 root INFO copying build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,667 root INFO copying build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,667 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/mn
2025-04-22 20:54:04,667 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,667 root INFO copying build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,667 root INFO copying build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,667 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ka
2025-04-22 20:54:04,667 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,668 root INFO copying build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,668 root INFO copying build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,668 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/nl
2025-04-22 20:54:04,668 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,668 root INFO copying build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,668 root INFO copying build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,668 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/te
2025-04-22 20:54:04,669 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/te/LC_MESSAGES
2025-04-22 20:54:04,669 root INFO copying build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/te/LC_MESSAGES
2025-04-22 20:54:04,669 root INFO copying build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/te/LC_MESSAGES
2025-04-22 20:54:04,669 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/pt
2025-04-22 20:54:04,669 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,669 root INFO copying build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,669 root INFO copying build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,670 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/bn
2025-04-22 20:54:04,670 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,670 root INFO copying build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,670 root INFO copying build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,670 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/he
2025-04-22 20:54:04,670 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/he/LC_MESSAGES
2025-04-22 20:54:04,670 root INFO copying build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/he/LC_MESSAGES
2025-04-22 20:54:04,671 root INFO copying build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/he/LC_MESSAGES
2025-04-22 20:54:04,671 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/br
2025-04-22 20:54:04,671 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/br/LC_MESSAGES
2025-04-22 20:54:04,671 root INFO copying build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/br/LC_MESSAGES
2025-04-22 20:54:04,671 root INFO copying build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/br/LC_MESSAGES
2025-04-22 20:54:04,671 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/fa
2025-04-22 20:54:04,671 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,671 root INFO copying build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,672 root INFO copying build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,672 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/tg
2025-04-22 20:54:04,672 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,672 root INFO copying build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,672 root INFO copying build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,672 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/km
2025-04-22 20:54:04,673 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/km/LC_MESSAGES
2025-04-22 20:54:04,673 root INFO copying build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/km/LC_MESSAGES
2025-04-22 20:54:04,673 root INFO copying build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/km/LC_MESSAGES
2025-04-22 20:54:04,673 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/da
2025-04-22 20:54:04,673 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/da/LC_MESSAGES
2025-04-22 20:54:04,673 root INFO copying build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/da/LC_MESSAGES
2025-04-22 20:54:04,673 root INFO copying build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/flatpages/locale/da/LC_MESSAGES
2025-04-22 20:54:04,674 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/staticfiles
2025-04-22 20:54:04,674 root INFO copying build/lib/django/contrib/staticfiles/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/staticfiles
2025-04-22 20:54:04,674 root INFO copying build/lib/django/contrib/staticfiles/handlers.py -> build/bdist.linux-aarch64/wheel/django/contrib/staticfiles
2025-04-22 20:54:04,674 root INFO copying build/lib/django/contrib/staticfiles/views.py -> build/bdist.linux-aarch64/wheel/django/contrib/staticfiles
2025-04-22 20:54:04,674 root INFO copying build/lib/django/contrib/staticfiles/testing.py -> build/bdist.linux-aarch64/wheel/django/contrib/staticfiles
2025-04-22 20:54:04,674 root INFO copying build/lib/django/contrib/staticfiles/apps.py -> build/bdist.linux-aarch64/wheel/django/contrib/staticfiles
2025-04-22 20:54:04,674 root INFO copying build/lib/django/contrib/staticfiles/urls.py -> build/bdist.linux-aarch64/wheel/django/contrib/staticfiles
2025-04-22 20:54:04,674 root INFO copying build/lib/django/contrib/staticfiles/utils.py -> build/bdist.linux-aarch64/wheel/django/contrib/staticfiles
2025-04-22 20:54:04,675 root INFO copying build/lib/django/contrib/staticfiles/checks.py -> build/bdist.linux-aarch64/wheel/django/contrib/staticfiles
2025-04-22 20:54:04,675 root INFO copying build/lib/django/contrib/staticfiles/finders.py -> build/bdist.linux-aarch64/wheel/django/contrib/staticfiles
2025-04-22 20:54:04,675 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/staticfiles/management
2025-04-22 20:54:04,675 root INFO copying build/lib/django/contrib/staticfiles/management/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/staticfiles/management
2025-04-22 20:54:04,675 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/staticfiles/management/commands
2025-04-22 20:54:04,675 root INFO copying build/lib/django/contrib/staticfiles/management/commands/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/staticfiles/management/commands
2025-04-22 20:54:04,676 root INFO copying build/lib/django/contrib/staticfiles/management/commands/collectstatic.py -> build/bdist.linux-aarch64/wheel/django/contrib/staticfiles/management/commands
2025-04-22 20:54:04,676 root INFO copying build/lib/django/contrib/staticfiles/management/commands/findstatic.py -> build/bdist.linux-aarch64/wheel/django/contrib/staticfiles/management/commands
2025-04-22 20:54:04,676 root INFO copying build/lib/django/contrib/staticfiles/management/commands/runserver.py -> build/bdist.linux-aarch64/wheel/django/contrib/staticfiles/management/commands
2025-04-22 20:54:04,676 root INFO copying build/lib/django/contrib/staticfiles/storage.py -> build/bdist.linux-aarch64/wheel/django/contrib/staticfiles
2025-04-22 20:54:04,676 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions
2025-04-22 20:54:04,676 root INFO copying build/lib/django/contrib/sessions/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions
2025-04-22 20:54:04,676 root INFO copying build/lib/django/contrib/sessions/middleware.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions
2025-04-22 20:54:04,677 root INFO copying build/lib/django/contrib/sessions/exceptions.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions
2025-04-22 20:54:04,677 root INFO copying build/lib/django/contrib/sessions/base_session.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions
2025-04-22 20:54:04,677 root INFO copying build/lib/django/contrib/sessions/models.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions
2025-04-22 20:54:04,677 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/migrations
2025-04-22 20:54:04,677 root INFO copying build/lib/django/contrib/sessions/migrations/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/migrations
2025-04-22 20:54:04,677 root INFO copying build/lib/django/contrib/sessions/migrations/0001_initial.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/migrations
2025-04-22 20:54:04,677 root INFO copying build/lib/django/contrib/sessions/apps.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions
2025-04-22 20:54:04,678 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/management
2025-04-22 20:54:04,678 root INFO copying build/lib/django/contrib/sessions/management/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/management
2025-04-22 20:54:04,678 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/management/commands
2025-04-22 20:54:04,678 root INFO copying build/lib/django/contrib/sessions/management/commands/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/management/commands
2025-04-22 20:54:04,678 root INFO copying build/lib/django/contrib/sessions/management/commands/clearsessions.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/management/commands
2025-04-22 20:54:04,678 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale
2025-04-22 20:54:04,679 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/lv
2025-04-22 20:54:04,679 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,679 root INFO copying build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,679 root INFO copying build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,679 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sw
2025-04-22 20:54:04,679 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,679 root INFO copying build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,679 root INFO copying build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,680 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/en_AU
2025-04-22 20:54:04,680 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,680 root INFO copying build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,680 root INFO copying build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,680 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/mr
2025-04-22 20:54:04,680 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,680 root INFO copying build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,681 root INFO copying build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,681 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/lb
2025-04-22 20:54:04,681 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,681 root INFO copying build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,681 root INFO copying build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,681 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ca
2025-04-22 20:54:04,681 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,681 root INFO copying build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,682 root INFO copying build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,682 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/en_GB
2025-04-22 20:54:04,682 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,682 root INFO copying build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,682 root INFO copying build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,682 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/el
2025-04-22 20:54:04,683 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/el/LC_MESSAGES
2025-04-22 20:54:04,683 root INFO copying build/lib/django/contrib/sessions/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/el/LC_MESSAGES
2025-04-22 20:54:04,683 root INFO copying build/lib/django/contrib/sessions/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/el/LC_MESSAGES
2025-04-22 20:54:04,683 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es_VE
2025-04-22 20:54:04,683 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,683 root INFO copying build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,683 root INFO copying build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,684 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/af
2025-04-22 20:54:04,684 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/af/LC_MESSAGES
2025-04-22 20:54:04,684 root INFO copying build/lib/django/contrib/sessions/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/af/LC_MESSAGES
2025-04-22 20:54:04,684 root INFO copying build/lib/django/contrib/sessions/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/af/LC_MESSAGES
2025-04-22 20:54:04,684 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/en
2025-04-22 20:54:04,684 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/en/LC_MESSAGES
2025-04-22 20:54:04,684 root INFO copying build/lib/django/contrib/sessions/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/en/LC_MESSAGES
2025-04-22 20:54:04,684 root INFO copying build/lib/django/contrib/sessions/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/en/LC_MESSAGES
2025-04-22 20:54:04,685 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/dsb
2025-04-22 20:54:04,685 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,685 root INFO copying build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,685 root INFO copying build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,685 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/et
2025-04-22 20:54:04,685 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/et/LC_MESSAGES
2025-04-22 20:54:04,685 root INFO copying build/lib/django/contrib/sessions/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/et/LC_MESSAGES
2025-04-22 20:54:04,686 root INFO copying build/lib/django/contrib/sessions/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/et/LC_MESSAGES
2025-04-22 20:54:04,686 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/nn
2025-04-22 20:54:04,686 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,686 root INFO copying build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,686 root INFO copying build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,686 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/cy
2025-04-22 20:54:04,687 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,687 root INFO copying build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,687 root INFO copying build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,687 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ko
2025-04-22 20:54:04,687 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,687 root INFO copying build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,687 root INFO copying build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,687 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/is
2025-04-22 20:54:04,688 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/is/LC_MESSAGES
2025-04-22 20:54:04,688 root INFO copying build/lib/django/contrib/sessions/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/is/LC_MESSAGES
2025-04-22 20:54:04,688 root INFO copying build/lib/django/contrib/sessions/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/is/LC_MESSAGES
2025-04-22 20:54:04,688 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/pa
2025-04-22 20:54:04,688 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,688 root INFO copying build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,688 root INFO copying build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,689 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/tt
2025-04-22 20:54:04,689 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,689 root INFO copying build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,689 root INFO copying build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,689 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ne
2025-04-22 20:54:04,689 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,689 root INFO copying build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,690 root INFO copying build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,690 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sr_Latn
2025-04-22 20:54:04,690 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,690 root INFO copying build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,690 root INFO copying build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,690 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/fy
2025-04-22 20:54:04,690 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,690 root INFO copying build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,691 root INFO copying build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,691 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/bg
2025-04-22 20:54:04,691 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,691 root INFO copying build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,691 root INFO copying build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,691 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ga
2025-04-22 20:54:04,691 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,692 root INFO copying build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,692 root INFO copying build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,692 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/gl
2025-04-22 20:54:04,692 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,692 root INFO copying build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,692 root INFO copying build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,692 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/uk
2025-04-22 20:54:04,693 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,693 root INFO copying build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,693 root INFO copying build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,693 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/uz
2025-04-22 20:54:04,693 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,693 root INFO copying build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,693 root INFO copying build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,694 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/kn
2025-04-22 20:54:04,694 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,694 root INFO copying build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,694 root INFO copying build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,694 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ja
2025-04-22 20:54:04,694 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,694 root INFO copying build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,694 root INFO copying build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,695 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/cs
2025-04-22 20:54:04,695 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,695 root INFO copying build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,695 root INFO copying build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,695 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/os
2025-04-22 20:54:04,695 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/os/LC_MESSAGES
2025-04-22 20:54:04,695 root INFO copying build/lib/django/contrib/sessions/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/os/LC_MESSAGES
2025-04-22 20:54:04,696 root INFO copying build/lib/django/contrib/sessions/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/os/LC_MESSAGES
2025-04-22 20:54:04,696 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/tr
2025-04-22 20:54:04,696 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,696 root INFO copying build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,696 root INFO copying build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,696 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/io
2025-04-22 20:54:04,696 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/io/LC_MESSAGES
2025-04-22 20:54:04,697 root INFO copying build/lib/django/contrib/sessions/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/io/LC_MESSAGES
2025-04-22 20:54:04,697 root INFO copying build/lib/django/contrib/sessions/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/io/LC_MESSAGES
2025-04-22 20:54:04,697 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sl
2025-04-22 20:54:04,697 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,697 root INFO copying build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,697 root INFO copying build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,697 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sq
2025-04-22 20:54:04,698 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,698 root INFO copying build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,698 root INFO copying build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,698 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/az
2025-04-22 20:54:04,698 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/az/LC_MESSAGES
2025-04-22 20:54:04,698 root INFO copying build/lib/django/contrib/sessions/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/az/LC_MESSAGES
2025-04-22 20:54:04,698 root INFO copying build/lib/django/contrib/sessions/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/az/LC_MESSAGES
2025-04-22 20:54:04,699 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/eo
2025-04-22 20:54:04,699 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,699 root INFO copying build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,699 root INFO copying build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,699 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/pt_BR
2025-04-22 20:54:04,699 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,699 root INFO copying build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,699 root INFO copying build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,700 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/pl
2025-04-22 20:54:04,700 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,700 root INFO copying build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,700 root INFO copying build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,700 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/gd
2025-04-22 20:54:04,700 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,700 root INFO copying build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,701 root INFO copying build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,701 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hr
2025-04-22 20:54:04,701 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,701 root INFO copying build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,701 root INFO copying build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,701 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ru
2025-04-22 20:54:04,701 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,702 root INFO copying build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,702 root INFO copying build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,702 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es
2025-04-22 20:54:04,702 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es/LC_MESSAGES
2025-04-22 20:54:04,702 root INFO copying build/lib/django/contrib/sessions/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es/LC_MESSAGES
2025-04-22 20:54:04,702 root INFO copying build/lib/django/contrib/sessions/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es/LC_MESSAGES
2025-04-22 20:54:04,702 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/id
2025-04-22 20:54:04,703 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/id/LC_MESSAGES
2025-04-22 20:54:04,703 root INFO copying build/lib/django/contrib/sessions/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/id/LC_MESSAGES
2025-04-22 20:54:04,703 root INFO copying build/lib/django/contrib/sessions/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/id/LC_MESSAGES
2025-04-22 20:54:04,703 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/fi
2025-04-22 20:54:04,703 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,703 root INFO copying build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,703 root INFO copying build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,704 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/mk
2025-04-22 20:54:04,704 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,704 root INFO copying build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,704 root INFO copying build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,704 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hi
2025-04-22 20:54:04,704 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,704 root INFO copying build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,705 root INFO copying build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,705 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/kab
2025-04-22 20:54:04,705 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,705 root INFO copying build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,705 root INFO copying build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,705 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hsb
2025-04-22 20:54:04,706 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,706 root INFO copying build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,706 root INFO copying build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,706 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sk
2025-04-22 20:54:04,706 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,706 root INFO copying build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,706 root INFO copying build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,707 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/lt
2025-04-22 20:54:04,707 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,707 root INFO copying build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,707 root INFO copying build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,707 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/de
2025-04-22 20:54:04,707 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/de/LC_MESSAGES
2025-04-22 20:54:04,707 root INFO copying build/lib/django/contrib/sessions/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/de/LC_MESSAGES
2025-04-22 20:54:04,707 root INFO copying build/lib/django/contrib/sessions/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/de/LC_MESSAGES
2025-04-22 20:54:04,708 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/it
2025-04-22 20:54:04,708 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/it/LC_MESSAGES
2025-04-22 20:54:04,708 root INFO copying build/lib/django/contrib/sessions/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/it/LC_MESSAGES
2025-04-22 20:54:04,708 root INFO copying build/lib/django/contrib/sessions/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/it/LC_MESSAGES
2025-04-22 20:54:04,708 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/my
2025-04-22 20:54:04,708 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/my/LC_MESSAGES
2025-04-22 20:54:04,708 root INFO copying build/lib/django/contrib/sessions/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/my/LC_MESSAGES
2025-04-22 20:54:04,709 root INFO copying build/lib/django/contrib/sessions/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/my/LC_MESSAGES
2025-04-22 20:54:04,709 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sr
2025-04-22 20:54:04,709 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,709 root INFO copying build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,709 root INFO copying build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,709 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/bs
2025-04-22 20:54:04,709 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,709 root INFO copying build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,710 root INFO copying build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,710 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ro
2025-04-22 20:54:04,710 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,710 root INFO copying build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,710 root INFO copying build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,710 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ky
2025-04-22 20:54:04,710 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,711 root INFO copying build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,711 root INFO copying build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,711 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/fr
2025-04-22 20:54:04,711 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,711 root INFO copying build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,711 root INFO copying build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,711 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ar
2025-04-22 20:54:04,712 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,712 root INFO copying build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,712 root INFO copying build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,712 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hy
2025-04-22 20:54:04,712 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,712 root INFO copying build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,712 root INFO copying build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,713 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es_AR
2025-04-22 20:54:04,713 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,713 root INFO copying build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,713 root INFO copying build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,713 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/vi
2025-04-22 20:54:04,713 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,713 root INFO copying build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,713 root INFO copying build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,714 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ckb
2025-04-22 20:54:04,714 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,714 root INFO copying build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,714 root INFO copying build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,714 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sv
2025-04-22 20:54:04,714 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,714 root INFO copying build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,715 root INFO copying build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,715 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/zh_Hant
2025-04-22 20:54:04,715 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,715 root INFO copying build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,715 root INFO copying build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,715 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/kk
2025-04-22 20:54:04,716 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,716 root INFO copying build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,716 root INFO copying build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,716 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es_CO
2025-04-22 20:54:04,716 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,716 root INFO copying build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,716 root INFO copying build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,716 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/be
2025-04-22 20:54:04,717 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/be/LC_MESSAGES
2025-04-22 20:54:04,717 root INFO copying build/lib/django/contrib/sessions/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/be/LC_MESSAGES
2025-04-22 20:54:04,717 root INFO copying build/lib/django/contrib/sessions/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/be/LC_MESSAGES
2025-04-22 20:54:04,717 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/udm
2025-04-22 20:54:04,717 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,717 root INFO copying build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,717 root INFO copying build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,718 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ml
2025-04-22 20:54:04,718 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,718 root INFO copying build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,718 root INFO copying build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,718 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ar_DZ
2025-04-22 20:54:04,718 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,718 root INFO copying build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,719 root INFO copying build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,719 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ms
2025-04-22 20:54:04,719 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,719 root INFO copying build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,719 root INFO copying build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,719 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ast
2025-04-22 20:54:04,719 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,720 root INFO copying build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,720 root INFO copying build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,720 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/zh_Hans
2025-04-22 20:54:04,720 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,720 root INFO copying build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,720 root INFO copying build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,720 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ur
2025-04-22 20:54:04,721 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,721 root INFO copying build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,721 root INFO copying build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,721 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ia
2025-04-22 20:54:04,721 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,721 root INFO copying build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,721 root INFO copying build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,722 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hu
2025-04-22 20:54:04,722 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,722 root INFO copying build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,722 root INFO copying build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,722 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ta
2025-04-22 20:54:04,722 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,722 root INFO copying build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,723 root INFO copying build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,723 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/eu
2025-04-22 20:54:04,723 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,723 root INFO copying build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,723 root INFO copying build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,723 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es_MX
2025-04-22 20:54:04,723 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,723 root INFO copying build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,724 root INFO copying build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,724 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/tk
2025-04-22 20:54:04,724 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,724 root INFO copying build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,724 root INFO copying build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,724 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/th
2025-04-22 20:54:04,724 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/th/LC_MESSAGES
2025-04-22 20:54:04,725 root INFO copying build/lib/django/contrib/sessions/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/th/LC_MESSAGES
2025-04-22 20:54:04,725 root INFO copying build/lib/django/contrib/sessions/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/th/LC_MESSAGES
2025-04-22 20:54:04,725 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/nb
2025-04-22 20:54:04,725 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,725 root INFO copying build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,725 root INFO copying build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,725 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/mn
2025-04-22 20:54:04,726 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,726 root INFO copying build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,726 root INFO copying build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,726 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ka
2025-04-22 20:54:04,726 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,726 root INFO copying build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,726 root INFO copying build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,727 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/nl
2025-04-22 20:54:04,727 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,727 root INFO copying build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,727 root INFO copying build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,727 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/te
2025-04-22 20:54:04,727 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/te/LC_MESSAGES
2025-04-22 20:54:04,727 root INFO copying build/lib/django/contrib/sessions/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/te/LC_MESSAGES
2025-04-22 20:54:04,728 root INFO copying build/lib/django/contrib/sessions/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/te/LC_MESSAGES
2025-04-22 20:54:04,728 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/pt
2025-04-22 20:54:04,728 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,728 root INFO copying build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,728 root INFO copying build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,728 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/bn
2025-04-22 20:54:04,728 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,728 root INFO copying build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,729 root INFO copying build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,729 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/he
2025-04-22 20:54:04,729 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/he/LC_MESSAGES
2025-04-22 20:54:04,729 root INFO copying build/lib/django/contrib/sessions/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/he/LC_MESSAGES
2025-04-22 20:54:04,729 root INFO copying build/lib/django/contrib/sessions/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/he/LC_MESSAGES
2025-04-22 20:54:04,729 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/br
2025-04-22 20:54:04,729 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/br/LC_MESSAGES
2025-04-22 20:54:04,730 root INFO copying build/lib/django/contrib/sessions/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/br/LC_MESSAGES
2025-04-22 20:54:04,730 root INFO copying build/lib/django/contrib/sessions/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/br/LC_MESSAGES
2025-04-22 20:54:04,730 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/fa
2025-04-22 20:54:04,730 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,730 root INFO copying build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,730 root INFO copying build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,730 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/tg
2025-04-22 20:54:04,731 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,731 root INFO copying build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,731 root INFO copying build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,731 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/km
2025-04-22 20:54:04,731 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/km/LC_MESSAGES
2025-04-22 20:54:04,731 root INFO copying build/lib/django/contrib/sessions/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/km/LC_MESSAGES
2025-04-22 20:54:04,731 root INFO copying build/lib/django/contrib/sessions/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/km/LC_MESSAGES
2025-04-22 20:54:04,732 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/da
2025-04-22 20:54:04,732 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/da/LC_MESSAGES
2025-04-22 20:54:04,732 root INFO copying build/lib/django/contrib/sessions/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/da/LC_MESSAGES
2025-04-22 20:54:04,732 root INFO copying build/lib/django/contrib/sessions/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/locale/da/LC_MESSAGES
2025-04-22 20:54:04,732 root INFO copying build/lib/django/contrib/sessions/serializers.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions
2025-04-22 20:54:04,732 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/sessions/backends
2025-04-22 20:54:04,733 root INFO copying build/lib/django/contrib/sessions/backends/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/backends
2025-04-22 20:54:04,733 root INFO copying build/lib/django/contrib/sessions/backends/cache.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/backends
2025-04-22 20:54:04,733 root INFO copying build/lib/django/contrib/sessions/backends/db.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/backends
2025-04-22 20:54:04,733 root INFO copying build/lib/django/contrib/sessions/backends/cached_db.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/backends
2025-04-22 20:54:04,733 root INFO copying build/lib/django/contrib/sessions/backends/signed_cookies.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/backends
2025-04-22 20:54:04,733 root INFO copying build/lib/django/contrib/sessions/backends/base.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/backends
2025-04-22 20:54:04,733 root INFO copying build/lib/django/contrib/sessions/backends/file.py -> build/bdist.linux-aarch64/wheel/django/contrib/sessions/backends
2025-04-22 20:54:04,734 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs
2025-04-22 20:54:04,734 root INFO copying build/lib/django/contrib/admindocs/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs
2025-04-22 20:54:04,734 root INFO copying build/lib/django/contrib/admindocs/middleware.py -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs
2025-04-22 20:54:04,734 root INFO copying build/lib/django/contrib/admindocs/views.py -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs
2025-04-22 20:54:04,734 root INFO copying build/lib/django/contrib/admindocs/apps.py -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs
2025-04-22 20:54:04,734 root INFO copying build/lib/django/contrib/admindocs/urls.py -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs
2025-04-22 20:54:04,735 root INFO copying build/lib/django/contrib/admindocs/utils.py -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs
2025-04-22 20:54:04,735 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale
2025-04-22 20:54:04,735 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/lv
2025-04-22 20:54:04,735 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,735 root INFO copying build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,735 root INFO copying build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,735 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sw
2025-04-22 20:54:04,736 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,736 root INFO copying build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,736 root INFO copying build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,736 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/en_AU
2025-04-22 20:54:04,736 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,736 root INFO copying build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,736 root INFO copying build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,737 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/mr
2025-04-22 20:54:04,737 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,737 root INFO copying build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,737 root INFO copying build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,737 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/lb
2025-04-22 20:54:04,737 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,737 root INFO copying build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,738 root INFO copying build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,738 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ca
2025-04-22 20:54:04,738 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,738 root INFO copying build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,738 root INFO copying build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,738 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/en_GB
2025-04-22 20:54:04,738 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,739 root INFO copying build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,739 root INFO copying build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,739 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/el
2025-04-22 20:54:04,739 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/el/LC_MESSAGES
2025-04-22 20:54:04,739 root INFO copying build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/el/LC_MESSAGES
2025-04-22 20:54:04,739 root INFO copying build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/el/LC_MESSAGES
2025-04-22 20:54:04,739 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es_VE
2025-04-22 20:54:04,740 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,740 root INFO copying build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,740 root INFO copying build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,740 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/af
2025-04-22 20:54:04,740 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/af/LC_MESSAGES
2025-04-22 20:54:04,740 root INFO copying build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/af/LC_MESSAGES
2025-04-22 20:54:04,740 root INFO copying build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/af/LC_MESSAGES
2025-04-22 20:54:04,741 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/en
2025-04-22 20:54:04,741 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/en/LC_MESSAGES
2025-04-22 20:54:04,741 root INFO copying build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/en/LC_MESSAGES
2025-04-22 20:54:04,741 root INFO copying build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/en/LC_MESSAGES
2025-04-22 20:54:04,741 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/dsb
2025-04-22 20:54:04,741 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,741 root INFO copying build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,742 root INFO copying build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,742 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/et
2025-04-22 20:54:04,742 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/et/LC_MESSAGES
2025-04-22 20:54:04,742 root INFO copying build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/et/LC_MESSAGES
2025-04-22 20:54:04,742 root INFO copying build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/et/LC_MESSAGES
2025-04-22 20:54:04,742 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/nn
2025-04-22 20:54:04,742 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,743 root INFO copying build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,743 root INFO copying build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,743 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/cy
2025-04-22 20:54:04,743 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,743 root INFO copying build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,743 root INFO copying build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,744 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ko
2025-04-22 20:54:04,744 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,744 root INFO copying build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,744 root INFO copying build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,744 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/is
2025-04-22 20:54:04,744 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/is/LC_MESSAGES
2025-04-22 20:54:04,744 root INFO copying build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/is/LC_MESSAGES
2025-04-22 20:54:04,745 root INFO copying build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/is/LC_MESSAGES
2025-04-22 20:54:04,745 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/pa
2025-04-22 20:54:04,745 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,745 root INFO copying build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,745 root INFO copying build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,745 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/tt
2025-04-22 20:54:04,745 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,745 root INFO copying build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,746 root INFO copying build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,746 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ne
2025-04-22 20:54:04,746 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,746 root INFO copying build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,746 root INFO copying build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,746 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sr_Latn
2025-04-22 20:54:04,746 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,747 root INFO copying build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,747 root INFO copying build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,747 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/fy
2025-04-22 20:54:04,747 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,747 root INFO copying build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,747 root INFO copying build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,747 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/bg
2025-04-22 20:54:04,748 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,748 root INFO copying build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,748 root INFO copying build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,748 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ga
2025-04-22 20:54:04,748 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,748 root INFO copying build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,749 root INFO copying build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,749 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/gl
2025-04-22 20:54:04,749 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,749 root INFO copying build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,749 root INFO copying build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,749 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/uk
2025-04-22 20:54:04,749 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,749 root INFO copying build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,750 root INFO copying build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,750 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/kn
2025-04-22 20:54:04,750 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,750 root INFO copying build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,750 root INFO copying build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,750 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ja
2025-04-22 20:54:04,751 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,751 root INFO copying build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,751 root INFO copying build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,751 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/cs
2025-04-22 20:54:04,751 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,751 root INFO copying build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,751 root INFO copying build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,752 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/os
2025-04-22 20:54:04,752 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/os/LC_MESSAGES
2025-04-22 20:54:04,752 root INFO copying build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/os/LC_MESSAGES
2025-04-22 20:54:04,752 root INFO copying build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/os/LC_MESSAGES
2025-04-22 20:54:04,752 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/tr
2025-04-22 20:54:04,752 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,752 root INFO copying build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,752 root INFO copying build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,753 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/io
2025-04-22 20:54:04,753 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/io/LC_MESSAGES
2025-04-22 20:54:04,753 root INFO copying build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/io/LC_MESSAGES
2025-04-22 20:54:04,753 root INFO copying build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/io/LC_MESSAGES
2025-04-22 20:54:04,753 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sl
2025-04-22 20:54:04,753 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,753 root INFO copying build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,754 root INFO copying build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,754 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sq
2025-04-22 20:54:04,754 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,754 root INFO copying build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,754 root INFO copying build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,754 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/az
2025-04-22 20:54:04,755 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/az/LC_MESSAGES
2025-04-22 20:54:04,755 root INFO copying build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/az/LC_MESSAGES
2025-04-22 20:54:04,755 root INFO copying build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/az/LC_MESSAGES
2025-04-22 20:54:04,755 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/eo
2025-04-22 20:54:04,755 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,755 root INFO copying build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,755 root INFO copying build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,756 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/pt_BR
2025-04-22 20:54:04,756 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,756 root INFO copying build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,756 root INFO copying build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,756 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/pl
2025-04-22 20:54:04,756 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,756 root INFO copying build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,757 root INFO copying build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,757 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/gd
2025-04-22 20:54:04,757 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,757 root INFO copying build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,757 root INFO copying build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,757 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/hr
2025-04-22 20:54:04,757 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,757 root INFO copying build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,758 root INFO copying build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,758 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ru
2025-04-22 20:54:04,758 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,758 root INFO copying build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,758 root INFO copying build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,759 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es
2025-04-22 20:54:04,759 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es/LC_MESSAGES
2025-04-22 20:54:04,759 root INFO copying build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es/LC_MESSAGES
2025-04-22 20:54:04,759 root INFO copying build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es/LC_MESSAGES
2025-04-22 20:54:04,759 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/id
2025-04-22 20:54:04,759 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/id/LC_MESSAGES
2025-04-22 20:54:04,759 root INFO copying build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/id/LC_MESSAGES
2025-04-22 20:54:04,760 root INFO copying build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/id/LC_MESSAGES
2025-04-22 20:54:04,760 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/fi
2025-04-22 20:54:04,760 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,760 root INFO copying build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,760 root INFO copying build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,760 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/mk
2025-04-22 20:54:04,760 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,761 root INFO copying build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,761 root INFO copying build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,761 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/hi
2025-04-22 20:54:04,761 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,761 root INFO copying build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,761 root INFO copying build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,761 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/kab
2025-04-22 20:54:04,762 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,762 root INFO copying build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,762 root INFO copying build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,762 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/hsb
2025-04-22 20:54:04,762 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,762 root INFO copying build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,762 root INFO copying build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,763 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sk
2025-04-22 20:54:04,763 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,763 root INFO copying build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,763 root INFO copying build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,763 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/lt
2025-04-22 20:54:04,763 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,763 root INFO copying build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,764 root INFO copying build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,764 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/de
2025-04-22 20:54:04,764 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/de/LC_MESSAGES
2025-04-22 20:54:04,764 root INFO copying build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/de/LC_MESSAGES
2025-04-22 20:54:04,764 root INFO copying build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/de/LC_MESSAGES
2025-04-22 20:54:04,764 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/it
2025-04-22 20:54:04,764 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/it/LC_MESSAGES
2025-04-22 20:54:04,764 root INFO copying build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/it/LC_MESSAGES
2025-04-22 20:54:04,765 root INFO copying build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/it/LC_MESSAGES
2025-04-22 20:54:04,765 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/my
2025-04-22 20:54:04,765 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/my/LC_MESSAGES
2025-04-22 20:54:04,765 root INFO copying build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/my/LC_MESSAGES
2025-04-22 20:54:04,765 root INFO copying build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/my/LC_MESSAGES
2025-04-22 20:54:04,765 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sr
2025-04-22 20:54:04,765 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,766 root INFO copying build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,766 root INFO copying build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,766 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/bs
2025-04-22 20:54:04,766 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,766 root INFO copying build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,766 root INFO copying build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,767 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ro
2025-04-22 20:54:04,767 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,767 root INFO copying build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,767 root INFO copying build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,767 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ky
2025-04-22 20:54:04,767 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,767 root INFO copying build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,767 root INFO copying build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,768 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/fr
2025-04-22 20:54:04,768 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,768 root INFO copying build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,768 root INFO copying build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,768 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ar
2025-04-22 20:54:04,768 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,768 root INFO copying build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,769 root INFO copying build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,769 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es_AR
2025-04-22 20:54:04,769 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,769 root INFO copying build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,769 root INFO copying build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,769 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/vi
2025-04-22 20:54:04,769 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,770 root INFO copying build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,770 root INFO copying build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,770 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ckb
2025-04-22 20:54:04,770 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,770 root INFO copying build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,770 root INFO copying build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,770 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sv
2025-04-22 20:54:04,771 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,771 root INFO copying build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,771 root INFO copying build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,771 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/zh_Hant
2025-04-22 20:54:04,771 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,771 root INFO copying build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,771 root INFO copying build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,772 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/kk
2025-04-22 20:54:04,772 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,772 root INFO copying build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,772 root INFO copying build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,772 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es_CO
2025-04-22 20:54:04,772 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,772 root INFO copying build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,773 root INFO copying build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,773 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/be
2025-04-22 20:54:04,773 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/be/LC_MESSAGES
2025-04-22 20:54:04,773 root INFO copying build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/be/LC_MESSAGES
2025-04-22 20:54:04,773 root INFO copying build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/be/LC_MESSAGES
2025-04-22 20:54:04,773 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/udm
2025-04-22 20:54:04,774 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,774 root INFO copying build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,774 root INFO copying build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,774 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ml
2025-04-22 20:54:04,774 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,774 root INFO copying build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,774 root INFO copying build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,775 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ar_DZ
2025-04-22 20:54:04,775 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,775 root INFO copying build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,775 root INFO copying build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,775 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ms
2025-04-22 20:54:04,775 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,775 root INFO copying build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,776 root INFO copying build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,776 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ast
2025-04-22 20:54:04,776 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,776 root INFO copying build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,776 root INFO copying build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,776 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/zh_Hans
2025-04-22 20:54:04,776 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,776 root INFO copying build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,777 root INFO copying build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,777 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ur
2025-04-22 20:54:04,777 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,777 root INFO copying build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,777 root INFO copying build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,777 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ia
2025-04-22 20:54:04,778 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,778 root INFO copying build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,778 root INFO copying build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,778 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/hu
2025-04-22 20:54:04,778 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,778 root INFO copying build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,778 root INFO copying build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,779 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ta
2025-04-22 20:54:04,779 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,779 root INFO copying build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,779 root INFO copying build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,779 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/eu
2025-04-22 20:54:04,779 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,779 root INFO copying build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,780 root INFO copying build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,780 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es_MX
2025-04-22 20:54:04,780 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,780 root INFO copying build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,780 root INFO copying build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,780 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/th
2025-04-22 20:54:04,780 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/th/LC_MESSAGES
2025-04-22 20:54:04,780 root INFO copying build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/th/LC_MESSAGES
2025-04-22 20:54:04,781 root INFO copying build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/th/LC_MESSAGES
2025-04-22 20:54:04,781 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/nb
2025-04-22 20:54:04,781 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,781 root INFO copying build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,781 root INFO copying build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,781 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/mn
2025-04-22 20:54:04,782 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,782 root INFO copying build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,782 root INFO copying build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,782 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ka
2025-04-22 20:54:04,782 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,782 root INFO copying build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,782 root INFO copying build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,783 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/nl
2025-04-22 20:54:04,783 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,783 root INFO copying build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,783 root INFO copying build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,783 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/te
2025-04-22 20:54:04,783 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/te/LC_MESSAGES
2025-04-22 20:54:04,783 root INFO copying build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/te/LC_MESSAGES
2025-04-22 20:54:04,784 root INFO copying build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/te/LC_MESSAGES
2025-04-22 20:54:04,784 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/pt
2025-04-22 20:54:04,784 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,784 root INFO copying build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,784 root INFO copying build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,784 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/bn
2025-04-22 20:54:04,784 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,784 root INFO copying build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,785 root INFO copying build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,785 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/he
2025-04-22 20:54:04,785 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/he/LC_MESSAGES
2025-04-22 20:54:04,785 root INFO copying build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/he/LC_MESSAGES
2025-04-22 20:54:04,785 root INFO copying build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/he/LC_MESSAGES
2025-04-22 20:54:04,786 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/br
2025-04-22 20:54:04,786 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/br/LC_MESSAGES
2025-04-22 20:54:04,786 root INFO copying build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/br/LC_MESSAGES
2025-04-22 20:54:04,786 root INFO copying build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/br/LC_MESSAGES
2025-04-22 20:54:04,786 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/fa
2025-04-22 20:54:04,786 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,786 root INFO copying build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,787 root INFO copying build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,787 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/tg
2025-04-22 20:54:04,787 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,787 root INFO copying build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,787 root INFO copying build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,787 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/km
2025-04-22 20:54:04,787 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/km/LC_MESSAGES
2025-04-22 20:54:04,787 root INFO copying build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/km/LC_MESSAGES
2025-04-22 20:54:04,788 root INFO copying build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/km/LC_MESSAGES
2025-04-22 20:54:04,788 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/da
2025-04-22 20:54:04,788 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/da/LC_MESSAGES
2025-04-22 20:54:04,788 root INFO copying build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/da/LC_MESSAGES
2025-04-22 20:54:04,788 root INFO copying build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/locale/da/LC_MESSAGES
2025-04-22 20:54:04,788 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/templates
2025-04-22 20:54:04,789 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:04,789 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/model_index.html -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:04,789 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/index.html -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:04,789 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/model_detail.html -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:04,789 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/view_index.html -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:04,789 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/view_detail.html -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:04,789 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/template_tag_index.html -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:04,790 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/missing_docutils.html -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:04,790 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/template_detail.html -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:04,790 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/bookmarklets.html -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:04,790 root INFO copying build/lib/django/contrib/admindocs/templates/admin_doc/template_filter_index.html -> build/bdist.linux-aarch64/wheel/django/contrib/admindocs/templates/admin_doc
2025-04-22 20:54:04,790 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/syndication
2025-04-22 20:54:04,790 root INFO copying build/lib/django/contrib/syndication/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/syndication
2025-04-22 20:54:04,790 root INFO copying build/lib/django/contrib/syndication/views.py -> build/bdist.linux-aarch64/wheel/django/contrib/syndication
2025-04-22 20:54:04,791 root INFO copying build/lib/django/contrib/syndication/apps.py -> build/bdist.linux-aarch64/wheel/django/contrib/syndication
2025-04-22 20:54:04,791 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres
2025-04-22 20:54:04,791 root INFO copying build/lib/django/contrib/postgres/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres
2025-04-22 20:54:04,791 root INFO copying build/lib/django/contrib/postgres/functions.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres
2025-04-22 20:54:04,791 root INFO copying build/lib/django/contrib/postgres/signals.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres
2025-04-22 20:54:04,791 root INFO copying build/lib/django/contrib/postgres/lookups.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres
2025-04-22 20:54:04,791 root INFO copying build/lib/django/contrib/postgres/validators.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres
2025-04-22 20:54:04,792 root INFO copying build/lib/django/contrib/postgres/operations.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres
2025-04-22 20:54:04,792 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/jinja2
2025-04-22 20:54:04,792 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/jinja2/postgres
2025-04-22 20:54:04,792 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/jinja2/postgres/widgets
2025-04-22 20:54:04,792 root INFO copying build/lib/django/contrib/postgres/jinja2/postgres/widgets/split_array.html -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/jinja2/postgres/widgets
2025-04-22 20:54:04,792 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/aggregates
2025-04-22 20:54:04,792 root INFO copying build/lib/django/contrib/postgres/aggregates/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/aggregates
2025-04-22 20:54:04,793 root INFO copying build/lib/django/contrib/postgres/aggregates/statistics.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/aggregates
2025-04-22 20:54:04,793 root INFO copying build/lib/django/contrib/postgres/aggregates/general.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/aggregates
2025-04-22 20:54:04,793 root INFO copying build/lib/django/contrib/postgres/aggregates/mixins.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/aggregates
2025-04-22 20:54:04,793 root INFO copying build/lib/django/contrib/postgres/apps.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres
2025-04-22 20:54:04,793 root INFO copying build/lib/django/contrib/postgres/indexes.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres
2025-04-22 20:54:04,793 root INFO copying build/lib/django/contrib/postgres/utils.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres
2025-04-22 20:54:04,793 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/fields
2025-04-22 20:54:04,793 root INFO copying build/lib/django/contrib/postgres/fields/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/fields
2025-04-22 20:54:04,794 root INFO copying build/lib/django/contrib/postgres/fields/hstore.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/fields
2025-04-22 20:54:04,794 root INFO copying build/lib/django/contrib/postgres/fields/citext.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/fields
2025-04-22 20:54:04,794 root INFO copying build/lib/django/contrib/postgres/fields/jsonb.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/fields
2025-04-22 20:54:04,794 root INFO copying build/lib/django/contrib/postgres/fields/utils.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/fields
2025-04-22 20:54:04,794 root INFO copying build/lib/django/contrib/postgres/fields/ranges.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/fields
2025-04-22 20:54:04,794 root INFO copying build/lib/django/contrib/postgres/fields/array.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/fields
2025-04-22 20:54:04,795 root INFO copying build/lib/django/contrib/postgres/expressions.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres
2025-04-22 20:54:04,795 root INFO copying build/lib/django/contrib/postgres/search.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres
2025-04-22 20:54:04,795 root INFO copying build/lib/django/contrib/postgres/constraints.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres
2025-04-22 20:54:04,795 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale
2025-04-22 20:54:04,795 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/lv
2025-04-22 20:54:04,795 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,795 root INFO copying build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,796 root INFO copying build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,796 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/en_AU
2025-04-22 20:54:04,796 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,796 root INFO copying build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,796 root INFO copying build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,796 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ca
2025-04-22 20:54:04,796 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,796 root INFO copying build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,797 root INFO copying build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,797 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/el
2025-04-22 20:54:04,797 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/el/LC_MESSAGES
2025-04-22 20:54:04,797 root INFO copying build/lib/django/contrib/postgres/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/el/LC_MESSAGES
2025-04-22 20:54:04,797 root INFO copying build/lib/django/contrib/postgres/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/el/LC_MESSAGES
2025-04-22 20:54:04,797 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/af
2025-04-22 20:54:04,797 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/af/LC_MESSAGES
2025-04-22 20:54:04,797 root INFO copying build/lib/django/contrib/postgres/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/af/LC_MESSAGES
2025-04-22 20:54:04,798 root INFO copying build/lib/django/contrib/postgres/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/af/LC_MESSAGES
2025-04-22 20:54:04,798 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/en
2025-04-22 20:54:04,798 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/en/LC_MESSAGES
2025-04-22 20:54:04,798 root INFO copying build/lib/django/contrib/postgres/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/en/LC_MESSAGES
2025-04-22 20:54:04,798 root INFO copying build/lib/django/contrib/postgres/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/en/LC_MESSAGES
2025-04-22 20:54:04,798 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/dsb
2025-04-22 20:54:04,798 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,798 root INFO copying build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,799 root INFO copying build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,799 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/et
2025-04-22 20:54:04,799 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/et/LC_MESSAGES
2025-04-22 20:54:04,799 root INFO copying build/lib/django/contrib/postgres/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/et/LC_MESSAGES
2025-04-22 20:54:04,799 root INFO copying build/lib/django/contrib/postgres/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/et/LC_MESSAGES
2025-04-22 20:54:04,799 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/nn
2025-04-22 20:54:04,799 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,799 root INFO copying build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,800 root INFO copying build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,800 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ko
2025-04-22 20:54:04,800 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,800 root INFO copying build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,800 root INFO copying build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,800 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/is
2025-04-22 20:54:04,800 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/is/LC_MESSAGES
2025-04-22 20:54:04,800 root INFO copying build/lib/django/contrib/postgres/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/is/LC_MESSAGES
2025-04-22 20:54:04,801 root INFO copying build/lib/django/contrib/postgres/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/is/LC_MESSAGES
2025-04-22 20:54:04,801 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ne
2025-04-22 20:54:04,801 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,801 root INFO copying build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,801 root INFO copying build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,801 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sr_Latn
2025-04-22 20:54:04,801 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,801 root INFO copying build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,802 root INFO copying build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,802 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/bg
2025-04-22 20:54:04,802 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,802 root INFO copying build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,802 root INFO copying build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,802 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/gl
2025-04-22 20:54:04,802 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,802 root INFO copying build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,803 root INFO copying build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,803 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/uk
2025-04-22 20:54:04,803 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,803 root INFO copying build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,803 root INFO copying build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,803 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/uz
2025-04-22 20:54:04,803 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,803 root INFO copying build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,804 root INFO copying build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,804 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ja
2025-04-22 20:54:04,804 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,804 root INFO copying build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,804 root INFO copying build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,804 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/cs
2025-04-22 20:54:04,804 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,804 root INFO copying build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,805 root INFO copying build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,805 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/tr
2025-04-22 20:54:04,805 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,805 root INFO copying build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,805 root INFO copying build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,805 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sl
2025-04-22 20:54:04,805 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,805 root INFO copying build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,806 root INFO copying build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,806 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sq
2025-04-22 20:54:04,806 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,806 root INFO copying build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,806 root INFO copying build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,806 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/az
2025-04-22 20:54:04,806 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/az/LC_MESSAGES
2025-04-22 20:54:04,806 root INFO copying build/lib/django/contrib/postgres/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/az/LC_MESSAGES
2025-04-22 20:54:04,807 root INFO copying build/lib/django/contrib/postgres/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/az/LC_MESSAGES
2025-04-22 20:54:04,807 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/eo
2025-04-22 20:54:04,807 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,807 root INFO copying build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,807 root INFO copying build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,807 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/pt_BR
2025-04-22 20:54:04,807 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,807 root INFO copying build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,808 root INFO copying build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,808 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/pl
2025-04-22 20:54:04,808 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,808 root INFO copying build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,808 root INFO copying build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,808 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/gd
2025-04-22 20:54:04,808 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,809 root INFO copying build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,809 root INFO copying build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,809 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/hr
2025-04-22 20:54:04,809 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,809 root INFO copying build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,809 root INFO copying build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,809 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ru
2025-04-22 20:54:04,809 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,810 root INFO copying build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,810 root INFO copying build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,810 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/es
2025-04-22 20:54:04,810 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/es/LC_MESSAGES
2025-04-22 20:54:04,810 root INFO copying build/lib/django/contrib/postgres/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/es/LC_MESSAGES
2025-04-22 20:54:04,810 root INFO copying build/lib/django/contrib/postgres/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/es/LC_MESSAGES
2025-04-22 20:54:04,810 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/id
2025-04-22 20:54:04,811 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/id/LC_MESSAGES
2025-04-22 20:54:04,811 root INFO copying build/lib/django/contrib/postgres/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/id/LC_MESSAGES
2025-04-22 20:54:04,811 root INFO copying build/lib/django/contrib/postgres/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/id/LC_MESSAGES
2025-04-22 20:54:04,811 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/fi
2025-04-22 20:54:04,811 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,811 root INFO copying build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,811 root INFO copying build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,811 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/mk
2025-04-22 20:54:04,812 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,812 root INFO copying build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,812 root INFO copying build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,812 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/hsb
2025-04-22 20:54:04,812 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,812 root INFO copying build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,812 root INFO copying build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,812 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sk
2025-04-22 20:54:04,813 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,813 root INFO copying build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,813 root INFO copying build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,813 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/lt
2025-04-22 20:54:04,813 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,813 root INFO copying build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,813 root INFO copying build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,813 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/de
2025-04-22 20:54:04,814 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/de/LC_MESSAGES
2025-04-22 20:54:04,814 root INFO copying build/lib/django/contrib/postgres/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/de/LC_MESSAGES
2025-04-22 20:54:04,814 root INFO copying build/lib/django/contrib/postgres/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/de/LC_MESSAGES
2025-04-22 20:54:04,814 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/it
2025-04-22 20:54:04,814 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/it/LC_MESSAGES
2025-04-22 20:54:04,814 root INFO copying build/lib/django/contrib/postgres/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/it/LC_MESSAGES
2025-04-22 20:54:04,814 root INFO copying build/lib/django/contrib/postgres/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/it/LC_MESSAGES
2025-04-22 20:54:04,815 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sr
2025-04-22 20:54:04,815 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,815 root INFO copying build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,815 root INFO copying build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,815 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ro
2025-04-22 20:54:04,815 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,815 root INFO copying build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,815 root INFO copying build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,816 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ky
2025-04-22 20:54:04,816 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,816 root INFO copying build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,816 root INFO copying build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,816 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/fr
2025-04-22 20:54:04,816 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,816 root INFO copying build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,816 root INFO copying build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,817 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ar
2025-04-22 20:54:04,817 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,817 root INFO copying build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,817 root INFO copying build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,817 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/hy
2025-04-22 20:54:04,817 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,817 root INFO copying build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,818 root INFO copying build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,818 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/es_AR
2025-04-22 20:54:04,818 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,818 root INFO copying build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,818 root INFO copying build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,818 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ckb
2025-04-22 20:54:04,818 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,818 root INFO copying build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,819 root INFO copying build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,819 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sv
2025-04-22 20:54:04,819 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,819 root INFO copying build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,819 root INFO copying build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,819 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/zh_Hant
2025-04-22 20:54:04,819 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,819 root INFO copying build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,820 root INFO copying build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,820 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/kk
2025-04-22 20:54:04,820 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,820 root INFO copying build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,820 root INFO copying build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,820 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/es_CO
2025-04-22 20:54:04,820 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,820 root INFO copying build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,821 root INFO copying build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,821 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/be
2025-04-22 20:54:04,821 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/be/LC_MESSAGES
2025-04-22 20:54:04,821 root INFO copying build/lib/django/contrib/postgres/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/be/LC_MESSAGES
2025-04-22 20:54:04,821 root INFO copying build/lib/django/contrib/postgres/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/be/LC_MESSAGES
2025-04-22 20:54:04,821 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ml
2025-04-22 20:54:04,821 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,822 root INFO copying build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,822 root INFO copying build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,822 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ar_DZ
2025-04-22 20:54:04,822 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,822 root INFO copying build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,822 root INFO copying build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,822 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ms
2025-04-22 20:54:04,823 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,823 root INFO copying build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,823 root INFO copying build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,823 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/zh_Hans
2025-04-22 20:54:04,823 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,823 root INFO copying build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,823 root INFO copying build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,823 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ia
2025-04-22 20:54:04,824 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,824 root INFO copying build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,824 root INFO copying build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,824 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/hu
2025-04-22 20:54:04,824 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,824 root INFO copying build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,824 root INFO copying build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,824 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/eu
2025-04-22 20:54:04,825 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,825 root INFO copying build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,825 root INFO copying build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,825 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/es_MX
2025-04-22 20:54:04,825 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,825 root INFO copying build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,825 root INFO copying build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,826 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/tk
2025-04-22 20:54:04,826 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,826 root INFO copying build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,826 root INFO copying build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/tk/LC_MESSAGES
2025-04-22 20:54:04,826 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/nb
2025-04-22 20:54:04,826 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,826 root INFO copying build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,827 root INFO copying build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,827 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/mn
2025-04-22 20:54:04,827 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,827 root INFO copying build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,827 root INFO copying build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,827 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ka
2025-04-22 20:54:04,827 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,827 root INFO copying build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,828 root INFO copying build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,828 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/nl
2025-04-22 20:54:04,828 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,828 root INFO copying build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,828 root INFO copying build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,828 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/pt
2025-04-22 20:54:04,828 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,828 root INFO copying build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,829 root INFO copying build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,829 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/he
2025-04-22 20:54:04,829 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/he/LC_MESSAGES
2025-04-22 20:54:04,829 root INFO copying build/lib/django/contrib/postgres/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/he/LC_MESSAGES
2025-04-22 20:54:04,829 root INFO copying build/lib/django/contrib/postgres/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/he/LC_MESSAGES
2025-04-22 20:54:04,829 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/fa
2025-04-22 20:54:04,829 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,829 root INFO copying build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,830 root INFO copying build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,830 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/tg
2025-04-22 20:54:04,830 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,830 root INFO copying build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,830 root INFO copying build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,830 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/da
2025-04-22 20:54:04,830 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/da/LC_MESSAGES
2025-04-22 20:54:04,830 root INFO copying build/lib/django/contrib/postgres/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/da/LC_MESSAGES
2025-04-22 20:54:04,831 root INFO copying build/lib/django/contrib/postgres/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/locale/da/LC_MESSAGES
2025-04-22 20:54:04,831 root INFO copying build/lib/django/contrib/postgres/serializers.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres
2025-04-22 20:54:04,831 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/templates
2025-04-22 20:54:04,831 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/templates/postgres
2025-04-22 20:54:04,831 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/templates/postgres/widgets
2025-04-22 20:54:04,831 root INFO copying build/lib/django/contrib/postgres/templates/postgres/widgets/split_array.html -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/templates/postgres/widgets
2025-04-22 20:54:04,831 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/postgres/forms
2025-04-22 20:54:04,831 root INFO copying build/lib/django/contrib/postgres/forms/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/forms
2025-04-22 20:54:04,832 root INFO copying build/lib/django/contrib/postgres/forms/hstore.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/forms
2025-04-22 20:54:04,832 root INFO copying build/lib/django/contrib/postgres/forms/ranges.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/forms
2025-04-22 20:54:04,832 root INFO copying build/lib/django/contrib/postgres/forms/array.py -> build/bdist.linux-aarch64/wheel/django/contrib/postgres/forms
2025-04-22 20:54:04,832 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis
2025-04-22 20:54:04,832 root INFO copying build/lib/django/contrib/gis/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis
2025-04-22 20:54:04,832 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/db
2025-04-22 20:54:04,832 root INFO copying build/lib/django/contrib/gis/db/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db
2025-04-22 20:54:04,833 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/db/models
2025-04-22 20:54:04,833 root INFO copying build/lib/django/contrib/gis/db/models/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/models
2025-04-22 20:54:04,833 root INFO copying build/lib/django/contrib/gis/db/models/functions.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/models
2025-04-22 20:54:04,833 root INFO copying build/lib/django/contrib/gis/db/models/lookups.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/models
2025-04-22 20:54:04,833 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/db/models/sql
2025-04-22 20:54:04,833 root INFO copying build/lib/django/contrib/gis/db/models/sql/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/models/sql
2025-04-22 20:54:04,833 root INFO copying build/lib/django/contrib/gis/db/models/sql/conversion.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/models/sql
2025-04-22 20:54:04,834 root INFO copying build/lib/django/contrib/gis/db/models/fields.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/models
2025-04-22 20:54:04,834 root INFO copying build/lib/django/contrib/gis/db/models/aggregates.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/models
2025-04-22 20:54:04,834 root INFO copying build/lib/django/contrib/gis/db/models/proxy.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/models
2025-04-22 20:54:04,834 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends
2025-04-22 20:54:04,834 root INFO copying build/lib/django/contrib/gis/db/backends/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends
2025-04-22 20:54:04,834 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:04,834 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:04,835 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/schema.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:04,835 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/features.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:04,835 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/operations.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:04,835 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/models.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:04,835 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/introspection.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:04,835 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/base.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:04,835 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/client.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:04,836 root INFO copying build/lib/django/contrib/gis/db/backends/spatialite/adapter.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/spatialite
2025-04-22 20:54:04,836 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/base
2025-04-22 20:54:04,836 root INFO copying build/lib/django/contrib/gis/db/backends/base/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/base
2025-04-22 20:54:04,836 root INFO copying build/lib/django/contrib/gis/db/backends/base/features.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/base
2025-04-22 20:54:04,836 root INFO copying build/lib/django/contrib/gis/db/backends/base/operations.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/base
2025-04-22 20:54:04,836 root INFO copying build/lib/django/contrib/gis/db/backends/base/models.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/base
2025-04-22 20:54:04,836 root INFO copying build/lib/django/contrib/gis/db/backends/base/adapter.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/base
2025-04-22 20:54:04,837 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:04,837 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:04,837 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/schema.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:04,837 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/features.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:04,837 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/operations.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:04,837 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/models.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:04,837 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/introspection.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:04,838 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/base.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:04,838 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/const.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:04,838 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/pgraster.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:04,838 root INFO copying build/lib/django/contrib/gis/db/backends/postgis/adapter.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/postgis
2025-04-22 20:54:04,838 root INFO copying build/lib/django/contrib/gis/db/backends/utils.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends
2025-04-22 20:54:04,838 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:04,838 root INFO copying build/lib/django/contrib/gis/db/backends/oracle/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:04,839 root INFO copying build/lib/django/contrib/gis/db/backends/oracle/schema.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:04,839 root INFO copying build/lib/django/contrib/gis/db/backends/oracle/features.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:04,839 root INFO copying build/lib/django/contrib/gis/db/backends/oracle/operations.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:04,839 root INFO copying build/lib/django/contrib/gis/db/backends/oracle/models.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:04,839 root INFO copying build/lib/django/contrib/gis/db/backends/oracle/introspection.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:04,839 root INFO copying build/lib/django/contrib/gis/db/backends/oracle/base.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:04,839 root INFO copying build/lib/django/contrib/gis/db/backends/oracle/adapter.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/oracle
2025-04-22 20:54:04,840 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/mysql
2025-04-22 20:54:04,840 root INFO copying build/lib/django/contrib/gis/db/backends/mysql/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/mysql
2025-04-22 20:54:04,840 root INFO copying build/lib/django/contrib/gis/db/backends/mysql/schema.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/mysql
2025-04-22 20:54:04,840 root INFO copying build/lib/django/contrib/gis/db/backends/mysql/features.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/mysql
2025-04-22 20:54:04,840 root INFO copying build/lib/django/contrib/gis/db/backends/mysql/operations.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/mysql
2025-04-22 20:54:04,840 root INFO copying build/lib/django/contrib/gis/db/backends/mysql/introspection.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/mysql
2025-04-22 20:54:04,840 root INFO copying build/lib/django/contrib/gis/db/backends/mysql/base.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/db/backends/mysql
2025-04-22 20:54:04,840 root INFO copying build/lib/django/contrib/gis/views.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis
2025-04-22 20:54:04,841 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/sitemaps
2025-04-22 20:54:04,841 root INFO copying build/lib/django/contrib/gis/sitemaps/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/sitemaps
2025-04-22 20:54:04,841 root INFO copying build/lib/django/contrib/gis/sitemaps/views.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/sitemaps
2025-04-22 20:54:04,841 root INFO copying build/lib/django/contrib/gis/sitemaps/kml.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/sitemaps
2025-04-22 20:54:04,841 root INFO copying build/lib/django/contrib/gis/apps.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis
2025-04-22 20:54:04,841 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/utils
2025-04-22 20:54:04,841 root INFO copying build/lib/django/contrib/gis/utils/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/utils
2025-04-22 20:54:04,842 root INFO copying build/lib/django/contrib/gis/utils/layermapping.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/utils
2025-04-22 20:54:04,842 root INFO copying build/lib/django/contrib/gis/utils/srs.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/utils
2025-04-22 20:54:04,842 root INFO copying build/lib/django/contrib/gis/utils/ogrinfo.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/utils
2025-04-22 20:54:04,842 root INFO copying build/lib/django/contrib/gis/utils/ogrinspect.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/utils
2025-04-22 20:54:04,842 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/geoip2
2025-04-22 20:54:04,843 root INFO copying build/lib/django/contrib/gis/geoip2/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geoip2
2025-04-22 20:54:04,843 root INFO copying build/lib/django/contrib/gis/geoip2/resources.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geoip2
2025-04-22 20:54:04,843 root INFO copying build/lib/django/contrib/gis/geoip2/base.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geoip2
2025-04-22 20:54:04,843 root INFO copying build/lib/django/contrib/gis/geometry.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis
2025-04-22 20:54:04,843 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/static
2025-04-22 20:54:04,843 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/static/gis
2025-04-22 20:54:04,843 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/static/gis/css
2025-04-22 20:54:04,843 root INFO copying build/lib/django/contrib/gis/static/gis/css/ol3.css -> build/bdist.linux-aarch64/wheel/django/contrib/gis/static/gis/css
2025-04-22 20:54:04,844 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/static/gis/img
2025-04-22 20:54:04,844 root INFO copying build/lib/django/contrib/gis/static/gis/img/draw_line_off.svg -> build/bdist.linux-aarch64/wheel/django/contrib/gis/static/gis/img
2025-04-22 20:54:04,844 root INFO copying build/lib/django/contrib/gis/static/gis/img/draw_point_on.svg -> build/bdist.linux-aarch64/wheel/django/contrib/gis/static/gis/img
2025-04-22 20:54:04,844 root INFO copying build/lib/django/contrib/gis/static/gis/img/draw_polygon_on.svg -> build/bdist.linux-aarch64/wheel/django/contrib/gis/static/gis/img
2025-04-22 20:54:04,844 root INFO copying build/lib/django/contrib/gis/static/gis/img/draw_polygon_off.svg -> build/bdist.linux-aarch64/wheel/django/contrib/gis/static/gis/img
2025-04-22 20:54:04,844 root INFO copying build/lib/django/contrib/gis/static/gis/img/draw_line_on.svg -> build/bdist.linux-aarch64/wheel/django/contrib/gis/static/gis/img
2025-04-22 20:54:04,844 root INFO copying build/lib/django/contrib/gis/static/gis/img/draw_point_off.svg -> build/bdist.linux-aarch64/wheel/django/contrib/gis/static/gis/img
2025-04-22 20:54:04,845 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/static/gis/js
2025-04-22 20:54:04,845 root INFO copying build/lib/django/contrib/gis/static/gis/js/OLMapWidget.js -> build/bdist.linux-aarch64/wheel/django/contrib/gis/static/gis/js
2025-04-22 20:54:04,845 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/management
2025-04-22 20:54:04,845 root INFO copying build/lib/django/contrib/gis/management/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/management
2025-04-22 20:54:04,845 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/management/commands
2025-04-22 20:54:04,845 root INFO copying build/lib/django/contrib/gis/management/commands/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/management/commands
2025-04-22 20:54:04,845 root INFO copying build/lib/django/contrib/gis/management/commands/inspectdb.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/management/commands
2025-04-22 20:54:04,846 root INFO copying build/lib/django/contrib/gis/management/commands/ogrinspect.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/management/commands
2025-04-22 20:54:04,846 root INFO copying build/lib/django/contrib/gis/feeds.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis
2025-04-22 20:54:04,846 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/serializers
2025-04-22 20:54:04,846 root INFO copying build/lib/django/contrib/gis/serializers/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/serializers
2025-04-22 20:54:04,846 root INFO copying build/lib/django/contrib/gis/serializers/geojson.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/serializers
2025-04-22 20:54:04,846 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/admin
2025-04-22 20:54:04,846 root INFO copying build/lib/django/contrib/gis/admin/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/admin
2025-04-22 20:54:04,846 root INFO copying build/lib/django/contrib/gis/admin/options.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/admin
2025-04-22 20:54:04,847 root INFO copying build/lib/django/contrib/gis/admin/widgets.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/admin
2025-04-22 20:54:04,847 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale
2025-04-22 20:54:04,847 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/lv
2025-04-22 20:54:04,847 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,847 root INFO copying build/lib/django/contrib/gis/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,847 root INFO copying build/lib/django/contrib/gis/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,847 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sw
2025-04-22 20:54:04,848 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,848 root INFO copying build/lib/django/contrib/gis/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,848 root INFO copying build/lib/django/contrib/gis/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,848 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/en_AU
2025-04-22 20:54:04,848 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,848 root INFO copying build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,848 root INFO copying build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,849 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/mr
2025-04-22 20:54:04,849 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,849 root INFO copying build/lib/django/contrib/gis/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,849 root INFO copying build/lib/django/contrib/gis/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,849 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/lb
2025-04-22 20:54:04,849 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,849 root INFO copying build/lib/django/contrib/gis/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,849 root INFO copying build/lib/django/contrib/gis/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,850 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ca
2025-04-22 20:54:04,850 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,850 root INFO copying build/lib/django/contrib/gis/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,850 root INFO copying build/lib/django/contrib/gis/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,850 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/en_GB
2025-04-22 20:54:04,850 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,850 root INFO copying build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,850 root INFO copying build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,851 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/el
2025-04-22 20:54:04,851 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/el/LC_MESSAGES
2025-04-22 20:54:04,851 root INFO copying build/lib/django/contrib/gis/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/el/LC_MESSAGES
2025-04-22 20:54:04,851 root INFO copying build/lib/django/contrib/gis/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/el/LC_MESSAGES
2025-04-22 20:54:04,851 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es_VE
2025-04-22 20:54:04,851 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,851 root INFO copying build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,851 root INFO copying build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,852 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/af
2025-04-22 20:54:04,852 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/af/LC_MESSAGES
2025-04-22 20:54:04,852 root INFO copying build/lib/django/contrib/gis/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/af/LC_MESSAGES
2025-04-22 20:54:04,852 root INFO copying build/lib/django/contrib/gis/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/af/LC_MESSAGES
2025-04-22 20:54:04,852 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/en
2025-04-22 20:54:04,852 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/en/LC_MESSAGES
2025-04-22 20:54:04,852 root INFO copying build/lib/django/contrib/gis/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/en/LC_MESSAGES
2025-04-22 20:54:04,852 root INFO copying build/lib/django/contrib/gis/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/en/LC_MESSAGES
2025-04-22 20:54:04,853 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/dsb
2025-04-22 20:54:04,853 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,853 root INFO copying build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,853 root INFO copying build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,853 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/et
2025-04-22 20:54:04,853 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/et/LC_MESSAGES
2025-04-22 20:54:04,853 root INFO copying build/lib/django/contrib/gis/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/et/LC_MESSAGES
2025-04-22 20:54:04,853 root INFO copying build/lib/django/contrib/gis/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/et/LC_MESSAGES
2025-04-22 20:54:04,854 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/nn
2025-04-22 20:54:04,854 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,854 root INFO copying build/lib/django/contrib/gis/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,854 root INFO copying build/lib/django/contrib/gis/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,854 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/cy
2025-04-22 20:54:04,854 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,854 root INFO copying build/lib/django/contrib/gis/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,854 root INFO copying build/lib/django/contrib/gis/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,855 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ko
2025-04-22 20:54:04,855 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,855 root INFO copying build/lib/django/contrib/gis/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,855 root INFO copying build/lib/django/contrib/gis/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,855 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/is
2025-04-22 20:54:04,855 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/is/LC_MESSAGES
2025-04-22 20:54:04,855 root INFO copying build/lib/django/contrib/gis/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/is/LC_MESSAGES
2025-04-22 20:54:04,856 root INFO copying build/lib/django/contrib/gis/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/is/LC_MESSAGES
2025-04-22 20:54:04,856 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/pa
2025-04-22 20:54:04,856 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,856 root INFO copying build/lib/django/contrib/gis/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,856 root INFO copying build/lib/django/contrib/gis/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,856 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/tt
2025-04-22 20:54:04,856 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,856 root INFO copying build/lib/django/contrib/gis/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,857 root INFO copying build/lib/django/contrib/gis/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,857 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ne
2025-04-22 20:54:04,857 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,857 root INFO copying build/lib/django/contrib/gis/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,857 root INFO copying build/lib/django/contrib/gis/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,857 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sr_Latn
2025-04-22 20:54:04,857 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,857 root INFO copying build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,858 root INFO copying build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,858 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/fy
2025-04-22 20:54:04,858 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,858 root INFO copying build/lib/django/contrib/gis/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,858 root INFO copying build/lib/django/contrib/gis/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,858 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/bg
2025-04-22 20:54:04,858 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,858 root INFO copying build/lib/django/contrib/gis/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,859 root INFO copying build/lib/django/contrib/gis/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,859 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ga
2025-04-22 20:54:04,859 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,859 root INFO copying build/lib/django/contrib/gis/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,859 root INFO copying build/lib/django/contrib/gis/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,859 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/gl
2025-04-22 20:54:04,859 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,859 root INFO copying build/lib/django/contrib/gis/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,860 root INFO copying build/lib/django/contrib/gis/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,860 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/uk
2025-04-22 20:54:04,860 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,860 root INFO copying build/lib/django/contrib/gis/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,860 root INFO copying build/lib/django/contrib/gis/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,860 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/kn
2025-04-22 20:54:04,860 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,860 root INFO copying build/lib/django/contrib/gis/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,861 root INFO copying build/lib/django/contrib/gis/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,861 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ja
2025-04-22 20:54:04,861 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,861 root INFO copying build/lib/django/contrib/gis/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,861 root INFO copying build/lib/django/contrib/gis/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,861 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/cs
2025-04-22 20:54:04,861 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,861 root INFO copying build/lib/django/contrib/gis/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,862 root INFO copying build/lib/django/contrib/gis/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,862 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/os
2025-04-22 20:54:04,862 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/os/LC_MESSAGES
2025-04-22 20:54:04,862 root INFO copying build/lib/django/contrib/gis/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/os/LC_MESSAGES
2025-04-22 20:54:04,862 root INFO copying build/lib/django/contrib/gis/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/os/LC_MESSAGES
2025-04-22 20:54:04,862 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/tr
2025-04-22 20:54:04,862 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,862 root INFO copying build/lib/django/contrib/gis/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,863 root INFO copying build/lib/django/contrib/gis/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,863 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/io
2025-04-22 20:54:04,863 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/io/LC_MESSAGES
2025-04-22 20:54:04,863 root INFO copying build/lib/django/contrib/gis/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/io/LC_MESSAGES
2025-04-22 20:54:04,863 root INFO copying build/lib/django/contrib/gis/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/io/LC_MESSAGES
2025-04-22 20:54:04,863 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sl
2025-04-22 20:54:04,863 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,863 root INFO copying build/lib/django/contrib/gis/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,864 root INFO copying build/lib/django/contrib/gis/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,864 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sq
2025-04-22 20:54:04,864 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,864 root INFO copying build/lib/django/contrib/gis/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,864 root INFO copying build/lib/django/contrib/gis/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,864 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/az
2025-04-22 20:54:04,864 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/az/LC_MESSAGES
2025-04-22 20:54:04,864 root INFO copying build/lib/django/contrib/gis/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/az/LC_MESSAGES
2025-04-22 20:54:04,864 root INFO copying build/lib/django/contrib/gis/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/az/LC_MESSAGES
2025-04-22 20:54:04,865 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/eo
2025-04-22 20:54:04,865 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,865 root INFO copying build/lib/django/contrib/gis/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,865 root INFO copying build/lib/django/contrib/gis/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,865 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/pt_BR
2025-04-22 20:54:04,865 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,865 root INFO copying build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,866 root INFO copying build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,866 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/pl
2025-04-22 20:54:04,866 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,866 root INFO copying build/lib/django/contrib/gis/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,866 root INFO copying build/lib/django/contrib/gis/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,866 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/gd
2025-04-22 20:54:04,866 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,866 root INFO copying build/lib/django/contrib/gis/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,867 root INFO copying build/lib/django/contrib/gis/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,867 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hr
2025-04-22 20:54:04,867 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,867 root INFO copying build/lib/django/contrib/gis/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,867 root INFO copying build/lib/django/contrib/gis/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,867 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ru
2025-04-22 20:54:04,867 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,867 root INFO copying build/lib/django/contrib/gis/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,868 root INFO copying build/lib/django/contrib/gis/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,868 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es
2025-04-22 20:54:04,868 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es/LC_MESSAGES
2025-04-22 20:54:04,868 root INFO copying build/lib/django/contrib/gis/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es/LC_MESSAGES
2025-04-22 20:54:04,868 root INFO copying build/lib/django/contrib/gis/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es/LC_MESSAGES
2025-04-22 20:54:04,868 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/id
2025-04-22 20:54:04,869 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/id/LC_MESSAGES
2025-04-22 20:54:04,869 root INFO copying build/lib/django/contrib/gis/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/id/LC_MESSAGES
2025-04-22 20:54:04,869 root INFO copying build/lib/django/contrib/gis/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/id/LC_MESSAGES
2025-04-22 20:54:04,869 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/fi
2025-04-22 20:54:04,869 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,869 root INFO copying build/lib/django/contrib/gis/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,869 root INFO copying build/lib/django/contrib/gis/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,869 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/mk
2025-04-22 20:54:04,870 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,870 root INFO copying build/lib/django/contrib/gis/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,870 root INFO copying build/lib/django/contrib/gis/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,870 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hi
2025-04-22 20:54:04,870 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,870 root INFO copying build/lib/django/contrib/gis/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,870 root INFO copying build/lib/django/contrib/gis/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,870 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hsb
2025-04-22 20:54:04,871 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,871 root INFO copying build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,871 root INFO copying build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,871 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sk
2025-04-22 20:54:04,871 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,871 root INFO copying build/lib/django/contrib/gis/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,871 root INFO copying build/lib/django/contrib/gis/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,871 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/lt
2025-04-22 20:54:04,872 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,872 root INFO copying build/lib/django/contrib/gis/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,872 root INFO copying build/lib/django/contrib/gis/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,872 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/de
2025-04-22 20:54:04,872 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/de/LC_MESSAGES
2025-04-22 20:54:04,872 root INFO copying build/lib/django/contrib/gis/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/de/LC_MESSAGES
2025-04-22 20:54:04,872 root INFO copying build/lib/django/contrib/gis/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/de/LC_MESSAGES
2025-04-22 20:54:04,872 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/it
2025-04-22 20:54:04,873 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/it/LC_MESSAGES
2025-04-22 20:54:04,873 root INFO copying build/lib/django/contrib/gis/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/it/LC_MESSAGES
2025-04-22 20:54:04,873 root INFO copying build/lib/django/contrib/gis/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/it/LC_MESSAGES
2025-04-22 20:54:04,873 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/my
2025-04-22 20:54:04,873 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/my/LC_MESSAGES
2025-04-22 20:54:04,873 root INFO copying build/lib/django/contrib/gis/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/my/LC_MESSAGES
2025-04-22 20:54:04,873 root INFO copying build/lib/django/contrib/gis/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/my/LC_MESSAGES
2025-04-22 20:54:04,873 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sr
2025-04-22 20:54:04,874 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,874 root INFO copying build/lib/django/contrib/gis/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,874 root INFO copying build/lib/django/contrib/gis/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,874 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/bs
2025-04-22 20:54:04,874 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,874 root INFO copying build/lib/django/contrib/gis/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,874 root INFO copying build/lib/django/contrib/gis/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,874 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ro
2025-04-22 20:54:04,875 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,875 root INFO copying build/lib/django/contrib/gis/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,875 root INFO copying build/lib/django/contrib/gis/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,875 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ky
2025-04-22 20:54:04,875 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,875 root INFO copying build/lib/django/contrib/gis/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,875 root INFO copying build/lib/django/contrib/gis/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,875 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/fr
2025-04-22 20:54:04,876 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,876 root INFO copying build/lib/django/contrib/gis/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,876 root INFO copying build/lib/django/contrib/gis/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,876 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ar
2025-04-22 20:54:04,876 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,876 root INFO copying build/lib/django/contrib/gis/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,876 root INFO copying build/lib/django/contrib/gis/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,876 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hy
2025-04-22 20:54:04,877 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,877 root INFO copying build/lib/django/contrib/gis/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,877 root INFO copying build/lib/django/contrib/gis/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,877 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es_AR
2025-04-22 20:54:04,877 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,877 root INFO copying build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,877 root INFO copying build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,877 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/vi
2025-04-22 20:54:04,878 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,878 root INFO copying build/lib/django/contrib/gis/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,878 root INFO copying build/lib/django/contrib/gis/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,878 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ckb
2025-04-22 20:54:04,878 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,878 root INFO copying build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,878 root INFO copying build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,878 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sv
2025-04-22 20:54:04,879 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,879 root INFO copying build/lib/django/contrib/gis/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,879 root INFO copying build/lib/django/contrib/gis/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,879 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/zh_Hant
2025-04-22 20:54:04,879 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,879 root INFO copying build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,879 root INFO copying build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,879 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/kk
2025-04-22 20:54:04,880 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,880 root INFO copying build/lib/django/contrib/gis/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,880 root INFO copying build/lib/django/contrib/gis/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,880 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es_CO
2025-04-22 20:54:04,880 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,880 root INFO copying build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,880 root INFO copying build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,880 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/be
2025-04-22 20:54:04,881 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/be/LC_MESSAGES
2025-04-22 20:54:04,881 root INFO copying build/lib/django/contrib/gis/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/be/LC_MESSAGES
2025-04-22 20:54:04,881 root INFO copying build/lib/django/contrib/gis/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/be/LC_MESSAGES
2025-04-22 20:54:04,881 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/udm
2025-04-22 20:54:04,881 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,881 root INFO copying build/lib/django/contrib/gis/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,881 root INFO copying build/lib/django/contrib/gis/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,881 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ml
2025-04-22 20:54:04,882 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,882 root INFO copying build/lib/django/contrib/gis/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,882 root INFO copying build/lib/django/contrib/gis/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,882 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ar_DZ
2025-04-22 20:54:04,882 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,882 root INFO copying build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,882 root INFO copying build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,883 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ms
2025-04-22 20:54:04,883 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,883 root INFO copying build/lib/django/contrib/gis/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,883 root INFO copying build/lib/django/contrib/gis/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,883 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ast
2025-04-22 20:54:04,883 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,883 root INFO copying build/lib/django/contrib/gis/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,883 root INFO copying build/lib/django/contrib/gis/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,883 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/zh_Hans
2025-04-22 20:54:04,884 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,884 root INFO copying build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,884 root INFO copying build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,884 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ur
2025-04-22 20:54:04,884 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,884 root INFO copying build/lib/django/contrib/gis/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,884 root INFO copying build/lib/django/contrib/gis/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,884 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ia
2025-04-22 20:54:04,885 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,885 root INFO copying build/lib/django/contrib/gis/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,885 root INFO copying build/lib/django/contrib/gis/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ia/LC_MESSAGES
2025-04-22 20:54:04,885 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hu
2025-04-22 20:54:04,885 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,885 root INFO copying build/lib/django/contrib/gis/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,885 root INFO copying build/lib/django/contrib/gis/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/hu/LC_MESSAGES
2025-04-22 20:54:04,886 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ta
2025-04-22 20:54:04,886 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,886 root INFO copying build/lib/django/contrib/gis/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,886 root INFO copying build/lib/django/contrib/gis/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ta/LC_MESSAGES
2025-04-22 20:54:04,886 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/eu
2025-04-22 20:54:04,886 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,886 root INFO copying build/lib/django/contrib/gis/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,886 root INFO copying build/lib/django/contrib/gis/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/eu/LC_MESSAGES
2025-04-22 20:54:04,887 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es_MX
2025-04-22 20:54:04,887 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,887 root INFO copying build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,887 root INFO copying build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:04,887 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/th
2025-04-22 20:54:04,887 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/th/LC_MESSAGES
2025-04-22 20:54:04,887 root INFO copying build/lib/django/contrib/gis/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/th/LC_MESSAGES
2025-04-22 20:54:04,887 root INFO copying build/lib/django/contrib/gis/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/th/LC_MESSAGES
2025-04-22 20:54:04,888 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/nb
2025-04-22 20:54:04,888 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,888 root INFO copying build/lib/django/contrib/gis/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,888 root INFO copying build/lib/django/contrib/gis/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/nb/LC_MESSAGES
2025-04-22 20:54:04,888 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/mn
2025-04-22 20:54:04,888 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,888 root INFO copying build/lib/django/contrib/gis/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,888 root INFO copying build/lib/django/contrib/gis/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/mn/LC_MESSAGES
2025-04-22 20:54:04,889 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ka
2025-04-22 20:54:04,889 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,889 root INFO copying build/lib/django/contrib/gis/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,889 root INFO copying build/lib/django/contrib/gis/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/ka/LC_MESSAGES
2025-04-22 20:54:04,889 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/nl
2025-04-22 20:54:04,889 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,889 root INFO copying build/lib/django/contrib/gis/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,889 root INFO copying build/lib/django/contrib/gis/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/nl/LC_MESSAGES
2025-04-22 20:54:04,890 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/te
2025-04-22 20:54:04,890 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/te/LC_MESSAGES
2025-04-22 20:54:04,890 root INFO copying build/lib/django/contrib/gis/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/te/LC_MESSAGES
2025-04-22 20:54:04,890 root INFO copying build/lib/django/contrib/gis/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/te/LC_MESSAGES
2025-04-22 20:54:04,890 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/pt
2025-04-22 20:54:04,890 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,890 root INFO copying build/lib/django/contrib/gis/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,890 root INFO copying build/lib/django/contrib/gis/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/pt/LC_MESSAGES
2025-04-22 20:54:04,891 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/bn
2025-04-22 20:54:04,891 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,891 root INFO copying build/lib/django/contrib/gis/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,891 root INFO copying build/lib/django/contrib/gis/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/bn/LC_MESSAGES
2025-04-22 20:54:04,891 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/he
2025-04-22 20:54:04,891 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/he/LC_MESSAGES
2025-04-22 20:54:04,891 root INFO copying build/lib/django/contrib/gis/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/he/LC_MESSAGES
2025-04-22 20:54:04,891 root INFO copying build/lib/django/contrib/gis/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/he/LC_MESSAGES
2025-04-22 20:54:04,892 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/br
2025-04-22 20:54:04,892 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/br/LC_MESSAGES
2025-04-22 20:54:04,892 root INFO copying build/lib/django/contrib/gis/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/br/LC_MESSAGES
2025-04-22 20:54:04,892 root INFO copying build/lib/django/contrib/gis/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/br/LC_MESSAGES
2025-04-22 20:54:04,892 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/fa
2025-04-22 20:54:04,892 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,892 root INFO copying build/lib/django/contrib/gis/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,892 root INFO copying build/lib/django/contrib/gis/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/fa/LC_MESSAGES
2025-04-22 20:54:04,893 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/tg
2025-04-22 20:54:04,893 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,893 root INFO copying build/lib/django/contrib/gis/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,893 root INFO copying build/lib/django/contrib/gis/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/tg/LC_MESSAGES
2025-04-22 20:54:04,893 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/km
2025-04-22 20:54:04,893 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/km/LC_MESSAGES
2025-04-22 20:54:04,893 root INFO copying build/lib/django/contrib/gis/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/km/LC_MESSAGES
2025-04-22 20:54:04,893 root INFO copying build/lib/django/contrib/gis/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/km/LC_MESSAGES
2025-04-22 20:54:04,894 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/da
2025-04-22 20:54:04,894 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/da/LC_MESSAGES
2025-04-22 20:54:04,894 root INFO copying build/lib/django/contrib/gis/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/da/LC_MESSAGES
2025-04-22 20:54:04,894 root INFO copying build/lib/django/contrib/gis/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/gis/locale/da/LC_MESSAGES
2025-04-22 20:54:04,894 root INFO copying build/lib/django/contrib/gis/ptr.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis
2025-04-22 20:54:04,894 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/geos
2025-04-22 20:54:04,894 root INFO copying build/lib/django/contrib/gis/geos/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos
2025-04-22 20:54:04,895 root INFO copying build/lib/django/contrib/gis/geos/libgeos.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos
2025-04-22 20:54:04,895 root INFO copying build/lib/django/contrib/gis/geos/collections.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos
2025-04-22 20:54:04,895 root INFO copying build/lib/django/contrib/gis/geos/linestring.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos
2025-04-22 20:54:04,895 root INFO copying build/lib/django/contrib/gis/geos/LICENSE -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos
2025-04-22 20:54:04,895 root INFO copying build/lib/django/contrib/gis/geos/prepared.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos
2025-04-22 20:54:04,895 root INFO copying build/lib/django/contrib/gis/geos/io.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos
2025-04-22 20:54:04,895 root INFO copying build/lib/django/contrib/gis/geos/mutable_list.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos
2025-04-22 20:54:04,896 root INFO copying build/lib/django/contrib/gis/geos/point.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos
2025-04-22 20:54:04,896 root INFO copying build/lib/django/contrib/gis/geos/geometry.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos
2025-04-22 20:54:04,896 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/geos/prototypes
2025-04-22 20:54:04,896 root INFO copying build/lib/django/contrib/gis/geos/prototypes/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos/prototypes
2025-04-22 20:54:04,896 root INFO copying build/lib/django/contrib/gis/geos/prototypes/prepared.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos/prototypes
2025-04-22 20:54:04,896 root INFO copying build/lib/django/contrib/gis/geos/prototypes/io.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos/prototypes
2025-04-22 20:54:04,896 root INFO copying build/lib/django/contrib/gis/geos/prototypes/threadsafe.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos/prototypes
2025-04-22 20:54:04,897 root INFO copying build/lib/django/contrib/gis/geos/prototypes/errcheck.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos/prototypes
2025-04-22 20:54:04,897 root INFO copying build/lib/django/contrib/gis/geos/prototypes/misc.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos/prototypes
2025-04-22 20:54:04,897 root INFO copying build/lib/django/contrib/gis/geos/prototypes/predicates.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos/prototypes
2025-04-22 20:54:04,897 root INFO copying build/lib/django/contrib/gis/geos/prototypes/topology.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos/prototypes
2025-04-22 20:54:04,897 root INFO copying build/lib/django/contrib/gis/geos/prototypes/geom.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos/prototypes
2025-04-22 20:54:04,897 root INFO copying build/lib/django/contrib/gis/geos/prototypes/coordseq.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos/prototypes
2025-04-22 20:54:04,897 root INFO copying build/lib/django/contrib/gis/geos/polygon.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos
2025-04-22 20:54:04,898 root INFO copying build/lib/django/contrib/gis/geos/error.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos
2025-04-22 20:54:04,898 root INFO copying build/lib/django/contrib/gis/geos/factory.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos
2025-04-22 20:54:04,898 root INFO copying build/lib/django/contrib/gis/geos/base.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos
2025-04-22 20:54:04,898 root INFO copying build/lib/django/contrib/gis/geos/coordseq.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/geos
2025-04-22 20:54:04,898 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/templates
2025-04-22 20:54:04,898 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/templates/gis
2025-04-22 20:54:04,899 root INFO copying build/lib/django/contrib/gis/templates/gis/openlayers.html -> build/bdist.linux-aarch64/wheel/django/contrib/gis/templates/gis
2025-04-22 20:54:04,899 root INFO copying build/lib/django/contrib/gis/templates/gis/openlayers-osm.html -> build/bdist.linux-aarch64/wheel/django/contrib/gis/templates/gis
2025-04-22 20:54:04,899 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/templates/gis/admin
2025-04-22 20:54:04,899 root INFO copying build/lib/django/contrib/gis/templates/gis/admin/osm.html -> build/bdist.linux-aarch64/wheel/django/contrib/gis/templates/gis/admin
2025-04-22 20:54:04,899 root INFO copying build/lib/django/contrib/gis/templates/gis/admin/openlayers.html -> build/bdist.linux-aarch64/wheel/django/contrib/gis/templates/gis/admin
2025-04-22 20:54:04,899 root INFO copying build/lib/django/contrib/gis/templates/gis/admin/openlayers.js -> build/bdist.linux-aarch64/wheel/django/contrib/gis/templates/gis/admin
2025-04-22 20:54:04,899 root INFO copying build/lib/django/contrib/gis/templates/gis/admin/osm.js -> build/bdist.linux-aarch64/wheel/django/contrib/gis/templates/gis/admin
2025-04-22 20:54:04,900 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/templates/gis/kml
2025-04-22 20:54:04,900 root INFO copying build/lib/django/contrib/gis/templates/gis/kml/placemarks.kml -> build/bdist.linux-aarch64/wheel/django/contrib/gis/templates/gis/kml
2025-04-22 20:54:04,900 root INFO copying build/lib/django/contrib/gis/templates/gis/kml/base.kml -> build/bdist.linux-aarch64/wheel/django/contrib/gis/templates/gis/kml
2025-04-22 20:54:04,900 root INFO copying build/lib/django/contrib/gis/shortcuts.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis
2025-04-22 20:54:04,900 root INFO copying build/lib/django/contrib/gis/measure.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis
2025-04-22 20:54:04,900 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal
2025-04-22 20:54:04,900 root INFO copying build/lib/django/contrib/gis/gdal/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal
2025-04-22 20:54:04,900 root INFO copying build/lib/django/contrib/gis/gdal/geomtype.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal
2025-04-22 20:54:04,901 root INFO copying build/lib/django/contrib/gis/gdal/field.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal
2025-04-22 20:54:04,901 root INFO copying build/lib/django/contrib/gis/gdal/LICENSE -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal
2025-04-22 20:54:04,901 root INFO copying build/lib/django/contrib/gis/gdal/geometries.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal
2025-04-22 20:54:04,901 root INFO copying build/lib/django/contrib/gis/gdal/feature.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal
2025-04-22 20:54:04,901 root INFO copying build/lib/django/contrib/gis/gdal/envelope.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal
2025-04-22 20:54:04,901 root INFO copying build/lib/django/contrib/gis/gdal/libgdal.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal
2025-04-22 20:54:04,902 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal/raster
2025-04-22 20:54:04,902 root INFO copying build/lib/django/contrib/gis/gdal/raster/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal/raster
2025-04-22 20:54:04,902 root INFO copying build/lib/django/contrib/gis/gdal/raster/source.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal/raster
2025-04-22 20:54:04,902 root INFO copying build/lib/django/contrib/gis/gdal/raster/band.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal/raster
2025-04-22 20:54:04,902 root INFO copying build/lib/django/contrib/gis/gdal/raster/base.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal/raster
2025-04-22 20:54:04,902 root INFO copying build/lib/django/contrib/gis/gdal/raster/const.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal/raster
2025-04-22 20:54:04,902 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal/prototypes
2025-04-22 20:54:04,903 root INFO copying build/lib/django/contrib/gis/gdal/prototypes/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal/prototypes
2025-04-22 20:54:04,903 root INFO copying build/lib/django/contrib/gis/gdal/prototypes/generation.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal/prototypes
2025-04-22 20:54:04,903 root INFO copying build/lib/django/contrib/gis/gdal/prototypes/ds.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal/prototypes
2025-04-22 20:54:04,903 root INFO copying build/lib/django/contrib/gis/gdal/prototypes/raster.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal/prototypes
2025-04-22 20:54:04,903 root INFO copying build/lib/django/contrib/gis/gdal/prototypes/srs.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal/prototypes
2025-04-22 20:54:04,903 root INFO copying build/lib/django/contrib/gis/gdal/prototypes/errcheck.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal/prototypes
2025-04-22 20:54:04,903 root INFO copying build/lib/django/contrib/gis/gdal/prototypes/geom.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal/prototypes
2025-04-22 20:54:04,904 root INFO copying build/lib/django/contrib/gis/gdal/srs.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal
2025-04-22 20:54:04,904 root INFO copying build/lib/django/contrib/gis/gdal/error.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal
2025-04-22 20:54:04,904 root INFO copying build/lib/django/contrib/gis/gdal/datasource.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal
2025-04-22 20:54:04,904 root INFO copying build/lib/django/contrib/gis/gdal/driver.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal
2025-04-22 20:54:04,904 root INFO copying build/lib/django/contrib/gis/gdal/layer.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal
2025-04-22 20:54:04,904 root INFO copying build/lib/django/contrib/gis/gdal/base.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/gdal
2025-04-22 20:54:04,904 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/gis/forms
2025-04-22 20:54:04,905 root INFO copying build/lib/django/contrib/gis/forms/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/forms
2025-04-22 20:54:04,905 root INFO copying build/lib/django/contrib/gis/forms/widgets.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/forms
2025-04-22 20:54:04,905 root INFO copying build/lib/django/contrib/gis/forms/fields.py -> build/bdist.linux-aarch64/wheel/django/contrib/gis/forms
2025-04-22 20:54:04,905 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin
2025-04-22 20:54:04,905 root INFO copying build/lib/django/contrib/admin/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin
2025-04-22 20:54:04,905 root INFO copying build/lib/django/contrib/admin/options.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin
2025-04-22 20:54:04,906 root INFO copying build/lib/django/contrib/admin/widgets.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin
2025-04-22 20:54:04,906 root INFO copying build/lib/django/contrib/admin/forms.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin
2025-04-22 20:54:04,906 root INFO copying build/lib/django/contrib/admin/decorators.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin
2025-04-22 20:54:04,906 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/views
2025-04-22 20:54:04,906 root INFO copying build/lib/django/contrib/admin/views/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin/views
2025-04-22 20:54:04,906 root INFO copying build/lib/django/contrib/admin/views/decorators.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin/views
2025-04-22 20:54:04,907 root INFO copying build/lib/django/contrib/admin/views/autocomplete.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin/views
2025-04-22 20:54:04,907 root INFO copying build/lib/django/contrib/admin/views/main.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin/views
2025-04-22 20:54:04,907 root INFO copying build/lib/django/contrib/admin/filters.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin
2025-04-22 20:54:04,907 root INFO copying build/lib/django/contrib/admin/exceptions.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin
2025-04-22 20:54:04,907 root INFO copying build/lib/django/contrib/admin/models.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin
2025-04-22 20:54:04,907 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/migrations
2025-04-22 20:54:04,907 root INFO copying build/lib/django/contrib/admin/migrations/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin/migrations
2025-04-22 20:54:04,908 root INFO copying build/lib/django/contrib/admin/migrations/0002_logentry_remove_auto_add.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin/migrations
2025-04-22 20:54:04,908 root INFO copying build/lib/django/contrib/admin/migrations/0001_initial.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin/migrations
2025-04-22 20:54:04,908 root INFO copying build/lib/django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin/migrations
2025-04-22 20:54:04,908 root INFO copying build/lib/django/contrib/admin/apps.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin
2025-04-22 20:54:04,908 root INFO copying build/lib/django/contrib/admin/utils.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin
2025-04-22 20:54:04,908 root INFO copying build/lib/django/contrib/admin/checks.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin
2025-04-22 20:54:04,909 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/static
2025-04-22 20:54:04,909 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin
2025-04-22 20:54:04,909 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,909 root INFO copying build/lib/django/contrib/admin/static/admin/css/changelists.css -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,909 root INFO copying build/lib/django/contrib/admin/static/admin/css/autocomplete.css -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,909 root INFO copying build/lib/django/contrib/admin/static/admin/css/dashboard.css -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,909 root INFO copying build/lib/django/contrib/admin/static/admin/css/responsive.css -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,910 root INFO copying build/lib/django/contrib/admin/static/admin/css/dark_mode.css -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,910 root INFO copying build/lib/django/contrib/admin/static/admin/css/responsive_rtl.css -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,910 root INFO copying build/lib/django/contrib/admin/static/admin/css/rtl.css -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,910 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css/vendor
2025-04-22 20:54:04,910 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css/vendor/select2
2025-04-22 20:54:04,910 root INFO copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css/vendor/select2
2025-04-22 20:54:04,910 root INFO copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/select2.min.css -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css/vendor/select2
2025-04-22 20:54:04,910 root INFO copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/select2.css -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css/vendor/select2
2025-04-22 20:54:04,911 root INFO copying build/lib/django/contrib/admin/static/admin/css/nav_sidebar.css -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,911 root INFO copying build/lib/django/contrib/admin/static/admin/css/widgets.css -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,911 root INFO copying build/lib/django/contrib/admin/static/admin/css/forms.css -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,911 root INFO copying build/lib/django/contrib/admin/static/admin/css/base.css -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,911 root INFO copying build/lib/django/contrib/admin/static/admin/css/login.css -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/css
2025-04-22 20:54:04,911 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,912 root INFO copying build/lib/django/contrib/admin/static/admin/img/search.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,912 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-clock.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,912 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-viewlink.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,912 root INFO copying build/lib/django/contrib/admin/static/admin/img/LICENSE -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,912 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-changelink.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,912 root INFO copying build/lib/django/contrib/admin/static/admin/img/inline-delete.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,912 root INFO copying build/lib/django/contrib/admin/static/admin/img/sorting-icons.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,913 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-no.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,913 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-yes.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,913 root INFO copying build/lib/django/contrib/admin/static/admin/img/tooltag-add.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,913 root INFO copying build/lib/django/contrib/admin/static/admin/img/selector-icons.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,913 root INFO copying build/lib/django/contrib/admin/static/admin/img/tooltag-arrowright.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,913 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img/gis
2025-04-22 20:54:04,913 root INFO copying build/lib/django/contrib/admin/static/admin/img/gis/move_vertex_on.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img/gis
2025-04-22 20:54:04,913 root INFO copying build/lib/django/contrib/admin/static/admin/img/gis/move_vertex_off.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img/gis
2025-04-22 20:54:04,914 root INFO copying build/lib/django/contrib/admin/static/admin/img/README.txt -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,914 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-unknown-alt.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,914 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-alert.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,914 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-addlink.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,914 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-unknown.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,914 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-calendar.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,914 root INFO copying build/lib/django/contrib/admin/static/admin/img/calendar-icons.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,915 root INFO copying build/lib/django/contrib/admin/static/admin/img/icon-deletelink.svg -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/img
2025-04-22 20:54:04,915 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,915 root INFO copying build/lib/django/contrib/admin/static/admin/js/urlify.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,915 root INFO copying build/lib/django/contrib/admin/static/admin/js/jquery.init.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,915 root INFO copying build/lib/django/contrib/admin/static/admin/js/filters.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,916 root INFO copying build/lib/django/contrib/admin/static/admin/js/SelectBox.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,916 root INFO copying build/lib/django/contrib/admin/static/admin/js/autocomplete.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,916 root INFO copying build/lib/django/contrib/admin/static/admin/js/SelectFilter2.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,916 root INFO copying build/lib/django/contrib/admin/static/admin/js/nav_sidebar.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,916 root INFO copying build/lib/django/contrib/admin/static/admin/js/inlines.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,916 root INFO copying build/lib/django/contrib/admin/static/admin/js/change_form.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,916 root INFO copying build/lib/django/contrib/admin/static/admin/js/core.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,917 root INFO copying build/lib/django/contrib/admin/static/admin/js/theme.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,917 root INFO copying build/lib/django/contrib/admin/static/admin/js/popup_response.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,917 root INFO copying build/lib/django/contrib/admin/static/admin/js/collapse.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,917 root INFO copying build/lib/django/contrib/admin/static/admin/js/prepopulate_init.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,917 root INFO copying build/lib/django/contrib/admin/static/admin/js/calendar.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,917 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/admin
2025-04-22 20:54:04,917 root INFO copying build/lib/django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/admin
2025-04-22 20:54:04,918 root INFO copying build/lib/django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/admin
2025-04-22 20:54:04,918 root INFO copying build/lib/django/contrib/admin/static/admin/js/cancel.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,918 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor
2025-04-22 20:54:04,918 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/xregexp
2025-04-22 20:54:04,918 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/xregexp
2025-04-22 20:54:04,918 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/xregexp
2025-04-22 20:54:04,919 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/xregexp
2025-04-22 20:54:04,919 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/jquery
2025-04-22 20:54:04,919 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/jquery
2025-04-22 20:54:04,919 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/jquery.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/jquery
2025-04-22 20:54:04,920 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/jquery
2025-04-22 20:54:04,920 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2
2025-04-22 20:54:04,920 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2
2025-04-22 20:54:04,921 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/select2.full.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2
2025-04-22 20:54:04,921 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2
2025-04-22 20:54:04,921 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,921 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,922 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,922 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,922 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,922 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,922 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,922 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,922 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,923 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,923 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,923 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,923 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,923 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,923 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,923 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,923 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,924 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,924 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,924 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,924 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,924 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,924 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,924 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,925 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,925 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,925 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,925 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,925 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,925 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,925 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,926 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,926 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,926 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,926 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,926 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,926 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,926 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,927 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,927 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,927 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,927 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,927 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,927 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,927 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,927 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,928 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,928 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,928 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,928 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,928 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,928 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,928 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,929 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,929 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,929 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,929 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,929 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,929 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,929 root INFO copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
2025-04-22 20:54:04,930 root INFO copying build/lib/django/contrib/admin/static/admin/js/prepopulate.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,930 root INFO copying build/lib/django/contrib/admin/static/admin/js/actions.js -> build/bdist.linux-aarch64/wheel/django/contrib/admin/static/admin/js
2025-04-22 20:54:04,930 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/templatetags
2025-04-22 20:54:04,930 root INFO copying build/lib/django/contrib/admin/templatetags/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templatetags
2025-04-22 20:54:04,930 root INFO copying build/lib/django/contrib/admin/templatetags/log.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templatetags
2025-04-22 20:54:04,930 root INFO copying build/lib/django/contrib/admin/templatetags/admin_urls.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templatetags
2025-04-22 20:54:04,930 root INFO copying build/lib/django/contrib/admin/templatetags/admin_modify.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templatetags
2025-04-22 20:54:04,931 root INFO copying build/lib/django/contrib/admin/templatetags/admin_list.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templatetags
2025-04-22 20:54:04,931 root INFO copying build/lib/django/contrib/admin/templatetags/base.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templatetags
2025-04-22 20:54:04,931 root INFO copying build/lib/django/contrib/admin/tests.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin
2025-04-22 20:54:04,931 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale
2025-04-22 20:54:04,931 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lv
2025-04-22 20:54:04,931 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,932 root INFO copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,932 root INFO copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,932 root INFO copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,932 root INFO copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lv/LC_MESSAGES
2025-04-22 20:54:04,932 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sw
2025-04-22 20:54:04,932 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,932 root INFO copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,933 root INFO copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,933 root INFO copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,933 root INFO copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sw/LC_MESSAGES
2025-04-22 20:54:04,933 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en_AU
2025-04-22 20:54:04,933 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,933 root INFO copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,933 root INFO copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,934 root INFO copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,934 root INFO copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:04,934 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mr
2025-04-22 20:54:04,934 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,934 root INFO copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,934 root INFO copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,935 root INFO copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,935 root INFO copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mr/LC_MESSAGES
2025-04-22 20:54:04,935 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lb
2025-04-22 20:54:04,935 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,935 root INFO copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,935 root INFO copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,935 root INFO copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,935 root INFO copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lb/LC_MESSAGES
2025-04-22 20:54:04,936 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ca
2025-04-22 20:54:04,936 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,936 root INFO copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,936 root INFO copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,936 root INFO copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,936 root INFO copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ca/LC_MESSAGES
2025-04-22 20:54:04,937 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en_GB
2025-04-22 20:54:04,937 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,937 root INFO copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,937 root INFO copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,937 root INFO copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,937 root INFO copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:04,937 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/el
2025-04-22 20:54:04,938 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 20:54:04,938 root INFO copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 20:54:04,938 root INFO copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 20:54:04,938 root INFO copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 20:54:04,938 root INFO copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/el/LC_MESSAGES
2025-04-22 20:54:04,938 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_VE
2025-04-22 20:54:04,938 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,939 root INFO copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,939 root INFO copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,939 root INFO copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,939 root INFO copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:04,939 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/af
2025-04-22 20:54:04,939 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 20:54:04,939 root INFO copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 20:54:04,940 root INFO copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 20:54:04,940 root INFO copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 20:54:04,940 root INFO copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/af/LC_MESSAGES
2025-04-22 20:54:04,940 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en
2025-04-22 20:54:04,940 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 20:54:04,940 root INFO copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 20:54:04,941 root INFO copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 20:54:04,941 root INFO copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 20:54:04,941 root INFO copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/en/LC_MESSAGES
2025-04-22 20:54:04,941 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/dsb
2025-04-22 20:54:04,941 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,941 root INFO copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,941 root INFO copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,942 root INFO copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,942 root INFO copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES
2025-04-22 20:54:04,942 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/et
2025-04-22 20:54:04,942 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 20:54:04,942 root INFO copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 20:54:04,942 root INFO copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 20:54:04,943 root INFO copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 20:54:04,943 root INFO copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/et/LC_MESSAGES
2025-04-22 20:54:04,943 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nn
2025-04-22 20:54:04,943 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,943 root INFO copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,943 root INFO copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,943 root INFO copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,944 root INFO copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nn/LC_MESSAGES
2025-04-22 20:54:04,944 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/cy
2025-04-22 20:54:04,944 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,944 root INFO copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,944 root INFO copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,944 root INFO copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,944 root INFO copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/cy/LC_MESSAGES
2025-04-22 20:54:04,945 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ko
2025-04-22 20:54:04,945 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,945 root INFO copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,945 root INFO copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,945 root INFO copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,945 root INFO copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ko/LC_MESSAGES
2025-04-22 20:54:04,946 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/is
2025-04-22 20:54:04,946 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 20:54:04,946 root INFO copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 20:54:04,946 root INFO copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 20:54:04,946 root INFO copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 20:54:04,946 root INFO copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/is/LC_MESSAGES
2025-04-22 20:54:04,946 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pa
2025-04-22 20:54:04,947 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,947 root INFO copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,947 root INFO copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,947 root INFO copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,947 root INFO copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pa/LC_MESSAGES
2025-04-22 20:54:04,947 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tt
2025-04-22 20:54:04,947 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,948 root INFO copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,948 root INFO copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,948 root INFO copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,948 root INFO copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tt/LC_MESSAGES
2025-04-22 20:54:04,948 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ne
2025-04-22 20:54:04,948 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,948 root INFO copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,949 root INFO copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,949 root INFO copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,949 root INFO copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ne/LC_MESSAGES
2025-04-22 20:54:04,949 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sr_Latn
2025-04-22 20:54:04,949 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,949 root INFO copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,949 root INFO copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,950 root INFO copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,950 root INFO copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:04,950 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fy
2025-04-22 20:54:04,950 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,950 root INFO copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,950 root INFO copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,951 root INFO copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,951 root INFO copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fy/LC_MESSAGES
2025-04-22 20:54:04,951 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bg
2025-04-22 20:54:04,951 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,951 root INFO copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,951 root INFO copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,951 root INFO copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,952 root INFO copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bg/LC_MESSAGES
2025-04-22 20:54:04,952 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ga
2025-04-22 20:54:04,952 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,952 root INFO copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,952 root INFO copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,952 root INFO copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,952 root INFO copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ga/LC_MESSAGES
2025-04-22 20:54:04,953 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/gl
2025-04-22 20:54:04,953 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,953 root INFO copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,953 root INFO copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,953 root INFO copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,953 root INFO copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/gl/LC_MESSAGES
2025-04-22 20:54:04,954 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/uk
2025-04-22 20:54:04,954 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,954 root INFO copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,954 root INFO copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,954 root INFO copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,954 root INFO copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/uk/LC_MESSAGES
2025-04-22 20:54:04,954 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/uz
2025-04-22 20:54:04,955 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,955 root INFO copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,955 root INFO copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,955 root INFO copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,955 root INFO copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/uz/LC_MESSAGES
2025-04-22 20:54:04,955 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kn
2025-04-22 20:54:04,955 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,955 root INFO copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,956 root INFO copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,956 root INFO copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,956 root INFO copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kn/LC_MESSAGES
2025-04-22 20:54:04,956 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ja
2025-04-22 20:54:04,956 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,956 root INFO copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,956 root INFO copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,957 root INFO copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,957 root INFO copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ja/LC_MESSAGES
2025-04-22 20:54:04,957 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/cs
2025-04-22 20:54:04,957 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,957 root INFO copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,957 root INFO copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,958 root INFO copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,958 root INFO copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/cs/LC_MESSAGES
2025-04-22 20:54:04,958 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/os
2025-04-22 20:54:04,958 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 20:54:04,958 root INFO copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 20:54:04,958 root INFO copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 20:54:04,958 root INFO copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 20:54:04,959 root INFO copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/os/LC_MESSAGES
2025-04-22 20:54:04,959 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tr
2025-04-22 20:54:04,959 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,959 root INFO copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,959 root INFO copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,959 root INFO copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,960 root INFO copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tr/LC_MESSAGES
2025-04-22 20:54:04,960 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/io
2025-04-22 20:54:04,960 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 20:54:04,960 root INFO copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 20:54:04,960 root INFO copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 20:54:04,960 root INFO copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 20:54:04,960 root INFO copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/io/LC_MESSAGES
2025-04-22 20:54:04,961 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sl
2025-04-22 20:54:04,961 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,961 root INFO copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,961 root INFO copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,961 root INFO copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,961 root INFO copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sl/LC_MESSAGES
2025-04-22 20:54:04,961 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sq
2025-04-22 20:54:04,962 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,962 root INFO copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,962 root INFO copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,962 root INFO copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,962 root INFO copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sq/LC_MESSAGES
2025-04-22 20:54:04,962 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/az
2025-04-22 20:54:04,963 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 20:54:04,963 root INFO copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 20:54:04,963 root INFO copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 20:54:04,963 root INFO copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 20:54:04,963 root INFO copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/az/LC_MESSAGES
2025-04-22 20:54:04,963 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/eo
2025-04-22 20:54:04,963 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,964 root INFO copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,964 root INFO copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,964 root INFO copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,964 root INFO copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/eo/LC_MESSAGES
2025-04-22 20:54:04,964 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pt_BR
2025-04-22 20:54:04,964 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,964 root INFO copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,965 root INFO copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,965 root INFO copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,965 root INFO copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:04,965 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pl
2025-04-22 20:54:04,965 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,965 root INFO copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,965 root INFO copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,966 root INFO copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,966 root INFO copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pl/LC_MESSAGES
2025-04-22 20:54:04,966 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/gd
2025-04-22 20:54:04,966 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,966 root INFO copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,966 root INFO copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,966 root INFO copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,967 root INFO copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/gd/LC_MESSAGES
2025-04-22 20:54:04,967 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hr
2025-04-22 20:54:04,967 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,967 root INFO copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,967 root INFO copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,967 root INFO copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,967 root INFO copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hr/LC_MESSAGES
2025-04-22 20:54:04,968 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ru
2025-04-22 20:54:04,968 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,968 root INFO copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,968 root INFO copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,968 root INFO copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,969 root INFO copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ru/LC_MESSAGES
2025-04-22 20:54:04,969 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es
2025-04-22 20:54:04,969 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 20:54:04,969 root INFO copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 20:54:04,969 root INFO copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 20:54:04,969 root INFO copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 20:54:04,969 root INFO copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es/LC_MESSAGES
2025-04-22 20:54:04,970 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/id
2025-04-22 20:54:04,970 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 20:54:04,970 root INFO copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 20:54:04,970 root INFO copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 20:54:04,970 root INFO copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 20:54:04,970 root INFO copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/id/LC_MESSAGES
2025-04-22 20:54:04,971 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fi
2025-04-22 20:54:04,971 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,971 root INFO copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,971 root INFO copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,971 root INFO copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,971 root INFO copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fi/LC_MESSAGES
2025-04-22 20:54:04,971 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mk
2025-04-22 20:54:04,972 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,972 root INFO copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,972 root INFO copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,972 root INFO copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,972 root INFO copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mk/LC_MESSAGES
2025-04-22 20:54:04,972 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hi
2025-04-22 20:54:04,973 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,973 root INFO copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,973 root INFO copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,973 root INFO copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,973 root INFO copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hi/LC_MESSAGES
2025-04-22 20:54:04,973 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kab
2025-04-22 20:54:04,973 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,973 root INFO copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,974 root INFO copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,974 root INFO copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,974 root INFO copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kab/LC_MESSAGES
2025-04-22 20:54:04,974 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hsb
2025-04-22 20:54:04,974 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,974 root INFO copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,974 root INFO copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,975 root INFO copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,975 root INFO copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES
2025-04-22 20:54:04,975 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sk
2025-04-22 20:54:04,975 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,975 root INFO copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,975 root INFO copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,976 root INFO copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,976 root INFO copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sk/LC_MESSAGES
2025-04-22 20:54:04,976 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lt
2025-04-22 20:54:04,976 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,976 root INFO copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,976 root INFO copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,976 root INFO copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,977 root INFO copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/lt/LC_MESSAGES
2025-04-22 20:54:04,977 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/de
2025-04-22 20:54:04,977 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 20:54:04,977 root INFO copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 20:54:04,977 root INFO copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 20:54:04,977 root INFO copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 20:54:04,977 root INFO copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/de/LC_MESSAGES
2025-04-22 20:54:04,978 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/it
2025-04-22 20:54:04,978 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 20:54:04,978 root INFO copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 20:54:04,978 root INFO copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 20:54:04,978 root INFO copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 20:54:04,978 root INFO copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/it/LC_MESSAGES
2025-04-22 20:54:04,979 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/my
2025-04-22 20:54:04,979 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 20:54:04,979 root INFO copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 20:54:04,979 root INFO copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 20:54:04,979 root INFO copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 20:54:04,979 root INFO copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/my/LC_MESSAGES
2025-04-22 20:54:04,979 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sr
2025-04-22 20:54:04,980 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,980 root INFO copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,980 root INFO copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,980 root INFO copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,980 root INFO copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sr/LC_MESSAGES
2025-04-22 20:54:04,980 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bs
2025-04-22 20:54:04,980 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,981 root INFO copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,981 root INFO copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,981 root INFO copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,981 root INFO copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bs/LC_MESSAGES
2025-04-22 20:54:04,981 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ro
2025-04-22 20:54:04,981 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,981 root INFO copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,982 root INFO copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,982 root INFO copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,982 root INFO copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ro/LC_MESSAGES
2025-04-22 20:54:04,982 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ky
2025-04-22 20:54:04,982 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,982 root INFO copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,982 root INFO copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,983 root INFO copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,983 root INFO copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ky/LC_MESSAGES
2025-04-22 20:54:04,983 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fr
2025-04-22 20:54:04,983 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,983 root INFO copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,983 root INFO copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,984 root INFO copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,984 root INFO copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fr/LC_MESSAGES
2025-04-22 20:54:04,984 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/am
2025-04-22 20:54:04,984 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/am/LC_MESSAGES
2025-04-22 20:54:04,984 root INFO copying build/lib/django/contrib/admin/locale/am/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/am/LC_MESSAGES
2025-04-22 20:54:04,984 root INFO copying build/lib/django/contrib/admin/locale/am/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/am/LC_MESSAGES
2025-04-22 20:54:04,984 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ar
2025-04-22 20:54:04,985 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,985 root INFO copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,985 root INFO copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,985 root INFO copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,985 root INFO copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ar/LC_MESSAGES
2025-04-22 20:54:04,985 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hy
2025-04-22 20:54:04,985 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,986 root INFO copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,986 root INFO copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,986 root INFO copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,986 root INFO copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hy/LC_MESSAGES
2025-04-22 20:54:04,986 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_AR
2025-04-22 20:54:04,986 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,986 root INFO copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,987 root INFO copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,987 root INFO copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,987 root INFO copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:04,987 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/vi
2025-04-22 20:54:04,987 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,987 root INFO copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,988 root INFO copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,988 root INFO copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,988 root INFO copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/vi/LC_MESSAGES
2025-04-22 20:54:04,988 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ckb
2025-04-22 20:54:04,988 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,988 root INFO copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,988 root INFO copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,989 root INFO copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,989 root INFO copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ckb/LC_MESSAGES
2025-04-22 20:54:04,989 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sv
2025-04-22 20:54:04,989 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,989 root INFO copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,989 root INFO copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,989 root INFO copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,990 root INFO copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/sv/LC_MESSAGES
2025-04-22 20:54:04,990 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/zh_Hant
2025-04-22 20:54:04,990 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,990 root INFO copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,990 root INFO copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,990 root INFO copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,990 root INFO copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:04,991 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kk
2025-04-22 20:54:04,991 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,991 root INFO copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,991 root INFO copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,991 root INFO copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,991 root INFO copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/kk/LC_MESSAGES
2025-04-22 20:54:04,992 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_CO
2025-04-22 20:54:04,992 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,992 root INFO copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,992 root INFO copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,992 root INFO copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,992 root INFO copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:04,992 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/be
2025-04-22 20:54:04,993 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 20:54:04,993 root INFO copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 20:54:04,993 root INFO copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 20:54:04,993 root INFO copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 20:54:04,993 root INFO copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/be/LC_MESSAGES
2025-04-22 20:54:04,993 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/udm
2025-04-22 20:54:04,993 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,994 root INFO copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,994 root INFO copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,994 root INFO copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,994 root INFO copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/udm/LC_MESSAGES
2025-04-22 20:54:04,994 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ml
2025-04-22 20:54:04,994 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,994 root INFO copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,995 root INFO copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,995 root INFO copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,995 root INFO copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ml/LC_MESSAGES
2025-04-22 20:54:04,995 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ar_DZ
2025-04-22 20:54:04,995 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,995 root INFO copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,996 root INFO copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,996 root INFO copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,996 root INFO copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:04,996 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ms
2025-04-22 20:54:04,996 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,996 root INFO copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,996 root INFO copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,997 root INFO copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,997 root INFO copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ms/LC_MESSAGES
2025-04-22 20:54:04,997 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ast
2025-04-22 20:54:04,997 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,997 root INFO copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,997 root INFO copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,997 root INFO copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,998 root INFO copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ast/LC_MESSAGES
2025-04-22 20:54:04,998 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/zh_Hans
2025-04-22 20:54:04,998 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,998 root INFO copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,998 root INFO copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,999 root INFO copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,999 root INFO copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:04,999 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ur
2025-04-22 20:54:04,999 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,999 root INFO copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,999 root INFO copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 20:54:04,999 root INFO copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 20:54:05,000 root INFO copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ur/LC_MESSAGES
2025-04-22 20:54:05,000 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ia
2025-04-22 20:54:05,000 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 20:54:05,000 root INFO copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 20:54:05,000 root INFO copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 20:54:05,000 root INFO copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 20:54:05,000 root INFO copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ia/LC_MESSAGES
2025-04-22 20:54:05,001 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hu
2025-04-22 20:54:05,001 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 20:54:05,001 root INFO copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 20:54:05,001 root INFO copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 20:54:05,001 root INFO copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 20:54:05,001 root INFO copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/hu/LC_MESSAGES
2025-04-22 20:54:05,001 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ta
2025-04-22 20:54:05,002 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 20:54:05,002 root INFO copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 20:54:05,002 root INFO copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 20:54:05,002 root INFO copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 20:54:05,002 root INFO copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ta/LC_MESSAGES
2025-04-22 20:54:05,002 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/eu
2025-04-22 20:54:05,003 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 20:54:05,003 root INFO copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 20:54:05,003 root INFO copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 20:54:05,003 root INFO copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 20:54:05,003 root INFO copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/eu/LC_MESSAGES
2025-04-22 20:54:05,003 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_MX
2025-04-22 20:54:05,003 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:05,004 root INFO copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:05,004 root INFO copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:05,004 root INFO copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:05,004 root INFO copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:05,004 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tk
2025-04-22 20:54:05,004 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tk/LC_MESSAGES
2025-04-22 20:54:05,004 root INFO copying build/lib/django/contrib/admin/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tk/LC_MESSAGES
2025-04-22 20:54:05,005 root INFO copying build/lib/django/contrib/admin/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tk/LC_MESSAGES
2025-04-22 20:54:05,005 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/th
2025-04-22 20:54:05,005 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 20:54:05,005 root INFO copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 20:54:05,005 root INFO copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 20:54:05,005 root INFO copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 20:54:05,006 root INFO copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/th/LC_MESSAGES
2025-04-22 20:54:05,006 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nb
2025-04-22 20:54:05,006 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 20:54:05,006 root INFO copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 20:54:05,006 root INFO copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 20:54:05,006 root INFO copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 20:54:05,006 root INFO copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nb/LC_MESSAGES
2025-04-22 20:54:05,007 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mn
2025-04-22 20:54:05,007 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 20:54:05,007 root INFO copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 20:54:05,007 root INFO copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 20:54:05,007 root INFO copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 20:54:05,007 root INFO copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/mn/LC_MESSAGES
2025-04-22 20:54:05,007 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ka
2025-04-22 20:54:05,008 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 20:54:05,008 root INFO copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 20:54:05,008 root INFO copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 20:54:05,008 root INFO copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 20:54:05,008 root INFO copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/ka/LC_MESSAGES
2025-04-22 20:54:05,008 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nl
2025-04-22 20:54:05,009 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 20:54:05,009 root INFO copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 20:54:05,009 root INFO copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 20:54:05,009 root INFO copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 20:54:05,009 root INFO copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/nl/LC_MESSAGES
2025-04-22 20:54:05,009 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/te
2025-04-22 20:54:05,009 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 20:54:05,010 root INFO copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 20:54:05,010 root INFO copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 20:54:05,010 root INFO copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 20:54:05,010 root INFO copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/te/LC_MESSAGES
2025-04-22 20:54:05,010 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pt
2025-04-22 20:54:05,010 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 20:54:05,010 root INFO copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 20:54:05,011 root INFO copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 20:54:05,011 root INFO copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 20:54:05,011 root INFO copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/pt/LC_MESSAGES
2025-04-22 20:54:05,011 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bn
2025-04-22 20:54:05,011 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 20:54:05,011 root INFO copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 20:54:05,011 root INFO copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 20:54:05,012 root INFO copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 20:54:05,012 root INFO copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/bn/LC_MESSAGES
2025-04-22 20:54:05,012 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/he
2025-04-22 20:54:05,012 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 20:54:05,012 root INFO copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 20:54:05,012 root INFO copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 20:54:05,013 root INFO copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 20:54:05,013 root INFO copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/he/LC_MESSAGES
2025-04-22 20:54:05,013 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/br
2025-04-22 20:54:05,013 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 20:54:05,013 root INFO copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 20:54:05,013 root INFO copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 20:54:05,013 root INFO copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 20:54:05,014 root INFO copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/br/LC_MESSAGES
2025-04-22 20:54:05,014 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fa
2025-04-22 20:54:05,014 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 20:54:05,014 root INFO copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 20:54:05,014 root INFO copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 20:54:05,014 root INFO copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 20:54:05,014 root INFO copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/fa/LC_MESSAGES
2025-04-22 20:54:05,015 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tg
2025-04-22 20:54:05,015 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 20:54:05,015 root INFO copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 20:54:05,015 root INFO copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 20:54:05,015 root INFO copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 20:54:05,015 root INFO copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/tg/LC_MESSAGES
2025-04-22 20:54:05,016 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/km
2025-04-22 20:54:05,016 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 20:54:05,016 root INFO copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 20:54:05,016 root INFO copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 20:54:05,016 root INFO copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 20:54:05,016 root INFO copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/km/LC_MESSAGES
2025-04-22 20:54:05,016 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/da
2025-04-22 20:54:05,017 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 20:54:05,017 root INFO copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 20:54:05,017 root INFO copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 20:54:05,017 root INFO copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 20:54:05,017 root INFO copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/admin/locale/da/LC_MESSAGES
2025-04-22 20:54:05,017 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/templates
2025-04-22 20:54:05,017 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,018 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/auth
2025-04-22 20:54:05,018 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/auth/user
2025-04-22 20:54:05,018 root INFO copying build/lib/django/contrib/admin/templates/admin/auth/user/add_form.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/auth/user
2025-04-22 20:54:05,018 root INFO copying build/lib/django/contrib/admin/templates/admin/auth/user/change_password.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/auth/user
2025-04-22 20:54:05,018 root INFO copying build/lib/django/contrib/admin/templates/admin/change_list_object_tools.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,018 root INFO copying build/lib/django/contrib/admin/templates/admin/change_form.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,018 root INFO copying build/lib/django/contrib/admin/templates/admin/change_list.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,019 root INFO copying build/lib/django/contrib/admin/templates/admin/login.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,019 root INFO copying build/lib/django/contrib/admin/templates/admin/index.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,019 root INFO copying build/lib/django/contrib/admin/templates/admin/prepopulated_fields_js.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,019 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/includes
2025-04-22 20:54:05,019 root INFO copying build/lib/django/contrib/admin/templates/admin/includes/fieldset.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/includes
2025-04-22 20:54:05,019 root INFO copying build/lib/django/contrib/admin/templates/admin/includes/object_delete_summary.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/includes
2025-04-22 20:54:05,020 root INFO copying build/lib/django/contrib/admin/templates/admin/500.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,020 root INFO copying build/lib/django/contrib/admin/templates/admin/filter.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,020 root INFO copying build/lib/django/contrib/admin/templates/admin/delete_selected_confirmation.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,020 root INFO copying build/lib/django/contrib/admin/templates/admin/base.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,020 root INFO copying build/lib/django/contrib/admin/templates/admin/nav_sidebar.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,020 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/edit_inline
2025-04-22 20:54:05,020 root INFO copying build/lib/django/contrib/admin/templates/admin/edit_inline/stacked.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/edit_inline
2025-04-22 20:54:05,021 root INFO copying build/lib/django/contrib/admin/templates/admin/edit_inline/tabular.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/edit_inline
2025-04-22 20:54:05,021 root INFO copying build/lib/django/contrib/admin/templates/admin/change_form_object_tools.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,021 root INFO copying build/lib/django/contrib/admin/templates/admin/search_form.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,021 root INFO copying build/lib/django/contrib/admin/templates/admin/popup_response.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,021 root INFO copying build/lib/django/contrib/admin/templates/admin/pagination.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,021 root INFO copying build/lib/django/contrib/admin/templates/admin/invalid_setup.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,022 root INFO copying build/lib/django/contrib/admin/templates/admin/404.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,022 root INFO copying build/lib/django/contrib/admin/templates/admin/date_hierarchy.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,022 root INFO copying build/lib/django/contrib/admin/templates/admin/color_theme_toggle.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,022 root INFO copying build/lib/django/contrib/admin/templates/admin/delete_confirmation.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,022 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:05,023 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/radio.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:05,023 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/time.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:05,023 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/url.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:05,023 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/split_datetime.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:05,023 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:05,023 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/clearable_file_input.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:05,023 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:05,024 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/date.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:05,024 root INFO copying build/lib/django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin/widgets
2025-04-22 20:54:05,024 root INFO copying build/lib/django/contrib/admin/templates/admin/base_site.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,024 root INFO copying build/lib/django/contrib/admin/templates/admin/app_index.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,024 root INFO copying build/lib/django/contrib/admin/templates/admin/change_list_results.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,024 root INFO copying build/lib/django/contrib/admin/templates/admin/object_history.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,025 root INFO copying build/lib/django/contrib/admin/templates/admin/actions.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,025 root INFO copying build/lib/django/contrib/admin/templates/admin/submit_line.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,025 root INFO copying build/lib/django/contrib/admin/templates/admin/app_list.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/admin
2025-04-22 20:54:05,025 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/registration
2025-04-22 20:54:05,025 root INFO copying build/lib/django/contrib/admin/templates/registration/password_change_done.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/registration
2025-04-22 20:54:05,025 root INFO copying build/lib/django/contrib/admin/templates/registration/password_reset_confirm.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/registration
2025-04-22 20:54:05,025 root INFO copying build/lib/django/contrib/admin/templates/registration/password_reset_complete.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/registration
2025-04-22 20:54:05,026 root INFO copying build/lib/django/contrib/admin/templates/registration/logged_out.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/registration
2025-04-22 20:54:05,026 root INFO copying build/lib/django/contrib/admin/templates/registration/password_reset_form.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/registration
2025-04-22 20:54:05,026 root INFO copying build/lib/django/contrib/admin/templates/registration/password_reset_done.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/registration
2025-04-22 20:54:05,026 root INFO copying build/lib/django/contrib/admin/templates/registration/password_change_form.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/registration
2025-04-22 20:54:05,026 root INFO copying build/lib/django/contrib/admin/templates/registration/password_reset_email.html -> build/bdist.linux-aarch64/wheel/django/contrib/admin/templates/registration
2025-04-22 20:54:05,026 root INFO copying build/lib/django/contrib/admin/helpers.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin
2025-04-22 20:54:05,027 root INFO copying build/lib/django/contrib/admin/sites.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin
2025-04-22 20:54:05,027 root INFO copying build/lib/django/contrib/admin/actions.py -> build/bdist.linux-aarch64/wheel/django/contrib/admin
2025-04-22 20:54:05,027 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize
2025-04-22 20:54:05,027 root INFO copying build/lib/django/contrib/humanize/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/humanize
2025-04-22 20:54:05,027 root INFO copying build/lib/django/contrib/humanize/apps.py -> build/bdist.linux-aarch64/wheel/django/contrib/humanize
2025-04-22 20:54:05,027 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/templatetags
2025-04-22 20:54:05,028 root INFO copying build/lib/django/contrib/humanize/templatetags/__init__.py -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/templatetags
2025-04-22 20:54:05,028 root INFO copying build/lib/django/contrib/humanize/templatetags/humanize.py -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/templatetags
2025-04-22 20:54:05,028 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale
2025-04-22 20:54:05,028 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/lv
2025-04-22 20:54:05,028 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/lv/LC_MESSAGES
2025-04-22 20:54:05,028 root INFO copying build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/lv/LC_MESSAGES
2025-04-22 20:54:05,029 root INFO copying build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/lv/LC_MESSAGES
2025-04-22 20:54:05,029 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sw
2025-04-22 20:54:05,029 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sw/LC_MESSAGES
2025-04-22 20:54:05,029 root INFO copying build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sw/LC_MESSAGES
2025-04-22 20:54:05,029 root INFO copying build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sw/LC_MESSAGES
2025-04-22 20:54:05,029 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/en_AU
2025-04-22 20:54:05,029 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:05,029 root INFO copying build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:05,030 root INFO copying build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/en_AU/LC_MESSAGES
2025-04-22 20:54:05,030 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/mr
2025-04-22 20:54:05,030 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/mr/LC_MESSAGES
2025-04-22 20:54:05,030 root INFO copying build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/mr/LC_MESSAGES
2025-04-22 20:54:05,030 root INFO copying build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/mr/LC_MESSAGES
2025-04-22 20:54:05,030 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/lb
2025-04-22 20:54:05,030 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/lb/LC_MESSAGES
2025-04-22 20:54:05,031 root INFO copying build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/lb/LC_MESSAGES
2025-04-22 20:54:05,031 root INFO copying build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/lb/LC_MESSAGES
2025-04-22 20:54:05,031 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ca
2025-04-22 20:54:05,031 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ca/LC_MESSAGES
2025-04-22 20:54:05,031 root INFO copying build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ca/LC_MESSAGES
2025-04-22 20:54:05,031 root INFO copying build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ca/LC_MESSAGES
2025-04-22 20:54:05,031 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/en_GB
2025-04-22 20:54:05,031 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:05,032 root INFO copying build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:05,032 root INFO copying build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/en_GB/LC_MESSAGES
2025-04-22 20:54:05,032 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/el
2025-04-22 20:54:05,032 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/el/LC_MESSAGES
2025-04-22 20:54:05,032 root INFO copying build/lib/django/contrib/humanize/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/el/LC_MESSAGES
2025-04-22 20:54:05,032 root INFO copying build/lib/django/contrib/humanize/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/el/LC_MESSAGES
2025-04-22 20:54:05,033 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es_VE
2025-04-22 20:54:05,033 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:05,033 root INFO copying build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:05,033 root INFO copying build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es_VE/LC_MESSAGES
2025-04-22 20:54:05,033 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/af
2025-04-22 20:54:05,033 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/af/LC_MESSAGES
2025-04-22 20:54:05,033 root INFO copying build/lib/django/contrib/humanize/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/af/LC_MESSAGES
2025-04-22 20:54:05,033 root INFO copying build/lib/django/contrib/humanize/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/af/LC_MESSAGES
2025-04-22 20:54:05,034 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/en
2025-04-22 20:54:05,034 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/en/LC_MESSAGES
2025-04-22 20:54:05,034 root INFO copying build/lib/django/contrib/humanize/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/en/LC_MESSAGES
2025-04-22 20:54:05,034 root INFO copying build/lib/django/contrib/humanize/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/en/LC_MESSAGES
2025-04-22 20:54:05,034 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/dsb
2025-04-22 20:54:05,034 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/dsb/LC_MESSAGES
2025-04-22 20:54:05,034 root INFO copying build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/dsb/LC_MESSAGES
2025-04-22 20:54:05,034 root INFO copying build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/dsb/LC_MESSAGES
2025-04-22 20:54:05,035 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/et
2025-04-22 20:54:05,035 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/et/LC_MESSAGES
2025-04-22 20:54:05,035 root INFO copying build/lib/django/contrib/humanize/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/et/LC_MESSAGES
2025-04-22 20:54:05,035 root INFO copying build/lib/django/contrib/humanize/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/et/LC_MESSAGES
2025-04-22 20:54:05,035 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/nn
2025-04-22 20:54:05,035 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/nn/LC_MESSAGES
2025-04-22 20:54:05,035 root INFO copying build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/nn/LC_MESSAGES
2025-04-22 20:54:05,036 root INFO copying build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/nn/LC_MESSAGES
2025-04-22 20:54:05,036 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/cy
2025-04-22 20:54:05,036 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/cy/LC_MESSAGES
2025-04-22 20:54:05,036 root INFO copying build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/cy/LC_MESSAGES
2025-04-22 20:54:05,036 root INFO copying build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/cy/LC_MESSAGES
2025-04-22 20:54:05,036 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ko
2025-04-22 20:54:05,036 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ko/LC_MESSAGES
2025-04-22 20:54:05,037 root INFO copying build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ko/LC_MESSAGES
2025-04-22 20:54:05,037 root INFO copying build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ko/LC_MESSAGES
2025-04-22 20:54:05,037 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/is
2025-04-22 20:54:05,037 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/is/LC_MESSAGES
2025-04-22 20:54:05,037 root INFO copying build/lib/django/contrib/humanize/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/is/LC_MESSAGES
2025-04-22 20:54:05,037 root INFO copying build/lib/django/contrib/humanize/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/is/LC_MESSAGES
2025-04-22 20:54:05,037 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/pa
2025-04-22 20:54:05,038 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/pa/LC_MESSAGES
2025-04-22 20:54:05,038 root INFO copying build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/pa/LC_MESSAGES
2025-04-22 20:54:05,038 root INFO copying build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/pa/LC_MESSAGES
2025-04-22 20:54:05,038 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/tt
2025-04-22 20:54:05,038 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/tt/LC_MESSAGES
2025-04-22 20:54:05,038 root INFO copying build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/tt/LC_MESSAGES
2025-04-22 20:54:05,038 root INFO copying build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/tt/LC_MESSAGES
2025-04-22 20:54:05,038 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ne
2025-04-22 20:54:05,039 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ne/LC_MESSAGES
2025-04-22 20:54:05,039 root INFO copying build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ne/LC_MESSAGES
2025-04-22 20:54:05,039 root INFO copying build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ne/LC_MESSAGES
2025-04-22 20:54:05,039 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sr_Latn
2025-04-22 20:54:05,039 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:05,039 root INFO copying build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:05,039 root INFO copying build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
2025-04-22 20:54:05,039 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/fy
2025-04-22 20:54:05,040 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/fy/LC_MESSAGES
2025-04-22 20:54:05,040 root INFO copying build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/fy/LC_MESSAGES
2025-04-22 20:54:05,040 root INFO copying build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/fy/LC_MESSAGES
2025-04-22 20:54:05,040 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/bg
2025-04-22 20:54:05,040 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/bg/LC_MESSAGES
2025-04-22 20:54:05,040 root INFO copying build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/bg/LC_MESSAGES
2025-04-22 20:54:05,040 root INFO copying build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/bg/LC_MESSAGES
2025-04-22 20:54:05,040 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ga
2025-04-22 20:54:05,041 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ga/LC_MESSAGES
2025-04-22 20:54:05,041 root INFO copying build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ga/LC_MESSAGES
2025-04-22 20:54:05,041 root INFO copying build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ga/LC_MESSAGES
2025-04-22 20:54:05,041 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/gl
2025-04-22 20:54:05,041 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/gl/LC_MESSAGES
2025-04-22 20:54:05,041 root INFO copying build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/gl/LC_MESSAGES
2025-04-22 20:54:05,041 root INFO copying build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/gl/LC_MESSAGES
2025-04-22 20:54:05,042 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/uk
2025-04-22 20:54:05,042 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/uk/LC_MESSAGES
2025-04-22 20:54:05,042 root INFO copying build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/uk/LC_MESSAGES
2025-04-22 20:54:05,042 root INFO copying build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/uk/LC_MESSAGES
2025-04-22 20:54:05,042 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/uz
2025-04-22 20:54:05,042 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/uz/LC_MESSAGES
2025-04-22 20:54:05,042 root INFO copying build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/uz/LC_MESSAGES
2025-04-22 20:54:05,042 root INFO copying build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/uz/LC_MESSAGES
2025-04-22 20:54:05,043 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/kn
2025-04-22 20:54:05,043 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/kn/LC_MESSAGES
2025-04-22 20:54:05,043 root INFO copying build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/kn/LC_MESSAGES
2025-04-22 20:54:05,043 root INFO copying build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/kn/LC_MESSAGES
2025-04-22 20:54:05,043 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ja
2025-04-22 20:54:05,043 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ja/LC_MESSAGES
2025-04-22 20:54:05,043 root INFO copying build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ja/LC_MESSAGES
2025-04-22 20:54:05,043 root INFO copying build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ja/LC_MESSAGES
2025-04-22 20:54:05,044 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/cs
2025-04-22 20:54:05,044 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/cs/LC_MESSAGES
2025-04-22 20:54:05,044 root INFO copying build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/cs/LC_MESSAGES
2025-04-22 20:54:05,044 root INFO copying build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/cs/LC_MESSAGES
2025-04-22 20:54:05,044 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/os
2025-04-22 20:54:05,044 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/os/LC_MESSAGES
2025-04-22 20:54:05,044 root INFO copying build/lib/django/contrib/humanize/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/os/LC_MESSAGES
2025-04-22 20:54:05,044 root INFO copying build/lib/django/contrib/humanize/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/os/LC_MESSAGES
2025-04-22 20:54:05,045 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/tr
2025-04-22 20:54:05,045 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/tr/LC_MESSAGES
2025-04-22 20:54:05,045 root INFO copying build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/tr/LC_MESSAGES
2025-04-22 20:54:05,045 root INFO copying build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/tr/LC_MESSAGES
2025-04-22 20:54:05,045 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/io
2025-04-22 20:54:05,046 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/io/LC_MESSAGES
2025-04-22 20:54:05,046 root INFO copying build/lib/django/contrib/humanize/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/io/LC_MESSAGES
2025-04-22 20:54:05,046 root INFO copying build/lib/django/contrib/humanize/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/io/LC_MESSAGES
2025-04-22 20:54:05,046 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sl
2025-04-22 20:54:05,046 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sl/LC_MESSAGES
2025-04-22 20:54:05,046 root INFO copying build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sl/LC_MESSAGES
2025-04-22 20:54:05,046 root INFO copying build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sl/LC_MESSAGES
2025-04-22 20:54:05,046 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sq
2025-04-22 20:54:05,047 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sq/LC_MESSAGES
2025-04-22 20:54:05,047 root INFO copying build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sq/LC_MESSAGES
2025-04-22 20:54:05,047 root INFO copying build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sq/LC_MESSAGES
2025-04-22 20:54:05,047 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/az
2025-04-22 20:54:05,047 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/az/LC_MESSAGES
2025-04-22 20:54:05,047 root INFO copying build/lib/django/contrib/humanize/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/az/LC_MESSAGES
2025-04-22 20:54:05,047 root INFO copying build/lib/django/contrib/humanize/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/az/LC_MESSAGES
2025-04-22 20:54:05,047 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/eo
2025-04-22 20:54:05,048 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/eo/LC_MESSAGES
2025-04-22 20:54:05,048 root INFO copying build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/eo/LC_MESSAGES
2025-04-22 20:54:05,048 root INFO copying build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/eo/LC_MESSAGES
2025-04-22 20:54:05,048 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/pt_BR
2025-04-22 20:54:05,048 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:05,048 root INFO copying build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:05,048 root INFO copying build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
2025-04-22 20:54:05,049 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/pl
2025-04-22 20:54:05,049 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/pl/LC_MESSAGES
2025-04-22 20:54:05,049 root INFO copying build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/pl/LC_MESSAGES
2025-04-22 20:54:05,049 root INFO copying build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/pl/LC_MESSAGES
2025-04-22 20:54:05,049 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/gd
2025-04-22 20:54:05,049 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/gd/LC_MESSAGES
2025-04-22 20:54:05,049 root INFO copying build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/gd/LC_MESSAGES
2025-04-22 20:54:05,049 root INFO copying build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/gd/LC_MESSAGES
2025-04-22 20:54:05,050 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hr
2025-04-22 20:54:05,050 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hr/LC_MESSAGES
2025-04-22 20:54:05,050 root INFO copying build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hr/LC_MESSAGES
2025-04-22 20:54:05,050 root INFO copying build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hr/LC_MESSAGES
2025-04-22 20:54:05,050 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ru
2025-04-22 20:54:05,050 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ru/LC_MESSAGES
2025-04-22 20:54:05,050 root INFO copying build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ru/LC_MESSAGES
2025-04-22 20:54:05,051 root INFO copying build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ru/LC_MESSAGES
2025-04-22 20:54:05,051 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es
2025-04-22 20:54:05,051 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es/LC_MESSAGES
2025-04-22 20:54:05,051 root INFO copying build/lib/django/contrib/humanize/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es/LC_MESSAGES
2025-04-22 20:54:05,051 root INFO copying build/lib/django/contrib/humanize/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es/LC_MESSAGES
2025-04-22 20:54:05,051 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/id
2025-04-22 20:54:05,051 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/id/LC_MESSAGES
2025-04-22 20:54:05,052 root INFO copying build/lib/django/contrib/humanize/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/id/LC_MESSAGES
2025-04-22 20:54:05,052 root INFO copying build/lib/django/contrib/humanize/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/id/LC_MESSAGES
2025-04-22 20:54:05,052 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/fi
2025-04-22 20:54:05,052 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/fi/LC_MESSAGES
2025-04-22 20:54:05,052 root INFO copying build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/fi/LC_MESSAGES
2025-04-22 20:54:05,052 root INFO copying build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/fi/LC_MESSAGES
2025-04-22 20:54:05,052 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/mk
2025-04-22 20:54:05,053 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/mk/LC_MESSAGES
2025-04-22 20:54:05,053 root INFO copying build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/mk/LC_MESSAGES
2025-04-22 20:54:05,053 root INFO copying build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/mk/LC_MESSAGES
2025-04-22 20:54:05,053 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hi
2025-04-22 20:54:05,053 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hi/LC_MESSAGES
2025-04-22 20:54:05,053 root INFO copying build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hi/LC_MESSAGES
2025-04-22 20:54:05,053 root INFO copying build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hi/LC_MESSAGES
2025-04-22 20:54:05,053 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hsb
2025-04-22 20:54:05,054 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hsb/LC_MESSAGES
2025-04-22 20:54:05,054 root INFO copying build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hsb/LC_MESSAGES
2025-04-22 20:54:05,054 root INFO copying build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hsb/LC_MESSAGES
2025-04-22 20:54:05,054 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sk
2025-04-22 20:54:05,054 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sk/LC_MESSAGES
2025-04-22 20:54:05,054 root INFO copying build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sk/LC_MESSAGES
2025-04-22 20:54:05,054 root INFO copying build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sk/LC_MESSAGES
2025-04-22 20:54:05,055 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/lt
2025-04-22 20:54:05,055 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/lt/LC_MESSAGES
2025-04-22 20:54:05,055 root INFO copying build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/lt/LC_MESSAGES
2025-04-22 20:54:05,055 root INFO copying build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/lt/LC_MESSAGES
2025-04-22 20:54:05,055 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/de
2025-04-22 20:54:05,055 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/de/LC_MESSAGES
2025-04-22 20:54:05,055 root INFO copying build/lib/django/contrib/humanize/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/de/LC_MESSAGES
2025-04-22 20:54:05,055 root INFO copying build/lib/django/contrib/humanize/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/de/LC_MESSAGES
2025-04-22 20:54:05,056 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/it
2025-04-22 20:54:05,056 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/it/LC_MESSAGES
2025-04-22 20:54:05,056 root INFO copying build/lib/django/contrib/humanize/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/it/LC_MESSAGES
2025-04-22 20:54:05,056 root INFO copying build/lib/django/contrib/humanize/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/it/LC_MESSAGES
2025-04-22 20:54:05,056 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/my
2025-04-22 20:54:05,056 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/my/LC_MESSAGES
2025-04-22 20:54:05,056 root INFO copying build/lib/django/contrib/humanize/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/my/LC_MESSAGES
2025-04-22 20:54:05,056 root INFO copying build/lib/django/contrib/humanize/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/my/LC_MESSAGES
2025-04-22 20:54:05,057 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sr
2025-04-22 20:54:05,057 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sr/LC_MESSAGES
2025-04-22 20:54:05,057 root INFO copying build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sr/LC_MESSAGES
2025-04-22 20:54:05,057 root INFO copying build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sr/LC_MESSAGES
2025-04-22 20:54:05,057 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/bs
2025-04-22 20:54:05,057 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/bs/LC_MESSAGES
2025-04-22 20:54:05,057 root INFO copying build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/bs/LC_MESSAGES
2025-04-22 20:54:05,057 root INFO copying build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/bs/LC_MESSAGES
2025-04-22 20:54:05,058 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ro
2025-04-22 20:54:05,058 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ro/LC_MESSAGES
2025-04-22 20:54:05,058 root INFO copying build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ro/LC_MESSAGES
2025-04-22 20:54:05,058 root INFO copying build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ro/LC_MESSAGES
2025-04-22 20:54:05,058 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ky
2025-04-22 20:54:05,058 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ky/LC_MESSAGES
2025-04-22 20:54:05,058 root INFO copying build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ky/LC_MESSAGES
2025-04-22 20:54:05,059 root INFO copying build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ky/LC_MESSAGES
2025-04-22 20:54:05,059 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/fr
2025-04-22 20:54:05,059 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/fr/LC_MESSAGES
2025-04-22 20:54:05,059 root INFO copying build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/fr/LC_MESSAGES
2025-04-22 20:54:05,059 root INFO copying build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/fr/LC_MESSAGES
2025-04-22 20:54:05,059 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ar
2025-04-22 20:54:05,059 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ar/LC_MESSAGES
2025-04-22 20:54:05,060 root INFO copying build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ar/LC_MESSAGES
2025-04-22 20:54:05,060 root INFO copying build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ar/LC_MESSAGES
2025-04-22 20:54:05,060 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hy
2025-04-22 20:54:05,060 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hy/LC_MESSAGES
2025-04-22 20:54:05,060 root INFO copying build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hy/LC_MESSAGES
2025-04-22 20:54:05,060 root INFO copying build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hy/LC_MESSAGES
2025-04-22 20:54:05,060 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es_AR
2025-04-22 20:54:05,061 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:05,061 root INFO copying build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:05,061 root INFO copying build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es_AR/LC_MESSAGES
2025-04-22 20:54:05,061 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/vi
2025-04-22 20:54:05,061 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/vi/LC_MESSAGES
2025-04-22 20:54:05,061 root INFO copying build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/vi/LC_MESSAGES
2025-04-22 20:54:05,061 root INFO copying build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/vi/LC_MESSAGES
2025-04-22 20:54:05,062 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ckb
2025-04-22 20:54:05,062 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ckb/LC_MESSAGES
2025-04-22 20:54:05,062 root INFO copying build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ckb/LC_MESSAGES
2025-04-22 20:54:05,062 root INFO copying build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ckb/LC_MESSAGES
2025-04-22 20:54:05,062 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sv
2025-04-22 20:54:05,062 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sv/LC_MESSAGES
2025-04-22 20:54:05,062 root INFO copying build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sv/LC_MESSAGES
2025-04-22 20:54:05,062 root INFO copying build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/sv/LC_MESSAGES
2025-04-22 20:54:05,063 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/zh_Hant
2025-04-22 20:54:05,063 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:05,063 root INFO copying build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:05,063 root INFO copying build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
2025-04-22 20:54:05,063 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/kk
2025-04-22 20:54:05,063 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/kk/LC_MESSAGES
2025-04-22 20:54:05,063 root INFO copying build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/kk/LC_MESSAGES
2025-04-22 20:54:05,063 root INFO copying build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/kk/LC_MESSAGES
2025-04-22 20:54:05,064 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es_CO
2025-04-22 20:54:05,064 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:05,064 root INFO copying build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:05,064 root INFO copying build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es_CO/LC_MESSAGES
2025-04-22 20:54:05,064 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/be
2025-04-22 20:54:05,064 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/be/LC_MESSAGES
2025-04-22 20:54:05,064 root INFO copying build/lib/django/contrib/humanize/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/be/LC_MESSAGES
2025-04-22 20:54:05,064 root INFO copying build/lib/django/contrib/humanize/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/be/LC_MESSAGES
2025-04-22 20:54:05,065 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/udm
2025-04-22 20:54:05,065 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/udm/LC_MESSAGES
2025-04-22 20:54:05,065 root INFO copying build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/udm/LC_MESSAGES
2025-04-22 20:54:05,065 root INFO copying build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/udm/LC_MESSAGES
2025-04-22 20:54:05,065 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ml
2025-04-22 20:54:05,065 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ml/LC_MESSAGES
2025-04-22 20:54:05,065 root INFO copying build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ml/LC_MESSAGES
2025-04-22 20:54:05,066 root INFO copying build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ml/LC_MESSAGES
2025-04-22 20:54:05,066 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ar_DZ
2025-04-22 20:54:05,066 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:05,066 root INFO copying build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:05,066 root INFO copying build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
2025-04-22 20:54:05,066 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ms
2025-04-22 20:54:05,067 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ms/LC_MESSAGES
2025-04-22 20:54:05,067 root INFO copying build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ms/LC_MESSAGES
2025-04-22 20:54:05,067 root INFO copying build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ms/LC_MESSAGES
2025-04-22 20:54:05,067 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ast
2025-04-22 20:54:05,067 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ast/LC_MESSAGES
2025-04-22 20:54:05,067 root INFO copying build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ast/LC_MESSAGES
2025-04-22 20:54:05,067 root INFO copying build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ast/LC_MESSAGES
2025-04-22 20:54:05,067 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/zh_Hans
2025-04-22 20:54:05,068 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:05,068 root INFO copying build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:05,068 root INFO copying build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
2025-04-22 20:54:05,068 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ur
2025-04-22 20:54:05,068 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ur/LC_MESSAGES
2025-04-22 20:54:05,068 root INFO copying build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ur/LC_MESSAGES
2025-04-22 20:54:05,069 root INFO copying build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ur/LC_MESSAGES
2025-04-22 20:54:05,069 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ia
2025-04-22 20:54:05,069 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ia/LC_MESSAGES
2025-04-22 20:54:05,069 root INFO copying build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ia/LC_MESSAGES
2025-04-22 20:54:05,069 root INFO copying build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ia/LC_MESSAGES
2025-04-22 20:54:05,069 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hu
2025-04-22 20:54:05,069 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hu/LC_MESSAGES
2025-04-22 20:54:05,069 root INFO copying build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hu/LC_MESSAGES
2025-04-22 20:54:05,070 root INFO copying build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/hu/LC_MESSAGES
2025-04-22 20:54:05,070 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ta
2025-04-22 20:54:05,070 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ta/LC_MESSAGES
2025-04-22 20:54:05,070 root INFO copying build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ta/LC_MESSAGES
2025-04-22 20:54:05,070 root INFO copying build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ta/LC_MESSAGES
2025-04-22 20:54:05,070 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/eu
2025-04-22 20:54:05,070 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/eu/LC_MESSAGES
2025-04-22 20:54:05,071 root INFO copying build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/eu/LC_MESSAGES
2025-04-22 20:54:05,071 root INFO copying build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/eu/LC_MESSAGES
2025-04-22 20:54:05,071 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es_MX
2025-04-22 20:54:05,071 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:05,071 root INFO copying build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:05,071 root INFO copying build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/es_MX/LC_MESSAGES
2025-04-22 20:54:05,071 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/tk
2025-04-22 20:54:05,071 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/tk/LC_MESSAGES
2025-04-22 20:54:05,072 root INFO copying build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/tk/LC_MESSAGES
2025-04-22 20:54:05,072 root INFO copying build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/tk/LC_MESSAGES
2025-04-22 20:54:05,072 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/th
2025-04-22 20:54:05,072 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/th/LC_MESSAGES
2025-04-22 20:54:05,072 root INFO copying build/lib/django/contrib/humanize/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/th/LC_MESSAGES
2025-04-22 20:54:05,072 root INFO copying build/lib/django/contrib/humanize/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/th/LC_MESSAGES
2025-04-22 20:54:05,072 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/nb
2025-04-22 20:54:05,073 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/nb/LC_MESSAGES
2025-04-22 20:54:05,073 root INFO copying build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/nb/LC_MESSAGES
2025-04-22 20:54:05,073 root INFO copying build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/nb/LC_MESSAGES
2025-04-22 20:54:05,073 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/mn
2025-04-22 20:54:05,073 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/mn/LC_MESSAGES
2025-04-22 20:54:05,073 root INFO copying build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/mn/LC_MESSAGES
2025-04-22 20:54:05,073 root INFO copying build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/mn/LC_MESSAGES
2025-04-22 20:54:05,073 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ka
2025-04-22 20:54:05,074 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ka/LC_MESSAGES
2025-04-22 20:54:05,074 root INFO copying build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ka/LC_MESSAGES
2025-04-22 20:54:05,074 root INFO copying build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/ka/LC_MESSAGES
2025-04-22 20:54:05,074 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/nl
2025-04-22 20:54:05,074 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/nl/LC_MESSAGES
2025-04-22 20:54:05,074 root INFO copying build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/nl/LC_MESSAGES
2025-04-22 20:54:05,074 root INFO copying build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/nl/LC_MESSAGES
2025-04-22 20:54:05,075 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/te
2025-04-22 20:54:05,075 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/te/LC_MESSAGES
2025-04-22 20:54:05,075 root INFO copying build/lib/django/contrib/humanize/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/te/LC_MESSAGES
2025-04-22 20:54:05,075 root INFO copying build/lib/django/contrib/humanize/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/te/LC_MESSAGES
2025-04-22 20:54:05,075 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/pt
2025-04-22 20:54:05,075 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/pt/LC_MESSAGES
2025-04-22 20:54:05,075 root INFO copying build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/pt/LC_MESSAGES
2025-04-22 20:54:05,075 root INFO copying build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/pt/LC_MESSAGES
2025-04-22 20:54:05,076 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/bn
2025-04-22 20:54:05,076 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/bn/LC_MESSAGES
2025-04-22 20:54:05,076 root INFO copying build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/bn/LC_MESSAGES
2025-04-22 20:54:05,076 root INFO copying build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/bn/LC_MESSAGES
2025-04-22 20:54:05,076 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/he
2025-04-22 20:54:05,076 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/he/LC_MESSAGES
2025-04-22 20:54:05,076 root INFO copying build/lib/django/contrib/humanize/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/he/LC_MESSAGES
2025-04-22 20:54:05,077 root INFO copying build/lib/django/contrib/humanize/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/he/LC_MESSAGES
2025-04-22 20:54:05,077 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/br
2025-04-22 20:54:05,077 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/br/LC_MESSAGES
2025-04-22 20:54:05,077 root INFO copying build/lib/django/contrib/humanize/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/br/LC_MESSAGES
2025-04-22 20:54:05,077 root INFO copying build/lib/django/contrib/humanize/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/br/LC_MESSAGES
2025-04-22 20:54:05,077 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/fa
2025-04-22 20:54:05,077 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/fa/LC_MESSAGES
2025-04-22 20:54:05,078 root INFO copying build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/fa/LC_MESSAGES
2025-04-22 20:54:05,078 root INFO copying build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/fa/LC_MESSAGES
2025-04-22 20:54:05,078 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/tg
2025-04-22 20:54:05,078 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/tg/LC_MESSAGES
2025-04-22 20:54:05,078 root INFO copying build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/tg/LC_MESSAGES
2025-04-22 20:54:05,078 root INFO copying build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/tg/LC_MESSAGES
2025-04-22 20:54:05,078 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/km
2025-04-22 20:54:05,079 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/km/LC_MESSAGES
2025-04-22 20:54:05,079 root INFO copying build/lib/django/contrib/humanize/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/km/LC_MESSAGES
2025-04-22 20:54:05,079 root INFO copying build/lib/django/contrib/humanize/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/km/LC_MESSAGES
2025-04-22 20:54:05,079 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/da
2025-04-22 20:54:05,079 root INFO creating build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/da/LC_MESSAGES
2025-04-22 20:54:05,079 root INFO copying build/lib/django/contrib/humanize/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/da/LC_MESSAGES
2025-04-22 20:54:05,079 root INFO copying build/lib/django/contrib/humanize/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-aarch64/wheel/django/contrib/humanize/locale/da/LC_MESSAGES
2025-04-22 20:54:05,080 root INFO creating build/bdist.linux-aarch64/wheel/django/forms
2025-04-22 20:54:05,080 root INFO copying build/lib/django/forms/__init__.py -> build/bdist.linux-aarch64/wheel/django/forms
2025-04-22 20:54:05,080 root INFO copying build/lib/django/forms/widgets.py -> build/bdist.linux-aarch64/wheel/django/forms
2025-04-22 20:54:05,080 root INFO copying build/lib/django/forms/forms.py -> build/bdist.linux-aarch64/wheel/django/forms
2025-04-22 20:54:05,080 root INFO creating build/bdist.linux-aarch64/wheel/django/forms/jinja2
2025-04-22 20:54:05,080 root INFO creating build/bdist.linux-aarch64/wheel/django/forms/jinja2/django
2025-04-22 20:54:05,081 root INFO creating build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms
2025-04-22 20:54:05,081 root INFO copying build/lib/django/forms/jinja2/django/forms/table.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms
2025-04-22 20:54:05,081 root INFO copying build/lib/django/forms/jinja2/django/forms/label.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms
2025-04-22 20:54:05,081 root INFO copying build/lib/django/forms/jinja2/django/forms/default.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms
2025-04-22 20:54:05,081 root INFO creating build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/errors
2025-04-22 20:54:05,081 root INFO creating build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/errors/dict
2025-04-22 20:54:05,081 root INFO copying build/lib/django/forms/jinja2/django/forms/errors/dict/default.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/errors/dict
2025-04-22 20:54:05,081 root INFO copying build/lib/django/forms/jinja2/django/forms/errors/dict/text.txt -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/errors/dict
2025-04-22 20:54:05,082 root INFO copying build/lib/django/forms/jinja2/django/forms/errors/dict/ul.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/errors/dict
2025-04-22 20:54:05,082 root INFO creating build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/errors/list
2025-04-22 20:54:05,082 root INFO copying build/lib/django/forms/jinja2/django/forms/errors/list/default.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/errors/list
2025-04-22 20:54:05,082 root INFO copying build/lib/django/forms/jinja2/django/forms/errors/list/text.txt -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/errors/list
2025-04-22 20:54:05,082 root INFO copying build/lib/django/forms/jinja2/django/forms/errors/list/ul.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/errors/list
2025-04-22 20:54:05,082 root INFO creating build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,082 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/radio.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,083 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/multiwidget.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,083 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/radio_option.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,083 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/input.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,083 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/time.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,083 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/email.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,083 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/splitdatetime.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,083 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/password.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,083 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/url.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,084 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/multiple_input.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,084 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/select_date.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,084 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/select_option.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,084 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,084 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/select.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,084 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/multiple_hidden.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,084 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/hidden.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,084 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/clearable_file_input.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,085 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/file.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,085 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/datetime.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,085 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/date.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,085 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/textarea.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,085 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/number.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,085 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/text.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,085 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/input_option.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,085 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/splithiddendatetime.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,086 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/attrs.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,086 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox_select.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,086 root INFO copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox_option.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/widgets
2025-04-22 20:54:05,086 root INFO copying build/lib/django/forms/jinja2/django/forms/div.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms
2025-04-22 20:54:05,086 root INFO copying build/lib/django/forms/jinja2/django/forms/p.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms
2025-04-22 20:54:05,086 root INFO creating build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/formsets
2025-04-22 20:54:05,086 root INFO copying build/lib/django/forms/jinja2/django/forms/formsets/table.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/formsets
2025-04-22 20:54:05,087 root INFO copying build/lib/django/forms/jinja2/django/forms/formsets/default.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/formsets
2025-04-22 20:54:05,087 root INFO copying build/lib/django/forms/jinja2/django/forms/formsets/div.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/formsets
2025-04-22 20:54:05,087 root INFO copying build/lib/django/forms/jinja2/django/forms/formsets/p.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/formsets
2025-04-22 20:54:05,087 root INFO copying build/lib/django/forms/jinja2/django/forms/formsets/ul.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms/formsets
2025-04-22 20:54:05,087 root INFO copying build/lib/django/forms/jinja2/django/forms/attrs.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms
2025-04-22 20:54:05,087 root INFO copying build/lib/django/forms/jinja2/django/forms/ul.html -> build/bdist.linux-aarch64/wheel/django/forms/jinja2/django/forms
2025-04-22 20:54:05,087 root INFO copying build/lib/django/forms/models.py -> build/bdist.linux-aarch64/wheel/django/forms
2025-04-22 20:54:05,088 root INFO copying build/lib/django/forms/utils.py -> build/bdist.linux-aarch64/wheel/django/forms
2025-04-22 20:54:05,088 root INFO copying build/lib/django/forms/renderers.py -> build/bdist.linux-aarch64/wheel/django/forms
2025-04-22 20:54:05,088 root INFO copying build/lib/django/forms/fields.py -> build/bdist.linux-aarch64/wheel/django/forms
2025-04-22 20:54:05,088 root INFO creating build/bdist.linux-aarch64/wheel/django/forms/templates
2025-04-22 20:54:05,088 root INFO creating build/bdist.linux-aarch64/wheel/django/forms/templates/django
2025-04-22 20:54:05,089 root INFO creating build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms
2025-04-22 20:54:05,089 root INFO copying build/lib/django/forms/templates/django/forms/table.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms
2025-04-22 20:54:05,089 root INFO copying build/lib/django/forms/templates/django/forms/label.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms
2025-04-22 20:54:05,089 root INFO copying build/lib/django/forms/templates/django/forms/default.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms
2025-04-22 20:54:05,089 root INFO creating build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/errors
2025-04-22 20:54:05,089 root INFO creating build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/errors/dict
2025-04-22 20:54:05,089 root INFO copying build/lib/django/forms/templates/django/forms/errors/dict/default.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/errors/dict
2025-04-22 20:54:05,089 root INFO copying build/lib/django/forms/templates/django/forms/errors/dict/text.txt -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/errors/dict
2025-04-22 20:54:05,090 root INFO copying build/lib/django/forms/templates/django/forms/errors/dict/ul.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/errors/dict
2025-04-22 20:54:05,090 root INFO creating build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/errors/list
2025-04-22 20:54:05,090 root INFO copying build/lib/django/forms/templates/django/forms/errors/list/default.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/errors/list
2025-04-22 20:54:05,090 root INFO copying build/lib/django/forms/templates/django/forms/errors/list/text.txt -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/errors/list
2025-04-22 20:54:05,090 root INFO copying build/lib/django/forms/templates/django/forms/errors/list/ul.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/errors/list
2025-04-22 20:54:05,090 root INFO creating build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,090 root INFO copying build/lib/django/forms/templates/django/forms/widgets/radio.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,090 root INFO copying build/lib/django/forms/templates/django/forms/widgets/multiwidget.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,091 root INFO copying build/lib/django/forms/templates/django/forms/widgets/radio_option.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,091 root INFO copying build/lib/django/forms/templates/django/forms/widgets/input.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,091 root INFO copying build/lib/django/forms/templates/django/forms/widgets/time.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,091 root INFO copying build/lib/django/forms/templates/django/forms/widgets/email.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,091 root INFO copying build/lib/django/forms/templates/django/forms/widgets/splitdatetime.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,091 root INFO copying build/lib/django/forms/templates/django/forms/widgets/password.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,091 root INFO copying build/lib/django/forms/templates/django/forms/widgets/url.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,092 root INFO copying build/lib/django/forms/templates/django/forms/widgets/multiple_input.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,092 root INFO copying build/lib/django/forms/templates/django/forms/widgets/select_date.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,092 root INFO copying build/lib/django/forms/templates/django/forms/widgets/select_option.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,092 root INFO copying build/lib/django/forms/templates/django/forms/widgets/checkbox.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,092 root INFO copying build/lib/django/forms/templates/django/forms/widgets/select.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,092 root INFO copying build/lib/django/forms/templates/django/forms/widgets/multiple_hidden.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,093 root INFO copying build/lib/django/forms/templates/django/forms/widgets/hidden.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,093 root INFO copying build/lib/django/forms/templates/django/forms/widgets/clearable_file_input.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,093 root INFO copying build/lib/django/forms/templates/django/forms/widgets/file.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,093 root INFO copying build/lib/django/forms/templates/django/forms/widgets/datetime.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,093 root INFO copying build/lib/django/forms/templates/django/forms/widgets/date.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,093 root INFO copying build/lib/django/forms/templates/django/forms/widgets/textarea.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,093 root INFO copying build/lib/django/forms/templates/django/forms/widgets/number.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,093 root INFO copying build/lib/django/forms/templates/django/forms/widgets/text.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,094 root INFO copying build/lib/django/forms/templates/django/forms/widgets/input_option.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,094 root INFO copying build/lib/django/forms/templates/django/forms/widgets/splithiddendatetime.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,094 root INFO copying build/lib/django/forms/templates/django/forms/widgets/attrs.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,094 root INFO copying build/lib/django/forms/templates/django/forms/widgets/checkbox_select.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,094 root INFO copying build/lib/django/forms/templates/django/forms/widgets/checkbox_option.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/widgets
2025-04-22 20:54:05,094 root INFO copying build/lib/django/forms/templates/django/forms/div.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms
2025-04-22 20:54:05,094 root INFO copying build/lib/django/forms/templates/django/forms/p.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms
2025-04-22 20:54:05,095 root INFO creating build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/formsets
2025-04-22 20:54:05,095 root INFO copying build/lib/django/forms/templates/django/forms/formsets/table.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/formsets
2025-04-22 20:54:05,095 root INFO copying build/lib/django/forms/templates/django/forms/formsets/default.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/formsets
2025-04-22 20:54:05,095 root INFO copying build/lib/django/forms/templates/django/forms/formsets/div.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/formsets
2025-04-22 20:54:05,095 root INFO copying build/lib/django/forms/templates/django/forms/formsets/p.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/formsets
2025-04-22 20:54:05,095 root INFO copying build/lib/django/forms/templates/django/forms/formsets/ul.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms/formsets
2025-04-22 20:54:05,095 root INFO copying build/lib/django/forms/templates/django/forms/attrs.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms
2025-04-22 20:54:05,096 root INFO copying build/lib/django/forms/templates/django/forms/ul.html -> build/bdist.linux-aarch64/wheel/django/forms/templates/django/forms
2025-04-22 20:54:05,096 root INFO copying build/lib/django/forms/boundfield.py -> build/bdist.linux-aarch64/wheel/django/forms
2025-04-22 20:54:05,096 root INFO copying build/lib/django/forms/formsets.py -> build/bdist.linux-aarch64/wheel/django/forms
2025-04-22 20:54:05,096 root INFO creating build/bdist.linux-aarch64/wheel/django/apps
2025-04-22 20:54:05,096 root INFO copying build/lib/django/apps/__init__.py -> build/bdist.linux-aarch64/wheel/django/apps
2025-04-22 20:54:05,096 root INFO copying build/lib/django/apps/registry.py -> build/bdist.linux-aarch64/wheel/django/apps
2025-04-22 20:54:05,097 root INFO copying build/lib/django/apps/config.py -> build/bdist.linux-aarch64/wheel/django/apps
2025-04-22 20:54:05,097 root INFO running install_egg_info
2025-04-22 20:54:05,099 root INFO Copying Django.egg-info to build/bdist.linux-aarch64/wheel/Django-4.2.20-py3.12.egg-info
2025-04-22 20:54:05,100 root INFO running install_scripts
2025-04-22 20:54:05,103 root INFO creating build/bdist.linux-aarch64/wheel/Django-4.2.20.dist-info/WHEEL
2025-04-22 20:54:05,104 wheel INFO creating '/home/buildozer/aports/community/py3-django/src/Django-4.2.20/.dist/.tmp-tuq7k683/Django-4.2.20-py3-none-any.whl' and adding 'build/bdist.linux-aarch64/wheel' to it
2025-04-22 20:54:05,104 wheel INFO adding 'django/__init__.py'
2025-04-22 20:54:05,105 wheel INFO adding 'django/__main__.py'
2025-04-22 20:54:05,105 wheel INFO adding 'django/shortcuts.py'
2025-04-22 20:54:05,105 wheel INFO adding 'django/apps/__init__.py'
2025-04-22 20:54:05,106 wheel INFO adding 'django/apps/config.py'
2025-04-22 20:54:05,106 wheel INFO adding 'django/apps/registry.py'
2025-04-22 20:54:05,106 wheel INFO adding 'django/conf/__init__.py'
2025-04-22 20:54:05,106 wheel INFO adding 'django/conf/global_settings.py'
2025-04-22 20:54:05,107 wheel INFO adding 'django/conf/app_template/__init__.py-tpl'
2025-04-22 20:54:05,107 wheel INFO adding 'django/conf/app_template/admin.py-tpl'
2025-04-22 20:54:05,107 wheel INFO adding 'django/conf/app_template/apps.py-tpl'
2025-04-22 20:54:05,107 wheel INFO adding 'django/conf/app_template/models.py-tpl'
2025-04-22 20:54:05,107 wheel INFO adding 'django/conf/app_template/tests.py-tpl'
2025-04-22 20:54:05,108 wheel INFO adding 'django/conf/app_template/views.py-tpl'
2025-04-22 20:54:05,108 wheel INFO adding 'django/conf/app_template/migrations/__init__.py-tpl'
2025-04-22 20:54:05,108 wheel INFO adding 'django/conf/locale/__init__.py'
2025-04-22 20:54:05,109 wheel INFO adding 'django/conf/locale/af/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,109 wheel INFO adding 'django/conf/locale/af/LC_MESSAGES/django.po'
2025-04-22 20:54:05,109 wheel INFO adding 'django/conf/locale/ar/__init__.py'
2025-04-22 20:54:05,110 wheel INFO adding 'django/conf/locale/ar/formats.py'
2025-04-22 20:54:05,110 wheel INFO adding 'django/conf/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,110 wheel INFO adding 'django/conf/locale/ar/LC_MESSAGES/django.po'
2025-04-22 20:54:05,110 wheel INFO adding 'django/conf/locale/ar_DZ/__init__.py'
2025-04-22 20:54:05,110 wheel INFO adding 'django/conf/locale/ar_DZ/formats.py'
2025-04-22 20:54:05,111 wheel INFO adding 'django/conf/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,111 wheel INFO adding 'django/conf/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 20:54:05,111 wheel INFO adding 'django/conf/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,112 wheel INFO adding 'django/conf/locale/ast/LC_MESSAGES/django.po'
2025-04-22 20:54:05,112 wheel INFO adding 'django/conf/locale/az/__init__.py'
2025-04-22 20:54:05,112 wheel INFO adding 'django/conf/locale/az/formats.py'
2025-04-22 20:54:05,112 wheel INFO adding 'django/conf/locale/az/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,113 wheel INFO adding 'django/conf/locale/az/LC_MESSAGES/django.po'
2025-04-22 20:54:05,113 wheel INFO adding 'django/conf/locale/be/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,113 wheel INFO adding 'django/conf/locale/be/LC_MESSAGES/django.po'
2025-04-22 20:54:05,113 wheel INFO adding 'django/conf/locale/bg/__init__.py'
2025-04-22 20:54:05,114 wheel INFO adding 'django/conf/locale/bg/formats.py'
2025-04-22 20:54:05,114 wheel INFO adding 'django/conf/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,114 wheel INFO adding 'django/conf/locale/bg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,114 wheel INFO adding 'django/conf/locale/bn/__init__.py'
2025-04-22 20:54:05,115 wheel INFO adding 'django/conf/locale/bn/formats.py'
2025-04-22 20:54:05,115 wheel INFO adding 'django/conf/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,115 wheel INFO adding 'django/conf/locale/bn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,116 wheel INFO adding 'django/conf/locale/br/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,116 wheel INFO adding 'django/conf/locale/br/LC_MESSAGES/django.po'
2025-04-22 20:54:05,116 wheel INFO adding 'django/conf/locale/bs/__init__.py'
2025-04-22 20:54:05,116 wheel INFO adding 'django/conf/locale/bs/formats.py'
2025-04-22 20:54:05,117 wheel INFO adding 'django/conf/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,117 wheel INFO adding 'django/conf/locale/bs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,117 wheel INFO adding 'django/conf/locale/ca/__init__.py'
2025-04-22 20:54:05,117 wheel INFO adding 'django/conf/locale/ca/formats.py'
2025-04-22 20:54:05,117 wheel INFO adding 'django/conf/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,118 wheel INFO adding 'django/conf/locale/ca/LC_MESSAGES/django.po'
2025-04-22 20:54:05,118 wheel INFO adding 'django/conf/locale/ckb/__init__.py'
2025-04-22 20:54:05,118 wheel INFO adding 'django/conf/locale/ckb/formats.py'
2025-04-22 20:54:05,118 wheel INFO adding 'django/conf/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,118 wheel INFO adding 'django/conf/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,119 wheel INFO adding 'django/conf/locale/cs/__init__.py'
2025-04-22 20:54:05,119 wheel INFO adding 'django/conf/locale/cs/formats.py'
2025-04-22 20:54:05,119 wheel INFO adding 'django/conf/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,119 wheel INFO adding 'django/conf/locale/cs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,120 wheel INFO adding 'django/conf/locale/cy/__init__.py'
2025-04-22 20:54:05,120 wheel INFO adding 'django/conf/locale/cy/formats.py'
2025-04-22 20:54:05,120 wheel INFO adding 'django/conf/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,120 wheel INFO adding 'django/conf/locale/cy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,120 wheel INFO adding 'django/conf/locale/da/__init__.py'
2025-04-22 20:54:05,120 wheel INFO adding 'django/conf/locale/da/formats.py'
2025-04-22 20:54:05,121 wheel INFO adding 'django/conf/locale/da/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,121 wheel INFO adding 'django/conf/locale/da/LC_MESSAGES/django.po'
2025-04-22 20:54:05,121 wheel INFO adding 'django/conf/locale/de/__init__.py'
2025-04-22 20:54:05,121 wheel INFO adding 'django/conf/locale/de/formats.py'
2025-04-22 20:54:05,121 wheel INFO adding 'django/conf/locale/de/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,122 wheel INFO adding 'django/conf/locale/de/LC_MESSAGES/django.po'
2025-04-22 20:54:05,122 wheel INFO adding 'django/conf/locale/de_CH/__init__.py'
2025-04-22 20:54:05,122 wheel INFO adding 'django/conf/locale/de_CH/formats.py'
2025-04-22 20:54:05,122 wheel INFO adding 'django/conf/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,123 wheel INFO adding 'django/conf/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,123 wheel INFO adding 'django/conf/locale/el/__init__.py'
2025-04-22 20:54:05,123 wheel INFO adding 'django/conf/locale/el/formats.py'
2025-04-22 20:54:05,123 wheel INFO adding 'django/conf/locale/el/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,123 wheel INFO adding 'django/conf/locale/el/LC_MESSAGES/django.po'
2025-04-22 20:54:05,124 wheel INFO adding 'django/conf/locale/en/__init__.py'
2025-04-22 20:54:05,124 wheel INFO adding 'django/conf/locale/en/formats.py'
2025-04-22 20:54:05,124 wheel INFO adding 'django/conf/locale/en/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,124 wheel INFO adding 'django/conf/locale/en/LC_MESSAGES/django.po'
2025-04-22 20:54:05,124 wheel INFO adding 'django/conf/locale/en_AU/__init__.py'
2025-04-22 20:54:05,125 wheel INFO adding 'django/conf/locale/en_AU/formats.py'
2025-04-22 20:54:05,125 wheel INFO adding 'django/conf/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,125 wheel INFO adding 'django/conf/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 20:54:05,125 wheel INFO adding 'django/conf/locale/en_GB/__init__.py'
2025-04-22 20:54:05,125 wheel INFO adding 'django/conf/locale/en_GB/formats.py'
2025-04-22 20:54:05,126 wheel INFO adding 'django/conf/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,126 wheel INFO adding 'django/conf/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 20:54:05,126 wheel INFO adding 'django/conf/locale/eo/__init__.py'
2025-04-22 20:54:05,126 wheel INFO adding 'django/conf/locale/eo/formats.py'
2025-04-22 20:54:05,126 wheel INFO adding 'django/conf/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,127 wheel INFO adding 'django/conf/locale/eo/LC_MESSAGES/django.po'
2025-04-22 20:54:05,127 wheel INFO adding 'django/conf/locale/es/__init__.py'
2025-04-22 20:54:05,127 wheel INFO adding 'django/conf/locale/es/formats.py'
2025-04-22 20:54:05,127 wheel INFO adding 'django/conf/locale/es/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,127 wheel INFO adding 'django/conf/locale/es/LC_MESSAGES/django.po'
2025-04-22 20:54:05,128 wheel INFO adding 'django/conf/locale/es_AR/__init__.py'
2025-04-22 20:54:05,128 wheel INFO adding 'django/conf/locale/es_AR/formats.py'
2025-04-22 20:54:05,128 wheel INFO adding 'django/conf/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,128 wheel INFO adding 'django/conf/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,129 wheel INFO adding 'django/conf/locale/es_CO/__init__.py'
2025-04-22 20:54:05,129 wheel INFO adding 'django/conf/locale/es_CO/formats.py'
2025-04-22 20:54:05,129 wheel INFO adding 'django/conf/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,129 wheel INFO adding 'django/conf/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 20:54:05,130 wheel INFO adding 'django/conf/locale/es_MX/__init__.py'
2025-04-22 20:54:05,130 wheel INFO adding 'django/conf/locale/es_MX/formats.py'
2025-04-22 20:54:05,130 wheel INFO adding 'django/conf/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,130 wheel INFO adding 'django/conf/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 20:54:05,130 wheel INFO adding 'django/conf/locale/es_NI/__init__.py'
2025-04-22 20:54:05,131 wheel INFO adding 'django/conf/locale/es_NI/formats.py'
2025-04-22 20:54:05,131 wheel INFO adding 'django/conf/locale/es_PR/__init__.py'
2025-04-22 20:54:05,131 wheel INFO adding 'django/conf/locale/es_PR/formats.py'
2025-04-22 20:54:05,131 wheel INFO adding 'django/conf/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,131 wheel INFO adding 'django/conf/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 20:54:05,131 wheel INFO adding 'django/conf/locale/et/__init__.py'
2025-04-22 20:54:05,132 wheel INFO adding 'django/conf/locale/et/formats.py'
2025-04-22 20:54:05,132 wheel INFO adding 'django/conf/locale/et/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,132 wheel INFO adding 'django/conf/locale/et/LC_MESSAGES/django.po'
2025-04-22 20:54:05,132 wheel INFO adding 'django/conf/locale/eu/__init__.py'
2025-04-22 20:54:05,132 wheel INFO adding 'django/conf/locale/eu/formats.py'
2025-04-22 20:54:05,133 wheel INFO adding 'django/conf/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,133 wheel INFO adding 'django/conf/locale/eu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,133 wheel INFO adding 'django/conf/locale/fa/__init__.py'
2025-04-22 20:54:05,133 wheel INFO adding 'django/conf/locale/fa/formats.py'
2025-04-22 20:54:05,133 wheel INFO adding 'django/conf/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,134 wheel INFO adding 'django/conf/locale/fa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,134 wheel INFO adding 'django/conf/locale/fi/__init__.py'
2025-04-22 20:54:05,134 wheel INFO adding 'django/conf/locale/fi/formats.py'
2025-04-22 20:54:05,134 wheel INFO adding 'django/conf/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,134 wheel INFO adding 'django/conf/locale/fi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,135 wheel INFO adding 'django/conf/locale/fr/__init__.py'
2025-04-22 20:54:05,135 wheel INFO adding 'django/conf/locale/fr/formats.py'
2025-04-22 20:54:05,135 wheel INFO adding 'django/conf/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,135 wheel INFO adding 'django/conf/locale/fr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,135 wheel INFO adding 'django/conf/locale/fy/__init__.py'
2025-04-22 20:54:05,136 wheel INFO adding 'django/conf/locale/fy/formats.py'
2025-04-22 20:54:05,136 wheel INFO adding 'django/conf/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,136 wheel INFO adding 'django/conf/locale/fy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,136 wheel INFO adding 'django/conf/locale/ga/__init__.py'
2025-04-22 20:54:05,136 wheel INFO adding 'django/conf/locale/ga/formats.py'
2025-04-22 20:54:05,136 wheel INFO adding 'django/conf/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,137 wheel INFO adding 'django/conf/locale/ga/LC_MESSAGES/django.po'
2025-04-22 20:54:05,137 wheel INFO adding 'django/conf/locale/gd/__init__.py'
2025-04-22 20:54:05,137 wheel INFO adding 'django/conf/locale/gd/formats.py'
2025-04-22 20:54:05,137 wheel INFO adding 'django/conf/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,137 wheel INFO adding 'django/conf/locale/gd/LC_MESSAGES/django.po'
2025-04-22 20:54:05,138 wheel INFO adding 'django/conf/locale/gl/__init__.py'
2025-04-22 20:54:05,138 wheel INFO adding 'django/conf/locale/gl/formats.py'
2025-04-22 20:54:05,138 wheel INFO adding 'django/conf/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,138 wheel INFO adding 'django/conf/locale/gl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,139 wheel INFO adding 'django/conf/locale/he/__init__.py'
2025-04-22 20:54:05,139 wheel INFO adding 'django/conf/locale/he/formats.py'
2025-04-22 20:54:05,139 wheel INFO adding 'django/conf/locale/he/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,139 wheel INFO adding 'django/conf/locale/he/LC_MESSAGES/django.po'
2025-04-22 20:54:05,139 wheel INFO adding 'django/conf/locale/hi/__init__.py'
2025-04-22 20:54:05,140 wheel INFO adding 'django/conf/locale/hi/formats.py'
2025-04-22 20:54:05,140 wheel INFO adding 'django/conf/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,140 wheel INFO adding 'django/conf/locale/hi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,140 wheel INFO adding 'django/conf/locale/hr/__init__.py'
2025-04-22 20:54:05,140 wheel INFO adding 'django/conf/locale/hr/formats.py'
2025-04-22 20:54:05,140 wheel INFO adding 'django/conf/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,141 wheel INFO adding 'django/conf/locale/hr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,141 wheel INFO adding 'django/conf/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,141 wheel INFO adding 'django/conf/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,141 wheel INFO adding 'django/conf/locale/hu/__init__.py'
2025-04-22 20:54:05,142 wheel INFO adding 'django/conf/locale/hu/formats.py'
2025-04-22 20:54:05,142 wheel INFO adding 'django/conf/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,142 wheel INFO adding 'django/conf/locale/hu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,142 wheel INFO adding 'django/conf/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,143 wheel INFO adding 'django/conf/locale/hy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,143 wheel INFO adding 'django/conf/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,143 wheel INFO adding 'django/conf/locale/ia/LC_MESSAGES/django.po'
2025-04-22 20:54:05,143 wheel INFO adding 'django/conf/locale/id/__init__.py'
2025-04-22 20:54:05,143 wheel INFO adding 'django/conf/locale/id/formats.py'
2025-04-22 20:54:05,144 wheel INFO adding 'django/conf/locale/id/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,144 wheel INFO adding 'django/conf/locale/id/LC_MESSAGES/django.po'
2025-04-22 20:54:05,144 wheel INFO adding 'django/conf/locale/ig/__init__.py'
2025-04-22 20:54:05,144 wheel INFO adding 'django/conf/locale/ig/formats.py'
2025-04-22 20:54:05,144 wheel INFO adding 'django/conf/locale/ig/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,145 wheel INFO adding 'django/conf/locale/ig/LC_MESSAGES/django.po'
2025-04-22 20:54:05,145 wheel INFO adding 'django/conf/locale/io/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,145 wheel INFO adding 'django/conf/locale/io/LC_MESSAGES/django.po'
2025-04-22 20:54:05,145 wheel INFO adding 'django/conf/locale/is/__init__.py'
2025-04-22 20:54:05,145 wheel INFO adding 'django/conf/locale/is/formats.py'
2025-04-22 20:54:05,146 wheel INFO adding 'django/conf/locale/is/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,146 wheel INFO adding 'django/conf/locale/is/LC_MESSAGES/django.po'
2025-04-22 20:54:05,146 wheel INFO adding 'django/conf/locale/it/__init__.py'
2025-04-22 20:54:05,146 wheel INFO adding 'django/conf/locale/it/formats.py'
2025-04-22 20:54:05,146 wheel INFO adding 'django/conf/locale/it/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,147 wheel INFO adding 'django/conf/locale/it/LC_MESSAGES/django.po'
2025-04-22 20:54:05,147 wheel INFO adding 'django/conf/locale/ja/__init__.py'
2025-04-22 20:54:05,147 wheel INFO adding 'django/conf/locale/ja/formats.py'
2025-04-22 20:54:05,147 wheel INFO adding 'django/conf/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,147 wheel INFO adding 'django/conf/locale/ja/LC_MESSAGES/django.po'
2025-04-22 20:54:05,148 wheel INFO adding 'django/conf/locale/ka/__init__.py'
2025-04-22 20:54:05,148 wheel INFO adding 'django/conf/locale/ka/formats.py'
2025-04-22 20:54:05,148 wheel INFO adding 'django/conf/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,148 wheel INFO adding 'django/conf/locale/ka/LC_MESSAGES/django.po'
2025-04-22 20:54:05,148 wheel INFO adding 'django/conf/locale/kab/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,149 wheel INFO adding 'django/conf/locale/kab/LC_MESSAGES/django.po'
2025-04-22 20:54:05,149 wheel INFO adding 'django/conf/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,149 wheel INFO adding 'django/conf/locale/kk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,149 wheel INFO adding 'django/conf/locale/km/__init__.py'
2025-04-22 20:54:05,149 wheel INFO adding 'django/conf/locale/km/formats.py'
2025-04-22 20:54:05,150 wheel INFO adding 'django/conf/locale/km/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,150 wheel INFO adding 'django/conf/locale/km/LC_MESSAGES/django.po'
2025-04-22 20:54:05,150 wheel INFO adding 'django/conf/locale/kn/__init__.py'
2025-04-22 20:54:05,150 wheel INFO adding 'django/conf/locale/kn/formats.py'
2025-04-22 20:54:05,150 wheel INFO adding 'django/conf/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,150 wheel INFO adding 'django/conf/locale/kn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,151 wheel INFO adding 'django/conf/locale/ko/__init__.py'
2025-04-22 20:54:05,151 wheel INFO adding 'django/conf/locale/ko/formats.py'
2025-04-22 20:54:05,151 wheel INFO adding 'django/conf/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,151 wheel INFO adding 'django/conf/locale/ko/LC_MESSAGES/django.po'
2025-04-22 20:54:05,151 wheel INFO adding 'django/conf/locale/ky/__init__.py'
2025-04-22 20:54:05,152 wheel INFO adding 'django/conf/locale/ky/formats.py'
2025-04-22 20:54:05,152 wheel INFO adding 'django/conf/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,152 wheel INFO adding 'django/conf/locale/ky/LC_MESSAGES/django.po'
2025-04-22 20:54:05,152 wheel INFO adding 'django/conf/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,153 wheel INFO adding 'django/conf/locale/lb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,153 wheel INFO adding 'django/conf/locale/lt/__init__.py'
2025-04-22 20:54:05,153 wheel INFO adding 'django/conf/locale/lt/formats.py'
2025-04-22 20:54:05,153 wheel INFO adding 'django/conf/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,153 wheel INFO adding 'django/conf/locale/lt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,153 wheel INFO adding 'django/conf/locale/lv/__init__.py'
2025-04-22 20:54:05,154 wheel INFO adding 'django/conf/locale/lv/formats.py'
2025-04-22 20:54:05,154 wheel INFO adding 'django/conf/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,154 wheel INFO adding 'django/conf/locale/lv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,154 wheel INFO adding 'django/conf/locale/mk/__init__.py'
2025-04-22 20:54:05,154 wheel INFO adding 'django/conf/locale/mk/formats.py'
2025-04-22 20:54:05,155 wheel INFO adding 'django/conf/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,155 wheel INFO adding 'django/conf/locale/mk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,155 wheel INFO adding 'django/conf/locale/ml/__init__.py'
2025-04-22 20:54:05,155 wheel INFO adding 'django/conf/locale/ml/formats.py'
2025-04-22 20:54:05,155 wheel INFO adding 'django/conf/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,156 wheel INFO adding 'django/conf/locale/ml/LC_MESSAGES/django.po'
2025-04-22 20:54:05,156 wheel INFO adding 'django/conf/locale/mn/__init__.py'
2025-04-22 20:54:05,156 wheel INFO adding 'django/conf/locale/mn/formats.py'
2025-04-22 20:54:05,156 wheel INFO adding 'django/conf/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,157 wheel INFO adding 'django/conf/locale/mn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,157 wheel INFO adding 'django/conf/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,157 wheel INFO adding 'django/conf/locale/mr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,157 wheel INFO adding 'django/conf/locale/ms/__init__.py'
2025-04-22 20:54:05,157 wheel INFO adding 'django/conf/locale/ms/formats.py'
2025-04-22 20:54:05,157 wheel INFO adding 'django/conf/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,158 wheel INFO adding 'django/conf/locale/ms/LC_MESSAGES/django.po'
2025-04-22 20:54:05,158 wheel INFO adding 'django/conf/locale/my/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,158 wheel INFO adding 'django/conf/locale/my/LC_MESSAGES/django.po'
2025-04-22 20:54:05,158 wheel INFO adding 'django/conf/locale/nb/__init__.py'
2025-04-22 20:54:05,158 wheel INFO adding 'django/conf/locale/nb/formats.py'
2025-04-22 20:54:05,159 wheel INFO adding 'django/conf/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,159 wheel INFO adding 'django/conf/locale/nb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,159 wheel INFO adding 'django/conf/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,159 wheel INFO adding 'django/conf/locale/ne/LC_MESSAGES/django.po'
2025-04-22 20:54:05,160 wheel INFO adding 'django/conf/locale/nl/__init__.py'
2025-04-22 20:54:05,160 wheel INFO adding 'django/conf/locale/nl/formats.py'
2025-04-22 20:54:05,160 wheel INFO adding 'django/conf/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,160 wheel INFO adding 'django/conf/locale/nl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,160 wheel INFO adding 'django/conf/locale/nn/__init__.py'
2025-04-22 20:54:05,161 wheel INFO adding 'django/conf/locale/nn/formats.py'
2025-04-22 20:54:05,161 wheel INFO adding 'django/conf/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,161 wheel INFO adding 'django/conf/locale/nn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,161 wheel INFO adding 'django/conf/locale/os/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,161 wheel INFO adding 'django/conf/locale/os/LC_MESSAGES/django.po'
2025-04-22 20:54:05,162 wheel INFO adding 'django/conf/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,162 wheel INFO adding 'django/conf/locale/pa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,162 wheel INFO adding 'django/conf/locale/pl/__init__.py'
2025-04-22 20:54:05,162 wheel INFO adding 'django/conf/locale/pl/formats.py'
2025-04-22 20:54:05,162 wheel INFO adding 'django/conf/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,163 wheel INFO adding 'django/conf/locale/pl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,163 wheel INFO adding 'django/conf/locale/pt/__init__.py'
2025-04-22 20:54:05,163 wheel INFO adding 'django/conf/locale/pt/formats.py'
2025-04-22 20:54:05,163 wheel INFO adding 'django/conf/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,163 wheel INFO adding 'django/conf/locale/pt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,164 wheel INFO adding 'django/conf/locale/pt_BR/__init__.py'
2025-04-22 20:54:05,164 wheel INFO adding 'django/conf/locale/pt_BR/formats.py'
2025-04-22 20:54:05,164 wheel INFO adding 'django/conf/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,164 wheel INFO adding 'django/conf/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,164 wheel INFO adding 'django/conf/locale/ro/__init__.py'
2025-04-22 20:54:05,165 wheel INFO adding 'django/conf/locale/ro/formats.py'
2025-04-22 20:54:05,165 wheel INFO adding 'django/conf/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,165 wheel INFO adding 'django/conf/locale/ro/LC_MESSAGES/django.po'
2025-04-22 20:54:05,165 wheel INFO adding 'django/conf/locale/ru/__init__.py'
2025-04-22 20:54:05,166 wheel INFO adding 'django/conf/locale/ru/formats.py'
2025-04-22 20:54:05,166 wheel INFO adding 'django/conf/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,166 wheel INFO adding 'django/conf/locale/ru/LC_MESSAGES/django.po'
2025-04-22 20:54:05,166 wheel INFO adding 'django/conf/locale/sk/__init__.py'
2025-04-22 20:54:05,166 wheel INFO adding 'django/conf/locale/sk/formats.py'
2025-04-22 20:54:05,167 wheel INFO adding 'django/conf/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,167 wheel INFO adding 'django/conf/locale/sk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,167 wheel INFO adding 'django/conf/locale/sl/__init__.py'
2025-04-22 20:54:05,167 wheel INFO adding 'django/conf/locale/sl/formats.py'
2025-04-22 20:54:05,167 wheel INFO adding 'django/conf/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,168 wheel INFO adding 'django/conf/locale/sl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,168 wheel INFO adding 'django/conf/locale/sq/__init__.py'
2025-04-22 20:54:05,168 wheel INFO adding 'django/conf/locale/sq/formats.py'
2025-04-22 20:54:05,168 wheel INFO adding 'django/conf/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,168 wheel INFO adding 'django/conf/locale/sq/LC_MESSAGES/django.po'
2025-04-22 20:54:05,169 wheel INFO adding 'django/conf/locale/sr/__init__.py'
2025-04-22 20:54:05,169 wheel INFO adding 'django/conf/locale/sr/formats.py'
2025-04-22 20:54:05,169 wheel INFO adding 'django/conf/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,169 wheel INFO adding 'django/conf/locale/sr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,170 wheel INFO adding 'django/conf/locale/sr_Latn/__init__.py'
2025-04-22 20:54:05,170 wheel INFO adding 'django/conf/locale/sr_Latn/formats.py'
2025-04-22 20:54:05,170 wheel INFO adding 'django/conf/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,170 wheel INFO adding 'django/conf/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,170 wheel INFO adding 'django/conf/locale/sv/__init__.py'
2025-04-22 20:54:05,170 wheel INFO adding 'django/conf/locale/sv/formats.py'
2025-04-22 20:54:05,171 wheel INFO adding 'django/conf/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,171 wheel INFO adding 'django/conf/locale/sv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,171 wheel INFO adding 'django/conf/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,171 wheel INFO adding 'django/conf/locale/sw/LC_MESSAGES/django.po'
2025-04-22 20:54:05,172 wheel INFO adding 'django/conf/locale/ta/__init__.py'
2025-04-22 20:54:05,172 wheel INFO adding 'django/conf/locale/ta/formats.py'
2025-04-22 20:54:05,172 wheel INFO adding 'django/conf/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,172 wheel INFO adding 'django/conf/locale/ta/LC_MESSAGES/django.po'
2025-04-22 20:54:05,172 wheel INFO adding 'django/conf/locale/te/__init__.py'
2025-04-22 20:54:05,172 wheel INFO adding 'django/conf/locale/te/formats.py'
2025-04-22 20:54:05,173 wheel INFO adding 'django/conf/locale/te/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,173 wheel INFO adding 'django/conf/locale/te/LC_MESSAGES/django.po'
2025-04-22 20:54:05,173 wheel INFO adding 'django/conf/locale/tg/__init__.py'
2025-04-22 20:54:05,173 wheel INFO adding 'django/conf/locale/tg/formats.py'
2025-04-22 20:54:05,173 wheel INFO adding 'django/conf/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,174 wheel INFO adding 'django/conf/locale/tg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,174 wheel INFO adding 'django/conf/locale/th/__init__.py'
2025-04-22 20:54:05,174 wheel INFO adding 'django/conf/locale/th/formats.py'
2025-04-22 20:54:05,174 wheel INFO adding 'django/conf/locale/th/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,174 wheel INFO adding 'django/conf/locale/th/LC_MESSAGES/django.po'
2025-04-22 20:54:05,174 wheel INFO adding 'django/conf/locale/tk/__init__.py'
2025-04-22 20:54:05,175 wheel INFO adding 'django/conf/locale/tk/formats.py'
2025-04-22 20:54:05,175 wheel INFO adding 'django/conf/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,175 wheel INFO adding 'django/conf/locale/tk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,175 wheel INFO adding 'django/conf/locale/tr/__init__.py'
2025-04-22 20:54:05,175 wheel INFO adding 'django/conf/locale/tr/formats.py'
2025-04-22 20:54:05,176 wheel INFO adding 'django/conf/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,176 wheel INFO adding 'django/conf/locale/tr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,176 wheel INFO adding 'django/conf/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,176 wheel INFO adding 'django/conf/locale/tt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,177 wheel INFO adding 'django/conf/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,177 wheel INFO adding 'django/conf/locale/udm/LC_MESSAGES/django.po'
2025-04-22 20:54:05,177 wheel INFO adding 'django/conf/locale/uk/__init__.py'
2025-04-22 20:54:05,177 wheel INFO adding 'django/conf/locale/uk/formats.py'
2025-04-22 20:54:05,178 wheel INFO adding 'django/conf/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,178 wheel INFO adding 'django/conf/locale/uk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,178 wheel INFO adding 'django/conf/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,179 wheel INFO adding 'django/conf/locale/ur/LC_MESSAGES/django.po'
2025-04-22 20:54:05,179 wheel INFO adding 'django/conf/locale/uz/__init__.py'
2025-04-22 20:54:05,179 wheel INFO adding 'django/conf/locale/uz/formats.py'
2025-04-22 20:54:05,179 wheel INFO adding 'django/conf/locale/uz/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,179 wheel INFO adding 'django/conf/locale/uz/LC_MESSAGES/django.po'
2025-04-22 20:54:05,180 wheel INFO adding 'django/conf/locale/vi/__init__.py'
2025-04-22 20:54:05,180 wheel INFO adding 'django/conf/locale/vi/formats.py'
2025-04-22 20:54:05,180 wheel INFO adding 'django/conf/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,180 wheel INFO adding 'django/conf/locale/vi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,180 wheel INFO adding 'django/conf/locale/zh_Hans/__init__.py'
2025-04-22 20:54:05,180 wheel INFO adding 'django/conf/locale/zh_Hans/formats.py'
2025-04-22 20:54:05,181 wheel INFO adding 'django/conf/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,181 wheel INFO adding 'django/conf/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 20:54:05,181 wheel INFO adding 'django/conf/locale/zh_Hant/__init__.py'
2025-04-22 20:54:05,181 wheel INFO adding 'django/conf/locale/zh_Hant/formats.py'
2025-04-22 20:54:05,181 wheel INFO adding 'django/conf/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,182 wheel INFO adding 'django/conf/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 20:54:05,182 wheel INFO adding 'django/conf/project_template/manage.py-tpl'
2025-04-22 20:54:05,182 wheel INFO adding 'django/conf/project_template/project_name/__init__.py-tpl'
2025-04-22 20:54:05,182 wheel INFO adding 'django/conf/project_template/project_name/asgi.py-tpl'
2025-04-22 20:54:05,182 wheel INFO adding 'django/conf/project_template/project_name/settings.py-tpl'
2025-04-22 20:54:05,182 wheel INFO adding 'django/conf/project_template/project_name/urls.py-tpl'
2025-04-22 20:54:05,182 wheel INFO adding 'django/conf/project_template/project_name/wsgi.py-tpl'
2025-04-22 20:54:05,183 wheel INFO adding 'django/conf/urls/__init__.py'
2025-04-22 20:54:05,183 wheel INFO adding 'django/conf/urls/i18n.py'
2025-04-22 20:54:05,183 wheel INFO adding 'django/conf/urls/static.py'
2025-04-22 20:54:05,183 wheel INFO adding 'django/contrib/__init__.py'
2025-04-22 20:54:05,183 wheel INFO adding 'django/contrib/admin/__init__.py'
2025-04-22 20:54:05,183 wheel INFO adding 'django/contrib/admin/actions.py'
2025-04-22 20:54:05,183 wheel INFO adding 'django/contrib/admin/apps.py'
2025-04-22 20:54:05,184 wheel INFO adding 'django/contrib/admin/checks.py'
2025-04-22 20:54:05,184 wheel INFO adding 'django/contrib/admin/decorators.py'
2025-04-22 20:54:05,184 wheel INFO adding 'django/contrib/admin/exceptions.py'
2025-04-22 20:54:05,184 wheel INFO adding 'django/contrib/admin/filters.py'
2025-04-22 20:54:05,184 wheel INFO adding 'django/contrib/admin/forms.py'
2025-04-22 20:54:05,184 wheel INFO adding 'django/contrib/admin/helpers.py'
2025-04-22 20:54:05,185 wheel INFO adding 'django/contrib/admin/models.py'
2025-04-22 20:54:05,185 wheel INFO adding 'django/contrib/admin/options.py'
2025-04-22 20:54:05,185 wheel INFO adding 'django/contrib/admin/sites.py'
2025-04-22 20:54:05,186 wheel INFO adding 'django/contrib/admin/tests.py'
2025-04-22 20:54:05,186 wheel INFO adding 'django/contrib/admin/utils.py'
2025-04-22 20:54:05,186 wheel INFO adding 'django/contrib/admin/widgets.py'
2025-04-22 20:54:05,187 wheel INFO adding 'django/contrib/admin/locale/af/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,187 wheel INFO adding 'django/contrib/admin/locale/af/LC_MESSAGES/django.po'
2025-04-22 20:54:05,187 wheel INFO adding 'django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,187 wheel INFO adding 'django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,187 wheel INFO adding 'django/contrib/admin/locale/am/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,188 wheel INFO adding 'django/contrib/admin/locale/am/LC_MESSAGES/django.po'
2025-04-22 20:54:05,188 wheel INFO adding 'django/contrib/admin/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,188 wheel INFO adding 'django/contrib/admin/locale/ar/LC_MESSAGES/django.po'
2025-04-22 20:54:05,188 wheel INFO adding 'django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,189 wheel INFO adding 'django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,189 wheel INFO adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,189 wheel INFO adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 20:54:05,189 wheel INFO adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,189 wheel INFO adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,190 wheel INFO adding 'django/contrib/admin/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,190 wheel INFO adding 'django/contrib/admin/locale/ast/LC_MESSAGES/django.po'
2025-04-22 20:54:05,190 wheel INFO adding 'django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,190 wheel INFO adding 'django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,190 wheel INFO adding 'django/contrib/admin/locale/az/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,190 wheel INFO adding 'django/contrib/admin/locale/az/LC_MESSAGES/django.po'
2025-04-22 20:54:05,191 wheel INFO adding 'django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,191 wheel INFO adding 'django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,191 wheel INFO adding 'django/contrib/admin/locale/be/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,191 wheel INFO adding 'django/contrib/admin/locale/be/LC_MESSAGES/django.po'
2025-04-22 20:54:05,191 wheel INFO adding 'django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,191 wheel INFO adding 'django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,192 wheel INFO adding 'django/contrib/admin/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,192 wheel INFO adding 'django/contrib/admin/locale/bg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,192 wheel INFO adding 'django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,192 wheel INFO adding 'django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,193 wheel INFO adding 'django/contrib/admin/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,193 wheel INFO adding 'django/contrib/admin/locale/bn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,193 wheel INFO adding 'django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,193 wheel INFO adding 'django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,193 wheel INFO adding 'django/contrib/admin/locale/br/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,193 wheel INFO adding 'django/contrib/admin/locale/br/LC_MESSAGES/django.po'
2025-04-22 20:54:05,194 wheel INFO adding 'django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,194 wheel INFO adding 'django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,194 wheel INFO adding 'django/contrib/admin/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,194 wheel INFO adding 'django/contrib/admin/locale/bs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,194 wheel INFO adding 'django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,194 wheel INFO adding 'django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,195 wheel INFO adding 'django/contrib/admin/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,195 wheel INFO adding 'django/contrib/admin/locale/ca/LC_MESSAGES/django.po'
2025-04-22 20:54:05,195 wheel INFO adding 'django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,195 wheel INFO adding 'django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,195 wheel INFO adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,196 wheel INFO adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,196 wheel INFO adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,196 wheel INFO adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,196 wheel INFO adding 'django/contrib/admin/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,196 wheel INFO adding 'django/contrib/admin/locale/cs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,196 wheel INFO adding 'django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,197 wheel INFO adding 'django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,197 wheel INFO adding 'django/contrib/admin/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,197 wheel INFO adding 'django/contrib/admin/locale/cy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,197 wheel INFO adding 'django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,197 wheel INFO adding 'django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,197 wheel INFO adding 'django/contrib/admin/locale/da/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,198 wheel INFO adding 'django/contrib/admin/locale/da/LC_MESSAGES/django.po'
2025-04-22 20:54:05,198 wheel INFO adding 'django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,198 wheel INFO adding 'django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,198 wheel INFO adding 'django/contrib/admin/locale/de/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,198 wheel INFO adding 'django/contrib/admin/locale/de/LC_MESSAGES/django.po'
2025-04-22 20:54:05,199 wheel INFO adding 'django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,199 wheel INFO adding 'django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,199 wheel INFO adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,199 wheel INFO adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,199 wheel INFO adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,199 wheel INFO adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,200 wheel INFO adding 'django/contrib/admin/locale/el/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,200 wheel INFO adding 'django/contrib/admin/locale/el/LC_MESSAGES/django.po'
2025-04-22 20:54:05,200 wheel INFO adding 'django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,200 wheel INFO adding 'django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,200 wheel INFO adding 'django/contrib/admin/locale/en/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,201 wheel INFO adding 'django/contrib/admin/locale/en/LC_MESSAGES/django.po'
2025-04-22 20:54:05,201 wheel INFO adding 'django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,201 wheel INFO adding 'django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,201 wheel INFO adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,201 wheel INFO adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 20:54:05,201 wheel INFO adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,202 wheel INFO adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,202 wheel INFO adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,202 wheel INFO adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 20:54:05,202 wheel INFO adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,202 wheel INFO adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,203 wheel INFO adding 'django/contrib/admin/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,203 wheel INFO adding 'django/contrib/admin/locale/eo/LC_MESSAGES/django.po'
2025-04-22 20:54:05,203 wheel INFO adding 'django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,203 wheel INFO adding 'django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,203 wheel INFO adding 'django/contrib/admin/locale/es/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,203 wheel INFO adding 'django/contrib/admin/locale/es/LC_MESSAGES/django.po'
2025-04-22 20:54:05,204 wheel INFO adding 'django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,204 wheel INFO adding 'django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,204 wheel INFO adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,204 wheel INFO adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,204 wheel INFO adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,204 wheel INFO adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,205 wheel INFO adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,205 wheel INFO adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 20:54:05,205 wheel INFO adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,205 wheel INFO adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,206 wheel INFO adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,206 wheel INFO adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 20:54:05,206 wheel INFO adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,206 wheel INFO adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,206 wheel INFO adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,206 wheel INFO adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 20:54:05,207 wheel INFO adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,207 wheel INFO adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,207 wheel INFO adding 'django/contrib/admin/locale/et/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,207 wheel INFO adding 'django/contrib/admin/locale/et/LC_MESSAGES/django.po'
2025-04-22 20:54:05,207 wheel INFO adding 'django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,207 wheel INFO adding 'django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,208 wheel INFO adding 'django/contrib/admin/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,208 wheel INFO adding 'django/contrib/admin/locale/eu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,208 wheel INFO adding 'django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,208 wheel INFO adding 'django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,208 wheel INFO adding 'django/contrib/admin/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,209 wheel INFO adding 'django/contrib/admin/locale/fa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,209 wheel INFO adding 'django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,209 wheel INFO adding 'django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,209 wheel INFO adding 'django/contrib/admin/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,209 wheel INFO adding 'django/contrib/admin/locale/fi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,209 wheel INFO adding 'django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,210 wheel INFO adding 'django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,210 wheel INFO adding 'django/contrib/admin/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,210 wheel INFO adding 'django/contrib/admin/locale/fr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,210 wheel INFO adding 'django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,210 wheel INFO adding 'django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,211 wheel INFO adding 'django/contrib/admin/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,211 wheel INFO adding 'django/contrib/admin/locale/fy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,211 wheel INFO adding 'django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,211 wheel INFO adding 'django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,211 wheel INFO adding 'django/contrib/admin/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,212 wheel INFO adding 'django/contrib/admin/locale/ga/LC_MESSAGES/django.po'
2025-04-22 20:54:05,212 wheel INFO adding 'django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,212 wheel INFO adding 'django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,212 wheel INFO adding 'django/contrib/admin/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,212 wheel INFO adding 'django/contrib/admin/locale/gd/LC_MESSAGES/django.po'
2025-04-22 20:54:05,213 wheel INFO adding 'django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,213 wheel INFO adding 'django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,213 wheel INFO adding 'django/contrib/admin/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,213 wheel INFO adding 'django/contrib/admin/locale/gl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,213 wheel INFO adding 'django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,214 wheel INFO adding 'django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,214 wheel INFO adding 'django/contrib/admin/locale/he/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,214 wheel INFO adding 'django/contrib/admin/locale/he/LC_MESSAGES/django.po'
2025-04-22 20:54:05,214 wheel INFO adding 'django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,214 wheel INFO adding 'django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,215 wheel INFO adding 'django/contrib/admin/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,215 wheel INFO adding 'django/contrib/admin/locale/hi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,215 wheel INFO adding 'django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,215 wheel INFO adding 'django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,215 wheel INFO adding 'django/contrib/admin/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,216 wheel INFO adding 'django/contrib/admin/locale/hr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,216 wheel INFO adding 'django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,216 wheel INFO adding 'django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,216 wheel INFO adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,216 wheel INFO adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,216 wheel INFO adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,217 wheel INFO adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,217 wheel INFO adding 'django/contrib/admin/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,217 wheel INFO adding 'django/contrib/admin/locale/hu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,217 wheel INFO adding 'django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,217 wheel INFO adding 'django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,218 wheel INFO adding 'django/contrib/admin/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,218 wheel INFO adding 'django/contrib/admin/locale/hy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,218 wheel INFO adding 'django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,218 wheel INFO adding 'django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,218 wheel INFO adding 'django/contrib/admin/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,218 wheel INFO adding 'django/contrib/admin/locale/ia/LC_MESSAGES/django.po'
2025-04-22 20:54:05,219 wheel INFO adding 'django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,219 wheel INFO adding 'django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,219 wheel INFO adding 'django/contrib/admin/locale/id/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,219 wheel INFO adding 'django/contrib/admin/locale/id/LC_MESSAGES/django.po'
2025-04-22 20:54:05,219 wheel INFO adding 'django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,219 wheel INFO adding 'django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,220 wheel INFO adding 'django/contrib/admin/locale/io/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,220 wheel INFO adding 'django/contrib/admin/locale/io/LC_MESSAGES/django.po'
2025-04-22 20:54:05,220 wheel INFO adding 'django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,220 wheel INFO adding 'django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,220 wheel INFO adding 'django/contrib/admin/locale/is/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,220 wheel INFO adding 'django/contrib/admin/locale/is/LC_MESSAGES/django.po'
2025-04-22 20:54:05,221 wheel INFO adding 'django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,221 wheel INFO adding 'django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,221 wheel INFO adding 'django/contrib/admin/locale/it/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,221 wheel INFO adding 'django/contrib/admin/locale/it/LC_MESSAGES/django.po'
2025-04-22 20:54:05,221 wheel INFO adding 'django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,221 wheel INFO adding 'django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,222 wheel INFO adding 'django/contrib/admin/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,222 wheel INFO adding 'django/contrib/admin/locale/ja/LC_MESSAGES/django.po'
2025-04-22 20:54:05,222 wheel INFO adding 'django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,222 wheel INFO adding 'django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,223 wheel INFO adding 'django/contrib/admin/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,223 wheel INFO adding 'django/contrib/admin/locale/ka/LC_MESSAGES/django.po'
2025-04-22 20:54:05,223 wheel INFO adding 'django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,223 wheel INFO adding 'django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,224 wheel INFO adding 'django/contrib/admin/locale/kab/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,224 wheel INFO adding 'django/contrib/admin/locale/kab/LC_MESSAGES/django.po'
2025-04-22 20:54:05,224 wheel INFO adding 'django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,224 wheel INFO adding 'django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,224 wheel INFO adding 'django/contrib/admin/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,224 wheel INFO adding 'django/contrib/admin/locale/kk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,225 wheel INFO adding 'django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,225 wheel INFO adding 'django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,225 wheel INFO adding 'django/contrib/admin/locale/km/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,225 wheel INFO adding 'django/contrib/admin/locale/km/LC_MESSAGES/django.po'
2025-04-22 20:54:05,225 wheel INFO adding 'django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,226 wheel INFO adding 'django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,226 wheel INFO adding 'django/contrib/admin/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,226 wheel INFO adding 'django/contrib/admin/locale/kn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,226 wheel INFO adding 'django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,226 wheel INFO adding 'django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,226 wheel INFO adding 'django/contrib/admin/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,227 wheel INFO adding 'django/contrib/admin/locale/ko/LC_MESSAGES/django.po'
2025-04-22 20:54:05,227 wheel INFO adding 'django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,227 wheel INFO adding 'django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,227 wheel INFO adding 'django/contrib/admin/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,227 wheel INFO adding 'django/contrib/admin/locale/ky/LC_MESSAGES/django.po'
2025-04-22 20:54:05,228 wheel INFO adding 'django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,228 wheel INFO adding 'django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,228 wheel INFO adding 'django/contrib/admin/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,228 wheel INFO adding 'django/contrib/admin/locale/lb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,228 wheel INFO adding 'django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,228 wheel INFO adding 'django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,229 wheel INFO adding 'django/contrib/admin/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,229 wheel INFO adding 'django/contrib/admin/locale/lt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,229 wheel INFO adding 'django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,229 wheel INFO adding 'django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,229 wheel INFO adding 'django/contrib/admin/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,229 wheel INFO adding 'django/contrib/admin/locale/lv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,230 wheel INFO adding 'django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,230 wheel INFO adding 'django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,230 wheel INFO adding 'django/contrib/admin/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,230 wheel INFO adding 'django/contrib/admin/locale/mk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,230 wheel INFO adding 'django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,230 wheel INFO adding 'django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,231 wheel INFO adding 'django/contrib/admin/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,231 wheel INFO adding 'django/contrib/admin/locale/ml/LC_MESSAGES/django.po'
2025-04-22 20:54:05,231 wheel INFO adding 'django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,231 wheel INFO adding 'django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,231 wheel INFO adding 'django/contrib/admin/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,232 wheel INFO adding 'django/contrib/admin/locale/mn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,232 wheel INFO adding 'django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,232 wheel INFO adding 'django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,232 wheel INFO adding 'django/contrib/admin/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,232 wheel INFO adding 'django/contrib/admin/locale/mr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,232 wheel INFO adding 'django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,233 wheel INFO adding 'django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,233 wheel INFO adding 'django/contrib/admin/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,233 wheel INFO adding 'django/contrib/admin/locale/ms/LC_MESSAGES/django.po'
2025-04-22 20:54:05,233 wheel INFO adding 'django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,233 wheel INFO adding 'django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,233 wheel INFO adding 'django/contrib/admin/locale/my/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,234 wheel INFO adding 'django/contrib/admin/locale/my/LC_MESSAGES/django.po'
2025-04-22 20:54:05,234 wheel INFO adding 'django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,234 wheel INFO adding 'django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,234 wheel INFO adding 'django/contrib/admin/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,234 wheel INFO adding 'django/contrib/admin/locale/nb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,234 wheel INFO adding 'django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,235 wheel INFO adding 'django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,235 wheel INFO adding 'django/contrib/admin/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,235 wheel INFO adding 'django/contrib/admin/locale/ne/LC_MESSAGES/django.po'
2025-04-22 20:54:05,235 wheel INFO adding 'django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,235 wheel INFO adding 'django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,236 wheel INFO adding 'django/contrib/admin/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,236 wheel INFO adding 'django/contrib/admin/locale/nl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,236 wheel INFO adding 'django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,236 wheel INFO adding 'django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,236 wheel INFO adding 'django/contrib/admin/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,236 wheel INFO adding 'django/contrib/admin/locale/nn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,237 wheel INFO adding 'django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,237 wheel INFO adding 'django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,237 wheel INFO adding 'django/contrib/admin/locale/os/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,237 wheel INFO adding 'django/contrib/admin/locale/os/LC_MESSAGES/django.po'
2025-04-22 20:54:05,237 wheel INFO adding 'django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,237 wheel INFO adding 'django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,238 wheel INFO adding 'django/contrib/admin/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,238 wheel INFO adding 'django/contrib/admin/locale/pa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,238 wheel INFO adding 'django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,238 wheel INFO adding 'django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,238 wheel INFO adding 'django/contrib/admin/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,238 wheel INFO adding 'django/contrib/admin/locale/pl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,239 wheel INFO adding 'django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,239 wheel INFO adding 'django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,239 wheel INFO adding 'django/contrib/admin/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,239 wheel INFO adding 'django/contrib/admin/locale/pt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,239 wheel INFO adding 'django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,239 wheel INFO adding 'django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,240 wheel INFO adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,240 wheel INFO adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,240 wheel INFO adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,240 wheel INFO adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,240 wheel INFO adding 'django/contrib/admin/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,241 wheel INFO adding 'django/contrib/admin/locale/ro/LC_MESSAGES/django.po'
2025-04-22 20:54:05,241 wheel INFO adding 'django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,241 wheel INFO adding 'django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,241 wheel INFO adding 'django/contrib/admin/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,241 wheel INFO adding 'django/contrib/admin/locale/ru/LC_MESSAGES/django.po'
2025-04-22 20:54:05,242 wheel INFO adding 'django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,242 wheel INFO adding 'django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,242 wheel INFO adding 'django/contrib/admin/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,242 wheel INFO adding 'django/contrib/admin/locale/sk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,243 wheel INFO adding 'django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,243 wheel INFO adding 'django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,243 wheel INFO adding 'django/contrib/admin/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,243 wheel INFO adding 'django/contrib/admin/locale/sl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,243 wheel INFO adding 'django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,243 wheel INFO adding 'django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,244 wheel INFO adding 'django/contrib/admin/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,244 wheel INFO adding 'django/contrib/admin/locale/sq/LC_MESSAGES/django.po'
2025-04-22 20:54:05,244 wheel INFO adding 'django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,245 wheel INFO adding 'django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,245 wheel INFO adding 'django/contrib/admin/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,245 wheel INFO adding 'django/contrib/admin/locale/sr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,246 wheel INFO adding 'django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,246 wheel INFO adding 'django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,246 wheel INFO adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,246 wheel INFO adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,246 wheel INFO adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,246 wheel INFO adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,247 wheel INFO adding 'django/contrib/admin/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,247 wheel INFO adding 'django/contrib/admin/locale/sv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,247 wheel INFO adding 'django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,247 wheel INFO adding 'django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,247 wheel INFO adding 'django/contrib/admin/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,248 wheel INFO adding 'django/contrib/admin/locale/sw/LC_MESSAGES/django.po'
2025-04-22 20:54:05,248 wheel INFO adding 'django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,248 wheel INFO adding 'django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,248 wheel INFO adding 'django/contrib/admin/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,250 wheel INFO adding 'django/contrib/admin/locale/ta/LC_MESSAGES/django.po'
2025-04-22 20:54:05,250 wheel INFO adding 'django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,251 wheel INFO adding 'django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,251 wheel INFO adding 'django/contrib/admin/locale/te/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,251 wheel INFO adding 'django/contrib/admin/locale/te/LC_MESSAGES/django.po'
2025-04-22 20:54:05,251 wheel INFO adding 'django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,251 wheel INFO adding 'django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,252 wheel INFO adding 'django/contrib/admin/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,252 wheel INFO adding 'django/contrib/admin/locale/tg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,252 wheel INFO adding 'django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,252 wheel INFO adding 'django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,252 wheel INFO adding 'django/contrib/admin/locale/th/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,253 wheel INFO adding 'django/contrib/admin/locale/th/LC_MESSAGES/django.po'
2025-04-22 20:54:05,253 wheel INFO adding 'django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,253 wheel INFO adding 'django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,253 wheel INFO adding 'django/contrib/admin/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,253 wheel INFO adding 'django/contrib/admin/locale/tk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,254 wheel INFO adding 'django/contrib/admin/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,254 wheel INFO adding 'django/contrib/admin/locale/tr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,254 wheel INFO adding 'django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,254 wheel INFO adding 'django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,254 wheel INFO adding 'django/contrib/admin/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,255 wheel INFO adding 'django/contrib/admin/locale/tt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,255 wheel INFO adding 'django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,255 wheel INFO adding 'django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,255 wheel INFO adding 'django/contrib/admin/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,255 wheel INFO adding 'django/contrib/admin/locale/udm/LC_MESSAGES/django.po'
2025-04-22 20:54:05,255 wheel INFO adding 'django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,255 wheel INFO adding 'django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,256 wheel INFO adding 'django/contrib/admin/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,256 wheel INFO adding 'django/contrib/admin/locale/uk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,256 wheel INFO adding 'django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,256 wheel INFO adding 'django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,257 wheel INFO adding 'django/contrib/admin/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,257 wheel INFO adding 'django/contrib/admin/locale/ur/LC_MESSAGES/django.po'
2025-04-22 20:54:05,257 wheel INFO adding 'django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,257 wheel INFO adding 'django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,257 wheel INFO adding 'django/contrib/admin/locale/uz/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,257 wheel INFO adding 'django/contrib/admin/locale/uz/LC_MESSAGES/django.po'
2025-04-22 20:54:05,258 wheel INFO adding 'django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,258 wheel INFO adding 'django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,258 wheel INFO adding 'django/contrib/admin/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,258 wheel INFO adding 'django/contrib/admin/locale/vi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,258 wheel INFO adding 'django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,258 wheel INFO adding 'django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,259 wheel INFO adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,259 wheel INFO adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 20:54:05,259 wheel INFO adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,259 wheel INFO adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,259 wheel INFO adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,260 wheel INFO adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 20:54:05,260 wheel INFO adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo'
2025-04-22 20:54:05,260 wheel INFO adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po'
2025-04-22 20:54:05,260 wheel INFO adding 'django/contrib/admin/migrations/0001_initial.py'
2025-04-22 20:54:05,260 wheel INFO adding 'django/contrib/admin/migrations/0002_logentry_remove_auto_add.py'
2025-04-22 20:54:05,260 wheel INFO adding 'django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py'
2025-04-22 20:54:05,260 wheel INFO adding 'django/contrib/admin/migrations/__init__.py'
2025-04-22 20:54:05,261 wheel INFO adding 'django/contrib/admin/static/admin/css/autocomplete.css'
2025-04-22 20:54:05,261 wheel INFO adding 'django/contrib/admin/static/admin/css/base.css'
2025-04-22 20:54:05,261 wheel INFO adding 'django/contrib/admin/static/admin/css/changelists.css'
2025-04-22 20:54:05,261 wheel INFO adding 'django/contrib/admin/static/admin/css/dark_mode.css'
2025-04-22 20:54:05,261 wheel INFO adding 'django/contrib/admin/static/admin/css/dashboard.css'
2025-04-22 20:54:05,261 wheel INFO adding 'django/contrib/admin/static/admin/css/forms.css'
2025-04-22 20:54:05,262 wheel INFO adding 'django/contrib/admin/static/admin/css/login.css'
2025-04-22 20:54:05,262 wheel INFO adding 'django/contrib/admin/static/admin/css/nav_sidebar.css'
2025-04-22 20:54:05,262 wheel INFO adding 'django/contrib/admin/static/admin/css/responsive.css'
2025-04-22 20:54:05,262 wheel INFO adding 'django/contrib/admin/static/admin/css/responsive_rtl.css'
2025-04-22 20:54:05,262 wheel INFO adding 'django/contrib/admin/static/admin/css/rtl.css'
2025-04-22 20:54:05,262 wheel INFO adding 'django/contrib/admin/static/admin/css/widgets.css'
2025-04-22 20:54:05,262 wheel INFO adding 'django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md'
2025-04-22 20:54:05,263 wheel INFO adding 'django/contrib/admin/static/admin/css/vendor/select2/select2.css'
2025-04-22 20:54:05,263 wheel INFO adding 'django/contrib/admin/static/admin/css/vendor/select2/select2.min.css'
2025-04-22 20:54:05,263 wheel INFO adding 'django/contrib/admin/static/admin/img/LICENSE'
2025-04-22 20:54:05,263 wheel INFO adding 'django/contrib/admin/static/admin/img/README.txt'
2025-04-22 20:54:05,263 wheel INFO adding 'django/contrib/admin/static/admin/img/calendar-icons.svg'
2025-04-22 20:54:05,263 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-addlink.svg'
2025-04-22 20:54:05,263 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-alert.svg'
2025-04-22 20:54:05,264 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-calendar.svg'
2025-04-22 20:54:05,264 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-changelink.svg'
2025-04-22 20:54:05,264 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-clock.svg'
2025-04-22 20:54:05,264 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-deletelink.svg'
2025-04-22 20:54:05,264 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-no.svg'
2025-04-22 20:54:05,264 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-unknown-alt.svg'
2025-04-22 20:54:05,264 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-unknown.svg'
2025-04-22 20:54:05,264 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-viewlink.svg'
2025-04-22 20:54:05,264 wheel INFO adding 'django/contrib/admin/static/admin/img/icon-yes.svg'
2025-04-22 20:54:05,265 wheel INFO adding 'django/contrib/admin/static/admin/img/inline-delete.svg'
2025-04-22 20:54:05,265 wheel INFO adding 'django/contrib/admin/static/admin/img/search.svg'
2025-04-22 20:54:05,265 wheel INFO adding 'django/contrib/admin/static/admin/img/selector-icons.svg'
2025-04-22 20:54:05,265 wheel INFO adding 'django/contrib/admin/static/admin/img/sorting-icons.svg'
2025-04-22 20:54:05,265 wheel INFO adding 'django/contrib/admin/static/admin/img/tooltag-add.svg'
2025-04-22 20:54:05,265 wheel INFO adding 'django/contrib/admin/static/admin/img/tooltag-arrowright.svg'
2025-04-22 20:54:05,265 wheel INFO adding 'django/contrib/admin/static/admin/img/gis/move_vertex_off.svg'
2025-04-22 20:54:05,265 wheel INFO adding 'django/contrib/admin/static/admin/img/gis/move_vertex_on.svg'
2025-04-22 20:54:05,266 wheel INFO adding 'django/contrib/admin/static/admin/js/SelectBox.js'
2025-04-22 20:54:05,266 wheel INFO adding 'django/contrib/admin/static/admin/js/SelectFilter2.js'
2025-04-22 20:54:05,266 wheel INFO adding 'django/contrib/admin/static/admin/js/actions.js'
2025-04-22 20:54:05,266 wheel INFO adding 'django/contrib/admin/static/admin/js/autocomplete.js'
2025-04-22 20:54:05,266 wheel INFO adding 'django/contrib/admin/static/admin/js/calendar.js'
2025-04-22 20:54:05,266 wheel INFO adding 'django/contrib/admin/static/admin/js/cancel.js'
2025-04-22 20:54:05,267 wheel INFO adding 'django/contrib/admin/static/admin/js/change_form.js'
2025-04-22 20:54:05,267 wheel INFO adding 'django/contrib/admin/static/admin/js/collapse.js'
2025-04-22 20:54:05,267 wheel INFO adding 'django/contrib/admin/static/admin/js/core.js'
2025-04-22 20:54:05,267 wheel INFO adding 'django/contrib/admin/static/admin/js/filters.js'
2025-04-22 20:54:05,267 wheel INFO adding 'django/contrib/admin/static/admin/js/inlines.js'
2025-04-22 20:54:05,267 wheel INFO adding 'django/contrib/admin/static/admin/js/jquery.init.js'
2025-04-22 20:54:05,267 wheel INFO adding 'django/contrib/admin/static/admin/js/nav_sidebar.js'
2025-04-22 20:54:05,267 wheel INFO adding 'django/contrib/admin/static/admin/js/popup_response.js'
2025-04-22 20:54:05,268 wheel INFO adding 'django/contrib/admin/static/admin/js/prepopulate.js'
2025-04-22 20:54:05,268 wheel INFO adding 'django/contrib/admin/static/admin/js/prepopulate_init.js'
2025-04-22 20:54:05,268 wheel INFO adding 'django/contrib/admin/static/admin/js/theme.js'
2025-04-22 20:54:05,268 wheel INFO adding 'django/contrib/admin/static/admin/js/urlify.js'
2025-04-22 20:54:05,268 wheel INFO adding 'django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js'
2025-04-22 20:54:05,268 wheel INFO adding 'django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js'
2025-04-22 20:54:05,269 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt'
2025-04-22 20:54:05,269 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/jquery/jquery.js'
2025-04-22 20:54:05,270 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js'
2025-04-22 20:54:05,270 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md'
2025-04-22 20:54:05,271 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/select2.full.js'
2025-04-22 20:54:05,271 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js'
2025-04-22 20:54:05,272 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js'
2025-04-22 20:54:05,272 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js'
2025-04-22 20:54:05,272 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js'
2025-04-22 20:54:05,272 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js'
2025-04-22 20:54:05,272 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js'
2025-04-22 20:54:05,272 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js'
2025-04-22 20:54:05,272 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js'
2025-04-22 20:54:05,272 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js'
2025-04-22 20:54:05,273 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js'
2025-04-22 20:54:05,273 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js'
2025-04-22 20:54:05,273 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js'
2025-04-22 20:54:05,273 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js'
2025-04-22 20:54:05,273 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js'
2025-04-22 20:54:05,273 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js'
2025-04-22 20:54:05,273 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js'
2025-04-22 20:54:05,273 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js'
2025-04-22 20:54:05,273 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js'
2025-04-22 20:54:05,274 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js'
2025-04-22 20:54:05,274 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js'
2025-04-22 20:54:05,274 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js'
2025-04-22 20:54:05,274 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js'
2025-04-22 20:54:05,274 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js'
2025-04-22 20:54:05,274 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js'
2025-04-22 20:54:05,274 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js'
2025-04-22 20:54:05,274 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js'
2025-04-22 20:54:05,274 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js'
2025-04-22 20:54:05,275 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js'
2025-04-22 20:54:05,275 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js'
2025-04-22 20:54:05,275 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js'
2025-04-22 20:54:05,275 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js'
2025-04-22 20:54:05,275 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js'
2025-04-22 20:54:05,275 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js'
2025-04-22 20:54:05,275 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js'
2025-04-22 20:54:05,275 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js'
2025-04-22 20:54:05,275 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js'
2025-04-22 20:54:05,276 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js'
2025-04-22 20:54:05,276 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js'
2025-04-22 20:54:05,276 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js'
2025-04-22 20:54:05,276 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js'
2025-04-22 20:54:05,276 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js'
2025-04-22 20:54:05,276 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js'
2025-04-22 20:54:05,276 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js'
2025-04-22 20:54:05,276 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js'
2025-04-22 20:54:05,276 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js'
2025-04-22 20:54:05,277 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js'
2025-04-22 20:54:05,277 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js'
2025-04-22 20:54:05,277 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js'
2025-04-22 20:54:05,277 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js'
2025-04-22 20:54:05,277 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js'
2025-04-22 20:54:05,277 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js'
2025-04-22 20:54:05,277 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js'
2025-04-22 20:54:05,277 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js'
2025-04-22 20:54:05,277 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js'
2025-04-22 20:54:05,278 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js'
2025-04-22 20:54:05,278 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js'
2025-04-22 20:54:05,278 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js'
2025-04-22 20:54:05,278 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js'
2025-04-22 20:54:05,278 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js'
2025-04-22 20:54:05,278 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js'
2025-04-22 20:54:05,278 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt'
2025-04-22 20:54:05,279 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js'
2025-04-22 20:54:05,280 wheel INFO adding 'django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js'
2025-04-22 20:54:05,280 wheel INFO adding 'django/contrib/admin/templates/admin/404.html'
2025-04-22 20:54:05,280 wheel INFO adding 'django/contrib/admin/templates/admin/500.html'
2025-04-22 20:54:05,280 wheel INFO adding 'django/contrib/admin/templates/admin/actions.html'
2025-04-22 20:54:05,280 wheel INFO adding 'django/contrib/admin/templates/admin/app_index.html'
2025-04-22 20:54:05,280 wheel INFO adding 'django/contrib/admin/templates/admin/app_list.html'
2025-04-22 20:54:05,281 wheel INFO adding 'django/contrib/admin/templates/admin/base.html'
2025-04-22 20:54:05,281 wheel INFO adding 'django/contrib/admin/templates/admin/base_site.html'
2025-04-22 20:54:05,281 wheel INFO adding 'django/contrib/admin/templates/admin/change_form.html'
2025-04-22 20:54:05,281 wheel INFO adding 'django/contrib/admin/templates/admin/change_form_object_tools.html'
2025-04-22 20:54:05,281 wheel INFO adding 'django/contrib/admin/templates/admin/change_list.html'
2025-04-22 20:54:05,281 wheel INFO adding 'django/contrib/admin/templates/admin/change_list_object_tools.html'
2025-04-22 20:54:05,281 wheel INFO adding 'django/contrib/admin/templates/admin/change_list_results.html'
2025-04-22 20:54:05,281 wheel INFO adding 'django/contrib/admin/templates/admin/color_theme_toggle.html'
2025-04-22 20:54:05,281 wheel INFO adding 'django/contrib/admin/templates/admin/date_hierarchy.html'
2025-04-22 20:54:05,282 wheel INFO adding 'django/contrib/admin/templates/admin/delete_confirmation.html'
2025-04-22 20:54:05,282 wheel INFO adding 'django/contrib/admin/templates/admin/delete_selected_confirmation.html'
2025-04-22 20:54:05,282 wheel INFO adding 'django/contrib/admin/templates/admin/filter.html'
2025-04-22 20:54:05,282 wheel INFO adding 'django/contrib/admin/templates/admin/index.html'
2025-04-22 20:54:05,282 wheel INFO adding 'django/contrib/admin/templates/admin/invalid_setup.html'
2025-04-22 20:54:05,282 wheel INFO adding 'django/contrib/admin/templates/admin/login.html'
2025-04-22 20:54:05,282 wheel INFO adding 'django/contrib/admin/templates/admin/nav_sidebar.html'
2025-04-22 20:54:05,282 wheel INFO adding 'django/contrib/admin/templates/admin/object_history.html'
2025-04-22 20:54:05,283 wheel INFO adding 'django/contrib/admin/templates/admin/pagination.html'
2025-04-22 20:54:05,283 wheel INFO adding 'django/contrib/admin/templates/admin/popup_response.html'
2025-04-22 20:54:05,283 wheel INFO adding 'django/contrib/admin/templates/admin/prepopulated_fields_js.html'
2025-04-22 20:54:05,283 wheel INFO adding 'django/contrib/admin/templates/admin/search_form.html'
2025-04-22 20:54:05,283 wheel INFO adding 'django/contrib/admin/templates/admin/submit_line.html'
2025-04-22 20:54:05,283 wheel INFO adding 'django/contrib/admin/templates/admin/auth/user/add_form.html'
2025-04-22 20:54:05,283 wheel INFO adding 'django/contrib/admin/templates/admin/auth/user/change_password.html'
2025-04-22 20:54:05,283 wheel INFO adding 'django/contrib/admin/templates/admin/edit_inline/stacked.html'
2025-04-22 20:54:05,284 wheel INFO adding 'django/contrib/admin/templates/admin/edit_inline/tabular.html'
2025-04-22 20:54:05,284 wheel INFO adding 'django/contrib/admin/templates/admin/includes/fieldset.html'
2025-04-22 20:54:05,284 wheel INFO adding 'django/contrib/admin/templates/admin/includes/object_delete_summary.html'
2025-04-22 20:54:05,284 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/clearable_file_input.html'
2025-04-22 20:54:05,284 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/date.html'
2025-04-22 20:54:05,284 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html'
2025-04-22 20:54:05,284 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html'
2025-04-22 20:54:05,284 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/radio.html'
2025-04-22 20:54:05,285 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html'
2025-04-22 20:54:05,285 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/split_datetime.html'
2025-04-22 20:54:05,285 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/time.html'
2025-04-22 20:54:05,285 wheel INFO adding 'django/contrib/admin/templates/admin/widgets/url.html'
2025-04-22 20:54:05,285 wheel INFO adding 'django/contrib/admin/templates/registration/logged_out.html'
2025-04-22 20:54:05,285 wheel INFO adding 'django/contrib/admin/templates/registration/password_change_done.html'
2025-04-22 20:54:05,285 wheel INFO adding 'django/contrib/admin/templates/registration/password_change_form.html'
2025-04-22 20:54:05,285 wheel INFO adding 'django/contrib/admin/templates/registration/password_reset_complete.html'
2025-04-22 20:54:05,285 wheel INFO adding 'django/contrib/admin/templates/registration/password_reset_confirm.html'
2025-04-22 20:54:05,286 wheel INFO adding 'django/contrib/admin/templates/registration/password_reset_done.html'
2025-04-22 20:54:05,286 wheel INFO adding 'django/contrib/admin/templates/registration/password_reset_email.html'
2025-04-22 20:54:05,286 wheel INFO adding 'django/contrib/admin/templates/registration/password_reset_form.html'
2025-04-22 20:54:05,286 wheel INFO adding 'django/contrib/admin/templatetags/__init__.py'
2025-04-22 20:54:05,286 wheel INFO adding 'django/contrib/admin/templatetags/admin_list.py'
2025-04-22 20:54:05,286 wheel INFO adding 'django/contrib/admin/templatetags/admin_modify.py'
2025-04-22 20:54:05,286 wheel INFO adding 'django/contrib/admin/templatetags/admin_urls.py'
2025-04-22 20:54:05,286 wheel INFO adding 'django/contrib/admin/templatetags/base.py'
2025-04-22 20:54:05,287 wheel INFO adding 'django/contrib/admin/templatetags/log.py'
2025-04-22 20:54:05,287 wheel INFO adding 'django/contrib/admin/views/__init__.py'
2025-04-22 20:54:05,287 wheel INFO adding 'django/contrib/admin/views/autocomplete.py'
2025-04-22 20:54:05,287 wheel INFO adding 'django/contrib/admin/views/decorators.py'
2025-04-22 20:54:05,287 wheel INFO adding 'django/contrib/admin/views/main.py'
2025-04-22 20:54:05,287 wheel INFO adding 'django/contrib/admindocs/__init__.py'
2025-04-22 20:54:05,288 wheel INFO adding 'django/contrib/admindocs/apps.py'
2025-04-22 20:54:05,288 wheel INFO adding 'django/contrib/admindocs/middleware.py'
2025-04-22 20:54:05,288 wheel INFO adding 'django/contrib/admindocs/urls.py'
2025-04-22 20:54:05,288 wheel INFO adding 'django/contrib/admindocs/utils.py'
2025-04-22 20:54:05,288 wheel INFO adding 'django/contrib/admindocs/views.py'
2025-04-22 20:54:05,289 wheel INFO adding 'django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,289 wheel INFO adding 'django/contrib/admindocs/locale/af/LC_MESSAGES/django.po'
2025-04-22 20:54:05,289 wheel INFO adding 'django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,289 wheel INFO adding 'django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po'
2025-04-22 20:54:05,290 wheel INFO adding 'django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,290 wheel INFO adding 'django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 20:54:05,290 wheel INFO adding 'django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,290 wheel INFO adding 'django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po'
2025-04-22 20:54:05,290 wheel INFO adding 'django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,290 wheel INFO adding 'django/contrib/admindocs/locale/az/LC_MESSAGES/django.po'
2025-04-22 20:54:05,291 wheel INFO adding 'django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,291 wheel INFO adding 'django/contrib/admindocs/locale/be/LC_MESSAGES/django.po'
2025-04-22 20:54:05,291 wheel INFO adding 'django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,291 wheel INFO adding 'django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,291 wheel INFO adding 'django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,291 wheel INFO adding 'django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,292 wheel INFO adding 'django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,292 wheel INFO adding 'django/contrib/admindocs/locale/br/LC_MESSAGES/django.po'
2025-04-22 20:54:05,292 wheel INFO adding 'django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,292 wheel INFO adding 'django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,292 wheel INFO adding 'django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,292 wheel INFO adding 'django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po'
2025-04-22 20:54:05,293 wheel INFO adding 'django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,293 wheel INFO adding 'django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,293 wheel INFO adding 'django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,293 wheel INFO adding 'django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,293 wheel INFO adding 'django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,293 wheel INFO adding 'django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,294 wheel INFO adding 'django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,294 wheel INFO adding 'django/contrib/admindocs/locale/da/LC_MESSAGES/django.po'
2025-04-22 20:54:05,294 wheel INFO adding 'django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,294 wheel INFO adding 'django/contrib/admindocs/locale/de/LC_MESSAGES/django.po'
2025-04-22 20:54:05,294 wheel INFO adding 'django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,294 wheel INFO adding 'django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,295 wheel INFO adding 'django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,295 wheel INFO adding 'django/contrib/admindocs/locale/el/LC_MESSAGES/django.po'
2025-04-22 20:54:05,295 wheel INFO adding 'django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,295 wheel INFO adding 'django/contrib/admindocs/locale/en/LC_MESSAGES/django.po'
2025-04-22 20:54:05,295 wheel INFO adding 'django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,296 wheel INFO adding 'django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 20:54:05,296 wheel INFO adding 'django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,296 wheel INFO adding 'django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 20:54:05,296 wheel INFO adding 'django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,296 wheel INFO adding 'django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po'
2025-04-22 20:54:05,296 wheel INFO adding 'django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,296 wheel INFO adding 'django/contrib/admindocs/locale/es/LC_MESSAGES/django.po'
2025-04-22 20:54:05,297 wheel INFO adding 'django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,297 wheel INFO adding 'django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,297 wheel INFO adding 'django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,297 wheel INFO adding 'django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 20:54:05,297 wheel INFO adding 'django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,297 wheel INFO adding 'django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 20:54:05,298 wheel INFO adding 'django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,298 wheel INFO adding 'django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 20:54:05,298 wheel INFO adding 'django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,298 wheel INFO adding 'django/contrib/admindocs/locale/et/LC_MESSAGES/django.po'
2025-04-22 20:54:05,298 wheel INFO adding 'django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,299 wheel INFO adding 'django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,299 wheel INFO adding 'django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,299 wheel INFO adding 'django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,299 wheel INFO adding 'django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,299 wheel INFO adding 'django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,299 wheel INFO adding 'django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,300 wheel INFO adding 'django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,300 wheel INFO adding 'django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,300 wheel INFO adding 'django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,300 wheel INFO adding 'django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,300 wheel INFO adding 'django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po'
2025-04-22 20:54:05,301 wheel INFO adding 'django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,301 wheel INFO adding 'django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po'
2025-04-22 20:54:05,301 wheel INFO adding 'django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,301 wheel INFO adding 'django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,301 wheel INFO adding 'django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,301 wheel INFO adding 'django/contrib/admindocs/locale/he/LC_MESSAGES/django.po'
2025-04-22 20:54:05,302 wheel INFO adding 'django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,302 wheel INFO adding 'django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,302 wheel INFO adding 'django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,302 wheel INFO adding 'django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,302 wheel INFO adding 'django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,302 wheel INFO adding 'django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,303 wheel INFO adding 'django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,303 wheel INFO adding 'django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,303 wheel INFO adding 'django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,303 wheel INFO adding 'django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po'
2025-04-22 20:54:05,303 wheel INFO adding 'django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,303 wheel INFO adding 'django/contrib/admindocs/locale/id/LC_MESSAGES/django.po'
2025-04-22 20:54:05,303 wheel INFO adding 'django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,304 wheel INFO adding 'django/contrib/admindocs/locale/io/LC_MESSAGES/django.po'
2025-04-22 20:54:05,304 wheel INFO adding 'django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,304 wheel INFO adding 'django/contrib/admindocs/locale/is/LC_MESSAGES/django.po'
2025-04-22 20:54:05,304 wheel INFO adding 'django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,304 wheel INFO adding 'django/contrib/admindocs/locale/it/LC_MESSAGES/django.po'
2025-04-22 20:54:05,304 wheel INFO adding 'django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,305 wheel INFO adding 'django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po'
2025-04-22 20:54:05,305 wheel INFO adding 'django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,305 wheel INFO adding 'django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po'
2025-04-22 20:54:05,305 wheel INFO adding 'django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,305 wheel INFO adding 'django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po'
2025-04-22 20:54:05,305 wheel INFO adding 'django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,306 wheel INFO adding 'django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,306 wheel INFO adding 'django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,306 wheel INFO adding 'django/contrib/admindocs/locale/km/LC_MESSAGES/django.po'
2025-04-22 20:54:05,306 wheel INFO adding 'django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,306 wheel INFO adding 'django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,306 wheel INFO adding 'django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,306 wheel INFO adding 'django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po'
2025-04-22 20:54:05,307 wheel INFO adding 'django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,307 wheel INFO adding 'django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po'
2025-04-22 20:54:05,307 wheel INFO adding 'django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,307 wheel INFO adding 'django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,307 wheel INFO adding 'django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,307 wheel INFO adding 'django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,308 wheel INFO adding 'django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,308 wheel INFO adding 'django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,308 wheel INFO adding 'django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,308 wheel INFO adding 'django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,308 wheel INFO adding 'django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,308 wheel INFO adding 'django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po'
2025-04-22 20:54:05,309 wheel INFO adding 'django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,309 wheel INFO adding 'django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,309 wheel INFO adding 'django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,309 wheel INFO adding 'django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,309 wheel INFO adding 'django/contrib/admindocs/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,309 wheel INFO adding 'django/contrib/admindocs/locale/ms/LC_MESSAGES/django.po'
2025-04-22 20:54:05,309 wheel INFO adding 'django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,310 wheel INFO adding 'django/contrib/admindocs/locale/my/LC_MESSAGES/django.po'
2025-04-22 20:54:05,310 wheel INFO adding 'django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,310 wheel INFO adding 'django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,310 wheel INFO adding 'django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,310 wheel INFO adding 'django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po'
2025-04-22 20:54:05,310 wheel INFO adding 'django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,311 wheel INFO adding 'django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,311 wheel INFO adding 'django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,311 wheel INFO adding 'django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,311 wheel INFO adding 'django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,311 wheel INFO adding 'django/contrib/admindocs/locale/os/LC_MESSAGES/django.po'
2025-04-22 20:54:05,311 wheel INFO adding 'django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,312 wheel INFO adding 'django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,312 wheel INFO adding 'django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,313 wheel INFO adding 'django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,313 wheel INFO adding 'django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,313 wheel INFO adding 'django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,313 wheel INFO adding 'django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,313 wheel INFO adding 'django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,313 wheel INFO adding 'django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,314 wheel INFO adding 'django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po'
2025-04-22 20:54:05,314 wheel INFO adding 'django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,314 wheel INFO adding 'django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po'
2025-04-22 20:54:05,314 wheel INFO adding 'django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,314 wheel INFO adding 'django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,314 wheel INFO adding 'django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,315 wheel INFO adding 'django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,315 wheel INFO adding 'django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,315 wheel INFO adding 'django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po'
2025-04-22 20:54:05,315 wheel INFO adding 'django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,315 wheel INFO adding 'django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,315 wheel INFO adding 'django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,316 wheel INFO adding 'django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,316 wheel INFO adding 'django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,316 wheel INFO adding 'django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,316 wheel INFO adding 'django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,316 wheel INFO adding 'django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po'
2025-04-22 20:54:05,316 wheel INFO adding 'django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,317 wheel INFO adding 'django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po'
2025-04-22 20:54:05,317 wheel INFO adding 'django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,317 wheel INFO adding 'django/contrib/admindocs/locale/te/LC_MESSAGES/django.po'
2025-04-22 20:54:05,317 wheel INFO adding 'django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,317 wheel INFO adding 'django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,317 wheel INFO adding 'django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,317 wheel INFO adding 'django/contrib/admindocs/locale/th/LC_MESSAGES/django.po'
2025-04-22 20:54:05,318 wheel INFO adding 'django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,318 wheel INFO adding 'django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,318 wheel INFO adding 'django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,318 wheel INFO adding 'django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,318 wheel INFO adding 'django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,318 wheel INFO adding 'django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po'
2025-04-22 20:54:05,319 wheel INFO adding 'django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,319 wheel INFO adding 'django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,319 wheel INFO adding 'django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,319 wheel INFO adding 'django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po'
2025-04-22 20:54:05,319 wheel INFO adding 'django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,319 wheel INFO adding 'django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,320 wheel INFO adding 'django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,320 wheel INFO adding 'django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 20:54:05,320 wheel INFO adding 'django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,320 wheel INFO adding 'django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 20:54:05,320 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/bookmarklets.html'
2025-04-22 20:54:05,320 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/index.html'
2025-04-22 20:54:05,321 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/missing_docutils.html'
2025-04-22 20:54:05,321 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/model_detail.html'
2025-04-22 20:54:05,321 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/model_index.html'
2025-04-22 20:54:05,321 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/template_detail.html'
2025-04-22 20:54:05,321 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/template_filter_index.html'
2025-04-22 20:54:05,321 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/template_tag_index.html'
2025-04-22 20:54:05,321 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/view_detail.html'
2025-04-22 20:54:05,321 wheel INFO adding 'django/contrib/admindocs/templates/admin_doc/view_index.html'
2025-04-22 20:54:05,322 wheel INFO adding 'django/contrib/auth/__init__.py'
2025-04-22 20:54:05,322 wheel INFO adding 'django/contrib/auth/admin.py'
2025-04-22 20:54:05,322 wheel INFO adding 'django/contrib/auth/apps.py'
2025-04-22 20:54:05,322 wheel INFO adding 'django/contrib/auth/backends.py'
2025-04-22 20:54:05,322 wheel INFO adding 'django/contrib/auth/base_user.py'
2025-04-22 20:54:05,322 wheel INFO adding 'django/contrib/auth/checks.py'
2025-04-22 20:54:05,323 wheel INFO adding 'django/contrib/auth/common-passwords.txt.gz'
2025-04-22 20:54:05,323 wheel INFO adding 'django/contrib/auth/context_processors.py'
2025-04-22 20:54:05,323 wheel INFO adding 'django/contrib/auth/decorators.py'
2025-04-22 20:54:05,323 wheel INFO adding 'django/contrib/auth/forms.py'
2025-04-22 20:54:05,323 wheel INFO adding 'django/contrib/auth/hashers.py'
2025-04-22 20:54:05,323 wheel INFO adding 'django/contrib/auth/middleware.py'
2025-04-22 20:54:05,324 wheel INFO adding 'django/contrib/auth/mixins.py'
2025-04-22 20:54:05,324 wheel INFO adding 'django/contrib/auth/models.py'
2025-04-22 20:54:05,324 wheel INFO adding 'django/contrib/auth/password_validation.py'
2025-04-22 20:54:05,324 wheel INFO adding 'django/contrib/auth/signals.py'
2025-04-22 20:54:05,324 wheel INFO adding 'django/contrib/auth/tokens.py'
2025-04-22 20:54:05,324 wheel INFO adding 'django/contrib/auth/urls.py'
2025-04-22 20:54:05,324 wheel INFO adding 'django/contrib/auth/validators.py'
2025-04-22 20:54:05,325 wheel INFO adding 'django/contrib/auth/views.py'
2025-04-22 20:54:05,325 wheel INFO adding 'django/contrib/auth/handlers/__init__.py'
2025-04-22 20:54:05,325 wheel INFO adding 'django/contrib/auth/handlers/modwsgi.py'
2025-04-22 20:54:05,326 wheel INFO adding 'django/contrib/auth/locale/af/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,326 wheel INFO adding 'django/contrib/auth/locale/af/LC_MESSAGES/django.po'
2025-04-22 20:54:05,326 wheel INFO adding 'django/contrib/auth/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,326 wheel INFO adding 'django/contrib/auth/locale/ar/LC_MESSAGES/django.po'
2025-04-22 20:54:05,326 wheel INFO adding 'django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,326 wheel INFO adding 'django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 20:54:05,327 wheel INFO adding 'django/contrib/auth/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,327 wheel INFO adding 'django/contrib/auth/locale/ast/LC_MESSAGES/django.po'
2025-04-22 20:54:05,327 wheel INFO adding 'django/contrib/auth/locale/az/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,327 wheel INFO adding 'django/contrib/auth/locale/az/LC_MESSAGES/django.po'
2025-04-22 20:54:05,327 wheel INFO adding 'django/contrib/auth/locale/be/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,327 wheel INFO adding 'django/contrib/auth/locale/be/LC_MESSAGES/django.po'
2025-04-22 20:54:05,328 wheel INFO adding 'django/contrib/auth/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,328 wheel INFO adding 'django/contrib/auth/locale/bg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,328 wheel INFO adding 'django/contrib/auth/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,328 wheel INFO adding 'django/contrib/auth/locale/bn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,328 wheel INFO adding 'django/contrib/auth/locale/br/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,328 wheel INFO adding 'django/contrib/auth/locale/br/LC_MESSAGES/django.po'
2025-04-22 20:54:05,329 wheel INFO adding 'django/contrib/auth/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,329 wheel INFO adding 'django/contrib/auth/locale/bs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,329 wheel INFO adding 'django/contrib/auth/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,329 wheel INFO adding 'django/contrib/auth/locale/ca/LC_MESSAGES/django.po'
2025-04-22 20:54:05,329 wheel INFO adding 'django/contrib/auth/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,329 wheel INFO adding 'django/contrib/auth/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,330 wheel INFO adding 'django/contrib/auth/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,330 wheel INFO adding 'django/contrib/auth/locale/cs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,330 wheel INFO adding 'django/contrib/auth/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,330 wheel INFO adding 'django/contrib/auth/locale/cy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,330 wheel INFO adding 'django/contrib/auth/locale/da/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,330 wheel INFO adding 'django/contrib/auth/locale/da/LC_MESSAGES/django.po'
2025-04-22 20:54:05,331 wheel INFO adding 'django/contrib/auth/locale/de/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,331 wheel INFO adding 'django/contrib/auth/locale/de/LC_MESSAGES/django.po'
2025-04-22 20:54:05,331 wheel INFO adding 'django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,331 wheel INFO adding 'django/contrib/auth/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,331 wheel INFO adding 'django/contrib/auth/locale/el/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,331 wheel INFO adding 'django/contrib/auth/locale/el/LC_MESSAGES/django.po'
2025-04-22 20:54:05,332 wheel INFO adding 'django/contrib/auth/locale/en/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,332 wheel INFO adding 'django/contrib/auth/locale/en/LC_MESSAGES/django.po'
2025-04-22 20:54:05,332 wheel INFO adding 'django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,332 wheel INFO adding 'django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 20:54:05,332 wheel INFO adding 'django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,332 wheel INFO adding 'django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 20:54:05,333 wheel INFO adding 'django/contrib/auth/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,333 wheel INFO adding 'django/contrib/auth/locale/eo/LC_MESSAGES/django.po'
2025-04-22 20:54:05,333 wheel INFO adding 'django/contrib/auth/locale/es/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,333 wheel INFO adding 'django/contrib/auth/locale/es/LC_MESSAGES/django.po'
2025-04-22 20:54:05,333 wheel INFO adding 'django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,333 wheel INFO adding 'django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,334 wheel INFO adding 'django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,334 wheel INFO adding 'django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 20:54:05,334 wheel INFO adding 'django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,334 wheel INFO adding 'django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 20:54:05,334 wheel INFO adding 'django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,334 wheel INFO adding 'django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 20:54:05,335 wheel INFO adding 'django/contrib/auth/locale/et/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,335 wheel INFO adding 'django/contrib/auth/locale/et/LC_MESSAGES/django.po'
2025-04-22 20:54:05,335 wheel INFO adding 'django/contrib/auth/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,335 wheel INFO adding 'django/contrib/auth/locale/eu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,335 wheel INFO adding 'django/contrib/auth/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,336 wheel INFO adding 'django/contrib/auth/locale/fa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,336 wheel INFO adding 'django/contrib/auth/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,336 wheel INFO adding 'django/contrib/auth/locale/fi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,336 wheel INFO adding 'django/contrib/auth/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,336 wheel INFO adding 'django/contrib/auth/locale/fr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,337 wheel INFO adding 'django/contrib/auth/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,337 wheel INFO adding 'django/contrib/auth/locale/fy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,337 wheel INFO adding 'django/contrib/auth/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,337 wheel INFO adding 'django/contrib/auth/locale/ga/LC_MESSAGES/django.po'
2025-04-22 20:54:05,337 wheel INFO adding 'django/contrib/auth/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,337 wheel INFO adding 'django/contrib/auth/locale/gd/LC_MESSAGES/django.po'
2025-04-22 20:54:05,337 wheel INFO adding 'django/contrib/auth/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,338 wheel INFO adding 'django/contrib/auth/locale/gl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,338 wheel INFO adding 'django/contrib/auth/locale/he/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,338 wheel INFO adding 'django/contrib/auth/locale/he/LC_MESSAGES/django.po'
2025-04-22 20:54:05,338 wheel INFO adding 'django/contrib/auth/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,338 wheel INFO adding 'django/contrib/auth/locale/hi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,339 wheel INFO adding 'django/contrib/auth/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,339 wheel INFO adding 'django/contrib/auth/locale/hr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,339 wheel INFO adding 'django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,339 wheel INFO adding 'django/contrib/auth/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,339 wheel INFO adding 'django/contrib/auth/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,339 wheel INFO adding 'django/contrib/auth/locale/hu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,340 wheel INFO adding 'django/contrib/auth/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,340 wheel INFO adding 'django/contrib/auth/locale/hy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,340 wheel INFO adding 'django/contrib/auth/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,340 wheel INFO adding 'django/contrib/auth/locale/ia/LC_MESSAGES/django.po'
2025-04-22 20:54:05,340 wheel INFO adding 'django/contrib/auth/locale/id/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,340 wheel INFO adding 'django/contrib/auth/locale/id/LC_MESSAGES/django.po'
2025-04-22 20:54:05,340 wheel INFO adding 'django/contrib/auth/locale/io/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,341 wheel INFO adding 'django/contrib/auth/locale/io/LC_MESSAGES/django.po'
2025-04-22 20:54:05,341 wheel INFO adding 'django/contrib/auth/locale/is/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,341 wheel INFO adding 'django/contrib/auth/locale/is/LC_MESSAGES/django.po'
2025-04-22 20:54:05,341 wheel INFO adding 'django/contrib/auth/locale/it/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,341 wheel INFO adding 'django/contrib/auth/locale/it/LC_MESSAGES/django.po'
2025-04-22 20:54:05,341 wheel INFO adding 'django/contrib/auth/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,342 wheel INFO adding 'django/contrib/auth/locale/ja/LC_MESSAGES/django.po'
2025-04-22 20:54:05,342 wheel INFO adding 'django/contrib/auth/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,342 wheel INFO adding 'django/contrib/auth/locale/ka/LC_MESSAGES/django.po'
2025-04-22 20:54:05,342 wheel INFO adding 'django/contrib/auth/locale/kab/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,342 wheel INFO adding 'django/contrib/auth/locale/kab/LC_MESSAGES/django.po'
2025-04-22 20:54:05,343 wheel INFO adding 'django/contrib/auth/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,343 wheel INFO adding 'django/contrib/auth/locale/kk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,343 wheel INFO adding 'django/contrib/auth/locale/km/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,343 wheel INFO adding 'django/contrib/auth/locale/km/LC_MESSAGES/django.po'
2025-04-22 20:54:05,343 wheel INFO adding 'django/contrib/auth/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,343 wheel INFO adding 'django/contrib/auth/locale/kn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,344 wheel INFO adding 'django/contrib/auth/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,344 wheel INFO adding 'django/contrib/auth/locale/ko/LC_MESSAGES/django.po'
2025-04-22 20:54:05,344 wheel INFO adding 'django/contrib/auth/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,344 wheel INFO adding 'django/contrib/auth/locale/ky/LC_MESSAGES/django.po'
2025-04-22 20:54:05,344 wheel INFO adding 'django/contrib/auth/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,344 wheel INFO adding 'django/contrib/auth/locale/lb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,345 wheel INFO adding 'django/contrib/auth/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,345 wheel INFO adding 'django/contrib/auth/locale/lt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,345 wheel INFO adding 'django/contrib/auth/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,345 wheel INFO adding 'django/contrib/auth/locale/lv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,345 wheel INFO adding 'django/contrib/auth/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,346 wheel INFO adding 'django/contrib/auth/locale/mk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,346 wheel INFO adding 'django/contrib/auth/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,346 wheel INFO adding 'django/contrib/auth/locale/ml/LC_MESSAGES/django.po'
2025-04-22 20:54:05,346 wheel INFO adding 'django/contrib/auth/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,346 wheel INFO adding 'django/contrib/auth/locale/mn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,347 wheel INFO adding 'django/contrib/auth/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,347 wheel INFO adding 'django/contrib/auth/locale/mr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,347 wheel INFO adding 'django/contrib/auth/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,347 wheel INFO adding 'django/contrib/auth/locale/ms/LC_MESSAGES/django.po'
2025-04-22 20:54:05,347 wheel INFO adding 'django/contrib/auth/locale/my/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,347 wheel INFO adding 'django/contrib/auth/locale/my/LC_MESSAGES/django.po'
2025-04-22 20:54:05,348 wheel INFO adding 'django/contrib/auth/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,348 wheel INFO adding 'django/contrib/auth/locale/nb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,348 wheel INFO adding 'django/contrib/auth/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,348 wheel INFO adding 'django/contrib/auth/locale/ne/LC_MESSAGES/django.po'
2025-04-22 20:54:05,348 wheel INFO adding 'django/contrib/auth/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,348 wheel INFO adding 'django/contrib/auth/locale/nl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,349 wheel INFO adding 'django/contrib/auth/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,349 wheel INFO adding 'django/contrib/auth/locale/nn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,349 wheel INFO adding 'django/contrib/auth/locale/os/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,349 wheel INFO adding 'django/contrib/auth/locale/os/LC_MESSAGES/django.po'
2025-04-22 20:54:05,349 wheel INFO adding 'django/contrib/auth/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,349 wheel INFO adding 'django/contrib/auth/locale/pa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,350 wheel INFO adding 'django/contrib/auth/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,350 wheel INFO adding 'django/contrib/auth/locale/pl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,350 wheel INFO adding 'django/contrib/auth/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,350 wheel INFO adding 'django/contrib/auth/locale/pt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,350 wheel INFO adding 'django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,351 wheel INFO adding 'django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,351 wheel INFO adding 'django/contrib/auth/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,351 wheel INFO adding 'django/contrib/auth/locale/ro/LC_MESSAGES/django.po'
2025-04-22 20:54:05,351 wheel INFO adding 'django/contrib/auth/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,351 wheel INFO adding 'django/contrib/auth/locale/ru/LC_MESSAGES/django.po'
2025-04-22 20:54:05,352 wheel INFO adding 'django/contrib/auth/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,352 wheel INFO adding 'django/contrib/auth/locale/sk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,352 wheel INFO adding 'django/contrib/auth/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,352 wheel INFO adding 'django/contrib/auth/locale/sl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,352 wheel INFO adding 'django/contrib/auth/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,352 wheel INFO adding 'django/contrib/auth/locale/sq/LC_MESSAGES/django.po'
2025-04-22 20:54:05,353 wheel INFO adding 'django/contrib/auth/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,353 wheel INFO adding 'django/contrib/auth/locale/sr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,353 wheel INFO adding 'django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,353 wheel INFO adding 'django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,353 wheel INFO adding 'django/contrib/auth/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,353 wheel INFO adding 'django/contrib/auth/locale/sv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,354 wheel INFO adding 'django/contrib/auth/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,354 wheel INFO adding 'django/contrib/auth/locale/sw/LC_MESSAGES/django.po'
2025-04-22 20:54:05,354 wheel INFO adding 'django/contrib/auth/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,354 wheel INFO adding 'django/contrib/auth/locale/ta/LC_MESSAGES/django.po'
2025-04-22 20:54:05,354 wheel INFO adding 'django/contrib/auth/locale/te/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,354 wheel INFO adding 'django/contrib/auth/locale/te/LC_MESSAGES/django.po'
2025-04-22 20:54:05,355 wheel INFO adding 'django/contrib/auth/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,356 wheel INFO adding 'django/contrib/auth/locale/tg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,357 wheel INFO adding 'django/contrib/auth/locale/th/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,357 wheel INFO adding 'django/contrib/auth/locale/th/LC_MESSAGES/django.po'
2025-04-22 20:54:05,357 wheel INFO adding 'django/contrib/auth/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,357 wheel INFO adding 'django/contrib/auth/locale/tk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,357 wheel INFO adding 'django/contrib/auth/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,357 wheel INFO adding 'django/contrib/auth/locale/tr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,358 wheel INFO adding 'django/contrib/auth/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,358 wheel INFO adding 'django/contrib/auth/locale/tt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,358 wheel INFO adding 'django/contrib/auth/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,358 wheel INFO adding 'django/contrib/auth/locale/udm/LC_MESSAGES/django.po'
2025-04-22 20:54:05,359 wheel INFO adding 'django/contrib/auth/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,359 wheel INFO adding 'django/contrib/auth/locale/uk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,359 wheel INFO adding 'django/contrib/auth/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,359 wheel INFO adding 'django/contrib/auth/locale/ur/LC_MESSAGES/django.po'
2025-04-22 20:54:05,359 wheel INFO adding 'django/contrib/auth/locale/uz/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,359 wheel INFO adding 'django/contrib/auth/locale/uz/LC_MESSAGES/django.po'
2025-04-22 20:54:05,360 wheel INFO adding 'django/contrib/auth/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,360 wheel INFO adding 'django/contrib/auth/locale/vi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,360 wheel INFO adding 'django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,360 wheel INFO adding 'django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 20:54:05,360 wheel INFO adding 'django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,360 wheel INFO adding 'django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 20:54:05,361 wheel INFO adding 'django/contrib/auth/management/__init__.py'
2025-04-22 20:54:05,361 wheel INFO adding 'django/contrib/auth/management/commands/__init__.py'
2025-04-22 20:54:05,361 wheel INFO adding 'django/contrib/auth/management/commands/changepassword.py'
2025-04-22 20:54:05,361 wheel INFO adding 'django/contrib/auth/management/commands/createsuperuser.py'
2025-04-22 20:54:05,362 wheel INFO adding 'django/contrib/auth/migrations/0001_initial.py'
2025-04-22 20:54:05,362 wheel INFO adding 'django/contrib/auth/migrations/0002_alter_permission_name_max_length.py'
2025-04-22 20:54:05,362 wheel INFO adding 'django/contrib/auth/migrations/0003_alter_user_email_max_length.py'
2025-04-22 20:54:05,362 wheel INFO adding 'django/contrib/auth/migrations/0004_alter_user_username_opts.py'
2025-04-22 20:54:05,362 wheel INFO adding 'django/contrib/auth/migrations/0005_alter_user_last_login_null.py'
2025-04-22 20:54:05,362 wheel INFO adding 'django/contrib/auth/migrations/0006_require_contenttypes_0002.py'
2025-04-22 20:54:05,362 wheel INFO adding 'django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py'
2025-04-22 20:54:05,362 wheel INFO adding 'django/contrib/auth/migrations/0008_alter_user_username_max_length.py'
2025-04-22 20:54:05,363 wheel INFO adding 'django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py'
2025-04-22 20:54:05,363 wheel INFO adding 'django/contrib/auth/migrations/0010_alter_group_name_max_length.py'
2025-04-22 20:54:05,363 wheel INFO adding 'django/contrib/auth/migrations/0011_update_proxy_permissions.py'
2025-04-22 20:54:05,363 wheel INFO adding 'django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py'
2025-04-22 20:54:05,363 wheel INFO adding 'django/contrib/auth/migrations/__init__.py'
2025-04-22 20:54:05,363 wheel INFO adding 'django/contrib/auth/templates/auth/widgets/read_only_password_hash.html'
2025-04-22 20:54:05,363 wheel INFO adding 'django/contrib/auth/templates/registration/password_reset_subject.txt'
2025-04-22 20:54:05,363 wheel INFO adding 'django/contrib/contenttypes/__init__.py'
2025-04-22 20:54:05,364 wheel INFO adding 'django/contrib/contenttypes/admin.py'
2025-04-22 20:54:05,364 wheel INFO adding 'django/contrib/contenttypes/apps.py'
2025-04-22 20:54:05,364 wheel INFO adding 'django/contrib/contenttypes/checks.py'
2025-04-22 20:54:05,364 wheel INFO adding 'django/contrib/contenttypes/fields.py'
2025-04-22 20:54:05,364 wheel INFO adding 'django/contrib/contenttypes/forms.py'
2025-04-22 20:54:05,364 wheel INFO adding 'django/contrib/contenttypes/models.py'
2025-04-22 20:54:05,364 wheel INFO adding 'django/contrib/contenttypes/views.py'
2025-04-22 20:54:05,365 wheel INFO adding 'django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,365 wheel INFO adding 'django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po'
2025-04-22 20:54:05,366 wheel INFO adding 'django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,366 wheel INFO adding 'django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po'
2025-04-22 20:54:05,366 wheel INFO adding 'django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,366 wheel INFO adding 'django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 20:54:05,366 wheel INFO adding 'django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,366 wheel INFO adding 'django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po'
2025-04-22 20:54:05,366 wheel INFO adding 'django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,366 wheel INFO adding 'django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po'
2025-04-22 20:54:05,367 wheel INFO adding 'django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,367 wheel INFO adding 'django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po'
2025-04-22 20:54:05,367 wheel INFO adding 'django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,367 wheel INFO adding 'django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,367 wheel INFO adding 'django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,367 wheel INFO adding 'django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,368 wheel INFO adding 'django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,368 wheel INFO adding 'django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po'
2025-04-22 20:54:05,368 wheel INFO adding 'django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,368 wheel INFO adding 'django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,368 wheel INFO adding 'django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,368 wheel INFO adding 'django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po'
2025-04-22 20:54:05,369 wheel INFO adding 'django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,369 wheel INFO adding 'django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,369 wheel INFO adding 'django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,369 wheel INFO adding 'django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,369 wheel INFO adding 'django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,369 wheel INFO adding 'django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,369 wheel INFO adding 'django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,370 wheel INFO adding 'django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po'
2025-04-22 20:54:05,370 wheel INFO adding 'django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,370 wheel INFO adding 'django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po'
2025-04-22 20:54:05,370 wheel INFO adding 'django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,370 wheel INFO adding 'django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,370 wheel INFO adding 'django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,370 wheel INFO adding 'django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po'
2025-04-22 20:54:05,371 wheel INFO adding 'django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,371 wheel INFO adding 'django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po'
2025-04-22 20:54:05,371 wheel INFO adding 'django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,371 wheel INFO adding 'django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 20:54:05,371 wheel INFO adding 'django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,371 wheel INFO adding 'django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 20:54:05,371 wheel INFO adding 'django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,372 wheel INFO adding 'django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po'
2025-04-22 20:54:05,372 wheel INFO adding 'django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,372 wheel INFO adding 'django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po'
2025-04-22 20:54:05,372 wheel INFO adding 'django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,372 wheel INFO adding 'django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,372 wheel INFO adding 'django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,372 wheel INFO adding 'django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 20:54:05,373 wheel INFO adding 'django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,373 wheel INFO adding 'django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 20:54:05,373 wheel INFO adding 'django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,373 wheel INFO adding 'django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 20:54:05,373 wheel INFO adding 'django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,373 wheel INFO adding 'django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po'
2025-04-22 20:54:05,374 wheel INFO adding 'django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,374 wheel INFO adding 'django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,374 wheel INFO adding 'django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,374 wheel INFO adding 'django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,374 wheel INFO adding 'django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,374 wheel INFO adding 'django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,374 wheel INFO adding 'django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,374 wheel INFO adding 'django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,375 wheel INFO adding 'django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,375 wheel INFO adding 'django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,375 wheel INFO adding 'django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,375 wheel INFO adding 'django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po'
2025-04-22 20:54:05,375 wheel INFO adding 'django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,375 wheel INFO adding 'django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po'
2025-04-22 20:54:05,376 wheel INFO adding 'django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,376 wheel INFO adding 'django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,376 wheel INFO adding 'django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,376 wheel INFO adding 'django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po'
2025-04-22 20:54:05,376 wheel INFO adding 'django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,376 wheel INFO adding 'django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,376 wheel INFO adding 'django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,377 wheel INFO adding 'django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,377 wheel INFO adding 'django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,377 wheel INFO adding 'django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,377 wheel INFO adding 'django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,377 wheel INFO adding 'django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,377 wheel INFO adding 'django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,377 wheel INFO adding 'django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,378 wheel INFO adding 'django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,378 wheel INFO adding 'django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po'
2025-04-22 20:54:05,378 wheel INFO adding 'django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,378 wheel INFO adding 'django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po'
2025-04-22 20:54:05,378 wheel INFO adding 'django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,378 wheel INFO adding 'django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po'
2025-04-22 20:54:05,378 wheel INFO adding 'django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,379 wheel INFO adding 'django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po'
2025-04-22 20:54:05,379 wheel INFO adding 'django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,379 wheel INFO adding 'django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po'
2025-04-22 20:54:05,379 wheel INFO adding 'django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,379 wheel INFO adding 'django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po'
2025-04-22 20:54:05,379 wheel INFO adding 'django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,379 wheel INFO adding 'django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po'
2025-04-22 20:54:05,380 wheel INFO adding 'django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,380 wheel INFO adding 'django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,380 wheel INFO adding 'django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,380 wheel INFO adding 'django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po'
2025-04-22 20:54:05,380 wheel INFO adding 'django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,380 wheel INFO adding 'django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,380 wheel INFO adding 'django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,381 wheel INFO adding 'django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po'
2025-04-22 20:54:05,381 wheel INFO adding 'django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,381 wheel INFO adding 'django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po'
2025-04-22 20:54:05,381 wheel INFO adding 'django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,381 wheel INFO adding 'django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,381 wheel INFO adding 'django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,381 wheel INFO adding 'django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,382 wheel INFO adding 'django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,382 wheel INFO adding 'django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,382 wheel INFO adding 'django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,382 wheel INFO adding 'django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,382 wheel INFO adding 'django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,382 wheel INFO adding 'django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po'
2025-04-22 20:54:05,382 wheel INFO adding 'django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,383 wheel INFO adding 'django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,383 wheel INFO adding 'django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,383 wheel INFO adding 'django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,383 wheel INFO adding 'django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,383 wheel INFO adding 'django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.po'
2025-04-22 20:54:05,383 wheel INFO adding 'django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,383 wheel INFO adding 'django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po'
2025-04-22 20:54:05,384 wheel INFO adding 'django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,384 wheel INFO adding 'django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,384 wheel INFO adding 'django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,384 wheel INFO adding 'django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po'
2025-04-22 20:54:05,384 wheel INFO adding 'django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,384 wheel INFO adding 'django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,384 wheel INFO adding 'django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,385 wheel INFO adding 'django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,385 wheel INFO adding 'django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,389 wheel INFO adding 'django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po'
2025-04-22 20:54:05,389 wheel INFO adding 'django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,389 wheel INFO adding 'django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,389 wheel INFO adding 'django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,389 wheel INFO adding 'django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,389 wheel INFO adding 'django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,390 wheel INFO adding 'django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,390 wheel INFO adding 'django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,390 wheel INFO adding 'django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,390 wheel INFO adding 'django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,390 wheel INFO adding 'django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po'
2025-04-22 20:54:05,390 wheel INFO adding 'django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,390 wheel INFO adding 'django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po'
2025-04-22 20:54:05,391 wheel INFO adding 'django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,391 wheel INFO adding 'django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,391 wheel INFO adding 'django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,391 wheel INFO adding 'django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,391 wheel INFO adding 'django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,391 wheel INFO adding 'django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po'
2025-04-22 20:54:05,391 wheel INFO adding 'django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,392 wheel INFO adding 'django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,392 wheel INFO adding 'django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,392 wheel INFO adding 'django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,392 wheel INFO adding 'django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,392 wheel INFO adding 'django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,392 wheel INFO adding 'django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,393 wheel INFO adding 'django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po'
2025-04-22 20:54:05,393 wheel INFO adding 'django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,393 wheel INFO adding 'django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po'
2025-04-22 20:54:05,393 wheel INFO adding 'django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,393 wheel INFO adding 'django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po'
2025-04-22 20:54:05,393 wheel INFO adding 'django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,393 wheel INFO adding 'django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,394 wheel INFO adding 'django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,394 wheel INFO adding 'django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po'
2025-04-22 20:54:05,394 wheel INFO adding 'django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,394 wheel INFO adding 'django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,394 wheel INFO adding 'django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,394 wheel INFO adding 'django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,394 wheel INFO adding 'django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,395 wheel INFO adding 'django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,395 wheel INFO adding 'django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,395 wheel INFO adding 'django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po'
2025-04-22 20:54:05,395 wheel INFO adding 'django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,395 wheel INFO adding 'django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,395 wheel INFO adding 'django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,396 wheel INFO adding 'django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po'
2025-04-22 20:54:05,396 wheel INFO adding 'django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,396 wheel INFO adding 'django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,396 wheel INFO adding 'django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,396 wheel INFO adding 'django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 20:54:05,396 wheel INFO adding 'django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,397 wheel INFO adding 'django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 20:54:05,397 wheel INFO adding 'django/contrib/contenttypes/management/__init__.py'
2025-04-22 20:54:05,397 wheel INFO adding 'django/contrib/contenttypes/management/commands/__init__.py'
2025-04-22 20:54:05,397 wheel INFO adding 'django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py'
2025-04-22 20:54:05,397 wheel INFO adding 'django/contrib/contenttypes/migrations/0001_initial.py'
2025-04-22 20:54:05,397 wheel INFO adding 'django/contrib/contenttypes/migrations/0002_remove_content_type_name.py'
2025-04-22 20:54:05,397 wheel INFO adding 'django/contrib/contenttypes/migrations/__init__.py'
2025-04-22 20:54:05,397 wheel INFO adding 'django/contrib/flatpages/__init__.py'
2025-04-22 20:54:05,398 wheel INFO adding 'django/contrib/flatpages/admin.py'
2025-04-22 20:54:05,398 wheel INFO adding 'django/contrib/flatpages/apps.py'
2025-04-22 20:54:05,398 wheel INFO adding 'django/contrib/flatpages/forms.py'
2025-04-22 20:54:05,398 wheel INFO adding 'django/contrib/flatpages/middleware.py'
2025-04-22 20:54:05,398 wheel INFO adding 'django/contrib/flatpages/models.py'
2025-04-22 20:54:05,398 wheel INFO adding 'django/contrib/flatpages/sitemaps.py'
2025-04-22 20:54:05,398 wheel INFO adding 'django/contrib/flatpages/urls.py'
2025-04-22 20:54:05,398 wheel INFO adding 'django/contrib/flatpages/views.py'
2025-04-22 20:54:05,399 wheel INFO adding 'django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,399 wheel INFO adding 'django/contrib/flatpages/locale/af/LC_MESSAGES/django.po'
2025-04-22 20:54:05,399 wheel INFO adding 'django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,400 wheel INFO adding 'django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po'
2025-04-22 20:54:05,400 wheel INFO adding 'django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,400 wheel INFO adding 'django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 20:54:05,400 wheel INFO adding 'django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,400 wheel INFO adding 'django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po'
2025-04-22 20:54:05,400 wheel INFO adding 'django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,400 wheel INFO adding 'django/contrib/flatpages/locale/az/LC_MESSAGES/django.po'
2025-04-22 20:54:05,401 wheel INFO adding 'django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,401 wheel INFO adding 'django/contrib/flatpages/locale/be/LC_MESSAGES/django.po'
2025-04-22 20:54:05,401 wheel INFO adding 'django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,401 wheel INFO adding 'django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,401 wheel INFO adding 'django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,401 wheel INFO adding 'django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,401 wheel INFO adding 'django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,402 wheel INFO adding 'django/contrib/flatpages/locale/br/LC_MESSAGES/django.po'
2025-04-22 20:54:05,402 wheel INFO adding 'django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,402 wheel INFO adding 'django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,402 wheel INFO adding 'django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,402 wheel INFO adding 'django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po'
2025-04-22 20:54:05,402 wheel INFO adding 'django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,403 wheel INFO adding 'django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,403 wheel INFO adding 'django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,403 wheel INFO adding 'django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,403 wheel INFO adding 'django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,403 wheel INFO adding 'django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,403 wheel INFO adding 'django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,403 wheel INFO adding 'django/contrib/flatpages/locale/da/LC_MESSAGES/django.po'
2025-04-22 20:54:05,404 wheel INFO adding 'django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,404 wheel INFO adding 'django/contrib/flatpages/locale/de/LC_MESSAGES/django.po'
2025-04-22 20:54:05,404 wheel INFO adding 'django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,404 wheel INFO adding 'django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,404 wheel INFO adding 'django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,404 wheel INFO adding 'django/contrib/flatpages/locale/el/LC_MESSAGES/django.po'
2025-04-22 20:54:05,404 wheel INFO adding 'django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,405 wheel INFO adding 'django/contrib/flatpages/locale/en/LC_MESSAGES/django.po'
2025-04-22 20:54:05,405 wheel INFO adding 'django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,405 wheel INFO adding 'django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 20:54:05,405 wheel INFO adding 'django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,405 wheel INFO adding 'django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 20:54:05,405 wheel INFO adding 'django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,406 wheel INFO adding 'django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po'
2025-04-22 20:54:05,406 wheel INFO adding 'django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,406 wheel INFO adding 'django/contrib/flatpages/locale/es/LC_MESSAGES/django.po'
2025-04-22 20:54:05,406 wheel INFO adding 'django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,406 wheel INFO adding 'django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,406 wheel INFO adding 'django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,407 wheel INFO adding 'django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 20:54:05,407 wheel INFO adding 'django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,407 wheel INFO adding 'django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 20:54:05,407 wheel INFO adding 'django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,407 wheel INFO adding 'django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 20:54:05,407 wheel INFO adding 'django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,407 wheel INFO adding 'django/contrib/flatpages/locale/et/LC_MESSAGES/django.po'
2025-04-22 20:54:05,408 wheel INFO adding 'django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,408 wheel INFO adding 'django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,408 wheel INFO adding 'django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,408 wheel INFO adding 'django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,408 wheel INFO adding 'django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,408 wheel INFO adding 'django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,409 wheel INFO adding 'django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,409 wheel INFO adding 'django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,409 wheel INFO adding 'django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,409 wheel INFO adding 'django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,409 wheel INFO adding 'django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,409 wheel INFO adding 'django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po'
2025-04-22 20:54:05,409 wheel INFO adding 'django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,410 wheel INFO adding 'django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po'
2025-04-22 20:54:05,410 wheel INFO adding 'django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,410 wheel INFO adding 'django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,410 wheel INFO adding 'django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,410 wheel INFO adding 'django/contrib/flatpages/locale/he/LC_MESSAGES/django.po'
2025-04-22 20:54:05,410 wheel INFO adding 'django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,410 wheel INFO adding 'django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,411 wheel INFO adding 'django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,411 wheel INFO adding 'django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,411 wheel INFO adding 'django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,411 wheel INFO adding 'django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,411 wheel INFO adding 'django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,411 wheel INFO adding 'django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,412 wheel INFO adding 'django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,412 wheel INFO adding 'django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,412 wheel INFO adding 'django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,412 wheel INFO adding 'django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po'
2025-04-22 20:54:05,412 wheel INFO adding 'django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,412 wheel INFO adding 'django/contrib/flatpages/locale/id/LC_MESSAGES/django.po'
2025-04-22 20:54:05,412 wheel INFO adding 'django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,413 wheel INFO adding 'django/contrib/flatpages/locale/io/LC_MESSAGES/django.po'
2025-04-22 20:54:05,413 wheel INFO adding 'django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,413 wheel INFO adding 'django/contrib/flatpages/locale/is/LC_MESSAGES/django.po'
2025-04-22 20:54:05,413 wheel INFO adding 'django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,413 wheel INFO adding 'django/contrib/flatpages/locale/it/LC_MESSAGES/django.po'
2025-04-22 20:54:05,413 wheel INFO adding 'django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,413 wheel INFO adding 'django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po'
2025-04-22 20:54:05,414 wheel INFO adding 'django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,414 wheel INFO adding 'django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po'
2025-04-22 20:54:05,414 wheel INFO adding 'django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,414 wheel INFO adding 'django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,414 wheel INFO adding 'django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,414 wheel INFO adding 'django/contrib/flatpages/locale/km/LC_MESSAGES/django.po'
2025-04-22 20:54:05,414 wheel INFO adding 'django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,415 wheel INFO adding 'django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,415 wheel INFO adding 'django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,415 wheel INFO adding 'django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po'
2025-04-22 20:54:05,415 wheel INFO adding 'django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,415 wheel INFO adding 'django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po'
2025-04-22 20:54:05,415 wheel INFO adding 'django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,416 wheel INFO adding 'django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,416 wheel INFO adding 'django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,416 wheel INFO adding 'django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,416 wheel INFO adding 'django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,416 wheel INFO adding 'django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,416 wheel INFO adding 'django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,416 wheel INFO adding 'django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,417 wheel INFO adding 'django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,417 wheel INFO adding 'django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po'
2025-04-22 20:54:05,417 wheel INFO adding 'django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,417 wheel INFO adding 'django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,417 wheel INFO adding 'django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,417 wheel INFO adding 'django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,418 wheel INFO adding 'django/contrib/flatpages/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,418 wheel INFO adding 'django/contrib/flatpages/locale/ms/LC_MESSAGES/django.po'
2025-04-22 20:54:05,418 wheel INFO adding 'django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,418 wheel INFO adding 'django/contrib/flatpages/locale/my/LC_MESSAGES/django.po'
2025-04-22 20:54:05,418 wheel INFO adding 'django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,418 wheel INFO adding 'django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,419 wheel INFO adding 'django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,419 wheel INFO adding 'django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po'
2025-04-22 20:54:05,419 wheel INFO adding 'django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,419 wheel INFO adding 'django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,419 wheel INFO adding 'django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,419 wheel INFO adding 'django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,419 wheel INFO adding 'django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,420 wheel INFO adding 'django/contrib/flatpages/locale/os/LC_MESSAGES/django.po'
2025-04-22 20:54:05,420 wheel INFO adding 'django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,420 wheel INFO adding 'django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,420 wheel INFO adding 'django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,420 wheel INFO adding 'django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,420 wheel INFO adding 'django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,420 wheel INFO adding 'django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,421 wheel INFO adding 'django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,421 wheel INFO adding 'django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,421 wheel INFO adding 'django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,421 wheel INFO adding 'django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po'
2025-04-22 20:54:05,421 wheel INFO adding 'django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,421 wheel INFO adding 'django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po'
2025-04-22 20:54:05,422 wheel INFO adding 'django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,422 wheel INFO adding 'django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,422 wheel INFO adding 'django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,422 wheel INFO adding 'django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,422 wheel INFO adding 'django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,422 wheel INFO adding 'django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po'
2025-04-22 20:54:05,422 wheel INFO adding 'django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,423 wheel INFO adding 'django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,423 wheel INFO adding 'django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,423 wheel INFO adding 'django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,423 wheel INFO adding 'django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,423 wheel INFO adding 'django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,423 wheel INFO adding 'django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,424 wheel INFO adding 'django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po'
2025-04-22 20:54:05,424 wheel INFO adding 'django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,424 wheel INFO adding 'django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po'
2025-04-22 20:54:05,424 wheel INFO adding 'django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,424 wheel INFO adding 'django/contrib/flatpages/locale/te/LC_MESSAGES/django.po'
2025-04-22 20:54:05,424 wheel INFO adding 'django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,424 wheel INFO adding 'django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,425 wheel INFO adding 'django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,425 wheel INFO adding 'django/contrib/flatpages/locale/th/LC_MESSAGES/django.po'
2025-04-22 20:54:05,425 wheel INFO adding 'django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,425 wheel INFO adding 'django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,425 wheel INFO adding 'django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,425 wheel INFO adding 'django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,425 wheel INFO adding 'django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,426 wheel INFO adding 'django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,426 wheel INFO adding 'django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,426 wheel INFO adding 'django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po'
2025-04-22 20:54:05,426 wheel INFO adding 'django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,426 wheel INFO adding 'django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,426 wheel INFO adding 'django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,427 wheel INFO adding 'django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po'
2025-04-22 20:54:05,427 wheel INFO adding 'django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,427 wheel INFO adding 'django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,427 wheel INFO adding 'django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,427 wheel INFO adding 'django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 20:54:05,427 wheel INFO adding 'django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,427 wheel INFO adding 'django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 20:54:05,428 wheel INFO adding 'django/contrib/flatpages/migrations/0001_initial.py'
2025-04-22 20:54:05,428 wheel INFO adding 'django/contrib/flatpages/migrations/__init__.py'
2025-04-22 20:54:05,428 wheel INFO adding 'django/contrib/flatpages/templatetags/__init__.py'
2025-04-22 20:54:05,428 wheel INFO adding 'django/contrib/flatpages/templatetags/flatpages.py'
2025-04-22 20:54:05,429 wheel INFO adding 'django/contrib/gis/__init__.py'
2025-04-22 20:54:05,429 wheel INFO adding 'django/contrib/gis/apps.py'
2025-04-22 20:54:05,429 wheel INFO adding 'django/contrib/gis/feeds.py'
2025-04-22 20:54:05,429 wheel INFO adding 'django/contrib/gis/geometry.py'
2025-04-22 20:54:05,429 wheel INFO adding 'django/contrib/gis/measure.py'
2025-04-22 20:54:05,429 wheel INFO adding 'django/contrib/gis/ptr.py'
2025-04-22 20:54:05,429 wheel INFO adding 'django/contrib/gis/shortcuts.py'
2025-04-22 20:54:05,430 wheel INFO adding 'django/contrib/gis/views.py'
2025-04-22 20:54:05,430 wheel INFO adding 'django/contrib/gis/admin/__init__.py'
2025-04-22 20:54:05,430 wheel INFO adding 'django/contrib/gis/admin/options.py'
2025-04-22 20:54:05,430 wheel INFO adding 'django/contrib/gis/admin/widgets.py'
2025-04-22 20:54:05,430 wheel INFO adding 'django/contrib/gis/db/__init__.py'
2025-04-22 20:54:05,430 wheel INFO adding 'django/contrib/gis/db/backends/__init__.py'
2025-04-22 20:54:05,430 wheel INFO adding 'django/contrib/gis/db/backends/utils.py'
2025-04-22 20:54:05,431 wheel INFO adding 'django/contrib/gis/db/backends/base/__init__.py'
2025-04-22 20:54:05,431 wheel INFO adding 'django/contrib/gis/db/backends/base/adapter.py'
2025-04-22 20:54:05,431 wheel INFO adding 'django/contrib/gis/db/backends/base/features.py'
2025-04-22 20:54:05,431 wheel INFO adding 'django/contrib/gis/db/backends/base/models.py'
2025-04-22 20:54:05,431 wheel INFO adding 'django/contrib/gis/db/backends/base/operations.py'
2025-04-22 20:54:05,431 wheel INFO adding 'django/contrib/gis/db/backends/mysql/__init__.py'
2025-04-22 20:54:05,431 wheel INFO adding 'django/contrib/gis/db/backends/mysql/base.py'
2025-04-22 20:54:05,432 wheel INFO adding 'django/contrib/gis/db/backends/mysql/features.py'
2025-04-22 20:54:05,432 wheel INFO adding 'django/contrib/gis/db/backends/mysql/introspection.py'
2025-04-22 20:54:05,432 wheel INFO adding 'django/contrib/gis/db/backends/mysql/operations.py'
2025-04-22 20:54:05,432 wheel INFO adding 'django/contrib/gis/db/backends/mysql/schema.py'
2025-04-22 20:54:05,432 wheel INFO adding 'django/contrib/gis/db/backends/oracle/__init__.py'
2025-04-22 20:54:05,432 wheel INFO adding 'django/contrib/gis/db/backends/oracle/adapter.py'
2025-04-22 20:54:05,432 wheel INFO adding 'django/contrib/gis/db/backends/oracle/base.py'
2025-04-22 20:54:05,432 wheel INFO adding 'django/contrib/gis/db/backends/oracle/features.py'
2025-04-22 20:54:05,433 wheel INFO adding 'django/contrib/gis/db/backends/oracle/introspection.py'
2025-04-22 20:54:05,433 wheel INFO adding 'django/contrib/gis/db/backends/oracle/models.py'
2025-04-22 20:54:05,433 wheel INFO adding 'django/contrib/gis/db/backends/oracle/operations.py'
2025-04-22 20:54:05,433 wheel INFO adding 'django/contrib/gis/db/backends/oracle/schema.py'
2025-04-22 20:54:05,433 wheel INFO adding 'django/contrib/gis/db/backends/postgis/__init__.py'
2025-04-22 20:54:05,433 wheel INFO adding 'django/contrib/gis/db/backends/postgis/adapter.py'
2025-04-22 20:54:05,433 wheel INFO adding 'django/contrib/gis/db/backends/postgis/base.py'
2025-04-22 20:54:05,434 wheel INFO adding 'django/contrib/gis/db/backends/postgis/const.py'
2025-04-22 20:54:05,434 wheel INFO adding 'django/contrib/gis/db/backends/postgis/features.py'
2025-04-22 20:54:05,434 wheel INFO adding 'django/contrib/gis/db/backends/postgis/introspection.py'
2025-04-22 20:54:05,434 wheel INFO adding 'django/contrib/gis/db/backends/postgis/models.py'
2025-04-22 20:54:05,434 wheel INFO adding 'django/contrib/gis/db/backends/postgis/operations.py'
2025-04-22 20:54:05,434 wheel INFO adding 'django/contrib/gis/db/backends/postgis/pgraster.py'
2025-04-22 20:54:05,434 wheel INFO adding 'django/contrib/gis/db/backends/postgis/schema.py'
2025-04-22 20:54:05,434 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/__init__.py'
2025-04-22 20:54:05,435 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/adapter.py'
2025-04-22 20:54:05,435 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/base.py'
2025-04-22 20:54:05,435 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/client.py'
2025-04-22 20:54:05,435 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/features.py'
2025-04-22 20:54:05,435 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/introspection.py'
2025-04-22 20:54:05,435 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/models.py'
2025-04-22 20:54:05,436 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/operations.py'
2025-04-22 20:54:05,436 wheel INFO adding 'django/contrib/gis/db/backends/spatialite/schema.py'
2025-04-22 20:54:05,436 wheel INFO adding 'django/contrib/gis/db/models/__init__.py'
2025-04-22 20:54:05,436 wheel INFO adding 'django/contrib/gis/db/models/aggregates.py'
2025-04-22 20:54:05,436 wheel INFO adding 'django/contrib/gis/db/models/fields.py'
2025-04-22 20:54:05,436 wheel INFO adding 'django/contrib/gis/db/models/functions.py'
2025-04-22 20:54:05,437 wheel INFO adding 'django/contrib/gis/db/models/lookups.py'
2025-04-22 20:54:05,437 wheel INFO adding 'django/contrib/gis/db/models/proxy.py'
2025-04-22 20:54:05,437 wheel INFO adding 'django/contrib/gis/db/models/sql/__init__.py'
2025-04-22 20:54:05,437 wheel INFO adding 'django/contrib/gis/db/models/sql/conversion.py'
2025-04-22 20:54:05,437 wheel INFO adding 'django/contrib/gis/forms/__init__.py'
2025-04-22 20:54:05,437 wheel INFO adding 'django/contrib/gis/forms/fields.py'
2025-04-22 20:54:05,437 wheel INFO adding 'django/contrib/gis/forms/widgets.py'
2025-04-22 20:54:05,438 wheel INFO adding 'django/contrib/gis/gdal/LICENSE'
2025-04-22 20:54:05,438 wheel INFO adding 'django/contrib/gis/gdal/__init__.py'
2025-04-22 20:54:05,438 wheel INFO adding 'django/contrib/gis/gdal/base.py'
2025-04-22 20:54:05,438 wheel INFO adding 'django/contrib/gis/gdal/datasource.py'
2025-04-22 20:54:05,438 wheel INFO adding 'django/contrib/gis/gdal/driver.py'
2025-04-22 20:54:05,438 wheel INFO adding 'django/contrib/gis/gdal/envelope.py'
2025-04-22 20:54:05,438 wheel INFO adding 'django/contrib/gis/gdal/error.py'
2025-04-22 20:54:05,438 wheel INFO adding 'django/contrib/gis/gdal/feature.py'
2025-04-22 20:54:05,439 wheel INFO adding 'django/contrib/gis/gdal/field.py'
2025-04-22 20:54:05,439 wheel INFO adding 'django/contrib/gis/gdal/geometries.py'
2025-04-22 20:54:05,439 wheel INFO adding 'django/contrib/gis/gdal/geomtype.py'
2025-04-22 20:54:05,439 wheel INFO adding 'django/contrib/gis/gdal/layer.py'
2025-04-22 20:54:05,439 wheel INFO adding 'django/contrib/gis/gdal/libgdal.py'
2025-04-22 20:54:05,439 wheel INFO adding 'django/contrib/gis/gdal/srs.py'
2025-04-22 20:54:05,440 wheel INFO adding 'django/contrib/gis/gdal/prototypes/__init__.py'
2025-04-22 20:54:05,440 wheel INFO adding 'django/contrib/gis/gdal/prototypes/ds.py'
2025-04-22 20:54:05,440 wheel INFO adding 'django/contrib/gis/gdal/prototypes/errcheck.py'
2025-04-22 20:54:05,440 wheel INFO adding 'django/contrib/gis/gdal/prototypes/generation.py'
2025-04-22 20:54:05,440 wheel INFO adding 'django/contrib/gis/gdal/prototypes/geom.py'
2025-04-22 20:54:05,440 wheel INFO adding 'django/contrib/gis/gdal/prototypes/raster.py'
2025-04-22 20:54:05,440 wheel INFO adding 'django/contrib/gis/gdal/prototypes/srs.py'
2025-04-22 20:54:05,441 wheel INFO adding 'django/contrib/gis/gdal/raster/__init__.py'
2025-04-22 20:54:05,441 wheel INFO adding 'django/contrib/gis/gdal/raster/band.py'
2025-04-22 20:54:05,441 wheel INFO adding 'django/contrib/gis/gdal/raster/base.py'
2025-04-22 20:54:05,441 wheel INFO adding 'django/contrib/gis/gdal/raster/const.py'
2025-04-22 20:54:05,441 wheel INFO adding 'django/contrib/gis/gdal/raster/source.py'
2025-04-22 20:54:05,441 wheel INFO adding 'django/contrib/gis/geoip2/__init__.py'
2025-04-22 20:54:05,441 wheel INFO adding 'django/contrib/gis/geoip2/base.py'
2025-04-22 20:54:05,442 wheel INFO adding 'django/contrib/gis/geoip2/resources.py'
2025-04-22 20:54:05,442 wheel INFO adding 'django/contrib/gis/geos/LICENSE'
2025-04-22 20:54:05,442 wheel INFO adding 'django/contrib/gis/geos/__init__.py'
2025-04-22 20:54:05,442 wheel INFO adding 'django/contrib/gis/geos/base.py'
2025-04-22 20:54:05,442 wheel INFO adding 'django/contrib/gis/geos/collections.py'
2025-04-22 20:54:05,442 wheel INFO adding 'django/contrib/gis/geos/coordseq.py'
2025-04-22 20:54:05,442 wheel INFO adding 'django/contrib/gis/geos/error.py'
2025-04-22 20:54:05,442 wheel INFO adding 'django/contrib/gis/geos/factory.py'
2025-04-22 20:54:05,443 wheel INFO adding 'django/contrib/gis/geos/geometry.py'
2025-04-22 20:54:05,443 wheel INFO adding 'django/contrib/gis/geos/io.py'
2025-04-22 20:54:05,443 wheel INFO adding 'django/contrib/gis/geos/libgeos.py'
2025-04-22 20:54:05,443 wheel INFO adding 'django/contrib/gis/geos/linestring.py'
2025-04-22 20:54:05,443 wheel INFO adding 'django/contrib/gis/geos/mutable_list.py'
2025-04-22 20:54:05,443 wheel INFO adding 'django/contrib/gis/geos/point.py'
2025-04-22 20:54:05,444 wheel INFO adding 'django/contrib/gis/geos/polygon.py'
2025-04-22 20:54:05,444 wheel INFO adding 'django/contrib/gis/geos/prepared.py'
2025-04-22 20:54:05,444 wheel INFO adding 'django/contrib/gis/geos/prototypes/__init__.py'
2025-04-22 20:54:05,444 wheel INFO adding 'django/contrib/gis/geos/prototypes/coordseq.py'
2025-04-22 20:54:05,444 wheel INFO adding 'django/contrib/gis/geos/prototypes/errcheck.py'
2025-04-22 20:54:05,444 wheel INFO adding 'django/contrib/gis/geos/prototypes/geom.py'
2025-04-22 20:54:05,444 wheel INFO adding 'django/contrib/gis/geos/prototypes/io.py'
2025-04-22 20:54:05,444 wheel INFO adding 'django/contrib/gis/geos/prototypes/misc.py'
2025-04-22 20:54:05,445 wheel INFO adding 'django/contrib/gis/geos/prototypes/predicates.py'
2025-04-22 20:54:05,445 wheel INFO adding 'django/contrib/gis/geos/prototypes/prepared.py'
2025-04-22 20:54:05,445 wheel INFO adding 'django/contrib/gis/geos/prototypes/threadsafe.py'
2025-04-22 20:54:05,445 wheel INFO adding 'django/contrib/gis/geos/prototypes/topology.py'
2025-04-22 20:54:05,446 wheel INFO adding 'django/contrib/gis/locale/af/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,446 wheel INFO adding 'django/contrib/gis/locale/af/LC_MESSAGES/django.po'
2025-04-22 20:54:05,446 wheel INFO adding 'django/contrib/gis/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,446 wheel INFO adding 'django/contrib/gis/locale/ar/LC_MESSAGES/django.po'
2025-04-22 20:54:05,446 wheel INFO adding 'django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,447 wheel INFO adding 'django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 20:54:05,447 wheel INFO adding 'django/contrib/gis/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,447 wheel INFO adding 'django/contrib/gis/locale/ast/LC_MESSAGES/django.po'
2025-04-22 20:54:05,447 wheel INFO adding 'django/contrib/gis/locale/az/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,447 wheel INFO adding 'django/contrib/gis/locale/az/LC_MESSAGES/django.po'
2025-04-22 20:54:05,447 wheel INFO adding 'django/contrib/gis/locale/be/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,447 wheel INFO adding 'django/contrib/gis/locale/be/LC_MESSAGES/django.po'
2025-04-22 20:54:05,448 wheel INFO adding 'django/contrib/gis/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,448 wheel INFO adding 'django/contrib/gis/locale/bg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,448 wheel INFO adding 'django/contrib/gis/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,448 wheel INFO adding 'django/contrib/gis/locale/bn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,448 wheel INFO adding 'django/contrib/gis/locale/br/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,448 wheel INFO adding 'django/contrib/gis/locale/br/LC_MESSAGES/django.po'
2025-04-22 20:54:05,448 wheel INFO adding 'django/contrib/gis/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,449 wheel INFO adding 'django/contrib/gis/locale/bs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,449 wheel INFO adding 'django/contrib/gis/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,449 wheel INFO adding 'django/contrib/gis/locale/ca/LC_MESSAGES/django.po'
2025-04-22 20:54:05,449 wheel INFO adding 'django/contrib/gis/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,449 wheel INFO adding 'django/contrib/gis/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,449 wheel INFO adding 'django/contrib/gis/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,449 wheel INFO adding 'django/contrib/gis/locale/cs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,450 wheel INFO adding 'django/contrib/gis/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,450 wheel INFO adding 'django/contrib/gis/locale/cy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,450 wheel INFO adding 'django/contrib/gis/locale/da/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,450 wheel INFO adding 'django/contrib/gis/locale/da/LC_MESSAGES/django.po'
2025-04-22 20:54:05,450 wheel INFO adding 'django/contrib/gis/locale/de/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,451 wheel INFO adding 'django/contrib/gis/locale/de/LC_MESSAGES/django.po'
2025-04-22 20:54:05,451 wheel INFO adding 'django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,451 wheel INFO adding 'django/contrib/gis/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,451 wheel INFO adding 'django/contrib/gis/locale/el/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,451 wheel INFO adding 'django/contrib/gis/locale/el/LC_MESSAGES/django.po'
2025-04-22 20:54:05,451 wheel INFO adding 'django/contrib/gis/locale/en/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,451 wheel INFO adding 'django/contrib/gis/locale/en/LC_MESSAGES/django.po'
2025-04-22 20:54:05,452 wheel INFO adding 'django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,452 wheel INFO adding 'django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 20:54:05,452 wheel INFO adding 'django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,452 wheel INFO adding 'django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 20:54:05,452 wheel INFO adding 'django/contrib/gis/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,452 wheel INFO adding 'django/contrib/gis/locale/eo/LC_MESSAGES/django.po'
2025-04-22 20:54:05,452 wheel INFO adding 'django/contrib/gis/locale/es/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,453 wheel INFO adding 'django/contrib/gis/locale/es/LC_MESSAGES/django.po'
2025-04-22 20:54:05,453 wheel INFO adding 'django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,453 wheel INFO adding 'django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,453 wheel INFO adding 'django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,453 wheel INFO adding 'django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 20:54:05,453 wheel INFO adding 'django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,453 wheel INFO adding 'django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 20:54:05,454 wheel INFO adding 'django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,454 wheel INFO adding 'django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 20:54:05,454 wheel INFO adding 'django/contrib/gis/locale/et/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,454 wheel INFO adding 'django/contrib/gis/locale/et/LC_MESSAGES/django.po'
2025-04-22 20:54:05,454 wheel INFO adding 'django/contrib/gis/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,454 wheel INFO adding 'django/contrib/gis/locale/eu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,455 wheel INFO adding 'django/contrib/gis/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,455 wheel INFO adding 'django/contrib/gis/locale/fa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,455 wheel INFO adding 'django/contrib/gis/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,455 wheel INFO adding 'django/contrib/gis/locale/fi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,455 wheel INFO adding 'django/contrib/gis/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,455 wheel INFO adding 'django/contrib/gis/locale/fr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,455 wheel INFO adding 'django/contrib/gis/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,456 wheel INFO adding 'django/contrib/gis/locale/fy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,456 wheel INFO adding 'django/contrib/gis/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,456 wheel INFO adding 'django/contrib/gis/locale/ga/LC_MESSAGES/django.po'
2025-04-22 20:54:05,456 wheel INFO adding 'django/contrib/gis/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,456 wheel INFO adding 'django/contrib/gis/locale/gd/LC_MESSAGES/django.po'
2025-04-22 20:54:05,456 wheel INFO adding 'django/contrib/gis/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,456 wheel INFO adding 'django/contrib/gis/locale/gl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,457 wheel INFO adding 'django/contrib/gis/locale/he/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,457 wheel INFO adding 'django/contrib/gis/locale/he/LC_MESSAGES/django.po'
2025-04-22 20:54:05,457 wheel INFO adding 'django/contrib/gis/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,457 wheel INFO adding 'django/contrib/gis/locale/hi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,457 wheel INFO adding 'django/contrib/gis/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,457 wheel INFO adding 'django/contrib/gis/locale/hr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,457 wheel INFO adding 'django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,458 wheel INFO adding 'django/contrib/gis/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,458 wheel INFO adding 'django/contrib/gis/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,458 wheel INFO adding 'django/contrib/gis/locale/hu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,458 wheel INFO adding 'django/contrib/gis/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,458 wheel INFO adding 'django/contrib/gis/locale/hy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,458 wheel INFO adding 'django/contrib/gis/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,458 wheel INFO adding 'django/contrib/gis/locale/ia/LC_MESSAGES/django.po'
2025-04-22 20:54:05,459 wheel INFO adding 'django/contrib/gis/locale/id/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,459 wheel INFO adding 'django/contrib/gis/locale/id/LC_MESSAGES/django.po'
2025-04-22 20:54:05,459 wheel INFO adding 'django/contrib/gis/locale/io/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,459 wheel INFO adding 'django/contrib/gis/locale/io/LC_MESSAGES/django.po'
2025-04-22 20:54:05,459 wheel INFO adding 'django/contrib/gis/locale/is/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,459 wheel INFO adding 'django/contrib/gis/locale/is/LC_MESSAGES/django.po'
2025-04-22 20:54:05,459 wheel INFO adding 'django/contrib/gis/locale/it/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,460 wheel INFO adding 'django/contrib/gis/locale/it/LC_MESSAGES/django.po'
2025-04-22 20:54:05,460 wheel INFO adding 'django/contrib/gis/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,460 wheel INFO adding 'django/contrib/gis/locale/ja/LC_MESSAGES/django.po'
2025-04-22 20:54:05,460 wheel INFO adding 'django/contrib/gis/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,460 wheel INFO adding 'django/contrib/gis/locale/ka/LC_MESSAGES/django.po'
2025-04-22 20:54:05,460 wheel INFO adding 'django/contrib/gis/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,461 wheel INFO adding 'django/contrib/gis/locale/kk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,461 wheel INFO adding 'django/contrib/gis/locale/km/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,461 wheel INFO adding 'django/contrib/gis/locale/km/LC_MESSAGES/django.po'
2025-04-22 20:54:05,461 wheel INFO adding 'django/contrib/gis/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,461 wheel INFO adding 'django/contrib/gis/locale/kn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,461 wheel INFO adding 'django/contrib/gis/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,461 wheel INFO adding 'django/contrib/gis/locale/ko/LC_MESSAGES/django.po'
2025-04-22 20:54:05,462 wheel INFO adding 'django/contrib/gis/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,462 wheel INFO adding 'django/contrib/gis/locale/ky/LC_MESSAGES/django.po'
2025-04-22 20:54:05,462 wheel INFO adding 'django/contrib/gis/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,462 wheel INFO adding 'django/contrib/gis/locale/lb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,462 wheel INFO adding 'django/contrib/gis/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,462 wheel INFO adding 'django/contrib/gis/locale/lt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,463 wheel INFO adding 'django/contrib/gis/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,463 wheel INFO adding 'django/contrib/gis/locale/lv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,463 wheel INFO adding 'django/contrib/gis/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,463 wheel INFO adding 'django/contrib/gis/locale/mk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,463 wheel INFO adding 'django/contrib/gis/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,463 wheel INFO adding 'django/contrib/gis/locale/ml/LC_MESSAGES/django.po'
2025-04-22 20:54:05,463 wheel INFO adding 'django/contrib/gis/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,464 wheel INFO adding 'django/contrib/gis/locale/mn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,464 wheel INFO adding 'django/contrib/gis/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,464 wheel INFO adding 'django/contrib/gis/locale/mr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,464 wheel INFO adding 'django/contrib/gis/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,464 wheel INFO adding 'django/contrib/gis/locale/ms/LC_MESSAGES/django.po'
2025-04-22 20:54:05,464 wheel INFO adding 'django/contrib/gis/locale/my/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,465 wheel INFO adding 'django/contrib/gis/locale/my/LC_MESSAGES/django.po'
2025-04-22 20:54:05,465 wheel INFO adding 'django/contrib/gis/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,465 wheel INFO adding 'django/contrib/gis/locale/nb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,465 wheel INFO adding 'django/contrib/gis/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,465 wheel INFO adding 'django/contrib/gis/locale/ne/LC_MESSAGES/django.po'
2025-04-22 20:54:05,466 wheel INFO adding 'django/contrib/gis/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,466 wheel INFO adding 'django/contrib/gis/locale/nl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,466 wheel INFO adding 'django/contrib/gis/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,466 wheel INFO adding 'django/contrib/gis/locale/nn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,466 wheel INFO adding 'django/contrib/gis/locale/os/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,466 wheel INFO adding 'django/contrib/gis/locale/os/LC_MESSAGES/django.po'
2025-04-22 20:54:05,466 wheel INFO adding 'django/contrib/gis/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,467 wheel INFO adding 'django/contrib/gis/locale/pa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,467 wheel INFO adding 'django/contrib/gis/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,467 wheel INFO adding 'django/contrib/gis/locale/pl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,467 wheel INFO adding 'django/contrib/gis/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,467 wheel INFO adding 'django/contrib/gis/locale/pt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,467 wheel INFO adding 'django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,467 wheel INFO adding 'django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,468 wheel INFO adding 'django/contrib/gis/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,468 wheel INFO adding 'django/contrib/gis/locale/ro/LC_MESSAGES/django.po'
2025-04-22 20:54:05,468 wheel INFO adding 'django/contrib/gis/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,468 wheel INFO adding 'django/contrib/gis/locale/ru/LC_MESSAGES/django.po'
2025-04-22 20:54:05,468 wheel INFO adding 'django/contrib/gis/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,468 wheel INFO adding 'django/contrib/gis/locale/sk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,468 wheel INFO adding 'django/contrib/gis/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,469 wheel INFO adding 'django/contrib/gis/locale/sl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,469 wheel INFO adding 'django/contrib/gis/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,469 wheel INFO adding 'django/contrib/gis/locale/sq/LC_MESSAGES/django.po'
2025-04-22 20:54:05,469 wheel INFO adding 'django/contrib/gis/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,469 wheel INFO adding 'django/contrib/gis/locale/sr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,469 wheel INFO adding 'django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,470 wheel INFO adding 'django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,470 wheel INFO adding 'django/contrib/gis/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,470 wheel INFO adding 'django/contrib/gis/locale/sv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,470 wheel INFO adding 'django/contrib/gis/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,470 wheel INFO adding 'django/contrib/gis/locale/sw/LC_MESSAGES/django.po'
2025-04-22 20:54:05,470 wheel INFO adding 'django/contrib/gis/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,470 wheel INFO adding 'django/contrib/gis/locale/ta/LC_MESSAGES/django.po'
2025-04-22 20:54:05,471 wheel INFO adding 'django/contrib/gis/locale/te/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,471 wheel INFO adding 'django/contrib/gis/locale/te/LC_MESSAGES/django.po'
2025-04-22 20:54:05,471 wheel INFO adding 'django/contrib/gis/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,471 wheel INFO adding 'django/contrib/gis/locale/tg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,471 wheel INFO adding 'django/contrib/gis/locale/th/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,471 wheel INFO adding 'django/contrib/gis/locale/th/LC_MESSAGES/django.po'
2025-04-22 20:54:05,471 wheel INFO adding 'django/contrib/gis/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,472 wheel INFO adding 'django/contrib/gis/locale/tr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,472 wheel INFO adding 'django/contrib/gis/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,472 wheel INFO adding 'django/contrib/gis/locale/tt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,472 wheel INFO adding 'django/contrib/gis/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,472 wheel INFO adding 'django/contrib/gis/locale/udm/LC_MESSAGES/django.po'
2025-04-22 20:54:05,472 wheel INFO adding 'django/contrib/gis/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,472 wheel INFO adding 'django/contrib/gis/locale/uk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,473 wheel INFO adding 'django/contrib/gis/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,473 wheel INFO adding 'django/contrib/gis/locale/ur/LC_MESSAGES/django.po'
2025-04-22 20:54:05,473 wheel INFO adding 'django/contrib/gis/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,473 wheel INFO adding 'django/contrib/gis/locale/vi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,473 wheel INFO adding 'django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,473 wheel INFO adding 'django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 20:54:05,473 wheel INFO adding 'django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,474 wheel INFO adding 'django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 20:54:05,474 wheel INFO adding 'django/contrib/gis/management/__init__.py'
2025-04-22 20:54:05,474 wheel INFO adding 'django/contrib/gis/management/commands/__init__.py'
2025-04-22 20:54:05,474 wheel INFO adding 'django/contrib/gis/management/commands/inspectdb.py'
2025-04-22 20:54:05,474 wheel INFO adding 'django/contrib/gis/management/commands/ogrinspect.py'
2025-04-22 20:54:05,474 wheel INFO adding 'django/contrib/gis/serializers/__init__.py'
2025-04-22 20:54:05,474 wheel INFO adding 'django/contrib/gis/serializers/geojson.py'
2025-04-22 20:54:05,475 wheel INFO adding 'django/contrib/gis/sitemaps/__init__.py'
2025-04-22 20:54:05,475 wheel INFO adding 'django/contrib/gis/sitemaps/kml.py'
2025-04-22 20:54:05,475 wheel INFO adding 'django/contrib/gis/sitemaps/views.py'
2025-04-22 20:54:05,475 wheel INFO adding 'django/contrib/gis/static/gis/css/ol3.css'
2025-04-22 20:54:05,475 wheel INFO adding 'django/contrib/gis/static/gis/img/draw_line_off.svg'
2025-04-22 20:54:05,475 wheel INFO adding 'django/contrib/gis/static/gis/img/draw_line_on.svg'
2025-04-22 20:54:05,475 wheel INFO adding 'django/contrib/gis/static/gis/img/draw_point_off.svg'
2025-04-22 20:54:05,475 wheel INFO adding 'django/contrib/gis/static/gis/img/draw_point_on.svg'
2025-04-22 20:54:05,476 wheel INFO adding 'django/contrib/gis/static/gis/img/draw_polygon_off.svg'
2025-04-22 20:54:05,476 wheel INFO adding 'django/contrib/gis/static/gis/img/draw_polygon_on.svg'
2025-04-22 20:54:05,476 wheel INFO adding 'django/contrib/gis/static/gis/js/OLMapWidget.js'
2025-04-22 20:54:05,476 wheel INFO adding 'django/contrib/gis/templates/gis/openlayers-osm.html'
2025-04-22 20:54:05,476 wheel INFO adding 'django/contrib/gis/templates/gis/openlayers.html'
2025-04-22 20:54:05,476 wheel INFO adding 'django/contrib/gis/templates/gis/admin/openlayers.html'
2025-04-22 20:54:05,476 wheel INFO adding 'django/contrib/gis/templates/gis/admin/openlayers.js'
2025-04-22 20:54:05,477 wheel INFO adding 'django/contrib/gis/templates/gis/admin/osm.html'
2025-04-22 20:54:05,477 wheel INFO adding 'django/contrib/gis/templates/gis/admin/osm.js'
2025-04-22 20:54:05,477 wheel INFO adding 'django/contrib/gis/templates/gis/kml/base.kml'
2025-04-22 20:54:05,477 wheel INFO adding 'django/contrib/gis/templates/gis/kml/placemarks.kml'
2025-04-22 20:54:05,477 wheel INFO adding 'django/contrib/gis/utils/__init__.py'
2025-04-22 20:54:05,477 wheel INFO adding 'django/contrib/gis/utils/layermapping.py'
2025-04-22 20:54:05,478 wheel INFO adding 'django/contrib/gis/utils/ogrinfo.py'
2025-04-22 20:54:05,478 wheel INFO adding 'django/contrib/gis/utils/ogrinspect.py'
2025-04-22 20:54:05,478 wheel INFO adding 'django/contrib/gis/utils/srs.py'
2025-04-22 20:54:05,478 wheel INFO adding 'django/contrib/humanize/__init__.py'
2025-04-22 20:54:05,478 wheel INFO adding 'django/contrib/humanize/apps.py'
2025-04-22 20:54:05,479 wheel INFO adding 'django/contrib/humanize/locale/af/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,479 wheel INFO adding 'django/contrib/humanize/locale/af/LC_MESSAGES/django.po'
2025-04-22 20:54:05,479 wheel INFO adding 'django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,479 wheel INFO adding 'django/contrib/humanize/locale/ar/LC_MESSAGES/django.po'
2025-04-22 20:54:05,479 wheel INFO adding 'django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,480 wheel INFO adding 'django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 20:54:05,480 wheel INFO adding 'django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,480 wheel INFO adding 'django/contrib/humanize/locale/ast/LC_MESSAGES/django.po'
2025-04-22 20:54:05,480 wheel INFO adding 'django/contrib/humanize/locale/az/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,480 wheel INFO adding 'django/contrib/humanize/locale/az/LC_MESSAGES/django.po'
2025-04-22 20:54:05,481 wheel INFO adding 'django/contrib/humanize/locale/be/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,481 wheel INFO adding 'django/contrib/humanize/locale/be/LC_MESSAGES/django.po'
2025-04-22 20:54:05,481 wheel INFO adding 'django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,481 wheel INFO adding 'django/contrib/humanize/locale/bg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,481 wheel INFO adding 'django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,481 wheel INFO adding 'django/contrib/humanize/locale/bn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,482 wheel INFO adding 'django/contrib/humanize/locale/br/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,482 wheel INFO adding 'django/contrib/humanize/locale/br/LC_MESSAGES/django.po'
2025-04-22 20:54:05,482 wheel INFO adding 'django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,482 wheel INFO adding 'django/contrib/humanize/locale/bs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,482 wheel INFO adding 'django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,483 wheel INFO adding 'django/contrib/humanize/locale/ca/LC_MESSAGES/django.po'
2025-04-22 20:54:05,483 wheel INFO adding 'django/contrib/humanize/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,483 wheel INFO adding 'django/contrib/humanize/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,483 wheel INFO adding 'django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,483 wheel INFO adding 'django/contrib/humanize/locale/cs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,483 wheel INFO adding 'django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,484 wheel INFO adding 'django/contrib/humanize/locale/cy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,484 wheel INFO adding 'django/contrib/humanize/locale/da/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,484 wheel INFO adding 'django/contrib/humanize/locale/da/LC_MESSAGES/django.po'
2025-04-22 20:54:05,484 wheel INFO adding 'django/contrib/humanize/locale/de/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,484 wheel INFO adding 'django/contrib/humanize/locale/de/LC_MESSAGES/django.po'
2025-04-22 20:54:05,484 wheel INFO adding 'django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,485 wheel INFO adding 'django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,485 wheel INFO adding 'django/contrib/humanize/locale/el/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,485 wheel INFO adding 'django/contrib/humanize/locale/el/LC_MESSAGES/django.po'
2025-04-22 20:54:05,485 wheel INFO adding 'django/contrib/humanize/locale/en/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,485 wheel INFO adding 'django/contrib/humanize/locale/en/LC_MESSAGES/django.po'
2025-04-22 20:54:05,486 wheel INFO adding 'django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,486 wheel INFO adding 'django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 20:54:05,486 wheel INFO adding 'django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,486 wheel INFO adding 'django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 20:54:05,486 wheel INFO adding 'django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,486 wheel INFO adding 'django/contrib/humanize/locale/eo/LC_MESSAGES/django.po'
2025-04-22 20:54:05,487 wheel INFO adding 'django/contrib/humanize/locale/es/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,487 wheel INFO adding 'django/contrib/humanize/locale/es/LC_MESSAGES/django.po'
2025-04-22 20:54:05,487 wheel INFO adding 'django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,487 wheel INFO adding 'django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,487 wheel INFO adding 'django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,487 wheel INFO adding 'django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 20:54:05,487 wheel INFO adding 'django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,488 wheel INFO adding 'django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 20:54:05,488 wheel INFO adding 'django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,488 wheel INFO adding 'django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 20:54:05,488 wheel INFO adding 'django/contrib/humanize/locale/et/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,488 wheel INFO adding 'django/contrib/humanize/locale/et/LC_MESSAGES/django.po'
2025-04-22 20:54:05,488 wheel INFO adding 'django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,489 wheel INFO adding 'django/contrib/humanize/locale/eu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,489 wheel INFO adding 'django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,489 wheel INFO adding 'django/contrib/humanize/locale/fa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,489 wheel INFO adding 'django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,489 wheel INFO adding 'django/contrib/humanize/locale/fi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,489 wheel INFO adding 'django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,490 wheel INFO adding 'django/contrib/humanize/locale/fr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,490 wheel INFO adding 'django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,490 wheel INFO adding 'django/contrib/humanize/locale/fy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,490 wheel INFO adding 'django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,490 wheel INFO adding 'django/contrib/humanize/locale/ga/LC_MESSAGES/django.po'
2025-04-22 20:54:05,490 wheel INFO adding 'django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,491 wheel INFO adding 'django/contrib/humanize/locale/gd/LC_MESSAGES/django.po'
2025-04-22 20:54:05,491 wheel INFO adding 'django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,491 wheel INFO adding 'django/contrib/humanize/locale/gl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,491 wheel INFO adding 'django/contrib/humanize/locale/he/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,491 wheel INFO adding 'django/contrib/humanize/locale/he/LC_MESSAGES/django.po'
2025-04-22 20:54:05,492 wheel INFO adding 'django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,492 wheel INFO adding 'django/contrib/humanize/locale/hi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,492 wheel INFO adding 'django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,492 wheel INFO adding 'django/contrib/humanize/locale/hr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,492 wheel INFO adding 'django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,492 wheel INFO adding 'django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,493 wheel INFO adding 'django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,493 wheel INFO adding 'django/contrib/humanize/locale/hu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,493 wheel INFO adding 'django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,493 wheel INFO adding 'django/contrib/humanize/locale/hy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,493 wheel INFO adding 'django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,493 wheel INFO adding 'django/contrib/humanize/locale/ia/LC_MESSAGES/django.po'
2025-04-22 20:54:05,494 wheel INFO adding 'django/contrib/humanize/locale/id/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,494 wheel INFO adding 'django/contrib/humanize/locale/id/LC_MESSAGES/django.po'
2025-04-22 20:54:05,494 wheel INFO adding 'django/contrib/humanize/locale/io/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,494 wheel INFO adding 'django/contrib/humanize/locale/io/LC_MESSAGES/django.po'
2025-04-22 20:54:05,494 wheel INFO adding 'django/contrib/humanize/locale/is/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,494 wheel INFO adding 'django/contrib/humanize/locale/is/LC_MESSAGES/django.po'
2025-04-22 20:54:05,495 wheel INFO adding 'django/contrib/humanize/locale/it/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,495 wheel INFO adding 'django/contrib/humanize/locale/it/LC_MESSAGES/django.po'
2025-04-22 20:54:05,495 wheel INFO adding 'django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,495 wheel INFO adding 'django/contrib/humanize/locale/ja/LC_MESSAGES/django.po'
2025-04-22 20:54:05,495 wheel INFO adding 'django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,496 wheel INFO adding 'django/contrib/humanize/locale/ka/LC_MESSAGES/django.po'
2025-04-22 20:54:05,496 wheel INFO adding 'django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,496 wheel INFO adding 'django/contrib/humanize/locale/kk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,496 wheel INFO adding 'django/contrib/humanize/locale/km/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,496 wheel INFO adding 'django/contrib/humanize/locale/km/LC_MESSAGES/django.po'
2025-04-22 20:54:05,496 wheel INFO adding 'django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,496 wheel INFO adding 'django/contrib/humanize/locale/kn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,497 wheel INFO adding 'django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,497 wheel INFO adding 'django/contrib/humanize/locale/ko/LC_MESSAGES/django.po'
2025-04-22 20:54:05,497 wheel INFO adding 'django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,497 wheel INFO adding 'django/contrib/humanize/locale/ky/LC_MESSAGES/django.po'
2025-04-22 20:54:05,497 wheel INFO adding 'django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,497 wheel INFO adding 'django/contrib/humanize/locale/lb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,498 wheel INFO adding 'django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,498 wheel INFO adding 'django/contrib/humanize/locale/lt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,498 wheel INFO adding 'django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,498 wheel INFO adding 'django/contrib/humanize/locale/lv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,498 wheel INFO adding 'django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,499 wheel INFO adding 'django/contrib/humanize/locale/mk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,499 wheel INFO adding 'django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,499 wheel INFO adding 'django/contrib/humanize/locale/ml/LC_MESSAGES/django.po'
2025-04-22 20:54:05,499 wheel INFO adding 'django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,499 wheel INFO adding 'django/contrib/humanize/locale/mn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,499 wheel INFO adding 'django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,500 wheel INFO adding 'django/contrib/humanize/locale/mr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,500 wheel INFO adding 'django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,500 wheel INFO adding 'django/contrib/humanize/locale/ms/LC_MESSAGES/django.po'
2025-04-22 20:54:05,500 wheel INFO adding 'django/contrib/humanize/locale/my/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,500 wheel INFO adding 'django/contrib/humanize/locale/my/LC_MESSAGES/django.po'
2025-04-22 20:54:05,500 wheel INFO adding 'django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,501 wheel INFO adding 'django/contrib/humanize/locale/nb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,501 wheel INFO adding 'django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,501 wheel INFO adding 'django/contrib/humanize/locale/ne/LC_MESSAGES/django.po'
2025-04-22 20:54:05,501 wheel INFO adding 'django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,501 wheel INFO adding 'django/contrib/humanize/locale/nl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,501 wheel INFO adding 'django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,502 wheel INFO adding 'django/contrib/humanize/locale/nn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,502 wheel INFO adding 'django/contrib/humanize/locale/os/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,502 wheel INFO adding 'django/contrib/humanize/locale/os/LC_MESSAGES/django.po'
2025-04-22 20:54:05,502 wheel INFO adding 'django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,502 wheel INFO adding 'django/contrib/humanize/locale/pa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,503 wheel INFO adding 'django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,503 wheel INFO adding 'django/contrib/humanize/locale/pl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,503 wheel INFO adding 'django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,503 wheel INFO adding 'django/contrib/humanize/locale/pt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,503 wheel INFO adding 'django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,503 wheel INFO adding 'django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,504 wheel INFO adding 'django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,504 wheel INFO adding 'django/contrib/humanize/locale/ro/LC_MESSAGES/django.po'
2025-04-22 20:54:05,504 wheel INFO adding 'django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,504 wheel INFO adding 'django/contrib/humanize/locale/ru/LC_MESSAGES/django.po'
2025-04-22 20:54:05,504 wheel INFO adding 'django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,505 wheel INFO adding 'django/contrib/humanize/locale/sk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,505 wheel INFO adding 'django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,505 wheel INFO adding 'django/contrib/humanize/locale/sl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,505 wheel INFO adding 'django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,505 wheel INFO adding 'django/contrib/humanize/locale/sq/LC_MESSAGES/django.po'
2025-04-22 20:54:05,506 wheel INFO adding 'django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,506 wheel INFO adding 'django/contrib/humanize/locale/sr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,506 wheel INFO adding 'django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,506 wheel INFO adding 'django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,506 wheel INFO adding 'django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,506 wheel INFO adding 'django/contrib/humanize/locale/sv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,506 wheel INFO adding 'django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,507 wheel INFO adding 'django/contrib/humanize/locale/sw/LC_MESSAGES/django.po'
2025-04-22 20:54:05,507 wheel INFO adding 'django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,507 wheel INFO adding 'django/contrib/humanize/locale/ta/LC_MESSAGES/django.po'
2025-04-22 20:54:05,507 wheel INFO adding 'django/contrib/humanize/locale/te/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,507 wheel INFO adding 'django/contrib/humanize/locale/te/LC_MESSAGES/django.po'
2025-04-22 20:54:05,507 wheel INFO adding 'django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,508 wheel INFO adding 'django/contrib/humanize/locale/tg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,508 wheel INFO adding 'django/contrib/humanize/locale/th/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,508 wheel INFO adding 'django/contrib/humanize/locale/th/LC_MESSAGES/django.po'
2025-04-22 20:54:05,508 wheel INFO adding 'django/contrib/humanize/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,508 wheel INFO adding 'django/contrib/humanize/locale/tk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,508 wheel INFO adding 'django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,509 wheel INFO adding 'django/contrib/humanize/locale/tr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,509 wheel INFO adding 'django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,509 wheel INFO adding 'django/contrib/humanize/locale/tt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,509 wheel INFO adding 'django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,509 wheel INFO adding 'django/contrib/humanize/locale/udm/LC_MESSAGES/django.po'
2025-04-22 20:54:05,509 wheel INFO adding 'django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,510 wheel INFO adding 'django/contrib/humanize/locale/uk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,510 wheel INFO adding 'django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,510 wheel INFO adding 'django/contrib/humanize/locale/ur/LC_MESSAGES/django.po'
2025-04-22 20:54:05,510 wheel INFO adding 'django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,510 wheel INFO adding 'django/contrib/humanize/locale/uz/LC_MESSAGES/django.po'
2025-04-22 20:54:05,510 wheel INFO adding 'django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,511 wheel INFO adding 'django/contrib/humanize/locale/vi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,511 wheel INFO adding 'django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,511 wheel INFO adding 'django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 20:54:05,511 wheel INFO adding 'django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,511 wheel INFO adding 'django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 20:54:05,511 wheel INFO adding 'django/contrib/humanize/templatetags/__init__.py'
2025-04-22 20:54:05,511 wheel INFO adding 'django/contrib/humanize/templatetags/humanize.py'
2025-04-22 20:54:05,512 wheel INFO adding 'django/contrib/messages/__init__.py'
2025-04-22 20:54:05,512 wheel INFO adding 'django/contrib/messages/api.py'
2025-04-22 20:54:05,512 wheel INFO adding 'django/contrib/messages/apps.py'
2025-04-22 20:54:05,512 wheel INFO adding 'django/contrib/messages/constants.py'
2025-04-22 20:54:05,512 wheel INFO adding 'django/contrib/messages/context_processors.py'
2025-04-22 20:54:05,512 wheel INFO adding 'django/contrib/messages/middleware.py'
2025-04-22 20:54:05,512 wheel INFO adding 'django/contrib/messages/utils.py'
2025-04-22 20:54:05,512 wheel INFO adding 'django/contrib/messages/views.py'
2025-04-22 20:54:05,513 wheel INFO adding 'django/contrib/messages/storage/__init__.py'
2025-04-22 20:54:05,513 wheel INFO adding 'django/contrib/messages/storage/base.py'
2025-04-22 20:54:05,513 wheel INFO adding 'django/contrib/messages/storage/cookie.py'
2025-04-22 20:54:05,513 wheel INFO adding 'django/contrib/messages/storage/fallback.py'
2025-04-22 20:54:05,513 wheel INFO adding 'django/contrib/messages/storage/session.py'
2025-04-22 20:54:05,513 wheel INFO adding 'django/contrib/postgres/__init__.py'
2025-04-22 20:54:05,513 wheel INFO adding 'django/contrib/postgres/apps.py'
2025-04-22 20:54:05,514 wheel INFO adding 'django/contrib/postgres/constraints.py'
2025-04-22 20:54:05,514 wheel INFO adding 'django/contrib/postgres/expressions.py'
2025-04-22 20:54:05,514 wheel INFO adding 'django/contrib/postgres/functions.py'
2025-04-22 20:54:05,514 wheel INFO adding 'django/contrib/postgres/indexes.py'
2025-04-22 20:54:05,514 wheel INFO adding 'django/contrib/postgres/lookups.py'
2025-04-22 20:54:05,514 wheel INFO adding 'django/contrib/postgres/operations.py'
2025-04-22 20:54:05,514 wheel INFO adding 'django/contrib/postgres/search.py'
2025-04-22 20:54:05,515 wheel INFO adding 'django/contrib/postgres/serializers.py'
2025-04-22 20:54:05,515 wheel INFO adding 'django/contrib/postgres/signals.py'
2025-04-22 20:54:05,515 wheel INFO adding 'django/contrib/postgres/utils.py'
2025-04-22 20:54:05,515 wheel INFO adding 'django/contrib/postgres/validators.py'
2025-04-22 20:54:05,515 wheel INFO adding 'django/contrib/postgres/aggregates/__init__.py'
2025-04-22 20:54:05,515 wheel INFO adding 'django/contrib/postgres/aggregates/general.py'
2025-04-22 20:54:05,515 wheel INFO adding 'django/contrib/postgres/aggregates/mixins.py'
2025-04-22 20:54:05,516 wheel INFO adding 'django/contrib/postgres/aggregates/statistics.py'
2025-04-22 20:54:05,516 wheel INFO adding 'django/contrib/postgres/fields/__init__.py'
2025-04-22 20:54:05,516 wheel INFO adding 'django/contrib/postgres/fields/array.py'
2025-04-22 20:54:05,516 wheel INFO adding 'django/contrib/postgres/fields/citext.py'
2025-04-22 20:54:05,516 wheel INFO adding 'django/contrib/postgres/fields/hstore.py'
2025-04-22 20:54:05,516 wheel INFO adding 'django/contrib/postgres/fields/jsonb.py'
2025-04-22 20:54:05,516 wheel INFO adding 'django/contrib/postgres/fields/ranges.py'
2025-04-22 20:54:05,517 wheel INFO adding 'django/contrib/postgres/fields/utils.py'
2025-04-22 20:54:05,517 wheel INFO adding 'django/contrib/postgres/forms/__init__.py'
2025-04-22 20:54:05,517 wheel INFO adding 'django/contrib/postgres/forms/array.py'
2025-04-22 20:54:05,517 wheel INFO adding 'django/contrib/postgres/forms/hstore.py'
2025-04-22 20:54:05,517 wheel INFO adding 'django/contrib/postgres/forms/ranges.py'
2025-04-22 20:54:05,517 wheel INFO adding 'django/contrib/postgres/jinja2/postgres/widgets/split_array.html'
2025-04-22 20:54:05,518 wheel INFO adding 'django/contrib/postgres/locale/af/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,518 wheel INFO adding 'django/contrib/postgres/locale/af/LC_MESSAGES/django.po'
2025-04-22 20:54:05,518 wheel INFO adding 'django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,518 wheel INFO adding 'django/contrib/postgres/locale/ar/LC_MESSAGES/django.po'
2025-04-22 20:54:05,519 wheel INFO adding 'django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,519 wheel INFO adding 'django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 20:54:05,519 wheel INFO adding 'django/contrib/postgres/locale/az/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,519 wheel INFO adding 'django/contrib/postgres/locale/az/LC_MESSAGES/django.po'
2025-04-22 20:54:05,519 wheel INFO adding 'django/contrib/postgres/locale/be/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,519 wheel INFO adding 'django/contrib/postgres/locale/be/LC_MESSAGES/django.po'
2025-04-22 20:54:05,519 wheel INFO adding 'django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,520 wheel INFO adding 'django/contrib/postgres/locale/bg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,520 wheel INFO adding 'django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,520 wheel INFO adding 'django/contrib/postgres/locale/ca/LC_MESSAGES/django.po'
2025-04-22 20:54:05,520 wheel INFO adding 'django/contrib/postgres/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,520 wheel INFO adding 'django/contrib/postgres/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,520 wheel INFO adding 'django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,521 wheel INFO adding 'django/contrib/postgres/locale/cs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,521 wheel INFO adding 'django/contrib/postgres/locale/da/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,521 wheel INFO adding 'django/contrib/postgres/locale/da/LC_MESSAGES/django.po'
2025-04-22 20:54:05,521 wheel INFO adding 'django/contrib/postgres/locale/de/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,521 wheel INFO adding 'django/contrib/postgres/locale/de/LC_MESSAGES/django.po'
2025-04-22 20:54:05,521 wheel INFO adding 'django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,521 wheel INFO adding 'django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,522 wheel INFO adding 'django/contrib/postgres/locale/el/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,522 wheel INFO adding 'django/contrib/postgres/locale/el/LC_MESSAGES/django.po'
2025-04-22 20:54:05,522 wheel INFO adding 'django/contrib/postgres/locale/en/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,522 wheel INFO adding 'django/contrib/postgres/locale/en/LC_MESSAGES/django.po'
2025-04-22 20:54:05,522 wheel INFO adding 'django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,522 wheel INFO adding 'django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 20:54:05,523 wheel INFO adding 'django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,523 wheel INFO adding 'django/contrib/postgres/locale/eo/LC_MESSAGES/django.po'
2025-04-22 20:54:05,523 wheel INFO adding 'django/contrib/postgres/locale/es/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,523 wheel INFO adding 'django/contrib/postgres/locale/es/LC_MESSAGES/django.po'
2025-04-22 20:54:05,523 wheel INFO adding 'django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,523 wheel INFO adding 'django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,523 wheel INFO adding 'django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,524 wheel INFO adding 'django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 20:54:05,524 wheel INFO adding 'django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,524 wheel INFO adding 'django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 20:54:05,524 wheel INFO adding 'django/contrib/postgres/locale/et/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,524 wheel INFO adding 'django/contrib/postgres/locale/et/LC_MESSAGES/django.po'
2025-04-22 20:54:05,524 wheel INFO adding 'django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,524 wheel INFO adding 'django/contrib/postgres/locale/eu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,525 wheel INFO adding 'django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,525 wheel INFO adding 'django/contrib/postgres/locale/fa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,525 wheel INFO adding 'django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,525 wheel INFO adding 'django/contrib/postgres/locale/fi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,525 wheel INFO adding 'django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,525 wheel INFO adding 'django/contrib/postgres/locale/fr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,526 wheel INFO adding 'django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,526 wheel INFO adding 'django/contrib/postgres/locale/gd/LC_MESSAGES/django.po'
2025-04-22 20:54:05,526 wheel INFO adding 'django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,526 wheel INFO adding 'django/contrib/postgres/locale/gl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,526 wheel INFO adding 'django/contrib/postgres/locale/he/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,526 wheel INFO adding 'django/contrib/postgres/locale/he/LC_MESSAGES/django.po'
2025-04-22 20:54:05,526 wheel INFO adding 'django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,527 wheel INFO adding 'django/contrib/postgres/locale/hr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,527 wheel INFO adding 'django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,527 wheel INFO adding 'django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,527 wheel INFO adding 'django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,527 wheel INFO adding 'django/contrib/postgres/locale/hu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,527 wheel INFO adding 'django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,528 wheel INFO adding 'django/contrib/postgres/locale/hy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,528 wheel INFO adding 'django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,528 wheel INFO adding 'django/contrib/postgres/locale/ia/LC_MESSAGES/django.po'
2025-04-22 20:54:05,528 wheel INFO adding 'django/contrib/postgres/locale/id/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,528 wheel INFO adding 'django/contrib/postgres/locale/id/LC_MESSAGES/django.po'
2025-04-22 20:54:05,528 wheel INFO adding 'django/contrib/postgres/locale/is/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,529 wheel INFO adding 'django/contrib/postgres/locale/is/LC_MESSAGES/django.po'
2025-04-22 20:54:05,529 wheel INFO adding 'django/contrib/postgres/locale/it/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,529 wheel INFO adding 'django/contrib/postgres/locale/it/LC_MESSAGES/django.po'
2025-04-22 20:54:05,529 wheel INFO adding 'django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,529 wheel INFO adding 'django/contrib/postgres/locale/ja/LC_MESSAGES/django.po'
2025-04-22 20:54:05,529 wheel INFO adding 'django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,530 wheel INFO adding 'django/contrib/postgres/locale/ka/LC_MESSAGES/django.po'
2025-04-22 20:54:05,530 wheel INFO adding 'django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,530 wheel INFO adding 'django/contrib/postgres/locale/kk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,530 wheel INFO adding 'django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,530 wheel INFO adding 'django/contrib/postgres/locale/ko/LC_MESSAGES/django.po'
2025-04-22 20:54:05,530 wheel INFO adding 'django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,530 wheel INFO adding 'django/contrib/postgres/locale/ky/LC_MESSAGES/django.po'
2025-04-22 20:54:05,531 wheel INFO adding 'django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,531 wheel INFO adding 'django/contrib/postgres/locale/lt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,531 wheel INFO adding 'django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,531 wheel INFO adding 'django/contrib/postgres/locale/lv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,531 wheel INFO adding 'django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,531 wheel INFO adding 'django/contrib/postgres/locale/mk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,531 wheel INFO adding 'django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,532 wheel INFO adding 'django/contrib/postgres/locale/ml/LC_MESSAGES/django.po'
2025-04-22 20:54:05,532 wheel INFO adding 'django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,532 wheel INFO adding 'django/contrib/postgres/locale/mn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,532 wheel INFO adding 'django/contrib/postgres/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,532 wheel INFO adding 'django/contrib/postgres/locale/ms/LC_MESSAGES/django.po'
2025-04-22 20:54:05,532 wheel INFO adding 'django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,533 wheel INFO adding 'django/contrib/postgres/locale/nb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,533 wheel INFO adding 'django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,533 wheel INFO adding 'django/contrib/postgres/locale/ne/LC_MESSAGES/django.po'
2025-04-22 20:54:05,533 wheel INFO adding 'django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,533 wheel INFO adding 'django/contrib/postgres/locale/nl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,533 wheel INFO adding 'django/contrib/postgres/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,533 wheel INFO adding 'django/contrib/postgres/locale/nn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,534 wheel INFO adding 'django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,534 wheel INFO adding 'django/contrib/postgres/locale/pl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,534 wheel INFO adding 'django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,534 wheel INFO adding 'django/contrib/postgres/locale/pt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,534 wheel INFO adding 'django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,534 wheel INFO adding 'django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,535 wheel INFO adding 'django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,535 wheel INFO adding 'django/contrib/postgres/locale/ro/LC_MESSAGES/django.po'
2025-04-22 20:54:05,535 wheel INFO adding 'django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,535 wheel INFO adding 'django/contrib/postgres/locale/ru/LC_MESSAGES/django.po'
2025-04-22 20:54:05,535 wheel INFO adding 'django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,535 wheel INFO adding 'django/contrib/postgres/locale/sk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,535 wheel INFO adding 'django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,536 wheel INFO adding 'django/contrib/postgres/locale/sl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,536 wheel INFO adding 'django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,536 wheel INFO adding 'django/contrib/postgres/locale/sq/LC_MESSAGES/django.po'
2025-04-22 20:54:05,536 wheel INFO adding 'django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,536 wheel INFO adding 'django/contrib/postgres/locale/sr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,536 wheel INFO adding 'django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,537 wheel INFO adding 'django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,537 wheel INFO adding 'django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,537 wheel INFO adding 'django/contrib/postgres/locale/sv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,537 wheel INFO adding 'django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,537 wheel INFO adding 'django/contrib/postgres/locale/tg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,537 wheel INFO adding 'django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,537 wheel INFO adding 'django/contrib/postgres/locale/tk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,538 wheel INFO adding 'django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,540 wheel INFO adding 'django/contrib/postgres/locale/tr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,540 wheel INFO adding 'django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,540 wheel INFO adding 'django/contrib/postgres/locale/uk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,540 wheel INFO adding 'django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,540 wheel INFO adding 'django/contrib/postgres/locale/uz/LC_MESSAGES/django.po'
2025-04-22 20:54:05,541 wheel INFO adding 'django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,541 wheel INFO adding 'django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 20:54:05,541 wheel INFO adding 'django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,541 wheel INFO adding 'django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 20:54:05,541 wheel INFO adding 'django/contrib/postgres/templates/postgres/widgets/split_array.html'
2025-04-22 20:54:05,541 wheel INFO adding 'django/contrib/redirects/__init__.py'
2025-04-22 20:54:05,541 wheel INFO adding 'django/contrib/redirects/admin.py'
2025-04-22 20:54:05,542 wheel INFO adding 'django/contrib/redirects/apps.py'
2025-04-22 20:54:05,542 wheel INFO adding 'django/contrib/redirects/middleware.py'
2025-04-22 20:54:05,542 wheel INFO adding 'django/contrib/redirects/models.py'
2025-04-22 20:54:05,543 wheel INFO adding 'django/contrib/redirects/locale/af/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,543 wheel INFO adding 'django/contrib/redirects/locale/af/LC_MESSAGES/django.po'
2025-04-22 20:54:05,543 wheel INFO adding 'django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,543 wheel INFO adding 'django/contrib/redirects/locale/ar/LC_MESSAGES/django.po'
2025-04-22 20:54:05,543 wheel INFO adding 'django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,543 wheel INFO adding 'django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 20:54:05,543 wheel INFO adding 'django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,544 wheel INFO adding 'django/contrib/redirects/locale/ast/LC_MESSAGES/django.po'
2025-04-22 20:54:05,544 wheel INFO adding 'django/contrib/redirects/locale/az/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,544 wheel INFO adding 'django/contrib/redirects/locale/az/LC_MESSAGES/django.po'
2025-04-22 20:54:05,544 wheel INFO adding 'django/contrib/redirects/locale/be/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,544 wheel INFO adding 'django/contrib/redirects/locale/be/LC_MESSAGES/django.po'
2025-04-22 20:54:05,544 wheel INFO adding 'django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,545 wheel INFO adding 'django/contrib/redirects/locale/bg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,545 wheel INFO adding 'django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,545 wheel INFO adding 'django/contrib/redirects/locale/bn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,545 wheel INFO adding 'django/contrib/redirects/locale/br/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,545 wheel INFO adding 'django/contrib/redirects/locale/br/LC_MESSAGES/django.po'
2025-04-22 20:54:05,545 wheel INFO adding 'django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,545 wheel INFO adding 'django/contrib/redirects/locale/bs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,546 wheel INFO adding 'django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,546 wheel INFO adding 'django/contrib/redirects/locale/ca/LC_MESSAGES/django.po'
2025-04-22 20:54:05,546 wheel INFO adding 'django/contrib/redirects/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,546 wheel INFO adding 'django/contrib/redirects/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,546 wheel INFO adding 'django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,546 wheel INFO adding 'django/contrib/redirects/locale/cs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,546 wheel INFO adding 'django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,547 wheel INFO adding 'django/contrib/redirects/locale/cy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,547 wheel INFO adding 'django/contrib/redirects/locale/da/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,547 wheel INFO adding 'django/contrib/redirects/locale/da/LC_MESSAGES/django.po'
2025-04-22 20:54:05,547 wheel INFO adding 'django/contrib/redirects/locale/de/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,547 wheel INFO adding 'django/contrib/redirects/locale/de/LC_MESSAGES/django.po'
2025-04-22 20:54:05,547 wheel INFO adding 'django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,547 wheel INFO adding 'django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,548 wheel INFO adding 'django/contrib/redirects/locale/el/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,548 wheel INFO adding 'django/contrib/redirects/locale/el/LC_MESSAGES/django.po'
2025-04-22 20:54:05,548 wheel INFO adding 'django/contrib/redirects/locale/en/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,548 wheel INFO adding 'django/contrib/redirects/locale/en/LC_MESSAGES/django.po'
2025-04-22 20:54:05,548 wheel INFO adding 'django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,548 wheel INFO adding 'django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 20:54:05,549 wheel INFO adding 'django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,549 wheel INFO adding 'django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 20:54:05,549 wheel INFO adding 'django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,549 wheel INFO adding 'django/contrib/redirects/locale/eo/LC_MESSAGES/django.po'
2025-04-22 20:54:05,549 wheel INFO adding 'django/contrib/redirects/locale/es/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,549 wheel INFO adding 'django/contrib/redirects/locale/es/LC_MESSAGES/django.po'
2025-04-22 20:54:05,549 wheel INFO adding 'django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,550 wheel INFO adding 'django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,550 wheel INFO adding 'django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,550 wheel INFO adding 'django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 20:54:05,550 wheel INFO adding 'django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,550 wheel INFO adding 'django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 20:54:05,550 wheel INFO adding 'django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,550 wheel INFO adding 'django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 20:54:05,551 wheel INFO adding 'django/contrib/redirects/locale/et/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,551 wheel INFO adding 'django/contrib/redirects/locale/et/LC_MESSAGES/django.po'
2025-04-22 20:54:05,551 wheel INFO adding 'django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,551 wheel INFO adding 'django/contrib/redirects/locale/eu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,551 wheel INFO adding 'django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,551 wheel INFO adding 'django/contrib/redirects/locale/fa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,551 wheel INFO adding 'django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,552 wheel INFO adding 'django/contrib/redirects/locale/fi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,552 wheel INFO adding 'django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,552 wheel INFO adding 'django/contrib/redirects/locale/fr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,552 wheel INFO adding 'django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,552 wheel INFO adding 'django/contrib/redirects/locale/fy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,552 wheel INFO adding 'django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,552 wheel INFO adding 'django/contrib/redirects/locale/ga/LC_MESSAGES/django.po'
2025-04-22 20:54:05,553 wheel INFO adding 'django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,553 wheel INFO adding 'django/contrib/redirects/locale/gd/LC_MESSAGES/django.po'
2025-04-22 20:54:05,553 wheel INFO adding 'django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,553 wheel INFO adding 'django/contrib/redirects/locale/gl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,553 wheel INFO adding 'django/contrib/redirects/locale/he/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,553 wheel INFO adding 'django/contrib/redirects/locale/he/LC_MESSAGES/django.po'
2025-04-22 20:54:05,553 wheel INFO adding 'django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,554 wheel INFO adding 'django/contrib/redirects/locale/hi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,554 wheel INFO adding 'django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,554 wheel INFO adding 'django/contrib/redirects/locale/hr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,554 wheel INFO adding 'django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,554 wheel INFO adding 'django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,554 wheel INFO adding 'django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,554 wheel INFO adding 'django/contrib/redirects/locale/hu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,555 wheel INFO adding 'django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,555 wheel INFO adding 'django/contrib/redirects/locale/hy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,555 wheel INFO adding 'django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,555 wheel INFO adding 'django/contrib/redirects/locale/ia/LC_MESSAGES/django.po'
2025-04-22 20:54:05,555 wheel INFO adding 'django/contrib/redirects/locale/id/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,555 wheel INFO adding 'django/contrib/redirects/locale/id/LC_MESSAGES/django.po'
2025-04-22 20:54:05,555 wheel INFO adding 'django/contrib/redirects/locale/io/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,556 wheel INFO adding 'django/contrib/redirects/locale/io/LC_MESSAGES/django.po'
2025-04-22 20:54:05,556 wheel INFO adding 'django/contrib/redirects/locale/is/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,556 wheel INFO adding 'django/contrib/redirects/locale/is/LC_MESSAGES/django.po'
2025-04-22 20:54:05,556 wheel INFO adding 'django/contrib/redirects/locale/it/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,556 wheel INFO adding 'django/contrib/redirects/locale/it/LC_MESSAGES/django.po'
2025-04-22 20:54:05,556 wheel INFO adding 'django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,557 wheel INFO adding 'django/contrib/redirects/locale/ja/LC_MESSAGES/django.po'
2025-04-22 20:54:05,557 wheel INFO adding 'django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,557 wheel INFO adding 'django/contrib/redirects/locale/ka/LC_MESSAGES/django.po'
2025-04-22 20:54:05,557 wheel INFO adding 'django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,557 wheel INFO adding 'django/contrib/redirects/locale/kab/LC_MESSAGES/django.po'
2025-04-22 20:54:05,557 wheel INFO adding 'django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,557 wheel INFO adding 'django/contrib/redirects/locale/kk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,558 wheel INFO adding 'django/contrib/redirects/locale/km/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,558 wheel INFO adding 'django/contrib/redirects/locale/km/LC_MESSAGES/django.po'
2025-04-22 20:54:05,558 wheel INFO adding 'django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,558 wheel INFO adding 'django/contrib/redirects/locale/kn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,558 wheel INFO adding 'django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,558 wheel INFO adding 'django/contrib/redirects/locale/ko/LC_MESSAGES/django.po'
2025-04-22 20:54:05,558 wheel INFO adding 'django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,559 wheel INFO adding 'django/contrib/redirects/locale/ky/LC_MESSAGES/django.po'
2025-04-22 20:54:05,559 wheel INFO adding 'django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,559 wheel INFO adding 'django/contrib/redirects/locale/lb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,559 wheel INFO adding 'django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,559 wheel INFO adding 'django/contrib/redirects/locale/lt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,559 wheel INFO adding 'django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,559 wheel INFO adding 'django/contrib/redirects/locale/lv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,560 wheel INFO adding 'django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,560 wheel INFO adding 'django/contrib/redirects/locale/mk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,560 wheel INFO adding 'django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,560 wheel INFO adding 'django/contrib/redirects/locale/ml/LC_MESSAGES/django.po'
2025-04-22 20:54:05,560 wheel INFO adding 'django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,560 wheel INFO adding 'django/contrib/redirects/locale/mn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,560 wheel INFO adding 'django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,561 wheel INFO adding 'django/contrib/redirects/locale/mr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,561 wheel INFO adding 'django/contrib/redirects/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,561 wheel INFO adding 'django/contrib/redirects/locale/ms/LC_MESSAGES/django.po'
2025-04-22 20:54:05,561 wheel INFO adding 'django/contrib/redirects/locale/my/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,561 wheel INFO adding 'django/contrib/redirects/locale/my/LC_MESSAGES/django.po'
2025-04-22 20:54:05,561 wheel INFO adding 'django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,561 wheel INFO adding 'django/contrib/redirects/locale/nb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,562 wheel INFO adding 'django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,562 wheel INFO adding 'django/contrib/redirects/locale/ne/LC_MESSAGES/django.po'
2025-04-22 20:54:05,562 wheel INFO adding 'django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,562 wheel INFO adding 'django/contrib/redirects/locale/nl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,562 wheel INFO adding 'django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,562 wheel INFO adding 'django/contrib/redirects/locale/nn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,563 wheel INFO adding 'django/contrib/redirects/locale/os/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,563 wheel INFO adding 'django/contrib/redirects/locale/os/LC_MESSAGES/django.po'
2025-04-22 20:54:05,563 wheel INFO adding 'django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,563 wheel INFO adding 'django/contrib/redirects/locale/pa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,563 wheel INFO adding 'django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,563 wheel INFO adding 'django/contrib/redirects/locale/pl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,563 wheel INFO adding 'django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,564 wheel INFO adding 'django/contrib/redirects/locale/pt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,564 wheel INFO adding 'django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,564 wheel INFO adding 'django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,564 wheel INFO adding 'django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,564 wheel INFO adding 'django/contrib/redirects/locale/ro/LC_MESSAGES/django.po'
2025-04-22 20:54:05,564 wheel INFO adding 'django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,564 wheel INFO adding 'django/contrib/redirects/locale/ru/LC_MESSAGES/django.po'
2025-04-22 20:54:05,565 wheel INFO adding 'django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,565 wheel INFO adding 'django/contrib/redirects/locale/sk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,565 wheel INFO adding 'django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,565 wheel INFO adding 'django/contrib/redirects/locale/sl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,565 wheel INFO adding 'django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,565 wheel INFO adding 'django/contrib/redirects/locale/sq/LC_MESSAGES/django.po'
2025-04-22 20:54:05,565 wheel INFO adding 'django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,566 wheel INFO adding 'django/contrib/redirects/locale/sr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,566 wheel INFO adding 'django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,566 wheel INFO adding 'django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,566 wheel INFO adding 'django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,566 wheel INFO adding 'django/contrib/redirects/locale/sv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,566 wheel INFO adding 'django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,566 wheel INFO adding 'django/contrib/redirects/locale/sw/LC_MESSAGES/django.po'
2025-04-22 20:54:05,567 wheel INFO adding 'django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,567 wheel INFO adding 'django/contrib/redirects/locale/ta/LC_MESSAGES/django.po'
2025-04-22 20:54:05,567 wheel INFO adding 'django/contrib/redirects/locale/te/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,567 wheel INFO adding 'django/contrib/redirects/locale/te/LC_MESSAGES/django.po'
2025-04-22 20:54:05,567 wheel INFO adding 'django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,567 wheel INFO adding 'django/contrib/redirects/locale/tg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,567 wheel INFO adding 'django/contrib/redirects/locale/th/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,568 wheel INFO adding 'django/contrib/redirects/locale/th/LC_MESSAGES/django.po'
2025-04-22 20:54:05,568 wheel INFO adding 'django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,568 wheel INFO adding 'django/contrib/redirects/locale/tk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,568 wheel INFO adding 'django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,568 wheel INFO adding 'django/contrib/redirects/locale/tr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,568 wheel INFO adding 'django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,569 wheel INFO adding 'django/contrib/redirects/locale/tt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,569 wheel INFO adding 'django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,569 wheel INFO adding 'django/contrib/redirects/locale/udm/LC_MESSAGES/django.po'
2025-04-22 20:54:05,569 wheel INFO adding 'django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,569 wheel INFO adding 'django/contrib/redirects/locale/uk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,569 wheel INFO adding 'django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,569 wheel INFO adding 'django/contrib/redirects/locale/ur/LC_MESSAGES/django.po'
2025-04-22 20:54:05,570 wheel INFO adding 'django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,570 wheel INFO adding 'django/contrib/redirects/locale/uz/LC_MESSAGES/django.po'
2025-04-22 20:54:05,570 wheel INFO adding 'django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,570 wheel INFO adding 'django/contrib/redirects/locale/vi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,570 wheel INFO adding 'django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,570 wheel INFO adding 'django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 20:54:05,570 wheel INFO adding 'django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,570 wheel INFO adding 'django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 20:54:05,571 wheel INFO adding 'django/contrib/redirects/migrations/0001_initial.py'
2025-04-22 20:54:05,571 wheel INFO adding 'django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py'
2025-04-22 20:54:05,571 wheel INFO adding 'django/contrib/redirects/migrations/__init__.py'
2025-04-22 20:54:05,571 wheel INFO adding 'django/contrib/sessions/__init__.py'
2025-04-22 20:54:05,571 wheel INFO adding 'django/contrib/sessions/apps.py'
2025-04-22 20:54:05,571 wheel INFO adding 'django/contrib/sessions/base_session.py'
2025-04-22 20:54:05,571 wheel INFO adding 'django/contrib/sessions/exceptions.py'
2025-04-22 20:54:05,572 wheel INFO adding 'django/contrib/sessions/middleware.py'
2025-04-22 20:54:05,572 wheel INFO adding 'django/contrib/sessions/models.py'
2025-04-22 20:54:05,572 wheel INFO adding 'django/contrib/sessions/serializers.py'
2025-04-22 20:54:05,572 wheel INFO adding 'django/contrib/sessions/backends/__init__.py'
2025-04-22 20:54:05,572 wheel INFO adding 'django/contrib/sessions/backends/base.py'
2025-04-22 20:54:05,572 wheel INFO adding 'django/contrib/sessions/backends/cache.py'
2025-04-22 20:54:05,572 wheel INFO adding 'django/contrib/sessions/backends/cached_db.py'
2025-04-22 20:54:05,573 wheel INFO adding 'django/contrib/sessions/backends/db.py'
2025-04-22 20:54:05,573 wheel INFO adding 'django/contrib/sessions/backends/file.py'
2025-04-22 20:54:05,573 wheel INFO adding 'django/contrib/sessions/backends/signed_cookies.py'
2025-04-22 20:54:05,574 wheel INFO adding 'django/contrib/sessions/locale/af/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,574 wheel INFO adding 'django/contrib/sessions/locale/af/LC_MESSAGES/django.po'
2025-04-22 20:54:05,574 wheel INFO adding 'django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,574 wheel INFO adding 'django/contrib/sessions/locale/ar/LC_MESSAGES/django.po'
2025-04-22 20:54:05,574 wheel INFO adding 'django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,574 wheel INFO adding 'django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 20:54:05,575 wheel INFO adding 'django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,575 wheel INFO adding 'django/contrib/sessions/locale/ast/LC_MESSAGES/django.po'
2025-04-22 20:54:05,575 wheel INFO adding 'django/contrib/sessions/locale/az/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,575 wheel INFO adding 'django/contrib/sessions/locale/az/LC_MESSAGES/django.po'
2025-04-22 20:54:05,576 wheel INFO adding 'django/contrib/sessions/locale/be/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,576 wheel INFO adding 'django/contrib/sessions/locale/be/LC_MESSAGES/django.po'
2025-04-22 20:54:05,576 wheel INFO adding 'django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,576 wheel INFO adding 'django/contrib/sessions/locale/bg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,576 wheel INFO adding 'django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,576 wheel INFO adding 'django/contrib/sessions/locale/bn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,576 wheel INFO adding 'django/contrib/sessions/locale/br/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,577 wheel INFO adding 'django/contrib/sessions/locale/br/LC_MESSAGES/django.po'
2025-04-22 20:54:05,577 wheel INFO adding 'django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,577 wheel INFO adding 'django/contrib/sessions/locale/bs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,577 wheel INFO adding 'django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,577 wheel INFO adding 'django/contrib/sessions/locale/ca/LC_MESSAGES/django.po'
2025-04-22 20:54:05,577 wheel INFO adding 'django/contrib/sessions/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,577 wheel INFO adding 'django/contrib/sessions/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,578 wheel INFO adding 'django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,578 wheel INFO adding 'django/contrib/sessions/locale/cs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,578 wheel INFO adding 'django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,578 wheel INFO adding 'django/contrib/sessions/locale/cy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,578 wheel INFO adding 'django/contrib/sessions/locale/da/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,578 wheel INFO adding 'django/contrib/sessions/locale/da/LC_MESSAGES/django.po'
2025-04-22 20:54:05,578 wheel INFO adding 'django/contrib/sessions/locale/de/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,579 wheel INFO adding 'django/contrib/sessions/locale/de/LC_MESSAGES/django.po'
2025-04-22 20:54:05,579 wheel INFO adding 'django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,579 wheel INFO adding 'django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,579 wheel INFO adding 'django/contrib/sessions/locale/el/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,579 wheel INFO adding 'django/contrib/sessions/locale/el/LC_MESSAGES/django.po'
2025-04-22 20:54:05,579 wheel INFO adding 'django/contrib/sessions/locale/en/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,579 wheel INFO adding 'django/contrib/sessions/locale/en/LC_MESSAGES/django.po'
2025-04-22 20:54:05,580 wheel INFO adding 'django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,580 wheel INFO adding 'django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 20:54:05,580 wheel INFO adding 'django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,580 wheel INFO adding 'django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 20:54:05,580 wheel INFO adding 'django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,580 wheel INFO adding 'django/contrib/sessions/locale/eo/LC_MESSAGES/django.po'
2025-04-22 20:54:05,580 wheel INFO adding 'django/contrib/sessions/locale/es/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,581 wheel INFO adding 'django/contrib/sessions/locale/es/LC_MESSAGES/django.po'
2025-04-22 20:54:05,581 wheel INFO adding 'django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,581 wheel INFO adding 'django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,581 wheel INFO adding 'django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,581 wheel INFO adding 'django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 20:54:05,581 wheel INFO adding 'django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,581 wheel INFO adding 'django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 20:54:05,582 wheel INFO adding 'django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,582 wheel INFO adding 'django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 20:54:05,582 wheel INFO adding 'django/contrib/sessions/locale/et/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,582 wheel INFO adding 'django/contrib/sessions/locale/et/LC_MESSAGES/django.po'
2025-04-22 20:54:05,582 wheel INFO adding 'django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,582 wheel INFO adding 'django/contrib/sessions/locale/eu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,583 wheel INFO adding 'django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,583 wheel INFO adding 'django/contrib/sessions/locale/fa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,583 wheel INFO adding 'django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,583 wheel INFO adding 'django/contrib/sessions/locale/fi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,583 wheel INFO adding 'django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,583 wheel INFO adding 'django/contrib/sessions/locale/fr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,583 wheel INFO adding 'django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,584 wheel INFO adding 'django/contrib/sessions/locale/fy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,584 wheel INFO adding 'django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,584 wheel INFO adding 'django/contrib/sessions/locale/ga/LC_MESSAGES/django.po'
2025-04-22 20:54:05,584 wheel INFO adding 'django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,584 wheel INFO adding 'django/contrib/sessions/locale/gd/LC_MESSAGES/django.po'
2025-04-22 20:54:05,584 wheel INFO adding 'django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,584 wheel INFO adding 'django/contrib/sessions/locale/gl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,585 wheel INFO adding 'django/contrib/sessions/locale/he/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,585 wheel INFO adding 'django/contrib/sessions/locale/he/LC_MESSAGES/django.po'
2025-04-22 20:54:05,585 wheel INFO adding 'django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,585 wheel INFO adding 'django/contrib/sessions/locale/hi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,585 wheel INFO adding 'django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,585 wheel INFO adding 'django/contrib/sessions/locale/hr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,585 wheel INFO adding 'django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,586 wheel INFO adding 'django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,586 wheel INFO adding 'django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,586 wheel INFO adding 'django/contrib/sessions/locale/hu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,586 wheel INFO adding 'django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,586 wheel INFO adding 'django/contrib/sessions/locale/hy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,586 wheel INFO adding 'django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,586 wheel INFO adding 'django/contrib/sessions/locale/ia/LC_MESSAGES/django.po'
2025-04-22 20:54:05,586 wheel INFO adding 'django/contrib/sessions/locale/id/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,587 wheel INFO adding 'django/contrib/sessions/locale/id/LC_MESSAGES/django.po'
2025-04-22 20:54:05,587 wheel INFO adding 'django/contrib/sessions/locale/io/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,587 wheel INFO adding 'django/contrib/sessions/locale/io/LC_MESSAGES/django.po'
2025-04-22 20:54:05,587 wheel INFO adding 'django/contrib/sessions/locale/is/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,587 wheel INFO adding 'django/contrib/sessions/locale/is/LC_MESSAGES/django.po'
2025-04-22 20:54:05,587 wheel INFO adding 'django/contrib/sessions/locale/it/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,587 wheel INFO adding 'django/contrib/sessions/locale/it/LC_MESSAGES/django.po'
2025-04-22 20:54:05,588 wheel INFO adding 'django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,588 wheel INFO adding 'django/contrib/sessions/locale/ja/LC_MESSAGES/django.po'
2025-04-22 20:54:05,588 wheel INFO adding 'django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,588 wheel INFO adding 'django/contrib/sessions/locale/ka/LC_MESSAGES/django.po'
2025-04-22 20:54:05,588 wheel INFO adding 'django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,588 wheel INFO adding 'django/contrib/sessions/locale/kab/LC_MESSAGES/django.po'
2025-04-22 20:54:05,588 wheel INFO adding 'django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,589 wheel INFO adding 'django/contrib/sessions/locale/kk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,589 wheel INFO adding 'django/contrib/sessions/locale/km/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,589 wheel INFO adding 'django/contrib/sessions/locale/km/LC_MESSAGES/django.po'
2025-04-22 20:54:05,589 wheel INFO adding 'django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,589 wheel INFO adding 'django/contrib/sessions/locale/kn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,589 wheel INFO adding 'django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,589 wheel INFO adding 'django/contrib/sessions/locale/ko/LC_MESSAGES/django.po'
2025-04-22 20:54:05,590 wheel INFO adding 'django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,590 wheel INFO adding 'django/contrib/sessions/locale/ky/LC_MESSAGES/django.po'
2025-04-22 20:54:05,590 wheel INFO adding 'django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,590 wheel INFO adding 'django/contrib/sessions/locale/lb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,590 wheel INFO adding 'django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,590 wheel INFO adding 'django/contrib/sessions/locale/lt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,590 wheel INFO adding 'django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,591 wheel INFO adding 'django/contrib/sessions/locale/lv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,591 wheel INFO adding 'django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,591 wheel INFO adding 'django/contrib/sessions/locale/mk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,591 wheel INFO adding 'django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,591 wheel INFO adding 'django/contrib/sessions/locale/ml/LC_MESSAGES/django.po'
2025-04-22 20:54:05,591 wheel INFO adding 'django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,591 wheel INFO adding 'django/contrib/sessions/locale/mn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,592 wheel INFO adding 'django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,592 wheel INFO adding 'django/contrib/sessions/locale/mr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,592 wheel INFO adding 'django/contrib/sessions/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,592 wheel INFO adding 'django/contrib/sessions/locale/ms/LC_MESSAGES/django.po'
2025-04-22 20:54:05,592 wheel INFO adding 'django/contrib/sessions/locale/my/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,592 wheel INFO adding 'django/contrib/sessions/locale/my/LC_MESSAGES/django.po'
2025-04-22 20:54:05,592 wheel INFO adding 'django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,593 wheel INFO adding 'django/contrib/sessions/locale/nb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,593 wheel INFO adding 'django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,593 wheel INFO adding 'django/contrib/sessions/locale/ne/LC_MESSAGES/django.po'
2025-04-22 20:54:05,593 wheel INFO adding 'django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,593 wheel INFO adding 'django/contrib/sessions/locale/nl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,593 wheel INFO adding 'django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,593 wheel INFO adding 'django/contrib/sessions/locale/nn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,594 wheel INFO adding 'django/contrib/sessions/locale/os/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,594 wheel INFO adding 'django/contrib/sessions/locale/os/LC_MESSAGES/django.po'
2025-04-22 20:54:05,594 wheel INFO adding 'django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,594 wheel INFO adding 'django/contrib/sessions/locale/pa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,594 wheel INFO adding 'django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,594 wheel INFO adding 'django/contrib/sessions/locale/pl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,594 wheel INFO adding 'django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,594 wheel INFO adding 'django/contrib/sessions/locale/pt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,595 wheel INFO adding 'django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,595 wheel INFO adding 'django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,595 wheel INFO adding 'django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,595 wheel INFO adding 'django/contrib/sessions/locale/ro/LC_MESSAGES/django.po'
2025-04-22 20:54:05,595 wheel INFO adding 'django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,595 wheel INFO adding 'django/contrib/sessions/locale/ru/LC_MESSAGES/django.po'
2025-04-22 20:54:05,596 wheel INFO adding 'django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,596 wheel INFO adding 'django/contrib/sessions/locale/sk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,596 wheel INFO adding 'django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,596 wheel INFO adding 'django/contrib/sessions/locale/sl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,596 wheel INFO adding 'django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,596 wheel INFO adding 'django/contrib/sessions/locale/sq/LC_MESSAGES/django.po'
2025-04-22 20:54:05,596 wheel INFO adding 'django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,596 wheel INFO adding 'django/contrib/sessions/locale/sr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,597 wheel INFO adding 'django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,597 wheel INFO adding 'django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,597 wheel INFO adding 'django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,597 wheel INFO adding 'django/contrib/sessions/locale/sv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,597 wheel INFO adding 'django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,597 wheel INFO adding 'django/contrib/sessions/locale/sw/LC_MESSAGES/django.po'
2025-04-22 20:54:05,598 wheel INFO adding 'django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,598 wheel INFO adding 'django/contrib/sessions/locale/ta/LC_MESSAGES/django.po'
2025-04-22 20:54:05,598 wheel INFO adding 'django/contrib/sessions/locale/te/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,598 wheel INFO adding 'django/contrib/sessions/locale/te/LC_MESSAGES/django.po'
2025-04-22 20:54:05,598 wheel INFO adding 'django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,598 wheel INFO adding 'django/contrib/sessions/locale/tg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,598 wheel INFO adding 'django/contrib/sessions/locale/th/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,599 wheel INFO adding 'django/contrib/sessions/locale/th/LC_MESSAGES/django.po'
2025-04-22 20:54:05,599 wheel INFO adding 'django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,599 wheel INFO adding 'django/contrib/sessions/locale/tk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,599 wheel INFO adding 'django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,599 wheel INFO adding 'django/contrib/sessions/locale/tr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,599 wheel INFO adding 'django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,599 wheel INFO adding 'django/contrib/sessions/locale/tt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,600 wheel INFO adding 'django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,600 wheel INFO adding 'django/contrib/sessions/locale/udm/LC_MESSAGES/django.po'
2025-04-22 20:54:05,600 wheel INFO adding 'django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,600 wheel INFO adding 'django/contrib/sessions/locale/uk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,600 wheel INFO adding 'django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,600 wheel INFO adding 'django/contrib/sessions/locale/ur/LC_MESSAGES/django.po'
2025-04-22 20:54:05,600 wheel INFO adding 'django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,601 wheel INFO adding 'django/contrib/sessions/locale/uz/LC_MESSAGES/django.po'
2025-04-22 20:54:05,601 wheel INFO adding 'django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,601 wheel INFO adding 'django/contrib/sessions/locale/vi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,601 wheel INFO adding 'django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,601 wheel INFO adding 'django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 20:54:05,601 wheel INFO adding 'django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,601 wheel INFO adding 'django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 20:54:05,602 wheel INFO adding 'django/contrib/sessions/management/__init__.py'
2025-04-22 20:54:05,602 wheel INFO adding 'django/contrib/sessions/management/commands/__init__.py'
2025-04-22 20:54:05,602 wheel INFO adding 'django/contrib/sessions/management/commands/clearsessions.py'
2025-04-22 20:54:05,602 wheel INFO adding 'django/contrib/sessions/migrations/0001_initial.py'
2025-04-22 20:54:05,602 wheel INFO adding 'django/contrib/sessions/migrations/__init__.py'
2025-04-22 20:54:05,602 wheel INFO adding 'django/contrib/sitemaps/__init__.py'
2025-04-22 20:54:05,602 wheel INFO adding 'django/contrib/sitemaps/apps.py'
2025-04-22 20:54:05,603 wheel INFO adding 'django/contrib/sitemaps/views.py'
2025-04-22 20:54:05,603 wheel INFO adding 'django/contrib/sitemaps/management/__init__.py'
2025-04-22 20:54:05,603 wheel INFO adding 'django/contrib/sitemaps/management/commands/__init__.py'
2025-04-22 20:54:05,603 wheel INFO adding 'django/contrib/sitemaps/management/commands/ping_google.py'
2025-04-22 20:54:05,603 wheel INFO adding 'django/contrib/sitemaps/templates/sitemap.xml'
2025-04-22 20:54:05,603 wheel INFO adding 'django/contrib/sitemaps/templates/sitemap_index.xml'
2025-04-22 20:54:05,603 wheel INFO adding 'django/contrib/sites/__init__.py'
2025-04-22 20:54:05,604 wheel INFO adding 'django/contrib/sites/admin.py'
2025-04-22 20:54:05,604 wheel INFO adding 'django/contrib/sites/apps.py'
2025-04-22 20:54:05,604 wheel INFO adding 'django/contrib/sites/checks.py'
2025-04-22 20:54:05,604 wheel INFO adding 'django/contrib/sites/management.py'
2025-04-22 20:54:05,604 wheel INFO adding 'django/contrib/sites/managers.py'
2025-04-22 20:54:05,604 wheel INFO adding 'django/contrib/sites/middleware.py'
2025-04-22 20:54:05,604 wheel INFO adding 'django/contrib/sites/models.py'
2025-04-22 20:54:05,604 wheel INFO adding 'django/contrib/sites/requests.py'
2025-04-22 20:54:05,604 wheel INFO adding 'django/contrib/sites/shortcuts.py'
2025-04-22 20:54:05,605 wheel INFO adding 'django/contrib/sites/locale/af/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,605 wheel INFO adding 'django/contrib/sites/locale/af/LC_MESSAGES/django.po'
2025-04-22 20:54:05,605 wheel INFO adding 'django/contrib/sites/locale/ar/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,606 wheel INFO adding 'django/contrib/sites/locale/ar/LC_MESSAGES/django.po'
2025-04-22 20:54:05,606 wheel INFO adding 'django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,606 wheel INFO adding 'django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po'
2025-04-22 20:54:05,606 wheel INFO adding 'django/contrib/sites/locale/ast/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,606 wheel INFO adding 'django/contrib/sites/locale/ast/LC_MESSAGES/django.po'
2025-04-22 20:54:05,606 wheel INFO adding 'django/contrib/sites/locale/az/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,606 wheel INFO adding 'django/contrib/sites/locale/az/LC_MESSAGES/django.po'
2025-04-22 20:54:05,607 wheel INFO adding 'django/contrib/sites/locale/be/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,607 wheel INFO adding 'django/contrib/sites/locale/be/LC_MESSAGES/django.po'
2025-04-22 20:54:05,607 wheel INFO adding 'django/contrib/sites/locale/bg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,607 wheel INFO adding 'django/contrib/sites/locale/bg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,607 wheel INFO adding 'django/contrib/sites/locale/bn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,607 wheel INFO adding 'django/contrib/sites/locale/bn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,607 wheel INFO adding 'django/contrib/sites/locale/br/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,608 wheel INFO adding 'django/contrib/sites/locale/br/LC_MESSAGES/django.po'
2025-04-22 20:54:05,608 wheel INFO adding 'django/contrib/sites/locale/bs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,608 wheel INFO adding 'django/contrib/sites/locale/bs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,608 wheel INFO adding 'django/contrib/sites/locale/ca/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,608 wheel INFO adding 'django/contrib/sites/locale/ca/LC_MESSAGES/django.po'
2025-04-22 20:54:05,608 wheel INFO adding 'django/contrib/sites/locale/ckb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,609 wheel INFO adding 'django/contrib/sites/locale/ckb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,609 wheel INFO adding 'django/contrib/sites/locale/cs/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,609 wheel INFO adding 'django/contrib/sites/locale/cs/LC_MESSAGES/django.po'
2025-04-22 20:54:05,609 wheel INFO adding 'django/contrib/sites/locale/cy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,609 wheel INFO adding 'django/contrib/sites/locale/cy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,609 wheel INFO adding 'django/contrib/sites/locale/da/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,609 wheel INFO adding 'django/contrib/sites/locale/da/LC_MESSAGES/django.po'
2025-04-22 20:54:05,610 wheel INFO adding 'django/contrib/sites/locale/de/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,610 wheel INFO adding 'django/contrib/sites/locale/de/LC_MESSAGES/django.po'
2025-04-22 20:54:05,610 wheel INFO adding 'django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,610 wheel INFO adding 'django/contrib/sites/locale/dsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,610 wheel INFO adding 'django/contrib/sites/locale/el/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,610 wheel INFO adding 'django/contrib/sites/locale/el/LC_MESSAGES/django.po'
2025-04-22 20:54:05,610 wheel INFO adding 'django/contrib/sites/locale/en/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,611 wheel INFO adding 'django/contrib/sites/locale/en/LC_MESSAGES/django.po'
2025-04-22 20:54:05,611 wheel INFO adding 'django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,611 wheel INFO adding 'django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po'
2025-04-22 20:54:05,611 wheel INFO adding 'django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,611 wheel INFO adding 'django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po'
2025-04-22 20:54:05,611 wheel INFO adding 'django/contrib/sites/locale/eo/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,611 wheel INFO adding 'django/contrib/sites/locale/eo/LC_MESSAGES/django.po'
2025-04-22 20:54:05,612 wheel INFO adding 'django/contrib/sites/locale/es/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,612 wheel INFO adding 'django/contrib/sites/locale/es/LC_MESSAGES/django.po'
2025-04-22 20:54:05,612 wheel INFO adding 'django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,612 wheel INFO adding 'django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,612 wheel INFO adding 'django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,612 wheel INFO adding 'django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po'
2025-04-22 20:54:05,612 wheel INFO adding 'django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,613 wheel INFO adding 'django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po'
2025-04-22 20:54:05,613 wheel INFO adding 'django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,613 wheel INFO adding 'django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po'
2025-04-22 20:54:05,613 wheel INFO adding 'django/contrib/sites/locale/et/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,613 wheel INFO adding 'django/contrib/sites/locale/et/LC_MESSAGES/django.po'
2025-04-22 20:54:05,613 wheel INFO adding 'django/contrib/sites/locale/eu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,613 wheel INFO adding 'django/contrib/sites/locale/eu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,614 wheel INFO adding 'django/contrib/sites/locale/fa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,614 wheel INFO adding 'django/contrib/sites/locale/fa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,614 wheel INFO adding 'django/contrib/sites/locale/fi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,614 wheel INFO adding 'django/contrib/sites/locale/fi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,614 wheel INFO adding 'django/contrib/sites/locale/fr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,614 wheel INFO adding 'django/contrib/sites/locale/fr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,614 wheel INFO adding 'django/contrib/sites/locale/fy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,614 wheel INFO adding 'django/contrib/sites/locale/fy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,615 wheel INFO adding 'django/contrib/sites/locale/ga/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,615 wheel INFO adding 'django/contrib/sites/locale/ga/LC_MESSAGES/django.po'
2025-04-22 20:54:05,615 wheel INFO adding 'django/contrib/sites/locale/gd/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,615 wheel INFO adding 'django/contrib/sites/locale/gd/LC_MESSAGES/django.po'
2025-04-22 20:54:05,616 wheel INFO adding 'django/contrib/sites/locale/gl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,616 wheel INFO adding 'django/contrib/sites/locale/gl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,616 wheel INFO adding 'django/contrib/sites/locale/he/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,616 wheel INFO adding 'django/contrib/sites/locale/he/LC_MESSAGES/django.po'
2025-04-22 20:54:05,616 wheel INFO adding 'django/contrib/sites/locale/hi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,616 wheel INFO adding 'django/contrib/sites/locale/hi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,616 wheel INFO adding 'django/contrib/sites/locale/hr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,616 wheel INFO adding 'django/contrib/sites/locale/hr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,617 wheel INFO adding 'django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,617 wheel INFO adding 'django/contrib/sites/locale/hsb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,617 wheel INFO adding 'django/contrib/sites/locale/hu/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,617 wheel INFO adding 'django/contrib/sites/locale/hu/LC_MESSAGES/django.po'
2025-04-22 20:54:05,617 wheel INFO adding 'django/contrib/sites/locale/hy/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,617 wheel INFO adding 'django/contrib/sites/locale/hy/LC_MESSAGES/django.po'
2025-04-22 20:54:05,618 wheel INFO adding 'django/contrib/sites/locale/ia/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,618 wheel INFO adding 'django/contrib/sites/locale/ia/LC_MESSAGES/django.po'
2025-04-22 20:54:05,618 wheel INFO adding 'django/contrib/sites/locale/id/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,618 wheel INFO adding 'django/contrib/sites/locale/id/LC_MESSAGES/django.po'
2025-04-22 20:54:05,618 wheel INFO adding 'django/contrib/sites/locale/io/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,618 wheel INFO adding 'django/contrib/sites/locale/io/LC_MESSAGES/django.po'
2025-04-22 20:54:05,618 wheel INFO adding 'django/contrib/sites/locale/is/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,618 wheel INFO adding 'django/contrib/sites/locale/is/LC_MESSAGES/django.po'
2025-04-22 20:54:05,619 wheel INFO adding 'django/contrib/sites/locale/it/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,619 wheel INFO adding 'django/contrib/sites/locale/it/LC_MESSAGES/django.po'
2025-04-22 20:54:05,619 wheel INFO adding 'django/contrib/sites/locale/ja/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,619 wheel INFO adding 'django/contrib/sites/locale/ja/LC_MESSAGES/django.po'
2025-04-22 20:54:05,619 wheel INFO adding 'django/contrib/sites/locale/ka/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,619 wheel INFO adding 'django/contrib/sites/locale/ka/LC_MESSAGES/django.po'
2025-04-22 20:54:05,619 wheel INFO adding 'django/contrib/sites/locale/kab/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,620 wheel INFO adding 'django/contrib/sites/locale/kab/LC_MESSAGES/django.po'
2025-04-22 20:54:05,620 wheel INFO adding 'django/contrib/sites/locale/kk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,620 wheel INFO adding 'django/contrib/sites/locale/kk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,620 wheel INFO adding 'django/contrib/sites/locale/km/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,620 wheel INFO adding 'django/contrib/sites/locale/km/LC_MESSAGES/django.po'
2025-04-22 20:54:05,620 wheel INFO adding 'django/contrib/sites/locale/kn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,620 wheel INFO adding 'django/contrib/sites/locale/kn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,621 wheel INFO adding 'django/contrib/sites/locale/ko/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,621 wheel INFO adding 'django/contrib/sites/locale/ko/LC_MESSAGES/django.po'
2025-04-22 20:54:05,621 wheel INFO adding 'django/contrib/sites/locale/ky/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,621 wheel INFO adding 'django/contrib/sites/locale/ky/LC_MESSAGES/django.po'
2025-04-22 20:54:05,621 wheel INFO adding 'django/contrib/sites/locale/lb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,621 wheel INFO adding 'django/contrib/sites/locale/lb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,621 wheel INFO adding 'django/contrib/sites/locale/lt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,622 wheel INFO adding 'django/contrib/sites/locale/lt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,622 wheel INFO adding 'django/contrib/sites/locale/lv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,622 wheel INFO adding 'django/contrib/sites/locale/lv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,622 wheel INFO adding 'django/contrib/sites/locale/mk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,622 wheel INFO adding 'django/contrib/sites/locale/mk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,622 wheel INFO adding 'django/contrib/sites/locale/ml/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,622 wheel INFO adding 'django/contrib/sites/locale/ml/LC_MESSAGES/django.po'
2025-04-22 20:54:05,623 wheel INFO adding 'django/contrib/sites/locale/mn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,623 wheel INFO adding 'django/contrib/sites/locale/mn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,623 wheel INFO adding 'django/contrib/sites/locale/mr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,623 wheel INFO adding 'django/contrib/sites/locale/mr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,623 wheel INFO adding 'django/contrib/sites/locale/ms/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,623 wheel INFO adding 'django/contrib/sites/locale/ms/LC_MESSAGES/django.po'
2025-04-22 20:54:05,623 wheel INFO adding 'django/contrib/sites/locale/my/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,623 wheel INFO adding 'django/contrib/sites/locale/my/LC_MESSAGES/django.po'
2025-04-22 20:54:05,624 wheel INFO adding 'django/contrib/sites/locale/nb/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,624 wheel INFO adding 'django/contrib/sites/locale/nb/LC_MESSAGES/django.po'
2025-04-22 20:54:05,624 wheel INFO adding 'django/contrib/sites/locale/ne/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,624 wheel INFO adding 'django/contrib/sites/locale/ne/LC_MESSAGES/django.po'
2025-04-22 20:54:05,624 wheel INFO adding 'django/contrib/sites/locale/nl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,624 wheel INFO adding 'django/contrib/sites/locale/nl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,624 wheel INFO adding 'django/contrib/sites/locale/nn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,625 wheel INFO adding 'django/contrib/sites/locale/nn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,625 wheel INFO adding 'django/contrib/sites/locale/os/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,625 wheel INFO adding 'django/contrib/sites/locale/os/LC_MESSAGES/django.po'
2025-04-22 20:54:05,625 wheel INFO adding 'django/contrib/sites/locale/pa/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,625 wheel INFO adding 'django/contrib/sites/locale/pa/LC_MESSAGES/django.po'
2025-04-22 20:54:05,625 wheel INFO adding 'django/contrib/sites/locale/pl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,625 wheel INFO adding 'django/contrib/sites/locale/pl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,626 wheel INFO adding 'django/contrib/sites/locale/pt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,626 wheel INFO adding 'django/contrib/sites/locale/pt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,626 wheel INFO adding 'django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,626 wheel INFO adding 'django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po'
2025-04-22 20:54:05,626 wheel INFO adding 'django/contrib/sites/locale/ro/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,626 wheel INFO adding 'django/contrib/sites/locale/ro/LC_MESSAGES/django.po'
2025-04-22 20:54:05,626 wheel INFO adding 'django/contrib/sites/locale/ru/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,627 wheel INFO adding 'django/contrib/sites/locale/ru/LC_MESSAGES/django.po'
2025-04-22 20:54:05,627 wheel INFO adding 'django/contrib/sites/locale/sk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,627 wheel INFO adding 'django/contrib/sites/locale/sk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,627 wheel INFO adding 'django/contrib/sites/locale/sl/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,627 wheel INFO adding 'django/contrib/sites/locale/sl/LC_MESSAGES/django.po'
2025-04-22 20:54:05,627 wheel INFO adding 'django/contrib/sites/locale/sq/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,627 wheel INFO adding 'django/contrib/sites/locale/sq/LC_MESSAGES/django.po'
2025-04-22 20:54:05,628 wheel INFO adding 'django/contrib/sites/locale/sr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,628 wheel INFO adding 'django/contrib/sites/locale/sr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,628 wheel INFO adding 'django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,628 wheel INFO adding 'django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po'
2025-04-22 20:54:05,628 wheel INFO adding 'django/contrib/sites/locale/sv/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,628 wheel INFO adding 'django/contrib/sites/locale/sv/LC_MESSAGES/django.po'
2025-04-22 20:54:05,628 wheel INFO adding 'django/contrib/sites/locale/sw/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,629 wheel INFO adding 'django/contrib/sites/locale/sw/LC_MESSAGES/django.po'
2025-04-22 20:54:05,629 wheel INFO adding 'django/contrib/sites/locale/ta/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,629 wheel INFO adding 'django/contrib/sites/locale/ta/LC_MESSAGES/django.po'
2025-04-22 20:54:05,629 wheel INFO adding 'django/contrib/sites/locale/te/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,629 wheel INFO adding 'django/contrib/sites/locale/te/LC_MESSAGES/django.po'
2025-04-22 20:54:05,629 wheel INFO adding 'django/contrib/sites/locale/tg/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,629 wheel INFO adding 'django/contrib/sites/locale/tg/LC_MESSAGES/django.po'
2025-04-22 20:54:05,630 wheel INFO adding 'django/contrib/sites/locale/th/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,630 wheel INFO adding 'django/contrib/sites/locale/th/LC_MESSAGES/django.po'
2025-04-22 20:54:05,630 wheel INFO adding 'django/contrib/sites/locale/tk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,630 wheel INFO adding 'django/contrib/sites/locale/tk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,630 wheel INFO adding 'django/contrib/sites/locale/tr/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,630 wheel INFO adding 'django/contrib/sites/locale/tr/LC_MESSAGES/django.po'
2025-04-22 20:54:05,630 wheel INFO adding 'django/contrib/sites/locale/tt/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,630 wheel INFO adding 'django/contrib/sites/locale/tt/LC_MESSAGES/django.po'
2025-04-22 20:54:05,631 wheel INFO adding 'django/contrib/sites/locale/udm/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,631 wheel INFO adding 'django/contrib/sites/locale/udm/LC_MESSAGES/django.po'
2025-04-22 20:54:05,631 wheel INFO adding 'django/contrib/sites/locale/uk/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,631 wheel INFO adding 'django/contrib/sites/locale/uk/LC_MESSAGES/django.po'
2025-04-22 20:54:05,631 wheel INFO adding 'django/contrib/sites/locale/ur/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,631 wheel INFO adding 'django/contrib/sites/locale/ur/LC_MESSAGES/django.po'
2025-04-22 20:54:05,631 wheel INFO adding 'django/contrib/sites/locale/uz/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,632 wheel INFO adding 'django/contrib/sites/locale/uz/LC_MESSAGES/django.po'
2025-04-22 20:54:05,632 wheel INFO adding 'django/contrib/sites/locale/vi/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,632 wheel INFO adding 'django/contrib/sites/locale/vi/LC_MESSAGES/django.po'
2025-04-22 20:54:05,632 wheel INFO adding 'django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,632 wheel INFO adding 'django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po'
2025-04-22 20:54:05,632 wheel INFO adding 'django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo'
2025-04-22 20:54:05,633 wheel INFO adding 'django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po'
2025-04-22 20:54:05,633 wheel INFO adding 'django/contrib/sites/migrations/0001_initial.py'
2025-04-22 20:54:05,633 wheel INFO adding 'django/contrib/sites/migrations/0002_alter_domain_unique.py'
2025-04-22 20:54:05,633 wheel INFO adding 'django/contrib/sites/migrations/__init__.py'
2025-04-22 20:54:05,633 wheel INFO adding 'django/contrib/staticfiles/__init__.py'
2025-04-22 20:54:05,633 wheel INFO adding 'django/contrib/staticfiles/apps.py'
2025-04-22 20:54:05,633 wheel INFO adding 'django/contrib/staticfiles/checks.py'
2025-04-22 20:54:05,633 wheel INFO adding 'django/contrib/staticfiles/finders.py'
2025-04-22 20:54:05,634 wheel INFO adding 'django/contrib/staticfiles/handlers.py'
2025-04-22 20:54:05,634 wheel INFO adding 'django/contrib/staticfiles/storage.py'
2025-04-22 20:54:05,634 wheel INFO adding 'django/contrib/staticfiles/testing.py'
2025-04-22 20:54:05,634 wheel INFO adding 'django/contrib/staticfiles/urls.py'
2025-04-22 20:54:05,634 wheel INFO adding 'django/contrib/staticfiles/utils.py'
2025-04-22 20:54:05,634 wheel INFO adding 'django/contrib/staticfiles/views.py'
2025-04-22 20:54:05,634 wheel INFO adding 'django/contrib/staticfiles/management/__init__.py'
2025-04-22 20:54:05,635 wheel INFO adding 'django/contrib/staticfiles/management/commands/__init__.py'
2025-04-22 20:54:05,635 wheel INFO adding 'django/contrib/staticfiles/management/commands/collectstatic.py'
2025-04-22 20:54:05,636 wheel INFO adding 'django/contrib/staticfiles/management/commands/findstatic.py'
2025-04-22 20:54:05,636 wheel INFO adding 'django/contrib/staticfiles/management/commands/runserver.py'
2025-04-22 20:54:05,636 wheel INFO adding 'django/contrib/syndication/__init__.py'
2025-04-22 20:54:05,636 wheel INFO adding 'django/contrib/syndication/apps.py'
2025-04-22 20:54:05,636 wheel INFO adding 'django/contrib/syndication/views.py'
2025-04-22 20:54:05,636 wheel INFO adding 'django/core/__init__.py'
2025-04-22 20:54:05,637 wheel INFO adding 'django/core/asgi.py'
2025-04-22 20:54:05,637 wheel INFO adding 'django/core/exceptions.py'
2025-04-22 20:54:05,637 wheel INFO adding 'django/core/paginator.py'
2025-04-22 20:54:05,637 wheel INFO adding 'django/core/signals.py'
2025-04-22 20:54:05,637 wheel INFO adding 'django/core/signing.py'
2025-04-22 20:54:05,637 wheel INFO adding 'django/core/validators.py'
2025-04-22 20:54:05,637 wheel INFO adding 'django/core/wsgi.py'
2025-04-22 20:54:05,638 wheel INFO adding 'django/core/cache/__init__.py'
2025-04-22 20:54:05,638 wheel INFO adding 'django/core/cache/utils.py'
2025-04-22 20:54:05,638 wheel INFO adding 'django/core/cache/backends/__init__.py'
2025-04-22 20:54:05,638 wheel INFO adding 'django/core/cache/backends/base.py'
2025-04-22 20:54:05,638 wheel INFO adding 'django/core/cache/backends/db.py'
2025-04-22 20:54:05,638 wheel INFO adding 'django/core/cache/backends/dummy.py'
2025-04-22 20:54:05,639 wheel INFO adding 'django/core/cache/backends/filebased.py'
2025-04-22 20:54:05,639 wheel INFO adding 'django/core/cache/backends/locmem.py'
2025-04-22 20:54:05,639 wheel INFO adding 'django/core/cache/backends/memcached.py'
2025-04-22 20:54:05,639 wheel INFO adding 'django/core/cache/backends/redis.py'
2025-04-22 20:54:05,639 wheel INFO adding 'django/core/checks/__init__.py'
2025-04-22 20:54:05,639 wheel INFO adding 'django/core/checks/async_checks.py'
2025-04-22 20:54:05,639 wheel INFO adding 'django/core/checks/caches.py'
2025-04-22 20:54:05,639 wheel INFO adding 'django/core/checks/database.py'
2025-04-22 20:54:05,640 wheel INFO adding 'django/core/checks/files.py'
2025-04-22 20:54:05,640 wheel INFO adding 'django/core/checks/messages.py'
2025-04-22 20:54:05,640 wheel INFO adding 'django/core/checks/model_checks.py'
2025-04-22 20:54:05,640 wheel INFO adding 'django/core/checks/registry.py'
2025-04-22 20:54:05,640 wheel INFO adding 'django/core/checks/templates.py'
2025-04-22 20:54:05,640 wheel INFO adding 'django/core/checks/translation.py'
2025-04-22 20:54:05,640 wheel INFO adding 'django/core/checks/urls.py'
2025-04-22 20:54:05,641 wheel INFO adding 'django/core/checks/compatibility/__init__.py'
2025-04-22 20:54:05,641 wheel INFO adding 'django/core/checks/compatibility/django_4_0.py'
2025-04-22 20:54:05,641 wheel INFO adding 'django/core/checks/security/__init__.py'
2025-04-22 20:54:05,641 wheel INFO adding 'django/core/checks/security/base.py'
2025-04-22 20:54:05,641 wheel INFO adding 'django/core/checks/security/csrf.py'
2025-04-22 20:54:05,641 wheel INFO adding 'django/core/checks/security/sessions.py'
2025-04-22 20:54:05,641 wheel INFO adding 'django/core/files/__init__.py'
2025-04-22 20:54:05,641 wheel INFO adding 'django/core/files/base.py'
2025-04-22 20:54:05,642 wheel INFO adding 'django/core/files/images.py'
2025-04-22 20:54:05,642 wheel INFO adding 'django/core/files/locks.py'
2025-04-22 20:54:05,642 wheel INFO adding 'django/core/files/move.py'
2025-04-22 20:54:05,642 wheel INFO adding 'django/core/files/temp.py'
2025-04-22 20:54:05,642 wheel INFO adding 'django/core/files/uploadedfile.py'
2025-04-22 20:54:05,642 wheel INFO adding 'django/core/files/uploadhandler.py'
2025-04-22 20:54:05,643 wheel INFO adding 'django/core/files/utils.py'
2025-04-22 20:54:05,643 wheel INFO adding 'django/core/files/storage/__init__.py'
2025-04-22 20:54:05,643 wheel INFO adding 'django/core/files/storage/base.py'
2025-04-22 20:54:05,643 wheel INFO adding 'django/core/files/storage/filesystem.py'
2025-04-22 20:54:05,643 wheel INFO adding 'django/core/files/storage/handler.py'
2025-04-22 20:54:05,643 wheel INFO adding 'django/core/files/storage/memory.py'
2025-04-22 20:54:05,643 wheel INFO adding 'django/core/files/storage/mixins.py'
2025-04-22 20:54:05,644 wheel INFO adding 'django/core/handlers/__init__.py'
2025-04-22 20:54:05,644 wheel INFO adding 'django/core/handlers/asgi.py'
2025-04-22 20:54:05,644 wheel INFO adding 'django/core/handlers/base.py'
2025-04-22 20:54:05,644 wheel INFO adding 'django/core/handlers/exception.py'
2025-04-22 20:54:05,644 wheel INFO adding 'django/core/handlers/wsgi.py'
2025-04-22 20:54:05,644 wheel INFO adding 'django/core/mail/__init__.py'
2025-04-22 20:54:05,644 wheel INFO adding 'django/core/mail/message.py'
2025-04-22 20:54:05,645 wheel INFO adding 'django/core/mail/utils.py'
2025-04-22 20:54:05,645 wheel INFO adding 'django/core/mail/backends/__init__.py'
2025-04-22 20:54:05,645 wheel INFO adding 'django/core/mail/backends/base.py'
2025-04-22 20:54:05,645 wheel INFO adding 'django/core/mail/backends/console.py'
2025-04-22 20:54:05,645 wheel INFO adding 'django/core/mail/backends/dummy.py'
2025-04-22 20:54:05,645 wheel INFO adding 'django/core/mail/backends/filebased.py'
2025-04-22 20:54:05,645 wheel INFO adding 'django/core/mail/backends/locmem.py'
2025-04-22 20:54:05,646 wheel INFO adding 'django/core/mail/backends/smtp.py'
2025-04-22 20:54:05,646 wheel INFO adding 'django/core/management/__init__.py'
2025-04-22 20:54:05,646 wheel INFO adding 'django/core/management/base.py'
2025-04-22 20:54:05,646 wheel INFO adding 'django/core/management/color.py'
2025-04-22 20:54:05,646 wheel INFO adding 'django/core/management/sql.py'
2025-04-22 20:54:05,646 wheel INFO adding 'django/core/management/templates.py'
2025-04-22 20:54:05,647 wheel INFO adding 'django/core/management/utils.py'
2025-04-22 20:54:05,647 wheel INFO adding 'django/core/management/commands/__init__.py'
2025-04-22 20:54:05,647 wheel INFO adding 'django/core/management/commands/check.py'
2025-04-22 20:54:05,647 wheel INFO adding 'django/core/management/commands/compilemessages.py'
2025-04-22 20:54:05,647 wheel INFO adding 'django/core/management/commands/createcachetable.py'
2025-04-22 20:54:05,647 wheel INFO adding 'django/core/management/commands/dbshell.py'
2025-04-22 20:54:05,647 wheel INFO adding 'django/core/management/commands/diffsettings.py'
2025-04-22 20:54:05,648 wheel INFO adding 'django/core/management/commands/dumpdata.py'
2025-04-22 20:54:05,648 wheel INFO adding 'django/core/management/commands/flush.py'
2025-04-22 20:54:05,648 wheel INFO adding 'django/core/management/commands/inspectdb.py'
2025-04-22 20:54:05,648 wheel INFO adding 'django/core/management/commands/loaddata.py'
2025-04-22 20:54:05,648 wheel INFO adding 'django/core/management/commands/makemessages.py'
2025-04-22 20:54:05,649 wheel INFO adding 'django/core/management/commands/makemigrations.py'
2025-04-22 20:54:05,649 wheel INFO adding 'django/core/management/commands/migrate.py'
2025-04-22 20:54:05,649 wheel INFO adding 'django/core/management/commands/optimizemigration.py'
2025-04-22 20:54:05,649 wheel INFO adding 'django/core/management/commands/runserver.py'
2025-04-22 20:54:05,649 wheel INFO adding 'django/core/management/commands/sendtestemail.py'
2025-04-22 20:54:05,649 wheel INFO adding 'django/core/management/commands/shell.py'
2025-04-22 20:54:05,649 wheel INFO adding 'django/core/management/commands/showmigrations.py'
2025-04-22 20:54:05,650 wheel INFO adding 'django/core/management/commands/sqlflush.py'
2025-04-22 20:54:05,650 wheel INFO adding 'django/core/management/commands/sqlmigrate.py'
2025-04-22 20:54:05,650 wheel INFO adding 'django/core/management/commands/sqlsequencereset.py'
2025-04-22 20:54:05,650 wheel INFO adding 'django/core/management/commands/squashmigrations.py'
2025-04-22 20:54:05,650 wheel INFO adding 'django/core/management/commands/startapp.py'
2025-04-22 20:54:05,650 wheel INFO adding 'django/core/management/commands/startproject.py'
2025-04-22 20:54:05,650 wheel INFO adding 'django/core/management/commands/test.py'
2025-04-22 20:54:05,650 wheel INFO adding 'django/core/management/commands/testserver.py'
2025-04-22 20:54:05,651 wheel INFO adding 'django/core/serializers/__init__.py'
2025-04-22 20:54:05,651 wheel INFO adding 'django/core/serializers/base.py'
2025-04-22 20:54:05,651 wheel INFO adding 'django/core/serializers/json.py'
2025-04-22 20:54:05,651 wheel INFO adding 'django/core/serializers/jsonl.py'
2025-04-22 20:54:05,651 wheel INFO adding 'django/core/serializers/python.py'
2025-04-22 20:54:05,651 wheel INFO adding 'django/core/serializers/pyyaml.py'
2025-04-22 20:54:05,652 wheel INFO adding 'django/core/serializers/xml_serializer.py'
2025-04-22 20:54:05,652 wheel INFO adding 'django/core/servers/__init__.py'
2025-04-22 20:54:05,652 wheel INFO adding 'django/core/servers/basehttp.py'
2025-04-22 20:54:05,652 wheel INFO adding 'django/db/__init__.py'
2025-04-22 20:54:05,652 wheel INFO adding 'django/db/transaction.py'
2025-04-22 20:54:05,652 wheel INFO adding 'django/db/utils.py'
2025-04-22 20:54:05,653 wheel INFO adding 'django/db/backends/__init__.py'
2025-04-22 20:54:05,653 wheel INFO adding 'django/db/backends/ddl_references.py'
2025-04-22 20:54:05,653 wheel INFO adding 'django/db/backends/signals.py'
2025-04-22 20:54:05,653 wheel INFO adding 'django/db/backends/utils.py'
2025-04-22 20:54:05,653 wheel INFO adding 'django/db/backends/base/__init__.py'
2025-04-22 20:54:05,653 wheel INFO adding 'django/db/backends/base/base.py'
2025-04-22 20:54:05,654 wheel INFO adding 'django/db/backends/base/client.py'
2025-04-22 20:54:05,654 wheel INFO adding 'django/db/backends/base/creation.py'
2025-04-22 20:54:05,654 wheel INFO adding 'django/db/backends/base/features.py'
2025-04-22 20:54:05,654 wheel INFO adding 'django/db/backends/base/introspection.py'
2025-04-22 20:54:05,654 wheel INFO adding 'django/db/backends/base/operations.py'
2025-04-22 20:54:05,655 wheel INFO adding 'django/db/backends/base/schema.py'
2025-04-22 20:54:05,655 wheel INFO adding 'django/db/backends/base/validation.py'
2025-04-22 20:54:05,655 wheel INFO adding 'django/db/backends/dummy/__init__.py'
2025-04-22 20:54:05,655 wheel INFO adding 'django/db/backends/dummy/base.py'
2025-04-22 20:54:05,655 wheel INFO adding 'django/db/backends/dummy/features.py'
2025-04-22 20:54:05,655 wheel INFO adding 'django/db/backends/mysql/__init__.py'
2025-04-22 20:54:05,656 wheel INFO adding 'django/db/backends/mysql/base.py'
2025-04-22 20:54:05,656 wheel INFO adding 'django/db/backends/mysql/client.py'
2025-04-22 20:54:05,656 wheel INFO adding 'django/db/backends/mysql/compiler.py'
2025-04-22 20:54:05,656 wheel INFO adding 'django/db/backends/mysql/creation.py'
2025-04-22 20:54:05,656 wheel INFO adding 'django/db/backends/mysql/features.py'
2025-04-22 20:54:05,656 wheel INFO adding 'django/db/backends/mysql/introspection.py'
2025-04-22 20:54:05,657 wheel INFO adding 'django/db/backends/mysql/operations.py'
2025-04-22 20:54:05,657 wheel INFO adding 'django/db/backends/mysql/schema.py'
2025-04-22 20:54:05,657 wheel INFO adding 'django/db/backends/mysql/validation.py'
2025-04-22 20:54:05,657 wheel INFO adding 'django/db/backends/oracle/__init__.py'
2025-04-22 20:54:05,657 wheel INFO adding 'django/db/backends/oracle/base.py'
2025-04-22 20:54:05,657 wheel INFO adding 'django/db/backends/oracle/client.py'
2025-04-22 20:54:05,658 wheel INFO adding 'django/db/backends/oracle/creation.py'
2025-04-22 20:54:05,658 wheel INFO adding 'django/db/backends/oracle/features.py'
2025-04-22 20:54:05,658 wheel INFO adding 'django/db/backends/oracle/functions.py'
2025-04-22 20:54:05,658 wheel INFO adding 'django/db/backends/oracle/introspection.py'
2025-04-22 20:54:05,658 wheel INFO adding 'django/db/backends/oracle/operations.py'
2025-04-22 20:54:05,659 wheel INFO adding 'django/db/backends/oracle/schema.py'
2025-04-22 20:54:05,659 wheel INFO adding 'django/db/backends/oracle/utils.py'
2025-04-22 20:54:05,659 wheel INFO adding 'django/db/backends/oracle/validation.py'
2025-04-22 20:54:05,659 wheel INFO adding 'django/db/backends/postgresql/__init__.py'
2025-04-22 20:54:05,659 wheel INFO adding 'django/db/backends/postgresql/base.py'
2025-04-22 20:54:05,659 wheel INFO adding 'django/db/backends/postgresql/client.py'
2025-04-22 20:54:05,660 wheel INFO adding 'django/db/backends/postgresql/creation.py'
2025-04-22 20:54:05,660 wheel INFO adding 'django/db/backends/postgresql/features.py'
2025-04-22 20:54:05,660 wheel INFO adding 'django/db/backends/postgresql/introspection.py'
2025-04-22 20:54:05,660 wheel INFO adding 'django/db/backends/postgresql/operations.py'
2025-04-22 20:54:05,660 wheel INFO adding 'django/db/backends/postgresql/psycopg_any.py'
2025-04-22 20:54:05,660 wheel INFO adding 'django/db/backends/postgresql/schema.py'
2025-04-22 20:54:05,661 wheel INFO adding 'django/db/backends/sqlite3/__init__.py'
2025-04-22 20:54:05,661 wheel INFO adding 'django/db/backends/sqlite3/_functions.py'
2025-04-22 20:54:05,661 wheel INFO adding 'django/db/backends/sqlite3/base.py'
2025-04-22 20:54:05,661 wheel INFO adding 'django/db/backends/sqlite3/client.py'
2025-04-22 20:54:05,661 wheel INFO adding 'django/db/backends/sqlite3/creation.py'
2025-04-22 20:54:05,661 wheel INFO adding 'django/db/backends/sqlite3/features.py'
2025-04-22 20:54:05,661 wheel INFO adding 'django/db/backends/sqlite3/introspection.py'
2025-04-22 20:54:05,662 wheel INFO adding 'django/db/backends/sqlite3/operations.py'
2025-04-22 20:54:05,662 wheel INFO adding 'django/db/backends/sqlite3/schema.py'
2025-04-22 20:54:05,662 wheel INFO adding 'django/db/migrations/__init__.py'
2025-04-22 20:54:05,662 wheel INFO adding 'django/db/migrations/autodetector.py'
2025-04-22 20:54:05,663 wheel INFO adding 'django/db/migrations/exceptions.py'
2025-04-22 20:54:05,663 wheel INFO adding 'django/db/migrations/executor.py'
2025-04-22 20:54:05,663 wheel INFO adding 'django/db/migrations/graph.py'
2025-04-22 20:54:05,663 wheel INFO adding 'django/db/migrations/loader.py'
2025-04-22 20:54:05,663 wheel INFO adding 'django/db/migrations/migration.py'
2025-04-22 20:54:05,663 wheel INFO adding 'django/db/migrations/optimizer.py'
2025-04-22 20:54:05,664 wheel INFO adding 'django/db/migrations/questioner.py'
2025-04-22 20:54:05,664 wheel INFO adding 'django/db/migrations/recorder.py'
2025-04-22 20:54:05,664 wheel INFO adding 'django/db/migrations/serializer.py'
2025-04-22 20:54:05,664 wheel INFO adding 'django/db/migrations/state.py'
2025-04-22 20:54:05,664 wheel INFO adding 'django/db/migrations/utils.py'
2025-04-22 20:54:05,665 wheel INFO adding 'django/db/migrations/writer.py'
2025-04-22 20:54:05,665 wheel INFO adding 'django/db/migrations/operations/__init__.py'
2025-04-22 20:54:05,665 wheel INFO adding 'django/db/migrations/operations/base.py'
2025-04-22 20:54:05,665 wheel INFO adding 'django/db/migrations/operations/fields.py'
2025-04-22 20:54:05,665 wheel INFO adding 'django/db/migrations/operations/models.py'
2025-04-22 20:54:05,666 wheel INFO adding 'django/db/migrations/operations/special.py'
2025-04-22 20:54:05,666 wheel INFO adding 'django/db/models/__init__.py'
2025-04-22 20:54:05,666 wheel INFO adding 'django/db/models/aggregates.py'
2025-04-22 20:54:05,666 wheel INFO adding 'django/db/models/base.py'
2025-04-22 20:54:05,667 wheel INFO adding 'django/db/models/constants.py'
2025-04-22 20:54:05,667 wheel INFO adding 'django/db/models/constraints.py'
2025-04-22 20:54:05,667 wheel INFO adding 'django/db/models/deletion.py'
2025-04-22 20:54:05,667 wheel INFO adding 'django/db/models/enums.py'
2025-04-22 20:54:05,667 wheel INFO adding 'django/db/models/expressions.py'
2025-04-22 20:54:05,668 wheel INFO adding 'django/db/models/indexes.py'
2025-04-22 20:54:05,668 wheel INFO adding 'django/db/models/lookups.py'
2025-04-22 20:54:05,668 wheel INFO adding 'django/db/models/manager.py'
2025-04-22 20:54:05,668 wheel INFO adding 'django/db/models/options.py'
2025-04-22 20:54:05,669 wheel INFO adding 'django/db/models/query.py'
2025-04-22 20:54:05,669 wheel INFO adding 'django/db/models/query_utils.py'
2025-04-22 20:54:05,669 wheel INFO adding 'django/db/models/signals.py'
2025-04-22 20:54:05,669 wheel INFO adding 'django/db/models/utils.py'
2025-04-22 20:54:05,670 wheel INFO adding 'django/db/models/fields/__init__.py'
2025-04-22 20:54:05,670 wheel INFO adding 'django/db/models/fields/files.py'
2025-04-22 20:54:05,670 wheel INFO adding 'django/db/models/fields/json.py'
2025-04-22 20:54:05,670 wheel INFO adding 'django/db/models/fields/mixins.py'
2025-04-22 20:54:05,671 wheel INFO adding 'django/db/models/fields/proxy.py'
2025-04-22 20:54:05,671 wheel INFO adding 'django/db/models/fields/related.py'
2025-04-22 20:54:05,671 wheel INFO adding 'django/db/models/fields/related_descriptors.py'
2025-04-22 20:54:05,671 wheel INFO adding 'django/db/models/fields/related_lookups.py'
2025-04-22 20:54:05,672 wheel INFO adding 'django/db/models/fields/reverse_related.py'
2025-04-22 20:54:05,673 wheel INFO adding 'django/db/models/functions/__init__.py'
2025-04-22 20:54:05,673 wheel INFO adding 'django/db/models/functions/comparison.py'
2025-04-22 20:54:05,673 wheel INFO adding 'django/db/models/functions/datetime.py'
2025-04-22 20:54:05,673 wheel INFO adding 'django/db/models/functions/math.py'
2025-04-22 20:54:05,673 wheel INFO adding 'django/db/models/functions/mixins.py'
2025-04-22 20:54:05,673 wheel INFO adding 'django/db/models/functions/text.py'
2025-04-22 20:54:05,673 wheel INFO adding 'django/db/models/functions/window.py'
2025-04-22 20:54:05,674 wheel INFO adding 'django/db/models/sql/__init__.py'
2025-04-22 20:54:05,674 wheel INFO adding 'django/db/models/sql/compiler.py'
2025-04-22 20:54:05,674 wheel INFO adding 'django/db/models/sql/constants.py'
2025-04-22 20:54:05,674 wheel INFO adding 'django/db/models/sql/datastructures.py'
2025-04-22 20:54:05,675 wheel INFO adding 'django/db/models/sql/query.py'
2025-04-22 20:54:05,675 wheel INFO adding 'django/db/models/sql/subqueries.py'
2025-04-22 20:54:05,675 wheel INFO adding 'django/db/models/sql/where.py'
2025-04-22 20:54:05,675 wheel INFO adding 'django/dispatch/__init__.py'
2025-04-22 20:54:05,675 wheel INFO adding 'django/dispatch/dispatcher.py'
2025-04-22 20:54:05,676 wheel INFO adding 'django/dispatch/license.txt'
2025-04-22 20:54:05,676 wheel INFO adding 'django/forms/__init__.py'
2025-04-22 20:54:05,676 wheel INFO adding 'django/forms/boundfield.py'
2025-04-22 20:54:05,676 wheel INFO adding 'django/forms/fields.py'
2025-04-22 20:54:05,676 wheel INFO adding 'django/forms/forms.py'
2025-04-22 20:54:05,677 wheel INFO adding 'django/forms/formsets.py'
2025-04-22 20:54:05,677 wheel INFO adding 'django/forms/models.py'
2025-04-22 20:54:05,677 wheel INFO adding 'django/forms/renderers.py'
2025-04-22 20:54:05,677 wheel INFO adding 'django/forms/utils.py'
2025-04-22 20:54:05,678 wheel INFO adding 'django/forms/widgets.py'
2025-04-22 20:54:05,678 wheel INFO adding 'django/forms/jinja2/django/forms/attrs.html'
2025-04-22 20:54:05,678 wheel INFO adding 'django/forms/jinja2/django/forms/default.html'
2025-04-22 20:54:05,678 wheel INFO adding 'django/forms/jinja2/django/forms/div.html'
2025-04-22 20:54:05,678 wheel INFO adding 'django/forms/jinja2/django/forms/label.html'
2025-04-22 20:54:05,678 wheel INFO adding 'django/forms/jinja2/django/forms/p.html'
2025-04-22 20:54:05,678 wheel INFO adding 'django/forms/jinja2/django/forms/table.html'
2025-04-22 20:54:05,679 wheel INFO adding 'django/forms/jinja2/django/forms/ul.html'
2025-04-22 20:54:05,679 wheel INFO adding 'django/forms/jinja2/django/forms/errors/dict/default.html'
2025-04-22 20:54:05,679 wheel INFO adding 'django/forms/jinja2/django/forms/errors/dict/text.txt'
2025-04-22 20:54:05,679 wheel INFO adding 'django/forms/jinja2/django/forms/errors/dict/ul.html'
2025-04-22 20:54:05,679 wheel INFO adding 'django/forms/jinja2/django/forms/errors/list/default.html'
2025-04-22 20:54:05,679 wheel INFO adding 'django/forms/jinja2/django/forms/errors/list/text.txt'
2025-04-22 20:54:05,679 wheel INFO adding 'django/forms/jinja2/django/forms/errors/list/ul.html'
2025-04-22 20:54:05,679 wheel INFO adding 'django/forms/jinja2/django/forms/formsets/default.html'
2025-04-22 20:54:05,680 wheel INFO adding 'django/forms/jinja2/django/forms/formsets/div.html'
2025-04-22 20:54:05,680 wheel INFO adding 'django/forms/jinja2/django/forms/formsets/p.html'
2025-04-22 20:54:05,680 wheel INFO adding 'django/forms/jinja2/django/forms/formsets/table.html'
2025-04-22 20:54:05,680 wheel INFO adding 'django/forms/jinja2/django/forms/formsets/ul.html'
2025-04-22 20:54:05,680 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/attrs.html'
2025-04-22 20:54:05,680 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/checkbox.html'
2025-04-22 20:54:05,680 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/checkbox_option.html'
2025-04-22 20:54:05,680 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/checkbox_select.html'
2025-04-22 20:54:05,681 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/clearable_file_input.html'
2025-04-22 20:54:05,681 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/date.html'
2025-04-22 20:54:05,681 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/datetime.html'
2025-04-22 20:54:05,681 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/email.html'
2025-04-22 20:54:05,681 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/file.html'
2025-04-22 20:54:05,681 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/hidden.html'
2025-04-22 20:54:05,681 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/input.html'
2025-04-22 20:54:05,681 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/input_option.html'
2025-04-22 20:54:05,681 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/multiple_hidden.html'
2025-04-22 20:54:05,681 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/multiple_input.html'
2025-04-22 20:54:05,682 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/multiwidget.html'
2025-04-22 20:54:05,682 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/number.html'
2025-04-22 20:54:05,682 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/password.html'
2025-04-22 20:54:05,682 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/radio.html'
2025-04-22 20:54:05,682 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/radio_option.html'
2025-04-22 20:54:05,682 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/select.html'
2025-04-22 20:54:05,682 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/select_date.html'
2025-04-22 20:54:05,682 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/select_option.html'
2025-04-22 20:54:05,683 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/splitdatetime.html'
2025-04-22 20:54:05,683 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/splithiddendatetime.html'
2025-04-22 20:54:05,683 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/text.html'
2025-04-22 20:54:05,683 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/textarea.html'
2025-04-22 20:54:05,683 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/time.html'
2025-04-22 20:54:05,683 wheel INFO adding 'django/forms/jinja2/django/forms/widgets/url.html'
2025-04-22 20:54:05,683 wheel INFO adding 'django/forms/templates/django/forms/attrs.html'
2025-04-22 20:54:05,683 wheel INFO adding 'django/forms/templates/django/forms/default.html'
2025-04-22 20:54:05,684 wheel INFO adding 'django/forms/templates/django/forms/div.html'
2025-04-22 20:54:05,684 wheel INFO adding 'django/forms/templates/django/forms/label.html'
2025-04-22 20:54:05,684 wheel INFO adding 'django/forms/templates/django/forms/p.html'
2025-04-22 20:54:05,684 wheel INFO adding 'django/forms/templates/django/forms/table.html'
2025-04-22 20:54:05,684 wheel INFO adding 'django/forms/templates/django/forms/ul.html'
2025-04-22 20:54:05,684 wheel INFO adding 'django/forms/templates/django/forms/errors/dict/default.html'
2025-04-22 20:54:05,684 wheel INFO adding 'django/forms/templates/django/forms/errors/dict/text.txt'
2025-04-22 20:54:05,684 wheel INFO adding 'django/forms/templates/django/forms/errors/dict/ul.html'
2025-04-22 20:54:05,685 wheel INFO adding 'django/forms/templates/django/forms/errors/list/default.html'
2025-04-22 20:54:05,685 wheel INFO adding 'django/forms/templates/django/forms/errors/list/text.txt'
2025-04-22 20:54:05,685 wheel INFO adding 'django/forms/templates/django/forms/errors/list/ul.html'
2025-04-22 20:54:05,685 wheel INFO adding 'django/forms/templates/django/forms/formsets/default.html'
2025-04-22 20:54:05,685 wheel INFO adding 'django/forms/templates/django/forms/formsets/div.html'
2025-04-22 20:54:05,685 wheel INFO adding 'django/forms/templates/django/forms/formsets/p.html'
2025-04-22 20:54:05,685 wheel INFO adding 'django/forms/templates/django/forms/formsets/table.html'
2025-04-22 20:54:05,685 wheel INFO adding 'django/forms/templates/django/forms/formsets/ul.html'
2025-04-22 20:54:05,686 wheel INFO adding 'django/forms/templates/django/forms/widgets/attrs.html'
2025-04-22 20:54:05,686 wheel INFO adding 'django/forms/templates/django/forms/widgets/checkbox.html'
2025-04-22 20:54:05,686 wheel INFO adding 'django/forms/templates/django/forms/widgets/checkbox_option.html'
2025-04-22 20:54:05,686 wheel INFO adding 'django/forms/templates/django/forms/widgets/checkbox_select.html'
2025-04-22 20:54:05,686 wheel INFO adding 'django/forms/templates/django/forms/widgets/clearable_file_input.html'
2025-04-22 20:54:05,686 wheel INFO adding 'django/forms/templates/django/forms/widgets/date.html'
2025-04-22 20:54:05,686 wheel INFO adding 'django/forms/templates/django/forms/widgets/datetime.html'
2025-04-22 20:54:05,686 wheel INFO adding 'django/forms/templates/django/forms/widgets/email.html'
2025-04-22 20:54:05,687 wheel INFO adding 'django/forms/templates/django/forms/widgets/file.html'
2025-04-22 20:54:05,687 wheel INFO adding 'django/forms/templates/django/forms/widgets/hidden.html'
2025-04-22 20:54:05,687 wheel INFO adding 'django/forms/templates/django/forms/widgets/input.html'
2025-04-22 20:54:05,687 wheel INFO adding 'django/forms/templates/django/forms/widgets/input_option.html'
2025-04-22 20:54:05,687 wheel INFO adding 'django/forms/templates/django/forms/widgets/multiple_hidden.html'
2025-04-22 20:54:05,687 wheel INFO adding 'django/forms/templates/django/forms/widgets/multiple_input.html'
2025-04-22 20:54:05,687 wheel INFO adding 'django/forms/templates/django/forms/widgets/multiwidget.html'
2025-04-22 20:54:05,687 wheel INFO adding 'django/forms/templates/django/forms/widgets/number.html'
2025-04-22 20:54:05,687 wheel INFO adding 'django/forms/templates/django/forms/widgets/password.html'
2025-04-22 20:54:05,687 wheel INFO adding 'django/forms/templates/django/forms/widgets/radio.html'
2025-04-22 20:54:05,688 wheel INFO adding 'django/forms/templates/django/forms/widgets/radio_option.html'
2025-04-22 20:54:05,688 wheel INFO adding 'django/forms/templates/django/forms/widgets/select.html'
2025-04-22 20:54:05,688 wheel INFO adding 'django/forms/templates/django/forms/widgets/select_date.html'
2025-04-22 20:54:05,688 wheel INFO adding 'django/forms/templates/django/forms/widgets/select_option.html'
2025-04-22 20:54:05,688 wheel INFO adding 'django/forms/templates/django/forms/widgets/splitdatetime.html'
2025-04-22 20:54:05,688 wheel INFO adding 'django/forms/templates/django/forms/widgets/splithiddendatetime.html'
2025-04-22 20:54:05,690 wheel INFO adding 'django/forms/templates/django/forms/widgets/text.html'
2025-04-22 20:54:05,690 wheel INFO adding 'django/forms/templates/django/forms/widgets/textarea.html'
2025-04-22 20:54:05,690 wheel INFO adding 'django/forms/templates/django/forms/widgets/time.html'
2025-04-22 20:54:05,690 wheel INFO adding 'django/forms/templates/django/forms/widgets/url.html'
2025-04-22 20:54:05,691 wheel INFO adding 'django/http/__init__.py'
2025-04-22 20:54:05,691 wheel INFO adding 'django/http/cookie.py'
2025-04-22 20:54:05,691 wheel INFO adding 'django/http/multipartparser.py'
2025-04-22 20:54:05,691 wheel INFO adding 'django/http/request.py'
2025-04-22 20:54:05,691 wheel INFO adding 'django/http/response.py'
2025-04-22 20:54:05,692 wheel INFO adding 'django/middleware/__init__.py'
2025-04-22 20:54:05,692 wheel INFO adding 'django/middleware/cache.py'
2025-04-22 20:54:05,692 wheel INFO adding 'django/middleware/clickjacking.py'
2025-04-22 20:54:05,692 wheel INFO adding 'django/middleware/common.py'
2025-04-22 20:54:05,692 wheel INFO adding 'django/middleware/csrf.py'
2025-04-22 20:54:05,693 wheel INFO adding 'django/middleware/gzip.py'
2025-04-22 20:54:05,693 wheel INFO adding 'django/middleware/http.py'
2025-04-22 20:54:05,693 wheel INFO adding 'django/middleware/locale.py'
2025-04-22 20:54:05,693 wheel INFO adding 'django/middleware/security.py'
2025-04-22 20:54:05,693 wheel INFO adding 'django/template/__init__.py'
2025-04-22 20:54:05,693 wheel INFO adding 'django/template/autoreload.py'
2025-04-22 20:54:05,693 wheel INFO adding 'django/template/base.py'
2025-04-22 20:54:05,694 wheel INFO adding 'django/template/context.py'
2025-04-22 20:54:05,694 wheel INFO adding 'django/template/context_processors.py'
2025-04-22 20:54:05,694 wheel INFO adding 'django/template/defaultfilters.py'
2025-04-22 20:54:05,694 wheel INFO adding 'django/template/defaulttags.py'
2025-04-22 20:54:05,695 wheel INFO adding 'django/template/engine.py'
2025-04-22 20:54:05,695 wheel INFO adding 'django/template/exceptions.py'
2025-04-22 20:54:05,695 wheel INFO adding 'django/template/library.py'
2025-04-22 20:54:05,695 wheel INFO adding 'django/template/loader.py'
2025-04-22 20:54:05,695 wheel INFO adding 'django/template/loader_tags.py'
2025-04-22 20:54:05,695 wheel INFO adding 'django/template/response.py'
2025-04-22 20:54:05,696 wheel INFO adding 'django/template/smartif.py'
2025-04-22 20:54:05,696 wheel INFO adding 'django/template/utils.py'
2025-04-22 20:54:05,696 wheel INFO adding 'django/template/backends/__init__.py'
2025-04-22 20:54:05,696 wheel INFO adding 'django/template/backends/base.py'
2025-04-22 20:54:05,696 wheel INFO adding 'django/template/backends/django.py'
2025-04-22 20:54:05,696 wheel INFO adding 'django/template/backends/dummy.py'
2025-04-22 20:54:05,696 wheel INFO adding 'django/template/backends/jinja2.py'
2025-04-22 20:54:05,697 wheel INFO adding 'django/template/backends/utils.py'
2025-04-22 20:54:05,697 wheel INFO adding 'django/template/loaders/__init__.py'
2025-04-22 20:54:05,697 wheel INFO adding 'django/template/loaders/app_directories.py'
2025-04-22 20:54:05,697 wheel INFO adding 'django/template/loaders/base.py'
2025-04-22 20:54:05,697 wheel INFO adding 'django/template/loaders/cached.py'
2025-04-22 20:54:05,697 wheel INFO adding 'django/template/loaders/filesystem.py'
2025-04-22 20:54:05,697 wheel INFO adding 'django/template/loaders/locmem.py'
2025-04-22 20:54:05,697 wheel INFO adding 'django/templatetags/__init__.py'
2025-04-22 20:54:05,698 wheel INFO adding 'django/templatetags/cache.py'
2025-04-22 20:54:05,698 wheel INFO adding 'django/templatetags/i18n.py'
2025-04-22 20:54:05,698 wheel INFO adding 'django/templatetags/l10n.py'
2025-04-22 20:54:05,698 wheel INFO adding 'django/templatetags/static.py'
2025-04-22 20:54:05,698 wheel INFO adding 'django/templatetags/tz.py'
2025-04-22 20:54:05,698 wheel INFO adding 'django/test/__init__.py'
2025-04-22 20:54:05,699 wheel INFO adding 'django/test/client.py'
2025-04-22 20:54:05,699 wheel INFO adding 'django/test/html.py'
2025-04-22 20:54:05,699 wheel INFO adding 'django/test/runner.py'
2025-04-22 20:54:05,699 wheel INFO adding 'django/test/selenium.py'
2025-04-22 20:54:05,699 wheel INFO adding 'django/test/signals.py'
2025-04-22 20:54:05,700 wheel INFO adding 'django/test/testcases.py'
2025-04-22 20:54:05,700 wheel INFO adding 'django/test/utils.py'
2025-04-22 20:54:05,700 wheel INFO adding 'django/urls/__init__.py'
2025-04-22 20:54:05,700 wheel INFO adding 'django/urls/base.py'
2025-04-22 20:54:05,700 wheel INFO adding 'django/urls/conf.py'
2025-04-22 20:54:05,701 wheel INFO adding 'django/urls/converters.py'
2025-04-22 20:54:05,701 wheel INFO adding 'django/urls/exceptions.py'
2025-04-22 20:54:05,701 wheel INFO adding 'django/urls/resolvers.py'
2025-04-22 20:54:05,701 wheel INFO adding 'django/urls/utils.py'
2025-04-22 20:54:05,701 wheel INFO adding 'django/utils/__init__.py'
2025-04-22 20:54:05,701 wheel INFO adding 'django/utils/_os.py'
2025-04-22 20:54:05,702 wheel INFO adding 'django/utils/archive.py'
2025-04-22 20:54:05,702 wheel INFO adding 'django/utils/asyncio.py'
2025-04-22 20:54:05,702 wheel INFO adding 'django/utils/autoreload.py'
2025-04-22 20:54:05,702 wheel INFO adding 'django/utils/baseconv.py'
2025-04-22 20:54:05,702 wheel INFO adding 'django/utils/cache.py'
2025-04-22 20:54:05,702 wheel INFO adding 'django/utils/connection.py'
2025-04-22 20:54:05,702 wheel INFO adding 'django/utils/crypto.py'
2025-04-22 20:54:05,703 wheel INFO adding 'django/utils/datastructures.py'
2025-04-22 20:54:05,703 wheel INFO adding 'django/utils/dateformat.py'
2025-04-22 20:54:05,703 wheel INFO adding 'django/utils/dateparse.py'
2025-04-22 20:54:05,703 wheel INFO adding 'django/utils/dates.py'
2025-04-22 20:54:05,703 wheel INFO adding 'django/utils/datetime_safe.py'
2025-04-22 20:54:05,703 wheel INFO adding 'django/utils/deconstruct.py'
2025-04-22 20:54:05,703 wheel INFO adding 'django/utils/decorators.py'
2025-04-22 20:54:05,704 wheel INFO adding 'django/utils/deprecation.py'
2025-04-22 20:54:05,704 wheel INFO adding 'django/utils/duration.py'
2025-04-22 20:54:05,704 wheel INFO adding 'django/utils/encoding.py'
2025-04-22 20:54:05,704 wheel INFO adding 'django/utils/feedgenerator.py'
2025-04-22 20:54:05,704 wheel INFO adding 'django/utils/formats.py'
2025-04-22 20:54:05,704 wheel INFO adding 'django/utils/functional.py'
2025-04-22 20:54:05,705 wheel INFO adding 'django/utils/hashable.py'
2025-04-22 20:54:05,705 wheel INFO adding 'django/utils/html.py'
2025-04-22 20:54:05,705 wheel INFO adding 'django/utils/http.py'
2025-04-22 20:54:05,705 wheel INFO adding 'django/utils/inspect.py'
2025-04-22 20:54:05,705 wheel INFO adding 'django/utils/ipv6.py'
2025-04-22 20:54:05,705 wheel INFO adding 'django/utils/itercompat.py'
2025-04-22 20:54:05,705 wheel INFO adding 'django/utils/jslex.py'
2025-04-22 20:54:05,706 wheel INFO adding 'django/utils/log.py'
2025-04-22 20:54:05,706 wheel INFO adding 'django/utils/lorem_ipsum.py'
2025-04-22 20:54:05,706 wheel INFO adding 'django/utils/module_loading.py'
2025-04-22 20:54:05,706 wheel INFO adding 'django/utils/numberformat.py'
2025-04-22 20:54:05,706 wheel INFO adding 'django/utils/regex_helper.py'
2025-04-22 20:54:05,706 wheel INFO adding 'django/utils/safestring.py'
2025-04-22 20:54:05,706 wheel INFO adding 'django/utils/termcolors.py'
2025-04-22 20:54:05,707 wheel INFO adding 'django/utils/text.py'
2025-04-22 20:54:05,707 wheel INFO adding 'django/utils/timesince.py'
2025-04-22 20:54:05,707 wheel INFO adding 'django/utils/timezone.py'
2025-04-22 20:54:05,707 wheel INFO adding 'django/utils/topological_sort.py'
2025-04-22 20:54:05,707 wheel INFO adding 'django/utils/tree.py'
2025-04-22 20:54:05,707 wheel INFO adding 'django/utils/version.py'
2025-04-22 20:54:05,707 wheel INFO adding 'django/utils/xmlutils.py'
2025-04-22 20:54:05,708 wheel INFO adding 'django/utils/translation/__init__.py'
2025-04-22 20:54:05,708 wheel INFO adding 'django/utils/translation/reloader.py'
2025-04-22 20:54:05,708 wheel INFO adding 'django/utils/translation/template.py'
2025-04-22 20:54:05,708 wheel INFO adding 'django/utils/translation/trans_null.py'
2025-04-22 20:54:05,708 wheel INFO adding 'django/utils/translation/trans_real.py'
2025-04-22 20:54:05,709 wheel INFO adding 'django/views/__init__.py'
2025-04-22 20:54:05,709 wheel INFO adding 'django/views/csrf.py'
2025-04-22 20:54:05,709 wheel INFO adding 'django/views/debug.py'
2025-04-22 20:54:05,709 wheel INFO adding 'django/views/defaults.py'
2025-04-22 20:54:05,709 wheel INFO adding 'django/views/i18n.py'
2025-04-22 20:54:05,709 wheel INFO adding 'django/views/static.py'
2025-04-22 20:54:05,710 wheel INFO adding 'django/views/decorators/__init__.py'
2025-04-22 20:54:05,710 wheel INFO adding 'django/views/decorators/cache.py'
2025-04-22 20:54:05,710 wheel INFO adding 'django/views/decorators/clickjacking.py'
2025-04-22 20:54:05,710 wheel INFO adding 'django/views/decorators/common.py'
2025-04-22 20:54:05,710 wheel INFO adding 'django/views/decorators/csrf.py'
2025-04-22 20:54:05,710 wheel INFO adding 'django/views/decorators/debug.py'
2025-04-22 20:54:05,710 wheel INFO adding 'django/views/decorators/gzip.py'
2025-04-22 20:54:05,710 wheel INFO adding 'django/views/decorators/http.py'
2025-04-22 20:54:05,711 wheel INFO adding 'django/views/decorators/vary.py'
2025-04-22 20:54:05,711 wheel INFO adding 'django/views/generic/__init__.py'
2025-04-22 20:54:05,711 wheel INFO adding 'django/views/generic/base.py'
2025-04-22 20:54:05,711 wheel INFO adding 'django/views/generic/dates.py'
2025-04-22 20:54:05,711 wheel INFO adding 'django/views/generic/detail.py'
2025-04-22 20:54:05,711 wheel INFO adding 'django/views/generic/edit.py'
2025-04-22 20:54:05,711 wheel INFO adding 'django/views/generic/list.py'
2025-04-22 20:54:05,712 wheel INFO adding 'django/views/templates/default_urlconf.html'
2025-04-22 20:54:05,712 wheel INFO adding 'django/views/templates/technical_404.html'
2025-04-22 20:54:05,712 wheel INFO adding 'django/views/templates/technical_500.html'
2025-04-22 20:54:05,712 wheel INFO adding 'django/views/templates/technical_500.txt'
2025-04-22 20:54:05,712 wheel INFO adding 'Django-4.2.20.dist-info/AUTHORS'
2025-04-22 20:54:05,713 wheel INFO adding 'Django-4.2.20.dist-info/LICENSE'
2025-04-22 20:54:05,713 wheel INFO adding 'Django-4.2.20.dist-info/LICENSE.python'
2025-04-22 20:54:05,713 wheel INFO adding 'Django-4.2.20.dist-info/METADATA'
2025-04-22 20:54:05,713 wheel INFO adding 'Django-4.2.20.dist-info/WHEEL'
2025-04-22 20:54:05,713 wheel INFO adding 'Django-4.2.20.dist-info/entry_points.txt'
2025-04-22 20:54:05,713 wheel INFO adding 'Django-4.2.20.dist-info/top_level.txt'
2025-04-22 20:54:05,726 wheel INFO adding 'Django-4.2.20.dist-info/RECORD'
2025-04-22 20:54:05,737 root INFO removing build/bdist.linux-aarch64/wheel
2025-04-22 20:54:05,890 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...
libfakeroot internal error: payload not recognized!
>>> 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 20:54:30 +0000 elapsed time 0h 0m 30s
>>> py3-django: Cleaning up srcdir
>>> py3-django: Cleaning up pkgdir
>>> py3-django: Uninstalling dependencies...
(1/29) Purging .makedepends-py3-django (20250422.205401)
(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 (70.3.0-r0)
(12/29) Purging py3-setuptools (70.3.0-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.1.4-r0)
(18/29) Purging py3-parsing (3.1.4-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.7-r0)
(26/29) Purging libpanelw (6.5_p20241006-r3)
(27/29) Purging mpdecimal (4.0.0-r0)
(28/29) Purging sqlite-libs (3.48.0-r1)
(29/29) Purging xz-libs (5.6.3-r1)
Executing busybox-1.37.0-r12.trigger
OK: 396 MiB in 102 packages
>>> py3-django: Updating the community/aarch64 repository index...
>>> py3-django: Signing the index...