=> Bootstrap dependency digest>=20211023: found digest-20220214
===> Skipping vulnerability checks.
WARNING: No /usr/pkg/pkgdb/pkg-vulnerabilities file found.
WARNING: To fix run: `/usr/sbin/pkg_admin -K /usr/pkg/pkgdb fetch-pkg-vulnerabilities'.
===> Building for py310-django-3.2.25
* Building wheel...
/usr/pkg/lib/python3.10/site-packages/setuptools/dist.py:452: SetuptoolsDeprecationWarning: Invalid dash-separated options
!!

        ********************************************************************************
        Usage of dash-separated 'install-script' will not be supported in future
        versions. Please use the underscore name 'install_script' instead.

        By 2024-Sep-26, you need to update your project and remove deprecated calls
        or your builds will no longer be supported.

        See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
        ********************************************************************************

!!
  opt = self.warn_dash_deprecation(opt, section)
running bdist_wheel
running build
running build_py
creating build
creating build/lib
creating build/lib/django
copying django/__init__.py -> build/lib/django
copying django/__main__.py -> build/lib/django
copying django/shortcuts.py -> build/lib/django
creating build/lib/django/apps
copying django/apps/__init__.py -> build/lib/django/apps
copying django/apps/config.py -> build/lib/django/apps
copying django/apps/registry.py -> build/lib/django/apps
creating build/lib/django/conf
copying django/conf/__init__.py -> build/lib/django/conf
copying django/conf/global_settings.py -> build/lib/django/conf
creating build/lib/django/contrib
copying django/contrib/__init__.py -> build/lib/django/contrib
creating build/lib/django/core
copying django/core/__init__.py -> build/lib/django/core
copying django/core/asgi.py -> build/lib/django/core
copying django/core/exceptions.py -> build/lib/django/core
copying django/core/paginator.py -> build/lib/django/core
copying django/core/signals.py -> build/lib/django/core
copying django/core/signing.py -> build/lib/django/core
copying django/core/validators.py -> build/lib/django/core
copying django/core/wsgi.py -> build/lib/django/core
creating build/lib/django/db
copying django/db/__init__.py -> build/lib/django/db
copying django/db/transaction.py -> build/lib/django/db
copying django/db/utils.py -> build/lib/django/db
creating build/lib/django/dispatch
copying django/dispatch/__init__.py -> build/lib/django/dispatch
copying django/dispatch/dispatcher.py -> build/lib/django/dispatch
creating build/lib/django/forms
copying django/forms/__init__.py -> build/lib/django/forms
copying django/forms/boundfield.py -> build/lib/django/forms
copying django/forms/fields.py -> build/lib/django/forms
copying django/forms/forms.py -> build/lib/django/forms
copying django/forms/formsets.py -> build/lib/django/forms
copying django/forms/models.py -> build/lib/django/forms
copying django/forms/renderers.py -> build/lib/django/forms
copying django/forms/utils.py -> build/lib/django/forms
copying django/forms/widgets.py -> build/lib/django/forms
creating build/lib/django/http
copying django/http/__init__.py -> build/lib/django/http
copying django/http/cookie.py -> build/lib/django/http
copying django/http/multipartparser.py -> build/lib/django/http
copying django/http/request.py -> build/lib/django/http
copying django/http/response.py -> build/lib/django/http
creating build/lib/django/middleware
copying django/middleware/__init__.py -> build/lib/django/middleware
copying django/middleware/cache.py -> build/lib/django/middleware
copying django/middleware/clickjacking.py -> build/lib/django/middleware
copying django/middleware/common.py -> build/lib/django/middleware
copying django/middleware/csrf.py -> build/lib/django/middleware
copying django/middleware/gzip.py -> build/lib/django/middleware
copying django/middleware/http.py -> build/lib/django/middleware
copying django/middleware/locale.py -> build/lib/django/middleware
copying django/middleware/security.py -> build/lib/django/middleware
creating build/lib/django/template
copying django/template/__init__.py -> build/lib/django/template
copying django/template/autoreload.py -> build/lib/django/template
copying django/template/base.py -> build/lib/django/template
copying django/template/context.py -> build/lib/django/template
copying django/template/context_processors.py -> build/lib/django/template
copying django/template/defaultfilters.py -> build/lib/django/template
copying django/template/defaulttags.py -> build/lib/django/template
copying django/template/engine.py -> build/lib/django/template
copying django/template/exceptions.py -> build/lib/django/template
copying django/template/library.py -> build/lib/django/template
copying django/template/loader.py -> build/lib/django/template
copying django/template/loader_tags.py -> build/lib/django/template
copying django/template/response.py -> build/lib/django/template
copying django/template/smartif.py -> build/lib/django/template
copying django/template/utils.py -> build/lib/django/template
creating build/lib/django/templatetags
copying django/templatetags/__init__.py -> build/lib/django/templatetags
copying django/templatetags/cache.py -> build/lib/django/templatetags
copying django/templatetags/i18n.py -> build/lib/django/templatetags
copying django/templatetags/l10n.py -> build/lib/django/templatetags
copying django/templatetags/static.py -> build/lib/django/templatetags
copying django/templatetags/tz.py -> build/lib/django/templatetags
creating build/lib/django/test
copying django/test/__init__.py -> build/lib/django/test
copying django/test/client.py -> build/lib/django/test
copying django/test/html.py -> build/lib/django/test
copying django/test/runner.py -> build/lib/django/test
copying django/test/selenium.py -> build/lib/django/test
copying django/test/signals.py -> build/lib/django/test
copying django/test/testcases.py -> build/lib/django/test
copying django/test/utils.py -> build/lib/django/test
creating build/lib/django/urls
copying django/urls/__init__.py -> build/lib/django/urls
copying django/urls/base.py -> build/lib/django/urls
copying django/urls/conf.py -> build/lib/django/urls
copying django/urls/converters.py -> build/lib/django/urls
copying django/urls/exceptions.py -> build/lib/django/urls
copying django/urls/resolvers.py -> build/lib/django/urls
copying django/urls/utils.py -> build/lib/django/urls
creating build/lib/django/utils
copying django/utils/__init__.py -> build/lib/django/utils
copying django/utils/_os.py -> build/lib/django/utils
copying django/utils/archive.py -> build/lib/django/utils
copying django/utils/asyncio.py -> build/lib/django/utils
copying django/utils/autoreload.py -> build/lib/django/utils
copying django/utils/baseconv.py -> build/lib/django/utils
copying django/utils/cache.py -> build/lib/django/utils
copying django/utils/connection.py -> build/lib/django/utils
copying django/utils/crypto.py -> build/lib/django/utils
copying django/utils/datastructures.py -> build/lib/django/utils
copying django/utils/dateformat.py -> build/lib/django/utils
copying django/utils/dateparse.py -> build/lib/django/utils
copying django/utils/dates.py -> build/lib/django/utils
copying django/utils/datetime_safe.py -> build/lib/django/utils
copying django/utils/deconstruct.py -> build/lib/django/utils
copying django/utils/decorators.py -> build/lib/django/utils
copying django/utils/deprecation.py -> build/lib/django/utils
copying django/utils/duration.py -> build/lib/django/utils
copying django/utils/encoding.py -> build/lib/django/utils
copying django/utils/feedgenerator.py -> build/lib/django/utils
copying django/utils/formats.py -> build/lib/django/utils
copying django/utils/functional.py -> build/lib/django/utils
copying django/utils/hashable.py -> build/lib/django/utils
copying django/utils/html.py -> build/lib/django/utils
copying django/utils/http.py -> build/lib/django/utils
copying django/utils/inspect.py -> build/lib/django/utils
copying django/utils/ipv6.py -> build/lib/django/utils
copying django/utils/itercompat.py -> build/lib/django/utils
copying django/utils/jslex.py -> build/lib/django/utils
copying django/utils/log.py -> build/lib/django/utils
copying django/utils/lorem_ipsum.py -> build/lib/django/utils
copying django/utils/module_loading.py -> build/lib/django/utils
copying django/utils/numberformat.py -> build/lib/django/utils
copying django/utils/regex_helper.py -> build/lib/django/utils
copying django/utils/safestring.py -> build/lib/django/utils
copying django/utils/termcolors.py -> build/lib/django/utils
copying django/utils/text.py -> build/lib/django/utils
copying django/utils/timesince.py -> build/lib/django/utils
copying django/utils/timezone.py -> build/lib/django/utils
copying django/utils/topological_sort.py -> build/lib/django/utils
copying django/utils/tree.py -> build/lib/django/utils
copying django/utils/version.py -> build/lib/django/utils
copying django/utils/xmlutils.py -> build/lib/django/utils
creating build/lib/django/views
copying django/views/__init__.py -> build/lib/django/views
copying django/views/csrf.py -> build/lib/django/views
copying django/views/debug.py -> build/lib/django/views
copying django/views/defaults.py -> build/lib/django/views
copying django/views/i18n.py -> build/lib/django/views
copying django/views/static.py -> build/lib/django/views
creating build/lib/django/conf/locale
copying django/conf/locale/__init__.py -> build/lib/django/conf/locale
creating build/lib/django/conf/urls
copying django/conf/urls/__init__.py -> build/lib/django/conf/urls
copying django/conf/urls/i18n.py -> build/lib/django/conf/urls
copying django/conf/urls/static.py -> build/lib/django/conf/urls
creating build/lib/django/conf/locale/ar
copying django/conf/locale/ar/__init__.py -> build/lib/django/conf/locale/ar
copying django/conf/locale/ar/formats.py -> build/lib/django/conf/locale/ar
creating build/lib/django/conf/locale/ar_DZ
copying django/conf/locale/ar_DZ/__init__.py -> build/lib/django/conf/locale/ar_DZ
copying django/conf/locale/ar_DZ/formats.py -> build/lib/django/conf/locale/ar_DZ
creating build/lib/django/conf/locale/az
copying django/conf/locale/az/__init__.py -> build/lib/django/conf/locale/az
copying django/conf/locale/az/formats.py -> build/lib/django/conf/locale/az
creating build/lib/django/conf/locale/bg
copying django/conf/locale/bg/__init__.py -> build/lib/django/conf/locale/bg
copying django/conf/locale/bg/formats.py -> build/lib/django/conf/locale/bg
creating build/lib/django/conf/locale/bn
copying django/conf/locale/bn/__init__.py -> build/lib/django/conf/locale/bn
copying django/conf/locale/bn/formats.py -> build/lib/django/conf/locale/bn
creating build/lib/django/conf/locale/bs
copying django/conf/locale/bs/__init__.py -> build/lib/django/conf/locale/bs
copying django/conf/locale/bs/formats.py -> build/lib/django/conf/locale/bs
creating build/lib/django/conf/locale/ca
copying django/conf/locale/ca/__init__.py -> build/lib/django/conf/locale/ca
copying django/conf/locale/ca/formats.py -> build/lib/django/conf/locale/ca
creating build/lib/django/conf/locale/cs
copying django/conf/locale/cs/__init__.py -> build/lib/django/conf/locale/cs
copying django/conf/locale/cs/formats.py -> build/lib/django/conf/locale/cs
creating build/lib/django/conf/locale/cy
copying django/conf/locale/cy/__init__.py -> build/lib/django/conf/locale/cy
copying django/conf/locale/cy/formats.py -> build/lib/django/conf/locale/cy
creating build/lib/django/conf/locale/da
copying django/conf/locale/da/__init__.py -> build/lib/django/conf/locale/da
copying django/conf/locale/da/formats.py -> build/lib/django/conf/locale/da
creating build/lib/django/conf/locale/de
copying django/conf/locale/de/__init__.py -> build/lib/django/conf/locale/de
copying django/conf/locale/de/formats.py -> build/lib/django/conf/locale/de
creating build/lib/django/conf/locale/de_CH
copying django/conf/locale/de_CH/__init__.py -> build/lib/django/conf/locale/de_CH
copying django/conf/locale/de_CH/formats.py -> build/lib/django/conf/locale/de_CH
creating build/lib/django/conf/locale/el
copying django/conf/locale/el/__init__.py -> build/lib/django/conf/locale/el
copying django/conf/locale/el/formats.py -> build/lib/django/conf/locale/el
creating build/lib/django/conf/locale/en
copying django/conf/locale/en/__init__.py -> build/lib/django/conf/locale/en
copying django/conf/locale/en/formats.py -> build/lib/django/conf/locale/en
creating build/lib/django/conf/locale/en_AU
copying django/conf/locale/en_AU/__init__.py -> build/lib/django/conf/locale/en_AU
copying django/conf/locale/en_AU/formats.py -> build/lib/django/conf/locale/en_AU
creating build/lib/django/conf/locale/en_GB
copying django/conf/locale/en_GB/__init__.py -> build/lib/django/conf/locale/en_GB
copying django/conf/locale/en_GB/formats.py -> build/lib/django/conf/locale/en_GB
creating build/lib/django/conf/locale/eo
copying django/conf/locale/eo/__init__.py -> build/lib/django/conf/locale/eo
copying django/conf/locale/eo/formats.py -> build/lib/django/conf/locale/eo
creating build/lib/django/conf/locale/es
copying django/conf/locale/es/__init__.py -> build/lib/django/conf/locale/es
copying django/conf/locale/es/formats.py -> build/lib/django/conf/locale/es
creating build/lib/django/conf/locale/es_AR
copying django/conf/locale/es_AR/__init__.py -> build/lib/django/conf/locale/es_AR
copying django/conf/locale/es_AR/formats.py -> build/lib/django/conf/locale/es_AR
creating build/lib/django/conf/locale/es_CO
copying django/conf/locale/es_CO/__init__.py -> build/lib/django/conf/locale/es_CO
copying django/conf/locale/es_CO/formats.py -> build/lib/django/conf/locale/es_CO
creating build/lib/django/conf/locale/es_MX
copying django/conf/locale/es_MX/__init__.py -> build/lib/django/conf/locale/es_MX
copying django/conf/locale/es_MX/formats.py -> build/lib/django/conf/locale/es_MX
creating build/lib/django/conf/locale/es_NI
copying django/conf/locale/es_NI/__init__.py -> build/lib/django/conf/locale/es_NI
copying django/conf/locale/es_NI/formats.py -> build/lib/django/conf/locale/es_NI
creating build/lib/django/conf/locale/es_PR
copying django/conf/locale/es_PR/__init__.py -> build/lib/django/conf/locale/es_PR
copying django/conf/locale/es_PR/formats.py -> build/lib/django/conf/locale/es_PR
creating build/lib/django/conf/locale/et
copying django/conf/locale/et/__init__.py -> build/lib/django/conf/locale/et
copying django/conf/locale/et/formats.py -> build/lib/django/conf/locale/et
creating build/lib/django/conf/locale/eu
copying django/conf/locale/eu/__init__.py -> build/lib/django/conf/locale/eu
copying django/conf/locale/eu/formats.py -> build/lib/django/conf/locale/eu
creating build/lib/django/conf/locale/fa
copying django/conf/locale/fa/__init__.py -> build/lib/django/conf/locale/fa
copying django/conf/locale/fa/formats.py -> build/lib/django/conf/locale/fa
creating build/lib/django/conf/locale/fi
copying django/conf/locale/fi/__init__.py -> build/lib/django/conf/locale/fi
copying django/conf/locale/fi/formats.py -> build/lib/django/conf/locale/fi
creating build/lib/django/conf/locale/fr
copying django/conf/locale/fr/__init__.py -> build/lib/django/conf/locale/fr
copying django/conf/locale/fr/formats.py -> build/lib/django/conf/locale/fr
creating build/lib/django/conf/locale/fy
copying django/conf/locale/fy/__init__.py -> build/lib/django/conf/locale/fy
copying django/conf/locale/fy/formats.py -> build/lib/django/conf/locale/fy
creating build/lib/django/conf/locale/ga
copying django/conf/locale/ga/__init__.py -> build/lib/django/conf/locale/ga
copying django/conf/locale/ga/formats.py -> build/lib/django/conf/locale/ga
creating build/lib/django/conf/locale/gd
copying django/conf/locale/gd/__init__.py -> build/lib/django/conf/locale/gd
copying django/conf/locale/gd/formats.py -> build/lib/django/conf/locale/gd
creating build/lib/django/conf/locale/gl
copying django/conf/locale/gl/__init__.py -> build/lib/django/conf/locale/gl
copying django/conf/locale/gl/formats.py -> build/lib/django/conf/locale/gl
creating build/lib/django/conf/locale/he
copying django/conf/locale/he/__init__.py -> build/lib/django/conf/locale/he
copying django/conf/locale/he/formats.py -> build/lib/django/conf/locale/he
creating build/lib/django/conf/locale/hi
copying django/conf/locale/hi/__init__.py -> build/lib/django/conf/locale/hi
copying django/conf/locale/hi/formats.py -> build/lib/django/conf/locale/hi
creating build/lib/django/conf/locale/hr
copying django/conf/locale/hr/__init__.py -> build/lib/django/conf/locale/hr
copying django/conf/locale/hr/formats.py -> build/lib/django/conf/locale/hr
creating build/lib/django/conf/locale/hu
copying django/conf/locale/hu/__init__.py -> build/lib/django/conf/locale/hu
copying django/conf/locale/hu/formats.py -> build/lib/django/conf/locale/hu
creating build/lib/django/conf/locale/id
copying django/conf/locale/id/__init__.py -> build/lib/django/conf/locale/id
copying django/conf/locale/id/formats.py -> build/lib/django/conf/locale/id
creating build/lib/django/conf/locale/ig
copying django/conf/locale/ig/__init__.py -> build/lib/django/conf/locale/ig
copying django/conf/locale/ig/formats.py -> build/lib/django/conf/locale/ig
creating build/lib/django/conf/locale/is
copying django/conf/locale/is/__init__.py -> build/lib/django/conf/locale/is
copying django/conf/locale/is/formats.py -> build/lib/django/conf/locale/is
creating build/lib/django/conf/locale/it
copying django/conf/locale/it/__init__.py -> build/lib/django/conf/locale/it
copying django/conf/locale/it/formats.py -> build/lib/django/conf/locale/it
creating build/lib/django/conf/locale/ja
copying django/conf/locale/ja/__init__.py -> build/lib/django/conf/locale/ja
copying django/conf/locale/ja/formats.py -> build/lib/django/conf/locale/ja
creating build/lib/django/conf/locale/ka
copying django/conf/locale/ka/__init__.py -> build/lib/django/conf/locale/ka
copying django/conf/locale/ka/formats.py -> build/lib/django/conf/locale/ka
creating build/lib/django/conf/locale/km
copying django/conf/locale/km/__init__.py -> build/lib/django/conf/locale/km
copying django/conf/locale/km/formats.py -> build/lib/django/conf/locale/km
creating build/lib/django/conf/locale/kn
copying django/conf/locale/kn/__init__.py -> build/lib/django/conf/locale/kn
copying django/conf/locale/kn/formats.py -> build/lib/django/conf/locale/kn
creating build/lib/django/conf/locale/ko
copying django/conf/locale/ko/__init__.py -> build/lib/django/conf/locale/ko
copying django/conf/locale/ko/formats.py -> build/lib/django/conf/locale/ko
creating build/lib/django/conf/locale/ky
copying django/conf/locale/ky/__init__.py -> build/lib/django/conf/locale/ky
copying django/conf/locale/ky/formats.py -> build/lib/django/conf/locale/ky
creating build/lib/django/conf/locale/lt
copying django/conf/locale/lt/__init__.py -> build/lib/django/conf/locale/lt
copying django/conf/locale/lt/formats.py -> build/lib/django/conf/locale/lt
creating build/lib/django/conf/locale/lv
copying django/conf/locale/lv/__init__.py -> build/lib/django/conf/locale/lv
copying django/conf/locale/lv/formats.py -> build/lib/django/conf/locale/lv
creating build/lib/django/conf/locale/mk
copying django/conf/locale/mk/__init__.py -> build/lib/django/conf/locale/mk
copying django/conf/locale/mk/formats.py -> build/lib/django/conf/locale/mk
creating build/lib/django/conf/locale/ml
copying django/conf/locale/ml/__init__.py -> build/lib/django/conf/locale/ml
copying django/conf/locale/ml/formats.py -> build/lib/django/conf/locale/ml
creating build/lib/django/conf/locale/mn
copying django/conf/locale/mn/__init__.py -> build/lib/django/conf/locale/mn
copying django/conf/locale/mn/formats.py -> build/lib/django/conf/locale/mn
creating build/lib/django/conf/locale/nb
copying django/conf/locale/nb/__init__.py -> build/lib/django/conf/locale/nb
copying django/conf/locale/nb/formats.py -> build/lib/django/conf/locale/nb
creating build/lib/django/conf/locale/nl
copying django/conf/locale/nl/__init__.py -> build/lib/django/conf/locale/nl
copying django/conf/locale/nl/formats.py -> build/lib/django/conf/locale/nl
creating build/lib/django/conf/locale/nn
copying django/conf/locale/nn/__init__.py -> build/lib/django/conf/locale/nn
copying django/conf/locale/nn/formats.py -> build/lib/django/conf/locale/nn
creating build/lib/django/conf/locale/pl
copying django/conf/locale/pl/__init__.py -> build/lib/django/conf/locale/pl
copying django/conf/locale/pl/formats.py -> build/lib/django/conf/locale/pl
creating build/lib/django/conf/locale/pt
copying django/conf/locale/pt/__init__.py -> build/lib/django/conf/locale/pt
copying django/conf/locale/pt/formats.py -> build/lib/django/conf/locale/pt
creating build/lib/django/conf/locale/pt_BR
copying django/conf/locale/pt_BR/__init__.py -> build/lib/django/conf/locale/pt_BR
copying django/conf/locale/pt_BR/formats.py -> build/lib/django/conf/locale/pt_BR
creating build/lib/django/conf/locale/ro
copying django/conf/locale/ro/__init__.py -> build/lib/django/conf/locale/ro
copying django/conf/locale/ro/formats.py -> build/lib/django/conf/locale/ro
creating build/lib/django/conf/locale/ru
copying django/conf/locale/ru/__init__.py -> build/lib/django/conf/locale/ru
copying django/conf/locale/ru/formats.py -> build/lib/django/conf/locale/ru
creating build/lib/django/conf/locale/sk
copying django/conf/locale/sk/__init__.py -> build/lib/django/conf/locale/sk
copying django/conf/locale/sk/formats.py -> build/lib/django/conf/locale/sk
creating build/lib/django/conf/locale/sl
copying django/conf/locale/sl/__init__.py -> build/lib/django/conf/locale/sl
copying django/conf/locale/sl/formats.py -> build/lib/django/conf/locale/sl
creating build/lib/django/conf/locale/sq
copying django/conf/locale/sq/__init__.py -> build/lib/django/conf/locale/sq
copying django/conf/locale/sq/formats.py -> build/lib/django/conf/locale/sq
creating build/lib/django/conf/locale/sr
copying django/conf/locale/sr/__init__.py -> build/lib/django/conf/locale/sr
copying django/conf/locale/sr/formats.py -> build/lib/django/conf/locale/sr
creating build/lib/django/conf/locale/sr_Latn
copying django/conf/locale/sr_Latn/__init__.py -> build/lib/django/conf/locale/sr_Latn
copying django/conf/locale/sr_Latn/formats.py -> build/lib/django/conf/locale/sr_Latn
creating build/lib/django/conf/locale/sv
copying django/conf/locale/sv/__init__.py -> build/lib/django/conf/locale/sv
copying django/conf/locale/sv/formats.py -> build/lib/django/conf/locale/sv
creating build/lib/django/conf/locale/ta
copying django/conf/locale/ta/__init__.py -> build/lib/django/conf/locale/ta
copying django/conf/locale/ta/formats.py -> build/lib/django/conf/locale/ta
creating build/lib/django/conf/locale/te
copying django/conf/locale/te/__init__.py -> build/lib/django/conf/locale/te
copying django/conf/locale/te/formats.py -> build/lib/django/conf/locale/te
creating build/lib/django/conf/locale/tg
copying django/conf/locale/tg/__init__.py -> build/lib/django/conf/locale/tg
copying django/conf/locale/tg/formats.py -> build/lib/django/conf/locale/tg
creating build/lib/django/conf/locale/th
copying django/conf/locale/th/__init__.py -> build/lib/django/conf/locale/th
copying django/conf/locale/th/formats.py -> build/lib/django/conf/locale/th
creating build/lib/django/conf/locale/tk
copying django/conf/locale/tk/__init__.py -> build/lib/django/conf/locale/tk
copying django/conf/locale/tk/formats.py -> build/lib/django/conf/locale/tk
creating build/lib/django/conf/locale/tr
copying django/conf/locale/tr/__init__.py -> build/lib/django/conf/locale/tr
copying django/conf/locale/tr/formats.py -> build/lib/django/conf/locale/tr
creating build/lib/django/conf/locale/uk
copying django/conf/locale/uk/__init__.py -> build/lib/django/conf/locale/uk
copying django/conf/locale/uk/formats.py -> build/lib/django/conf/locale/uk
creating build/lib/django/conf/locale/uz
copying django/conf/locale/uz/__init__.py -> build/lib/django/conf/locale/uz
copying django/conf/locale/uz/formats.py -> build/lib/django/conf/locale/uz
creating build/lib/django/conf/locale/vi
copying django/conf/locale/vi/__init__.py -> build/lib/django/conf/locale/vi
copying django/conf/locale/vi/formats.py -> build/lib/django/conf/locale/vi
creating build/lib/django/conf/locale/zh_Hans
copying django/conf/locale/zh_Hans/__init__.py -> build/lib/django/conf/locale/zh_Hans
copying django/conf/locale/zh_Hans/formats.py -> build/lib/django/conf/locale/zh_Hans
creating build/lib/django/conf/locale/zh_Hant
copying django/conf/locale/zh_Hant/__init__.py -> build/lib/django/conf/locale/zh_Hant
copying django/conf/locale/zh_Hant/formats.py -> build/lib/django/conf/locale/zh_Hant
creating build/lib/django/contrib/admin
copying django/contrib/admin/__init__.py -> build/lib/django/contrib/admin
copying django/contrib/admin/actions.py -> build/lib/django/contrib/admin
copying django/contrib/admin/apps.py -> build/lib/django/contrib/admin
copying django/contrib/admin/checks.py -> build/lib/django/contrib/admin
copying django/contrib/admin/decorators.py -> build/lib/django/contrib/admin
copying django/contrib/admin/exceptions.py -> build/lib/django/contrib/admin
copying django/contrib/admin/filters.py -> build/lib/django/contrib/admin
copying django/contrib/admin/forms.py -> build/lib/django/contrib/admin
copying django/contrib/admin/helpers.py -> build/lib/django/contrib/admin
copying django/contrib/admin/models.py -> build/lib/django/contrib/admin
copying django/contrib/admin/options.py -> build/lib/django/contrib/admin
copying django/contrib/admin/sites.py -> build/lib/django/contrib/admin
copying django/contrib/admin/tests.py -> build/lib/django/contrib/admin
copying django/contrib/admin/utils.py -> build/lib/django/contrib/admin
copying django/contrib/admin/widgets.py -> build/lib/django/contrib/admin
creating build/lib/django/contrib/admindocs
copying django/contrib/admindocs/__init__.py -> build/lib/django/contrib/admindocs
copying django/contrib/admindocs/apps.py -> build/lib/django/contrib/admindocs
copying django/contrib/admindocs/middleware.py -> build/lib/django/contrib/admindocs
copying django/contrib/admindocs/urls.py -> build/lib/django/contrib/admindocs
copying django/contrib/admindocs/utils.py -> build/lib/django/contrib/admindocs
copying django/contrib/admindocs/views.py -> build/lib/django/contrib/admindocs
creating build/lib/django/contrib/auth
copying django/contrib/auth/__init__.py -> build/lib/django/contrib/auth
copying django/contrib/auth/admin.py -> build/lib/django/contrib/auth
copying django/contrib/auth/apps.py -> build/lib/django/contrib/auth
copying django/contrib/auth/backends.py -> build/lib/django/contrib/auth
copying django/contrib/auth/base_user.py -> build/lib/django/contrib/auth
copying django/contrib/auth/checks.py -> build/lib/django/contrib/auth
copying django/contrib/auth/context_processors.py -> build/lib/django/contrib/auth
copying django/contrib/auth/decorators.py -> build/lib/django/contrib/auth
copying django/contrib/auth/forms.py -> build/lib/django/contrib/auth
copying django/contrib/auth/hashers.py -> build/lib/django/contrib/auth
copying django/contrib/auth/middleware.py -> build/lib/django/contrib/auth
copying django/contrib/auth/mixins.py -> build/lib/django/contrib/auth
copying django/contrib/auth/models.py -> build/lib/django/contrib/auth
copying django/contrib/auth/password_validation.py -> build/lib/django/contrib/auth
copying django/contrib/auth/signals.py -> build/lib/django/contrib/auth
copying django/contrib/auth/tokens.py -> build/lib/django/contrib/auth
copying django/contrib/auth/urls.py -> build/lib/django/contrib/auth
copying django/contrib/auth/validators.py -> build/lib/django/contrib/auth
copying django/contrib/auth/views.py -> build/lib/django/contrib/auth
creating build/lib/django/contrib/contenttypes
copying django/contrib/contenttypes/__init__.py -> build/lib/django/contrib/contenttypes
copying django/contrib/contenttypes/admin.py -> build/lib/django/contrib/contenttypes
copying django/contrib/contenttypes/apps.py -> build/lib/django/contrib/contenttypes
copying django/contrib/contenttypes/checks.py -> build/lib/django/contrib/contenttypes
copying django/contrib/contenttypes/fields.py -> build/lib/django/contrib/contenttypes
copying django/contrib/contenttypes/forms.py -> build/lib/django/contrib/contenttypes
copying django/contrib/contenttypes/models.py -> build/lib/django/contrib/contenttypes
copying django/contrib/contenttypes/views.py -> build/lib/django/contrib/contenttypes
creating build/lib/django/contrib/flatpages
copying django/contrib/flatpages/__init__.py -> build/lib/django/contrib/flatpages
copying django/contrib/flatpages/admin.py -> build/lib/django/contrib/flatpages
copying django/contrib/flatpages/apps.py -> build/lib/django/contrib/flatpages
copying django/contrib/flatpages/forms.py -> build/lib/django/contrib/flatpages
copying django/contrib/flatpages/middleware.py -> build/lib/django/contrib/flatpages
copying django/contrib/flatpages/models.py -> build/lib/django/contrib/flatpages
copying django/contrib/flatpages/sitemaps.py -> build/lib/django/contrib/flatpages
copying django/contrib/flatpages/urls.py -> build/lib/django/contrib/flatpages
copying django/contrib/flatpages/views.py -> build/lib/django/contrib/flatpages
creating build/lib/django/contrib/gis
copying django/contrib/gis/__init__.py -> build/lib/django/contrib/gis
copying django/contrib/gis/apps.py -> build/lib/django/contrib/gis
copying django/contrib/gis/feeds.py -> build/lib/django/contrib/gis
copying django/contrib/gis/geometry.py -> build/lib/django/contrib/gis
copying django/contrib/gis/measure.py -> build/lib/django/contrib/gis
copying django/contrib/gis/ptr.py -> build/lib/django/contrib/gis
copying django/contrib/gis/shortcuts.py -> build/lib/django/contrib/gis
copying django/contrib/gis/views.py -> build/lib/django/contrib/gis
creating build/lib/django/contrib/humanize
copying django/contrib/humanize/__init__.py -> build/lib/django/contrib/humanize
copying django/contrib/humanize/apps.py -> build/lib/django/contrib/humanize
creating build/lib/django/contrib/messages
copying django/contrib/messages/__init__.py -> build/lib/django/contrib/messages
copying django/contrib/messages/api.py -> build/lib/django/contrib/messages
copying django/contrib/messages/apps.py -> build/lib/django/contrib/messages
copying django/contrib/messages/constants.py -> build/lib/django/contrib/messages
copying django/contrib/messages/context_processors.py -> build/lib/django/contrib/messages
copying django/contrib/messages/middleware.py -> build/lib/django/contrib/messages
copying django/contrib/messages/utils.py -> build/lib/django/contrib/messages
copying django/contrib/messages/views.py -> build/lib/django/contrib/messages
creating build/lib/django/contrib/postgres
copying django/contrib/postgres/__init__.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/apps.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/constraints.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/functions.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/indexes.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/lookups.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/operations.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/search.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/serializers.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/signals.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/utils.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/validators.py -> build/lib/django/contrib/postgres
creating build/lib/django/contrib/redirects
copying django/contrib/redirects/__init__.py -> build/lib/django/contrib/redirects
copying django/contrib/redirects/admin.py -> build/lib/django/contrib/redirects
copying django/contrib/redirects/apps.py -> build/lib/django/contrib/redirects
copying django/contrib/redirects/middleware.py -> build/lib/django/contrib/redirects
copying django/contrib/redirects/models.py -> build/lib/django/contrib/redirects
creating build/lib/django/contrib/sessions
copying django/contrib/sessions/__init__.py -> build/lib/django/contrib/sessions
copying django/contrib/sessions/apps.py -> build/lib/django/contrib/sessions
copying django/contrib/sessions/base_session.py -> build/lib/django/contrib/sessions
copying django/contrib/sessions/exceptions.py -> build/lib/django/contrib/sessions
copying django/contrib/sessions/middleware.py -> build/lib/django/contrib/sessions
copying django/contrib/sessions/models.py -> build/lib/django/contrib/sessions
copying django/contrib/sessions/serializers.py -> build/lib/django/contrib/sessions
creating build/lib/django/contrib/sitemaps
copying django/contrib/sitemaps/__init__.py -> build/lib/django/contrib/sitemaps
copying django/contrib/sitemaps/apps.py -> build/lib/django/contrib/sitemaps
copying django/contrib/sitemaps/views.py -> build/lib/django/contrib/sitemaps
creating build/lib/django/contrib/sites
copying django/contrib/sites/__init__.py -> build/lib/django/contrib/sites
copying django/contrib/sites/admin.py -> build/lib/django/contrib/sites
copying django/contrib/sites/apps.py -> build/lib/django/contrib/sites
copying django/contrib/sites/checks.py -> build/lib/django/contrib/sites
copying django/contrib/sites/management.py -> build/lib/django/contrib/sites
copying django/contrib/sites/managers.py -> build/lib/django/contrib/sites
copying django/contrib/sites/middleware.py -> build/lib/django/contrib/sites
copying django/contrib/sites/models.py -> build/lib/django/contrib/sites
copying django/contrib/sites/requests.py -> build/lib/django/contrib/sites
copying django/contrib/sites/shortcuts.py -> build/lib/django/contrib/sites
creating build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/__init__.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/apps.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/checks.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/finders.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/handlers.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/storage.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/testing.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/urls.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/utils.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/views.py -> build/lib/django/contrib/staticfiles
creating build/lib/django/contrib/syndication
copying django/contrib/syndication/__init__.py -> build/lib/django/contrib/syndication
copying django/contrib/syndication/apps.py -> build/lib/django/contrib/syndication
copying django/contrib/syndication/views.py -> build/lib/django/contrib/syndication
creating build/lib/django/contrib/admin/migrations
copying django/contrib/admin/migrations/0001_initial.py -> build/lib/django/contrib/admin/migrations
copying django/contrib/admin/migrations/0002_logentry_remove_auto_add.py -> build/lib/django/contrib/admin/migrations
copying django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py -> build/lib/django/contrib/admin/migrations
copying django/contrib/admin/migrations/__init__.py -> build/lib/django/contrib/admin/migrations
creating build/lib/django/contrib/admin/templatetags
copying django/contrib/admin/templatetags/__init__.py -> build/lib/django/contrib/admin/templatetags
copying django/contrib/admin/templatetags/admin_list.py -> build/lib/django/contrib/admin/templatetags
copying django/contrib/admin/templatetags/admin_modify.py -> build/lib/django/contrib/admin/templatetags
copying django/contrib/admin/templatetags/admin_urls.py -> build/lib/django/contrib/admin/templatetags
copying django/contrib/admin/templatetags/base.py -> build/lib/django/contrib/admin/templatetags
copying django/contrib/admin/templatetags/log.py -> build/lib/django/contrib/admin/templatetags
creating build/lib/django/contrib/admin/views
copying django/contrib/admin/views/__init__.py -> build/lib/django/contrib/admin/views
copying django/contrib/admin/views/autocomplete.py -> build/lib/django/contrib/admin/views
copying django/contrib/admin/views/decorators.py -> build/lib/django/contrib/admin/views
copying django/contrib/admin/views/main.py -> build/lib/django/contrib/admin/views
creating build/lib/django/contrib/auth/handlers
copying django/contrib/auth/handlers/__init__.py -> build/lib/django/contrib/auth/handlers
copying django/contrib/auth/handlers/modwsgi.py -> build/lib/django/contrib/auth/handlers
creating build/lib/django/contrib/auth/management
copying django/contrib/auth/management/__init__.py -> build/lib/django/contrib/auth/management
creating build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0001_initial.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0002_alter_permission_name_max_length.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0003_alter_user_email_max_length.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0004_alter_user_username_opts.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0005_alter_user_last_login_null.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0006_require_contenttypes_0002.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0008_alter_user_username_max_length.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0010_alter_group_name_max_length.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0011_update_proxy_permissions.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/__init__.py -> build/lib/django/contrib/auth/migrations
creating build/lib/django/contrib/auth/management/commands
copying django/contrib/auth/management/commands/__init__.py -> build/lib/django/contrib/auth/management/commands
copying django/contrib/auth/management/commands/changepassword.py -> build/lib/django/contrib/auth/management/commands
copying django/contrib/auth/management/commands/createsuperuser.py -> build/lib/django/contrib/auth/management/commands
creating build/lib/django/contrib/contenttypes/management
copying django/contrib/contenttypes/management/__init__.py -> build/lib/django/contrib/contenttypes/management
creating build/lib/django/contrib/contenttypes/migrations
copying django/contrib/contenttypes/migrations/0001_initial.py -> build/lib/django/contrib/contenttypes/migrations
copying django/contrib/contenttypes/migrations/0002_remove_content_type_name.py -> build/lib/django/contrib/contenttypes/migrations
copying django/contrib/contenttypes/migrations/__init__.py -> build/lib/django/contrib/contenttypes/migrations
creating build/lib/django/contrib/contenttypes/management/commands
copying django/contrib/contenttypes/management/commands/__init__.py -> build/lib/django/contrib/contenttypes/management/commands
copying django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py -> build/lib/django/contrib/contenttypes/management/commands
creating build/lib/django/contrib/flatpages/migrations
copying django/contrib/flatpages/migrations/0001_initial.py -> build/lib/django/contrib/flatpages/migrations
copying django/contrib/flatpages/migrations/__init__.py -> build/lib/django/contrib/flatpages/migrations
creating build/lib/django/contrib/flatpages/templatetags
copying django/contrib/flatpages/templatetags/__init__.py -> build/lib/django/contrib/flatpages/templatetags
copying django/contrib/flatpages/templatetags/flatpages.py -> build/lib/django/contrib/flatpages/templatetags
creating build/lib/django/contrib/gis/admin
copying django/contrib/gis/admin/__init__.py -> build/lib/django/contrib/gis/admin
copying django/contrib/gis/admin/options.py -> build/lib/django/contrib/gis/admin
copying django/contrib/gis/admin/widgets.py -> build/lib/django/contrib/gis/admin
creating build/lib/django/contrib/gis/db
copying django/contrib/gis/db/__init__.py -> build/lib/django/contrib/gis/db
creating build/lib/django/contrib/gis/forms
copying django/contrib/gis/forms/__init__.py -> build/lib/django/contrib/gis/forms
copying django/contrib/gis/forms/fields.py -> build/lib/django/contrib/gis/forms
copying django/contrib/gis/forms/widgets.py -> build/lib/django/contrib/gis/forms
creating build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/__init__.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/base.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/datasource.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/driver.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/envelope.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/error.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/feature.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/field.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/geometries.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/geomtype.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/layer.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/libgdal.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/srs.py -> build/lib/django/contrib/gis/gdal
creating build/lib/django/contrib/gis/geoip2
copying django/contrib/gis/geoip2/__init__.py -> build/lib/django/contrib/gis/geoip2
copying django/contrib/gis/geoip2/base.py -> build/lib/django/contrib/gis/geoip2
copying django/contrib/gis/geoip2/resources.py -> build/lib/django/contrib/gis/geoip2
creating build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/__init__.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/base.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/collections.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/coordseq.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/error.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/factory.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/geometry.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/io.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/libgeos.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/linestring.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/mutable_list.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/point.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/polygon.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/prepared.py -> build/lib/django/contrib/gis/geos
creating build/lib/django/contrib/gis/management
copying django/contrib/gis/management/__init__.py -> build/lib/django/contrib/gis/management
creating build/lib/django/contrib/gis/serializers
copying django/contrib/gis/serializers/__init__.py -> build/lib/django/contrib/gis/serializers
copying django/contrib/gis/serializers/geojson.py -> build/lib/django/contrib/gis/serializers
creating build/lib/django/contrib/gis/sitemaps
copying django/contrib/gis/sitemaps/__init__.py -> build/lib/django/contrib/gis/sitemaps
copying django/contrib/gis/sitemaps/kml.py -> build/lib/django/contrib/gis/sitemaps
copying django/contrib/gis/sitemaps/views.py -> build/lib/django/contrib/gis/sitemaps
creating build/lib/django/contrib/gis/utils
copying django/contrib/gis/utils/__init__.py -> build/lib/django/contrib/gis/utils
copying django/contrib/gis/utils/layermapping.py -> build/lib/django/contrib/gis/utils
copying django/contrib/gis/utils/ogrinfo.py -> build/lib/django/contrib/gis/utils
copying django/contrib/gis/utils/ogrinspect.py -> build/lib/django/contrib/gis/utils
copying django/contrib/gis/utils/srs.py -> build/lib/django/contrib/gis/utils
creating build/lib/django/contrib/gis/db/backends
copying django/contrib/gis/db/backends/__init__.py -> build/lib/django/contrib/gis/db/backends
copying django/contrib/gis/db/backends/utils.py -> build/lib/django/contrib/gis/db/backends
creating build/lib/django/contrib/gis/db/models
copying django/contrib/gis/db/models/__init__.py -> build/lib/django/contrib/gis/db/models
copying django/contrib/gis/db/models/aggregates.py -> build/lib/django/contrib/gis/db/models
copying django/contrib/gis/db/models/fields.py -> build/lib/django/contrib/gis/db/models
copying django/contrib/gis/db/models/functions.py -> build/lib/django/contrib/gis/db/models
copying django/contrib/gis/db/models/lookups.py -> build/lib/django/contrib/gis/db/models
copying django/contrib/gis/db/models/proxy.py -> build/lib/django/contrib/gis/db/models
creating build/lib/django/contrib/gis/db/backends/base
copying django/contrib/gis/db/backends/base/__init__.py -> build/lib/django/contrib/gis/db/backends/base
copying django/contrib/gis/db/backends/base/adapter.py -> build/lib/django/contrib/gis/db/backends/base
copying django/contrib/gis/db/backends/base/features.py -> build/lib/django/contrib/gis/db/backends/base
copying django/contrib/gis/db/backends/base/models.py -> build/lib/django/contrib/gis/db/backends/base
copying django/contrib/gis/db/backends/base/operations.py -> build/lib/django/contrib/gis/db/backends/base
creating build/lib/django/contrib/gis/db/backends/mysql
copying django/contrib/gis/db/backends/mysql/__init__.py -> build/lib/django/contrib/gis/db/backends/mysql
copying django/contrib/gis/db/backends/mysql/base.py -> build/lib/django/contrib/gis/db/backends/mysql
copying django/contrib/gis/db/backends/mysql/features.py -> build/lib/django/contrib/gis/db/backends/mysql
copying django/contrib/gis/db/backends/mysql/introspection.py -> build/lib/django/contrib/gis/db/backends/mysql
copying django/contrib/gis/db/backends/mysql/operations.py -> build/lib/django/contrib/gis/db/backends/mysql
copying django/contrib/gis/db/backends/mysql/schema.py -> build/lib/django/contrib/gis/db/backends/mysql
creating build/lib/django/contrib/gis/db/backends/oracle
copying django/contrib/gis/db/backends/oracle/__init__.py -> build/lib/django/contrib/gis/db/backends/oracle
copying django/contrib/gis/db/backends/oracle/adapter.py -> build/lib/django/contrib/gis/db/backends/oracle
copying django/contrib/gis/db/backends/oracle/base.py -> build/lib/django/contrib/gis/db/backends/oracle
copying django/contrib/gis/db/backends/oracle/features.py -> build/lib/django/contrib/gis/db/backends/oracle
copying django/contrib/gis/db/backends/oracle/introspection.py -> build/lib/django/contrib/gis/db/backends/oracle
copying django/contrib/gis/db/backends/oracle/models.py -> build/lib/django/contrib/gis/db/backends/oracle
copying django/contrib/gis/db/backends/oracle/operations.py -> build/lib/django/contrib/gis/db/backends/oracle
copying django/contrib/gis/db/backends/oracle/schema.py -> build/lib/django/contrib/gis/db/backends/oracle
creating build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/__init__.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/adapter.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/base.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/const.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/features.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/introspection.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/models.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/operations.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/pgraster.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/schema.py -> build/lib/django/contrib/gis/db/backends/postgis
creating build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/__init__.py -> build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/adapter.py -> build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/base.py -> build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/client.py -> build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/features.py -> build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/introspection.py -> build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/models.py -> build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/operations.py -> build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/schema.py -> build/lib/django/contrib/gis/db/backends/spatialite
creating build/lib/django/contrib/gis/db/models/sql
copying django/contrib/gis/db/models/sql/__init__.py -> build/lib/django/contrib/gis/db/models/sql
copying django/contrib/gis/db/models/sql/conversion.py -> build/lib/django/contrib/gis/db/models/sql
creating build/lib/django/contrib/gis/gdal/prototypes
copying django/contrib/gis/gdal/prototypes/__init__.py -> build/lib/django/contrib/gis/gdal/prototypes
copying django/contrib/gis/gdal/prototypes/ds.py -> build/lib/django/contrib/gis/gdal/prototypes
copying django/contrib/gis/gdal/prototypes/errcheck.py -> build/lib/django/contrib/gis/gdal/prototypes
copying django/contrib/gis/gdal/prototypes/generation.py -> build/lib/django/contrib/gis/gdal/prototypes
copying django/contrib/gis/gdal/prototypes/geom.py -> build/lib/django/contrib/gis/gdal/prototypes
copying django/contrib/gis/gdal/prototypes/raster.py -> build/lib/django/contrib/gis/gdal/prototypes
copying django/contrib/gis/gdal/prototypes/srs.py -> build/lib/django/contrib/gis/gdal/prototypes
creating build/lib/django/contrib/gis/gdal/raster
copying django/contrib/gis/gdal/raster/__init__.py -> build/lib/django/contrib/gis/gdal/raster
copying django/contrib/gis/gdal/raster/band.py -> build/lib/django/contrib/gis/gdal/raster
copying django/contrib/gis/gdal/raster/base.py -> build/lib/django/contrib/gis/gdal/raster
copying django/contrib/gis/gdal/raster/const.py -> build/lib/django/contrib/gis/gdal/raster
copying django/contrib/gis/gdal/raster/source.py -> build/lib/django/contrib/gis/gdal/raster
creating build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/__init__.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/coordseq.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/errcheck.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/geom.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/io.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/misc.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/predicates.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/prepared.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/threadsafe.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/topology.py -> build/lib/django/contrib/gis/geos/prototypes
creating build/lib/django/contrib/gis/management/commands
copying django/contrib/gis/management/commands/__init__.py -> build/lib/django/contrib/gis/management/commands
copying django/contrib/gis/management/commands/inspectdb.py -> build/lib/django/contrib/gis/management/commands
copying django/contrib/gis/management/commands/ogrinspect.py -> build/lib/django/contrib/gis/management/commands
creating build/lib/django/contrib/humanize/templatetags
copying django/contrib/humanize/templatetags/__init__.py -> build/lib/django/contrib/humanize/templatetags
copying django/contrib/humanize/templatetags/humanize.py -> build/lib/django/contrib/humanize/templatetags
creating build/lib/django/contrib/messages/storage
copying django/contrib/messages/storage/__init__.py -> build/lib/django/contrib/messages/storage
copying django/contrib/messages/storage/base.py -> build/lib/django/contrib/messages/storage
copying django/contrib/messages/storage/cookie.py -> build/lib/django/contrib/messages/storage
copying django/contrib/messages/storage/fallback.py -> build/lib/django/contrib/messages/storage
copying django/contrib/messages/storage/session.py -> build/lib/django/contrib/messages/storage
creating build/lib/django/contrib/postgres/aggregates
copying django/contrib/postgres/aggregates/__init__.py -> build/lib/django/contrib/postgres/aggregates
copying django/contrib/postgres/aggregates/general.py -> build/lib/django/contrib/postgres/aggregates
copying django/contrib/postgres/aggregates/mixins.py -> build/lib/django/contrib/postgres/aggregates
copying django/contrib/postgres/aggregates/statistics.py -> build/lib/django/contrib/postgres/aggregates
creating build/lib/django/contrib/postgres/fields
copying django/contrib/postgres/fields/__init__.py -> build/lib/django/contrib/postgres/fields
copying django/contrib/postgres/fields/array.py -> build/lib/django/contrib/postgres/fields
copying django/contrib/postgres/fields/citext.py -> build/lib/django/contrib/postgres/fields
copying django/contrib/postgres/fields/hstore.py -> build/lib/django/contrib/postgres/fields
copying django/contrib/postgres/fields/jsonb.py -> build/lib/django/contrib/postgres/fields
copying django/contrib/postgres/fields/ranges.py -> build/lib/django/contrib/postgres/fields
copying django/contrib/postgres/fields/utils.py -> build/lib/django/contrib/postgres/fields
creating build/lib/django/contrib/postgres/forms
copying django/contrib/postgres/forms/__init__.py -> build/lib/django/contrib/postgres/forms
copying django/contrib/postgres/forms/array.py -> build/lib/django/contrib/postgres/forms
copying django/contrib/postgres/forms/hstore.py -> build/lib/django/contrib/postgres/forms
copying django/contrib/postgres/forms/jsonb.py -> build/lib/django/contrib/postgres/forms
copying django/contrib/postgres/forms/ranges.py -> build/lib/django/contrib/postgres/forms
creating build/lib/django/contrib/redirects/migrations
copying django/contrib/redirects/migrations/0001_initial.py -> build/lib/django/contrib/redirects/migrations
copying django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py -> build/lib/django/contrib/redirects/migrations
copying django/contrib/redirects/migrations/__init__.py -> build/lib/django/contrib/redirects/migrations
creating build/lib/django/contrib/sessions/backends
copying django/contrib/sessions/backends/__init__.py -> build/lib/django/contrib/sessions/backends
copying django/contrib/sessions/backends/base.py -> build/lib/django/contrib/sessions/backends
copying django/contrib/sessions/backends/cache.py -> build/lib/django/contrib/sessions/backends
copying django/contrib/sessions/backends/cached_db.py -> build/lib/django/contrib/sessions/backends
copying django/contrib/sessions/backends/db.py -> build/lib/django/contrib/sessions/backends
copying django/contrib/sessions/backends/file.py -> build/lib/django/contrib/sessions/backends
copying django/contrib/sessions/backends/signed_cookies.py -> build/lib/django/contrib/sessions/backends
creating build/lib/django/contrib/sessions/management
copying django/contrib/sessions/management/__init__.py -> build/lib/django/contrib/sessions/management
creating build/lib/django/contrib/sessions/migrations
copying django/contrib/sessions/migrations/0001_initial.py -> build/lib/django/contrib/sessions/migrations
copying django/contrib/sessions/migrations/__init__.py -> build/lib/django/contrib/sessions/migrations
creating build/lib/django/contrib/sessions/management/commands
copying django/contrib/sessions/management/commands/__init__.py -> build/lib/django/contrib/sessions/management/commands
copying django/contrib/sessions/management/commands/clearsessions.py -> build/lib/django/contrib/sessions/management/commands
creating build/lib/django/contrib/sitemaps/management
copying django/contrib/sitemaps/management/__init__.py -> build/lib/django/contrib/sitemaps/management
creating build/lib/django/contrib/sitemaps/management/commands
copying django/contrib/sitemaps/management/commands/__init__.py -> build/lib/django/contrib/sitemaps/management/commands
copying django/contrib/sitemaps/management/commands/ping_google.py -> build/lib/django/contrib/sitemaps/management/commands
creating build/lib/django/contrib/sites/migrations
copying django/contrib/sites/migrations/0001_initial.py -> build/lib/django/contrib/sites/migrations
copying django/contrib/sites/migrations/0002_alter_domain_unique.py -> build/lib/django/contrib/sites/migrations
copying django/contrib/sites/migrations/__init__.py -> build/lib/django/contrib/sites/migrations
creating build/lib/django/contrib/staticfiles/management
copying django/contrib/staticfiles/management/__init__.py -> build/lib/django/contrib/staticfiles/management
creating build/lib/django/contrib/staticfiles/management/commands
copying django/contrib/staticfiles/management/commands/__init__.py -> build/lib/django/contrib/staticfiles/management/commands
copying django/contrib/staticfiles/management/commands/collectstatic.py -> build/lib/django/contrib/staticfiles/management/commands
copying django/contrib/staticfiles/management/commands/findstatic.py -> build/lib/django/contrib/staticfiles/management/commands
copying django/contrib/staticfiles/management/commands/runserver.py -> build/lib/django/contrib/staticfiles/management/commands
creating build/lib/django/core/cache
copying django/core/cache/__init__.py -> build/lib/django/core/cache
copying django/core/cache/utils.py -> build/lib/django/core/cache
creating build/lib/django/core/checks
copying django/core/checks/__init__.py -> build/lib/django/core/checks
copying django/core/checks/async_checks.py -> build/lib/django/core/checks
copying django/core/checks/caches.py -> build/lib/django/core/checks
copying django/core/checks/database.py -> build/lib/django/core/checks
copying django/core/checks/messages.py -> build/lib/django/core/checks
copying django/core/checks/model_checks.py -> build/lib/django/core/checks
copying django/core/checks/registry.py -> build/lib/django/core/checks
copying django/core/checks/templates.py -> build/lib/django/core/checks
copying django/core/checks/translation.py -> build/lib/django/core/checks
copying django/core/checks/urls.py -> build/lib/django/core/checks
creating build/lib/django/core/files
copying django/core/files/__init__.py -> build/lib/django/core/files
copying django/core/files/base.py -> build/lib/django/core/files
copying django/core/files/images.py -> build/lib/django/core/files
copying django/core/files/locks.py -> build/lib/django/core/files
copying django/core/files/move.py -> build/lib/django/core/files
copying django/core/files/storage.py -> build/lib/django/core/files
copying django/core/files/temp.py -> build/lib/django/core/files
copying django/core/files/uploadedfile.py -> build/lib/django/core/files
copying django/core/files/uploadhandler.py -> build/lib/django/core/files
copying django/core/files/utils.py -> build/lib/django/core/files
creating build/lib/django/core/handlers
copying django/core/handlers/__init__.py -> build/lib/django/core/handlers
copying django/core/handlers/asgi.py -> build/lib/django/core/handlers
copying django/core/handlers/base.py -> build/lib/django/core/handlers
copying django/core/handlers/exception.py -> build/lib/django/core/handlers
copying django/core/handlers/wsgi.py -> build/lib/django/core/handlers
creating build/lib/django/core/mail
copying django/core/mail/__init__.py -> build/lib/django/core/mail
copying django/core/mail/message.py -> build/lib/django/core/mail
copying django/core/mail/utils.py -> build/lib/django/core/mail
creating build/lib/django/core/management
copying django/core/management/__init__.py -> build/lib/django/core/management
copying django/core/management/base.py -> build/lib/django/core/management
copying django/core/management/color.py -> build/lib/django/core/management
copying django/core/management/sql.py -> build/lib/django/core/management
copying django/core/management/templates.py -> build/lib/django/core/management
copying django/core/management/utils.py -> build/lib/django/core/management
creating build/lib/django/core/serializers
copying django/core/serializers/__init__.py -> build/lib/django/core/serializers
copying django/core/serializers/base.py -> build/lib/django/core/serializers
copying django/core/serializers/json.py -> build/lib/django/core/serializers
copying django/core/serializers/jsonl.py -> build/lib/django/core/serializers
copying django/core/serializers/python.py -> build/lib/django/core/serializers
copying django/core/serializers/pyyaml.py -> build/lib/django/core/serializers
copying django/core/serializers/xml_serializer.py -> build/lib/django/core/serializers
creating build/lib/django/core/servers
copying django/core/servers/__init__.py -> build/lib/django/core/servers
copying django/core/servers/basehttp.py -> build/lib/django/core/servers
creating build/lib/django/core/cache/backends
copying django/core/cache/backends/__init__.py -> build/lib/django/core/cache/backends
copying django/core/cache/backends/base.py -> build/lib/django/core/cache/backends
copying django/core/cache/backends/db.py -> build/lib/django/core/cache/backends
copying django/core/cache/backends/dummy.py -> build/lib/django/core/cache/backends
copying django/core/cache/backends/filebased.py -> build/lib/django/core/cache/backends
copying django/core/cache/backends/locmem.py -> build/lib/django/core/cache/backends
copying django/core/cache/backends/memcached.py -> build/lib/django/core/cache/backends
creating build/lib/django/core/checks/compatibility
copying django/core/checks/compatibility/__init__.py -> build/lib/django/core/checks/compatibility
creating build/lib/django/core/checks/security
copying django/core/checks/security/__init__.py -> build/lib/django/core/checks/security
copying django/core/checks/security/base.py -> build/lib/django/core/checks/security
copying django/core/checks/security/csrf.py -> build/lib/django/core/checks/security
copying django/core/checks/security/sessions.py -> build/lib/django/core/checks/security
creating build/lib/django/core/mail/backends
copying django/core/mail/backends/__init__.py -> build/lib/django/core/mail/backends
copying django/core/mail/backends/base.py -> build/lib/django/core/mail/backends
copying django/core/mail/backends/console.py -> build/lib/django/core/mail/backends
copying django/core/mail/backends/dummy.py -> build/lib/django/core/mail/backends
copying django/core/mail/backends/filebased.py -> build/lib/django/core/mail/backends
copying django/core/mail/backends/locmem.py -> build/lib/django/core/mail/backends
copying django/core/mail/backends/smtp.py -> build/lib/django/core/mail/backends
creating build/lib/django/core/management/commands
copying django/core/management/commands/__init__.py -> build/lib/django/core/management/commands
copying django/core/management/commands/check.py -> build/lib/django/core/management/commands
copying django/core/management/commands/compilemessages.py -> build/lib/django/core/management/commands
copying django/core/management/commands/createcachetable.py -> build/lib/django/core/management/commands
copying django/core/management/commands/dbshell.py -> build/lib/django/core/management/commands
copying django/core/management/commands/diffsettings.py -> build/lib/django/core/management/commands
copying django/core/management/commands/dumpdata.py -> build/lib/django/core/management/commands
copying django/core/management/commands/flush.py -> build/lib/django/core/management/commands
copying django/core/management/commands/inspectdb.py -> build/lib/django/core/management/commands
copying django/core/management/commands/loaddata.py -> build/lib/django/core/management/commands
copying django/core/management/commands/makemessages.py -> build/lib/django/core/management/commands
copying django/core/management/commands/makemigrations.py -> build/lib/django/core/management/commands
copying django/core/management/commands/migrate.py -> build/lib/django/core/management/commands
copying django/core/management/commands/runserver.py -> build/lib/django/core/management/commands
copying django/core/management/commands/sendtestemail.py -> build/lib/django/core/management/commands
copying django/core/management/commands/shell.py -> build/lib/django/core/management/commands
copying django/core/management/commands/showmigrations.py -> build/lib/django/core/management/commands
copying django/core/management/commands/sqlflush.py -> build/lib/django/core/management/commands
copying django/core/management/commands/sqlmigrate.py -> build/lib/django/core/management/commands
copying django/core/management/commands/sqlsequencereset.py -> build/lib/django/core/management/commands
copying django/core/management/commands/squashmigrations.py -> build/lib/django/core/management/commands
copying django/core/management/commands/startapp.py -> build/lib/django/core/management/commands
copying django/core/management/commands/startproject.py -> build/lib/django/core/management/commands
copying django/core/management/commands/test.py -> build/lib/django/core/management/commands
copying django/core/management/commands/testserver.py -> build/lib/django/core/management/commands
creating build/lib/django/db/backends
copying django/db/backends/__init__.py -> build/lib/django/db/backends
copying django/db/backends/ddl_references.py -> build/lib/django/db/backends
copying django/db/backends/signals.py -> build/lib/django/db/backends
copying django/db/backends/utils.py -> build/lib/django/db/backends
creating build/lib/django/db/migrations
copying django/db/migrations/__init__.py -> build/lib/django/db/migrations
copying django/db/migrations/autodetector.py -> build/lib/django/db/migrations
copying django/db/migrations/exceptions.py -> build/lib/django/db/migrations
copying django/db/migrations/executor.py -> build/lib/django/db/migrations
copying django/db/migrations/graph.py -> build/lib/django/db/migrations
copying django/db/migrations/loader.py -> build/lib/django/db/migrations
copying django/db/migrations/migration.py -> build/lib/django/db/migrations
copying django/db/migrations/optimizer.py -> build/lib/django/db/migrations
copying django/db/migrations/questioner.py -> build/lib/django/db/migrations
copying django/db/migrations/recorder.py -> build/lib/django/db/migrations
copying django/db/migrations/serializer.py -> build/lib/django/db/migrations
copying django/db/migrations/state.py -> build/lib/django/db/migrations
copying django/db/migrations/utils.py -> build/lib/django/db/migrations
copying django/db/migrations/writer.py -> build/lib/django/db/migrations
creating build/lib/django/db/models
copying django/db/models/__init__.py -> build/lib/django/db/models
copying django/db/models/aggregates.py -> build/lib/django/db/models
copying django/db/models/base.py -> build/lib/django/db/models
copying django/db/models/constants.py -> build/lib/django/db/models
copying django/db/models/constraints.py -> build/lib/django/db/models
copying django/db/models/deletion.py -> build/lib/django/db/models
copying django/db/models/enums.py -> build/lib/django/db/models
copying django/db/models/expressions.py -> build/lib/django/db/models
copying django/db/models/indexes.py -> build/lib/django/db/models
copying django/db/models/lookups.py -> build/lib/django/db/models
copying django/db/models/manager.py -> build/lib/django/db/models
copying django/db/models/options.py -> build/lib/django/db/models
copying django/db/models/query.py -> build/lib/django/db/models
copying django/db/models/query_utils.py -> build/lib/django/db/models
copying django/db/models/signals.py -> build/lib/django/db/models
copying django/db/models/utils.py -> build/lib/django/db/models
creating build/lib/django/db/backends/base
copying django/db/backends/base/__init__.py -> build/lib/django/db/backends/base
copying django/db/backends/base/base.py -> build/lib/django/db/backends/base
copying django/db/backends/base/client.py -> build/lib/django/db/backends/base
copying django/db/backends/base/creation.py -> build/lib/django/db/backends/base
copying django/db/backends/base/features.py -> build/lib/django/db/backends/base
copying django/db/backends/base/introspection.py -> build/lib/django/db/backends/base
copying django/db/backends/base/operations.py -> build/lib/django/db/backends/base
copying django/db/backends/base/schema.py -> build/lib/django/db/backends/base
copying django/db/backends/base/validation.py -> build/lib/django/db/backends/base
creating build/lib/django/db/backends/dummy
copying django/db/backends/dummy/__init__.py -> build/lib/django/db/backends/dummy
copying django/db/backends/dummy/base.py -> build/lib/django/db/backends/dummy
copying django/db/backends/dummy/features.py -> build/lib/django/db/backends/dummy
creating build/lib/django/db/backends/mysql
copying django/db/backends/mysql/__init__.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/base.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/client.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/compiler.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/creation.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/features.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/introspection.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/operations.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/schema.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/validation.py -> build/lib/django/db/backends/mysql
creating build/lib/django/db/backends/oracle
copying django/db/backends/oracle/__init__.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/base.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/client.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/creation.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/features.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/functions.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/introspection.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/operations.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/schema.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/utils.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/validation.py -> build/lib/django/db/backends/oracle
creating build/lib/django/db/backends/postgresql
copying django/db/backends/postgresql/__init__.py -> build/lib/django/db/backends/postgresql
copying django/db/backends/postgresql/base.py -> build/lib/django/db/backends/postgresql
copying django/db/backends/postgresql/client.py -> build/lib/django/db/backends/postgresql
copying django/db/backends/postgresql/creation.py -> build/lib/django/db/backends/postgresql
copying django/db/backends/postgresql/features.py -> build/lib/django/db/backends/postgresql
copying django/db/backends/postgresql/introspection.py -> build/lib/django/db/backends/postgresql
copying django/db/backends/postgresql/operations.py -> build/lib/django/db/backends/postgresql
copying django/db/backends/postgresql/schema.py -> build/lib/django/db/backends/postgresql
creating build/lib/django/db/backends/sqlite3
copying django/db/backends/sqlite3/__init__.py -> build/lib/django/db/backends/sqlite3
copying django/db/backends/sqlite3/base.py -> build/lib/django/db/backends/sqlite3
copying django/db/backends/sqlite3/client.py -> build/lib/django/db/backends/sqlite3
copying django/db/backends/sqlite3/creation.py -> build/lib/django/db/backends/sqlite3
copying django/db/backends/sqlite3/features.py -> build/lib/django/db/backends/sqlite3
copying django/db/backends/sqlite3/introspection.py -> build/lib/django/db/backends/sqlite3
copying django/db/backends/sqlite3/operations.py -> build/lib/django/db/backends/sqlite3
copying django/db/backends/sqlite3/schema.py -> build/lib/django/db/backends/sqlite3
creating build/lib/django/db/migrations/operations
copying django/db/migrations/operations/__init__.py -> build/lib/django/db/migrations/operations
copying django/db/migrations/operations/base.py -> build/lib/django/db/migrations/operations
copying django/db/migrations/operations/fields.py -> build/lib/django/db/migrations/operations
copying django/db/migrations/operations/models.py -> build/lib/django/db/migrations/operations
copying django/db/migrations/operations/special.py -> build/lib/django/db/migrations/operations
copying django/db/migrations/operations/utils.py -> build/lib/django/db/migrations/operations
creating build/lib/django/db/models/fields
copying django/db/models/fields/__init__.py -> build/lib/django/db/models/fields
copying django/db/models/fields/files.py -> build/lib/django/db/models/fields
copying django/db/models/fields/json.py -> build/lib/django/db/models/fields
copying django/db/models/fields/mixins.py -> build/lib/django/db/models/fields
copying django/db/models/fields/proxy.py -> build/lib/django/db/models/fields
copying django/db/models/fields/related.py -> build/lib/django/db/models/fields
copying django/db/models/fields/related_descriptors.py -> build/lib/django/db/models/fields
copying django/db/models/fields/related_lookups.py -> build/lib/django/db/models/fields
copying django/db/models/fields/reverse_related.py -> build/lib/django/db/models/fields
creating build/lib/django/db/models/functions
copying django/db/models/functions/__init__.py -> build/lib/django/db/models/functions
copying django/db/models/functions/comparison.py -> build/lib/django/db/models/functions
copying django/db/models/functions/datetime.py -> build/lib/django/db/models/functions
copying django/db/models/functions/math.py -> build/lib/django/db/models/functions
copying django/db/models/functions/mixins.py -> build/lib/django/db/models/functions
copying django/db/models/functions/text.py -> build/lib/django/db/models/functions
copying django/db/models/functions/window.py -> build/lib/django/db/models/functions
creating build/lib/django/db/models/sql
copying django/db/models/sql/__init__.py -> build/lib/django/db/models/sql
copying django/db/models/sql/compiler.py -> build/lib/django/db/models/sql
copying django/db/models/sql/constants.py -> build/lib/django/db/models/sql
copying django/db/models/sql/datastructures.py -> build/lib/django/db/models/sql
copying django/db/models/sql/query.py -> build/lib/django/db/models/sql
copying django/db/models/sql/subqueries.py -> build/lib/django/db/models/sql
copying django/db/models/sql/where.py -> build/lib/django/db/models/sql
creating build/lib/django/template/backends
copying django/template/backends/__init__.py -> build/lib/django/template/backends
copying django/template/backends/base.py -> build/lib/django/template/backends
copying django/template/backends/django.py -> build/lib/django/template/backends
copying django/template/backends/dummy.py -> build/lib/django/template/backends
copying django/template/backends/jinja2.py -> build/lib/django/template/backends
copying django/template/backends/utils.py -> build/lib/django/template/backends
creating build/lib/django/template/loaders
copying django/template/loaders/__init__.py -> build/lib/django/template/loaders
copying django/template/loaders/app_directories.py -> build/lib/django/template/loaders
copying django/template/loaders/base.py -> build/lib/django/template/loaders
copying django/template/loaders/cached.py -> build/lib/django/template/loaders
copying django/template/loaders/filesystem.py -> build/lib/django/template/loaders
copying django/template/loaders/locmem.py -> build/lib/django/template/loaders
creating build/lib/django/utils/translation
copying django/utils/translation/__init__.py -> build/lib/django/utils/translation
copying django/utils/translation/reloader.py -> build/lib/django/utils/translation
copying django/utils/translation/template.py -> build/lib/django/utils/translation
copying django/utils/translation/trans_null.py -> build/lib/django/utils/translation
copying django/utils/translation/trans_real.py -> build/lib/django/utils/translation
creating build/lib/django/views/decorators
copying django/views/decorators/__init__.py -> build/lib/django/views/decorators
copying django/views/decorators/cache.py -> build/lib/django/views/decorators
copying django/views/decorators/clickjacking.py -> build/lib/django/views/decorators
copying django/views/decorators/common.py -> build/lib/django/views/decorators
copying django/views/decorators/csrf.py -> build/lib/django/views/decorators
copying django/views/decorators/debug.py -> build/lib/django/views/decorators
copying django/views/decorators/gzip.py -> build/lib/django/views/decorators
copying django/views/decorators/http.py -> build/lib/django/views/decorators
copying django/views/decorators/vary.py -> build/lib/django/views/decorators
creating build/lib/django/views/generic
copying django/views/generic/__init__.py -> build/lib/django/views/generic
copying django/views/generic/base.py -> build/lib/django/views/generic
copying django/views/generic/dates.py -> build/lib/django/views/generic
copying django/views/generic/detail.py -> build/lib/django/views/generic
copying django/views/generic/edit.py -> build/lib/django/views/generic
copying django/views/generic/list.py -> build/lib/django/views/generic
running egg_info
writing Django.egg-info/PKG-INFO
writing dependency_links to Django.egg-info/dependency_links.txt
writing entry points to Django.egg-info/entry_points.txt
writing requirements to Django.egg-info/requires.txt
writing top-level names to Django.egg-info/top_level.txt
reading manifest file 'Django.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '__pycache__' found anywhere in distribution
adding license file 'LICENSE'
adding license file 'LICENSE.python'
adding license file 'AUTHORS'
writing manifest file 'Django.egg-info/SOURCES.txt'
/usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _Warning: Package 'django.bin' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.bin' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'django.bin' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'django.bin' to be distributed and are
        already explicitly excluding 'django.bin' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _Warning: Package 'django.contrib.admin.static.admin.fonts' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django.contrib.admin.static.admin.fonts' as an importable package[^1],
        but it is absent 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.fonts' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more 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.fonts' to be distributed and are
        already explicitly excluding 'django.contrib.admin.static.admin.fonts' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:218: _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)
creating build/lib/django/bin
copying django/bin/django-admin.py -> build/lib/django/bin
creating build/lib/django/conf/app_template
copying django/conf/app_template/__init__.py-tpl -> build/lib/django/conf/app_template
copying django/conf/app_template/admin.py-tpl -> build/lib/django/conf/app_template
copying django/conf/app_template/apps.py-tpl -> build/lib/django/conf/app_template
copying django/conf/app_template/models.py-tpl -> build/lib/django/conf/app_template
copying django/conf/app_template/tests.py-tpl -> build/lib/django/conf/app_template
copying django/conf/app_template/views.py-tpl -> build/lib/django/conf/app_template
creating build/lib/django/conf/app_template/migrations
copying django/conf/app_template/migrations/__init__.py-tpl -> build/lib/django/conf/app_template/migrations
creating build/lib/django/conf/project_template
copying django/conf/project_template/manage.py-tpl -> build/lib/django/conf/project_template
creating build/lib/django/conf/project_template/project_name
copying django/conf/project_template/project_name/__init__.py-tpl -> build/lib/django/conf/project_template/project_name
copying django/conf/project_template/project_name/asgi.py-tpl -> build/lib/django/conf/project_template/project_name
copying django/conf/project_template/project_name/settings.py-tpl -> build/lib/django/conf/project_template/project_name
copying django/conf/project_template/project_name/urls.py-tpl -> build/lib/django/conf/project_template/project_name
copying django/conf/project_template/project_name/wsgi.py-tpl -> build/lib/django/conf/project_template/project_name
copying django/dispatch/license.txt -> build/lib/django/dispatch
creating build/lib/django/forms/jinja2
creating build/lib/django/forms/jinja2/django
creating build/lib/django/forms/jinja2/django/forms
creating build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/attrs.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/checkbox.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/checkbox_option.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/checkbox_select.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/clearable_file_input.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/date.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/datetime.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/email.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/file.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/hidden.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/input.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/input_option.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/multiple_hidden.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/multiple_input.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/multiwidget.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/number.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/password.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/radio.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/radio_option.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/select.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/select_date.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/select_option.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/splitdatetime.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/splithiddendatetime.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/text.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/textarea.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/time.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/url.html -> build/lib/django/forms/jinja2/django/forms/widgets
creating build/lib/django/forms/templates
creating build/lib/django/forms/templates/django
creating build/lib/django/forms/templates/django/forms
creating build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/attrs.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/checkbox.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/checkbox_option.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/checkbox_select.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/clearable_file_input.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/date.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/datetime.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/email.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/file.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/hidden.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/input.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/input_option.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/multiple_hidden.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/multiple_input.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/multiwidget.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/number.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/password.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/radio.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/radio_option.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/select.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/select_date.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/select_option.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/splitdatetime.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/splithiddendatetime.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/text.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/textarea.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/time.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/url.html -> build/lib/django/forms/templates/django/forms/widgets
creating build/lib/django/views/templates
copying django/views/templates/default_urlconf.html -> build/lib/django/views/templates
copying django/views/templates/technical_404.html -> build/lib/django/views/templates
copying django/views/templates/technical_500.html -> build/lib/django/views/templates
copying django/views/templates/technical_500.txt -> build/lib/django/views/templates
creating build/lib/django/conf/locale/af
creating build/lib/django/conf/locale/af/LC_MESSAGES
copying django/conf/locale/af/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/af/LC_MESSAGES
copying django/conf/locale/af/LC_MESSAGES/django.po -> build/lib/django/conf/locale/af/LC_MESSAGES
creating build/lib/django/conf/locale/ast
creating build/lib/django/conf/locale/ast/LC_MESSAGES
copying django/conf/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ast/LC_MESSAGES
copying django/conf/locale/ast/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ast/LC_MESSAGES
creating build/lib/django/conf/locale/be
creating build/lib/django/conf/locale/be/LC_MESSAGES
copying django/conf/locale/be/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/be/LC_MESSAGES
copying django/conf/locale/be/LC_MESSAGES/django.po -> build/lib/django/conf/locale/be/LC_MESSAGES
creating build/lib/django/conf/locale/br
creating build/lib/django/conf/locale/br/LC_MESSAGES
copying django/conf/locale/br/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/br/LC_MESSAGES
copying django/conf/locale/br/LC_MESSAGES/django.po -> build/lib/django/conf/locale/br/LC_MESSAGES
creating build/lib/django/conf/locale/dsb
creating build/lib/django/conf/locale/dsb/LC_MESSAGES
copying django/conf/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/dsb/LC_MESSAGES
copying django/conf/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/dsb/LC_MESSAGES
creating build/lib/django/conf/locale/es_VE
creating build/lib/django/conf/locale/es_VE/LC_MESSAGES
copying django/conf/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_VE/LC_MESSAGES
copying django/conf/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_VE/LC_MESSAGES
creating build/lib/django/conf/locale/hsb
creating build/lib/django/conf/locale/hsb/LC_MESSAGES
copying django/conf/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hsb/LC_MESSAGES
copying django/conf/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hsb/LC_MESSAGES
creating build/lib/django/conf/locale/hy
creating build/lib/django/conf/locale/hy/LC_MESSAGES
copying django/conf/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hy/LC_MESSAGES
copying django/conf/locale/hy/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hy/LC_MESSAGES
creating build/lib/django/conf/locale/ia
creating build/lib/django/conf/locale/ia/LC_MESSAGES
copying django/conf/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ia/LC_MESSAGES
copying django/conf/locale/ia/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ia/LC_MESSAGES
creating build/lib/django/conf/locale/io
creating build/lib/django/conf/locale/io/LC_MESSAGES
copying django/conf/locale/io/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/io/LC_MESSAGES
copying django/conf/locale/io/LC_MESSAGES/django.po -> build/lib/django/conf/locale/io/LC_MESSAGES
creating build/lib/django/conf/locale/kab
creating build/lib/django/conf/locale/kab/LC_MESSAGES
copying django/conf/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/kab/LC_MESSAGES
copying django/conf/locale/kab/LC_MESSAGES/django.po -> build/lib/django/conf/locale/kab/LC_MESSAGES
creating build/lib/django/conf/locale/kk
creating build/lib/django/conf/locale/kk/LC_MESSAGES
copying django/conf/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/kk/LC_MESSAGES
copying django/conf/locale/kk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/kk/LC_MESSAGES
creating build/lib/django/conf/locale/lb
creating build/lib/django/conf/locale/lb/LC_MESSAGES
copying django/conf/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/lb/LC_MESSAGES
copying django/conf/locale/lb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/lb/LC_MESSAGES
creating build/lib/django/conf/locale/mr
creating build/lib/django/conf/locale/mr/LC_MESSAGES
copying django/conf/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/mr/LC_MESSAGES
copying django/conf/locale/mr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/mr/LC_MESSAGES
creating build/lib/django/conf/locale/my
creating build/lib/django/conf/locale/my/LC_MESSAGES
copying django/conf/locale/my/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/my/LC_MESSAGES
copying django/conf/locale/my/LC_MESSAGES/django.po -> build/lib/django/conf/locale/my/LC_MESSAGES
creating build/lib/django/conf/locale/ne
creating build/lib/django/conf/locale/ne/LC_MESSAGES
copying django/conf/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ne/LC_MESSAGES
copying django/conf/locale/ne/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ne/LC_MESSAGES
creating build/lib/django/conf/locale/os
creating build/lib/django/conf/locale/os/LC_MESSAGES
copying django/conf/locale/os/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/os/LC_MESSAGES
copying django/conf/locale/os/LC_MESSAGES/django.po -> build/lib/django/conf/locale/os/LC_MESSAGES
creating build/lib/django/conf/locale/pa
creating build/lib/django/conf/locale/pa/LC_MESSAGES
copying django/conf/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pa/LC_MESSAGES
copying django/conf/locale/pa/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pa/LC_MESSAGES
creating build/lib/django/conf/locale/sw
creating build/lib/django/conf/locale/sw/LC_MESSAGES
copying django/conf/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sw/LC_MESSAGES
copying django/conf/locale/sw/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sw/LC_MESSAGES
creating build/lib/django/conf/locale/tt
creating build/lib/django/conf/locale/tt/LC_MESSAGES
copying django/conf/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tt/LC_MESSAGES
copying django/conf/locale/tt/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tt/LC_MESSAGES
creating build/lib/django/conf/locale/udm
creating build/lib/django/conf/locale/udm/LC_MESSAGES
copying django/conf/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/udm/LC_MESSAGES
copying django/conf/locale/udm/LC_MESSAGES/django.po -> build/lib/django/conf/locale/udm/LC_MESSAGES
creating build/lib/django/conf/locale/ur
creating build/lib/django/conf/locale/ur/LC_MESSAGES
copying django/conf/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ur/LC_MESSAGES
copying django/conf/locale/ur/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ur/LC_MESSAGES
creating build/lib/django/conf/locale/ar/LC_MESSAGES
copying django/conf/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ar/LC_MESSAGES
copying django/conf/locale/ar/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ar/LC_MESSAGES
creating build/lib/django/conf/locale/ar_DZ/LC_MESSAGES
copying django/conf/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ar_DZ/LC_MESSAGES
copying django/conf/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/conf/locale/az/LC_MESSAGES
copying django/conf/locale/az/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/az/LC_MESSAGES
copying django/conf/locale/az/LC_MESSAGES/django.po -> build/lib/django/conf/locale/az/LC_MESSAGES
creating build/lib/django/conf/locale/bg/LC_MESSAGES
copying django/conf/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bg/LC_MESSAGES
copying django/conf/locale/bg/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bg/LC_MESSAGES
creating build/lib/django/conf/locale/bn/LC_MESSAGES
copying django/conf/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bn/LC_MESSAGES
copying django/conf/locale/bn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bn/LC_MESSAGES
creating build/lib/django/conf/locale/bs/LC_MESSAGES
copying django/conf/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bs/LC_MESSAGES
copying django/conf/locale/bs/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bs/LC_MESSAGES
creating build/lib/django/conf/locale/ca/LC_MESSAGES
copying django/conf/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ca/LC_MESSAGES
copying django/conf/locale/ca/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ca/LC_MESSAGES
creating build/lib/django/conf/locale/cs/LC_MESSAGES
copying django/conf/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/cs/LC_MESSAGES
copying django/conf/locale/cs/LC_MESSAGES/django.po -> build/lib/django/conf/locale/cs/LC_MESSAGES
creating build/lib/django/conf/locale/cy/LC_MESSAGES
copying django/conf/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/cy/LC_MESSAGES
copying django/conf/locale/cy/LC_MESSAGES/django.po -> build/lib/django/conf/locale/cy/LC_MESSAGES
creating build/lib/django/conf/locale/da/LC_MESSAGES
copying django/conf/locale/da/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/da/LC_MESSAGES
copying django/conf/locale/da/LC_MESSAGES/django.po -> build/lib/django/conf/locale/da/LC_MESSAGES
creating build/lib/django/conf/locale/de/LC_MESSAGES
copying django/conf/locale/de/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/de/LC_MESSAGES
copying django/conf/locale/de/LC_MESSAGES/django.po -> build/lib/django/conf/locale/de/LC_MESSAGES
creating build/lib/django/conf/locale/el/LC_MESSAGES
copying django/conf/locale/el/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/el/LC_MESSAGES
copying django/conf/locale/el/LC_MESSAGES/django.po -> build/lib/django/conf/locale/el/LC_MESSAGES
creating build/lib/django/conf/locale/en/LC_MESSAGES
copying django/conf/locale/en/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en/LC_MESSAGES
copying django/conf/locale/en/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en/LC_MESSAGES
creating build/lib/django/conf/locale/en_AU/LC_MESSAGES
copying django/conf/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en_AU/LC_MESSAGES
copying django/conf/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en_AU/LC_MESSAGES
creating build/lib/django/conf/locale/en_GB/LC_MESSAGES
copying django/conf/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en_GB/LC_MESSAGES
copying django/conf/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en_GB/LC_MESSAGES
creating build/lib/django/conf/locale/eo/LC_MESSAGES
copying django/conf/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/eo/LC_MESSAGES
copying django/conf/locale/eo/LC_MESSAGES/django.po -> build/lib/django/conf/locale/eo/LC_MESSAGES
creating build/lib/django/conf/locale/es/LC_MESSAGES
copying django/conf/locale/es/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es/LC_MESSAGES
copying django/conf/locale/es/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es/LC_MESSAGES
creating build/lib/django/conf/locale/es_AR/LC_MESSAGES
copying django/conf/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_AR/LC_MESSAGES
copying django/conf/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_AR/LC_MESSAGES
creating build/lib/django/conf/locale/es_CO/LC_MESSAGES
copying django/conf/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_CO/LC_MESSAGES
copying django/conf/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_CO/LC_MESSAGES
creating build/lib/django/conf/locale/es_MX/LC_MESSAGES
copying django/conf/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_MX/LC_MESSAGES
copying django/conf/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_MX/LC_MESSAGES
creating build/lib/django/conf/locale/et/LC_MESSAGES
copying django/conf/locale/et/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/et/LC_MESSAGES
copying django/conf/locale/et/LC_MESSAGES/django.po -> build/lib/django/conf/locale/et/LC_MESSAGES
creating build/lib/django/conf/locale/eu/LC_MESSAGES
copying django/conf/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/eu/LC_MESSAGES
copying django/conf/locale/eu/LC_MESSAGES/django.po -> build/lib/django/conf/locale/eu/LC_MESSAGES
creating build/lib/django/conf/locale/fa/LC_MESSAGES
copying django/conf/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fa/LC_MESSAGES
copying django/conf/locale/fa/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fa/LC_MESSAGES
creating build/lib/django/conf/locale/fi/LC_MESSAGES
copying django/conf/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fi/LC_MESSAGES
copying django/conf/locale/fi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fi/LC_MESSAGES
creating build/lib/django/conf/locale/fr/LC_MESSAGES
copying django/conf/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fr/LC_MESSAGES
copying django/conf/locale/fr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fr/LC_MESSAGES
creating build/lib/django/conf/locale/fy/LC_MESSAGES
copying django/conf/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fy/LC_MESSAGES
copying django/conf/locale/fy/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fy/LC_MESSAGES
creating build/lib/django/conf/locale/ga/LC_MESSAGES
copying django/conf/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ga/LC_MESSAGES
copying django/conf/locale/ga/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ga/LC_MESSAGES
creating build/lib/django/conf/locale/gd/LC_MESSAGES
copying django/conf/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/gd/LC_MESSAGES
copying django/conf/locale/gd/LC_MESSAGES/django.po -> build/lib/django/conf/locale/gd/LC_MESSAGES
creating build/lib/django/conf/locale/gl/LC_MESSAGES
copying django/conf/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/gl/LC_MESSAGES
copying django/conf/locale/gl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/gl/LC_MESSAGES
creating build/lib/django/conf/locale/he/LC_MESSAGES
copying django/conf/locale/he/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/he/LC_MESSAGES
copying django/conf/locale/he/LC_MESSAGES/django.po -> build/lib/django/conf/locale/he/LC_MESSAGES
creating build/lib/django/conf/locale/hi/LC_MESSAGES
copying django/conf/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hi/LC_MESSAGES
copying django/conf/locale/hi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hi/LC_MESSAGES
creating build/lib/django/conf/locale/hr/LC_MESSAGES
copying django/conf/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hr/LC_MESSAGES
copying django/conf/locale/hr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hr/LC_MESSAGES
creating build/lib/django/conf/locale/hu/LC_MESSAGES
copying django/conf/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hu/LC_MESSAGES
copying django/conf/locale/hu/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hu/LC_MESSAGES
creating build/lib/django/conf/locale/id/LC_MESSAGES
copying django/conf/locale/id/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/id/LC_MESSAGES
copying django/conf/locale/id/LC_MESSAGES/django.po -> build/lib/django/conf/locale/id/LC_MESSAGES
creating build/lib/django/conf/locale/ig/LC_MESSAGES
copying django/conf/locale/ig/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ig/LC_MESSAGES
copying django/conf/locale/ig/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ig/LC_MESSAGES
creating build/lib/django/conf/locale/is/LC_MESSAGES
copying django/conf/locale/is/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/is/LC_MESSAGES
copying django/conf/locale/is/LC_MESSAGES/django.po -> build/lib/django/conf/locale/is/LC_MESSAGES
creating build/lib/django/conf/locale/it/LC_MESSAGES
copying django/conf/locale/it/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/it/LC_MESSAGES
copying django/conf/locale/it/LC_MESSAGES/django.po -> build/lib/django/conf/locale/it/LC_MESSAGES
creating build/lib/django/conf/locale/ja/LC_MESSAGES
copying django/conf/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ja/LC_MESSAGES
copying django/conf/locale/ja/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ja/LC_MESSAGES
creating build/lib/django/conf/locale/ka/LC_MESSAGES
copying django/conf/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ka/LC_MESSAGES
copying django/conf/locale/ka/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ka/LC_MESSAGES
creating build/lib/django/conf/locale/km/LC_MESSAGES
copying django/conf/locale/km/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/km/LC_MESSAGES
copying django/conf/locale/km/LC_MESSAGES/django.po -> build/lib/django/conf/locale/km/LC_MESSAGES
creating build/lib/django/conf/locale/kn/LC_MESSAGES
copying django/conf/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/kn/LC_MESSAGES
copying django/conf/locale/kn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/kn/LC_MESSAGES
creating build/lib/django/conf/locale/ko/LC_MESSAGES
copying django/conf/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ko/LC_MESSAGES
copying django/conf/locale/ko/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ko/LC_MESSAGES
creating build/lib/django/conf/locale/ky/LC_MESSAGES
copying django/conf/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ky/LC_MESSAGES
copying django/conf/locale/ky/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ky/LC_MESSAGES
creating build/lib/django/conf/locale/lt/LC_MESSAGES
copying django/conf/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/lt/LC_MESSAGES
copying django/conf/locale/lt/LC_MESSAGES/django.po -> build/lib/django/conf/locale/lt/LC_MESSAGES
creating build/lib/django/conf/locale/lv/LC_MESSAGES
copying django/conf/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/lv/LC_MESSAGES
copying django/conf/locale/lv/LC_MESSAGES/django.po -> build/lib/django/conf/locale/lv/LC_MESSAGES
creating build/lib/django/conf/locale/mk/LC_MESSAGES
copying django/conf/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/mk/LC_MESSAGES
copying django/conf/locale/mk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/mk/LC_MESSAGES
creating build/lib/django/conf/locale/ml/LC_MESSAGES
copying django/conf/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ml/LC_MESSAGES
copying django/conf/locale/ml/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ml/LC_MESSAGES
creating build/lib/django/conf/locale/mn/LC_MESSAGES
copying django/conf/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/mn/LC_MESSAGES
copying django/conf/locale/mn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/mn/LC_MESSAGES
creating build/lib/django/conf/locale/nb/LC_MESSAGES
copying django/conf/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nb/LC_MESSAGES
copying django/conf/locale/nb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nb/LC_MESSAGES
creating build/lib/django/conf/locale/nl/LC_MESSAGES
copying django/conf/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nl/LC_MESSAGES
copying django/conf/locale/nl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nl/LC_MESSAGES
creating build/lib/django/conf/locale/nn/LC_MESSAGES
copying django/conf/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nn/LC_MESSAGES
copying django/conf/locale/nn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nn/LC_MESSAGES
creating build/lib/django/conf/locale/pl/LC_MESSAGES
copying django/conf/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pl/LC_MESSAGES
copying django/conf/locale/pl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pl/LC_MESSAGES
creating build/lib/django/conf/locale/pt/LC_MESSAGES
copying django/conf/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pt/LC_MESSAGES
copying django/conf/locale/pt/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pt/LC_MESSAGES
creating build/lib/django/conf/locale/pt_BR/LC_MESSAGES
copying django/conf/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pt_BR/LC_MESSAGES
copying django/conf/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pt_BR/LC_MESSAGES
creating build/lib/django/conf/locale/ro/LC_MESSAGES
copying django/conf/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ro/LC_MESSAGES
copying django/conf/locale/ro/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ro/LC_MESSAGES
creating build/lib/django/conf/locale/ru/LC_MESSAGES
copying django/conf/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ru/LC_MESSAGES
copying django/conf/locale/ru/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ru/LC_MESSAGES
creating build/lib/django/conf/locale/sk/LC_MESSAGES
copying django/conf/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sk/LC_MESSAGES
copying django/conf/locale/sk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sk/LC_MESSAGES
creating build/lib/django/conf/locale/sl/LC_MESSAGES
copying django/conf/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sl/LC_MESSAGES
copying django/conf/locale/sl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sl/LC_MESSAGES
creating build/lib/django/conf/locale/sq/LC_MESSAGES
copying django/conf/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sq/LC_MESSAGES
copying django/conf/locale/sq/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sq/LC_MESSAGES
creating build/lib/django/conf/locale/sr/LC_MESSAGES
copying django/conf/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sr/LC_MESSAGES
copying django/conf/locale/sr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sr/LC_MESSAGES
creating build/lib/django/conf/locale/sr_Latn/LC_MESSAGES
copying django/conf/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sr_Latn/LC_MESSAGES
copying django/conf/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/conf/locale/sv/LC_MESSAGES
copying django/conf/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sv/LC_MESSAGES
copying django/conf/locale/sv/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sv/LC_MESSAGES
creating build/lib/django/conf/locale/ta/LC_MESSAGES
copying django/conf/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ta/LC_MESSAGES
copying django/conf/locale/ta/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ta/LC_MESSAGES
creating build/lib/django/conf/locale/te/LC_MESSAGES
copying django/conf/locale/te/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/te/LC_MESSAGES
copying django/conf/locale/te/LC_MESSAGES/django.po -> build/lib/django/conf/locale/te/LC_MESSAGES
creating build/lib/django/conf/locale/tg/LC_MESSAGES
copying django/conf/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tg/LC_MESSAGES
copying django/conf/locale/tg/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tg/LC_MESSAGES
creating build/lib/django/conf/locale/th/LC_MESSAGES
copying django/conf/locale/th/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/th/LC_MESSAGES
copying django/conf/locale/th/LC_MESSAGES/django.po -> build/lib/django/conf/locale/th/LC_MESSAGES
creating build/lib/django/conf/locale/tk/LC_MESSAGES
copying django/conf/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tk/LC_MESSAGES
copying django/conf/locale/tk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tk/LC_MESSAGES
creating build/lib/django/conf/locale/tr/LC_MESSAGES
copying django/conf/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tr/LC_MESSAGES
copying django/conf/locale/tr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tr/LC_MESSAGES
creating build/lib/django/conf/locale/uk/LC_MESSAGES
copying django/conf/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/uk/LC_MESSAGES
copying django/conf/locale/uk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/uk/LC_MESSAGES
creating build/lib/django/conf/locale/uz/LC_MESSAGES
copying django/conf/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/uz/LC_MESSAGES
copying django/conf/locale/uz/LC_MESSAGES/django.po -> build/lib/django/conf/locale/uz/LC_MESSAGES
creating build/lib/django/conf/locale/vi/LC_MESSAGES
copying django/conf/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/vi/LC_MESSAGES
copying django/conf/locale/vi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/vi/LC_MESSAGES
creating build/lib/django/conf/locale/zh_Hans/LC_MESSAGES
copying django/conf/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/zh_Hans/LC_MESSAGES
copying django/conf/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/conf/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/conf/locale/zh_Hant/LC_MESSAGES
copying django/conf/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/zh_Hant/LC_MESSAGES
copying django/conf/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/conf/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/admin/locale
creating build/lib/django/contrib/admin/locale/af
creating build/lib/django/contrib/admin/locale/af/LC_MESSAGES
copying django/contrib/admin/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES
copying django/contrib/admin/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES
copying django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES
copying django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/am
creating build/lib/django/contrib/admin/locale/am/LC_MESSAGES
copying django/contrib/admin/locale/am/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/am/LC_MESSAGES
copying django/contrib/admin/locale/am/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/am/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ar
creating build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
copying django/contrib/admin/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
copying django/contrib/admin/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
copying django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
copying django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ar_DZ
creating build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ast
creating build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
copying django/contrib/admin/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
copying django/contrib/admin/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
copying django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
copying django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/az
creating build/lib/django/contrib/admin/locale/az/LC_MESSAGES
copying django/contrib/admin/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES
copying django/contrib/admin/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES
copying django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES
copying django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/be
creating build/lib/django/contrib/admin/locale/be/LC_MESSAGES
copying django/contrib/admin/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES
copying django/contrib/admin/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES
copying django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES
copying django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/bg
creating build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
copying django/contrib/admin/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
copying django/contrib/admin/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
copying django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
copying django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/bn
creating build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
copying django/contrib/admin/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
copying django/contrib/admin/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
copying django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
copying django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/br
creating build/lib/django/contrib/admin/locale/br/LC_MESSAGES
copying django/contrib/admin/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES
copying django/contrib/admin/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES
copying django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES
copying django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/bs
creating build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
copying django/contrib/admin/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
copying django/contrib/admin/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
copying django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
copying django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ca
creating build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
copying django/contrib/admin/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
copying django/contrib/admin/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
copying django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
copying django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/cs
creating build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
copying django/contrib/admin/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
copying django/contrib/admin/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
copying django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
copying django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/cy
creating build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
copying django/contrib/admin/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
copying django/contrib/admin/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
copying django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
copying django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/da
creating build/lib/django/contrib/admin/locale/da/LC_MESSAGES
copying django/contrib/admin/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES
copying django/contrib/admin/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES
copying django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES
copying django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/de
creating build/lib/django/contrib/admin/locale/de/LC_MESSAGES
copying django/contrib/admin/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES
copying django/contrib/admin/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES
copying django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES
copying django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/dsb
creating build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
copying django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
copying django/contrib/admin/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
copying django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
copying django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/el
creating build/lib/django/contrib/admin/locale/el/LC_MESSAGES
copying django/contrib/admin/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES
copying django/contrib/admin/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES
copying django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES
copying django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/en
creating build/lib/django/contrib/admin/locale/en/LC_MESSAGES
copying django/contrib/admin/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES
copying django/contrib/admin/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES
copying django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES
copying django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/en_AU
creating build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES
copying django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES
copying django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES
copying django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES
copying django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/en_GB
creating build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES
copying django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES
copying django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES
copying django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES
copying django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/eo
creating build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
copying django/contrib/admin/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
copying django/contrib/admin/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
copying django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
copying django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/es
creating build/lib/django/contrib/admin/locale/es/LC_MESSAGES
copying django/contrib/admin/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES
copying django/contrib/admin/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES
copying django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES
copying django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/es_AR
creating build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES
copying django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES
copying django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES
copying django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES
copying django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/es_CO
creating build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES
copying django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES
copying django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES
copying django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES
copying django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/es_MX
creating build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES
copying django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES
copying django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES
copying django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES
copying django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/es_VE
creating build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES
copying django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES
copying django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES
copying django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES
copying django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/et
creating build/lib/django/contrib/admin/locale/et/LC_MESSAGES
copying django/contrib/admin/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES
copying django/contrib/admin/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES
copying django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES
copying django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/eu
creating build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
copying django/contrib/admin/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
copying django/contrib/admin/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
copying django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
copying django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/fa
creating build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
copying django/contrib/admin/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
copying django/contrib/admin/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
copying django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
copying django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/fi
creating build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
copying django/contrib/admin/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
copying django/contrib/admin/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
copying django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
copying django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/fr
creating build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
copying django/contrib/admin/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
copying django/contrib/admin/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
copying django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
copying django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/fy
creating build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
copying django/contrib/admin/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
copying django/contrib/admin/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
copying django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
copying django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ga
creating build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
copying django/contrib/admin/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
copying django/contrib/admin/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
copying django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
copying django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/gd
creating build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
copying django/contrib/admin/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
copying django/contrib/admin/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
copying django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
copying django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/gl
creating build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
copying django/contrib/admin/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
copying django/contrib/admin/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
copying django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
copying django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/he
creating build/lib/django/contrib/admin/locale/he/LC_MESSAGES
copying django/contrib/admin/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES
copying django/contrib/admin/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES
copying django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES
copying django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/hi
creating build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
copying django/contrib/admin/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
copying django/contrib/admin/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
copying django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
copying django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/hr
creating build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
copying django/contrib/admin/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
copying django/contrib/admin/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
copying django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
copying django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/hsb
creating build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
copying django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
copying django/contrib/admin/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
copying django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
copying django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/hu
creating build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
copying django/contrib/admin/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
copying django/contrib/admin/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
copying django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
copying django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/hy
creating build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
copying django/contrib/admin/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
copying django/contrib/admin/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
copying django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
copying django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ia
creating build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
copying django/contrib/admin/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
copying django/contrib/admin/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
copying django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
copying django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/id
creating build/lib/django/contrib/admin/locale/id/LC_MESSAGES
copying django/contrib/admin/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES
copying django/contrib/admin/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES
copying django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES
copying django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/io
creating build/lib/django/contrib/admin/locale/io/LC_MESSAGES
copying django/contrib/admin/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES
copying django/contrib/admin/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES
copying django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES
copying django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/is
creating build/lib/django/contrib/admin/locale/is/LC_MESSAGES
copying django/contrib/admin/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES
copying django/contrib/admin/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES
copying django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES
copying django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/it
creating build/lib/django/contrib/admin/locale/it/LC_MESSAGES
copying django/contrib/admin/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES
copying django/contrib/admin/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES
copying django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES
copying django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ja
creating build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
copying django/contrib/admin/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
copying django/contrib/admin/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
copying django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
copying django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ka
creating build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
copying django/contrib/admin/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
copying django/contrib/admin/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
copying django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
copying django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/kab
creating build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
copying django/contrib/admin/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
copying django/contrib/admin/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
copying django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
copying django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/kk
creating build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
copying django/contrib/admin/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
copying django/contrib/admin/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
copying django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
copying django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/km
creating build/lib/django/contrib/admin/locale/km/LC_MESSAGES
copying django/contrib/admin/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES
copying django/contrib/admin/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES
copying django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES
copying django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/kn
creating build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
copying django/contrib/admin/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
copying django/contrib/admin/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
copying django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
copying django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ko
creating build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
copying django/contrib/admin/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
copying django/contrib/admin/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
copying django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
copying django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ky
creating build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
copying django/contrib/admin/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
copying django/contrib/admin/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
copying django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
copying django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/lb
creating build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
copying django/contrib/admin/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
copying django/contrib/admin/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
copying django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
copying django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/lt
creating build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
copying django/contrib/admin/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
copying django/contrib/admin/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
copying django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
copying django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/lv
creating build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
copying django/contrib/admin/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
copying django/contrib/admin/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
copying django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
copying django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/mk
creating build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
copying django/contrib/admin/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
copying django/contrib/admin/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
copying django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
copying django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ml
creating build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
copying django/contrib/admin/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
copying django/contrib/admin/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
copying django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
copying django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/mn
creating build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
copying django/contrib/admin/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
copying django/contrib/admin/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
copying django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
copying django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/mr
creating build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
copying django/contrib/admin/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
copying django/contrib/admin/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
copying django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
copying django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/my
creating build/lib/django/contrib/admin/locale/my/LC_MESSAGES
copying django/contrib/admin/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES
copying django/contrib/admin/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES
copying django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES
copying django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/nb
creating build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
copying django/contrib/admin/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
copying django/contrib/admin/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
copying django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
copying django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ne
creating build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
copying django/contrib/admin/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
copying django/contrib/admin/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
copying django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
copying django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/nl
creating build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
copying django/contrib/admin/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
copying django/contrib/admin/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
copying django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
copying django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/nn
creating build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
copying django/contrib/admin/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
copying django/contrib/admin/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
copying django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
copying django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/os
creating build/lib/django/contrib/admin/locale/os/LC_MESSAGES
copying django/contrib/admin/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES
copying django/contrib/admin/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES
copying django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES
copying django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/pa
creating build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
copying django/contrib/admin/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
copying django/contrib/admin/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
copying django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
copying django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/pl
creating build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
copying django/contrib/admin/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
copying django/contrib/admin/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
copying django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
copying django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/pt
creating build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
copying django/contrib/admin/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
copying django/contrib/admin/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
copying django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
copying django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/pt_BR
creating build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES
copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES
copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES
copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES
copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ro
creating build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
copying django/contrib/admin/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
copying django/contrib/admin/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
copying django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
copying django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ru
creating build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
copying django/contrib/admin/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
copying django/contrib/admin/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
copying django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
copying django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/sk
creating build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
copying django/contrib/admin/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
copying django/contrib/admin/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
copying django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
copying django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/sl
creating build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
copying django/contrib/admin/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
copying django/contrib/admin/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
copying django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
copying django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/sq
creating build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
copying django/contrib/admin/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
copying django/contrib/admin/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
copying django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
copying django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/sr
creating build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
copying django/contrib/admin/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
copying django/contrib/admin/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
copying django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
copying django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/sr_Latn
creating build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/sv
creating build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
copying django/contrib/admin/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
copying django/contrib/admin/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
copying django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
copying django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/sw
creating build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
copying django/contrib/admin/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
copying django/contrib/admin/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
copying django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
copying django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ta
creating build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
copying django/contrib/admin/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
copying django/contrib/admin/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
copying django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
copying django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/te
creating build/lib/django/contrib/admin/locale/te/LC_MESSAGES
copying django/contrib/admin/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES
copying django/contrib/admin/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES
copying django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES
copying django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/tg
creating build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
copying django/contrib/admin/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
copying django/contrib/admin/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
copying django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
copying django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/th
creating build/lib/django/contrib/admin/locale/th/LC_MESSAGES
copying django/contrib/admin/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES
copying django/contrib/admin/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES
copying django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES
copying django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/tr
creating build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
copying django/contrib/admin/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
copying django/contrib/admin/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
copying django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
copying django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/tt
creating build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
copying django/contrib/admin/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
copying django/contrib/admin/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
copying django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
copying django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/udm
creating build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
copying django/contrib/admin/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
copying django/contrib/admin/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
copying django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
copying django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/uk
creating build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
copying django/contrib/admin/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
copying django/contrib/admin/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
copying django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
copying django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ur
creating build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
copying django/contrib/admin/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
copying django/contrib/admin/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
copying django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
copying django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/uz
creating build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
copying django/contrib/admin/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
copying django/contrib/admin/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
copying django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
copying django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/vi
creating build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
copying django/contrib/admin/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
copying django/contrib/admin/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
copying django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
copying django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/zh_Hans
creating build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/zh_Hant
creating build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/admin/static
creating build/lib/django/contrib/admin/static/admin
creating build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/autocomplete.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/base.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/changelists.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/dashboard.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/fonts.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/forms.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/login.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/nav_sidebar.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/responsive.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/responsive_rtl.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/rtl.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/widgets.css -> build/lib/django/contrib/admin/static/admin/css
creating build/lib/django/contrib/admin/static/admin/css/vendor
creating build/lib/django/contrib/admin/static/admin/css/vendor/select2
copying django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md -> build/lib/django/contrib/admin/static/admin/css/vendor/select2
copying django/contrib/admin/static/admin/css/vendor/select2/select2.css -> build/lib/django/contrib/admin/static/admin/css/vendor/select2
copying django/contrib/admin/static/admin/css/vendor/select2/select2.min.css -> build/lib/django/contrib/admin/static/admin/css/vendor/select2
creating build/lib/django/contrib/admin/static/admin/fonts
copying django/contrib/admin/static/admin/fonts/LICENSE.txt -> build/lib/django/contrib/admin/static/admin/fonts
copying django/contrib/admin/static/admin/fonts/README.txt -> build/lib/django/contrib/admin/static/admin/fonts
copying django/contrib/admin/static/admin/fonts/Roboto-Bold-webfont.woff -> build/lib/django/contrib/admin/static/admin/fonts
copying django/contrib/admin/static/admin/fonts/Roboto-Light-webfont.woff -> build/lib/django/contrib/admin/static/admin/fonts
copying django/contrib/admin/static/admin/fonts/Roboto-Regular-webfont.woff -> build/lib/django/contrib/admin/static/admin/fonts
creating build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/LICENSE -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/README.txt -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/calendar-icons.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-addlink.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-alert.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-calendar.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-changelink.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-clock.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-deletelink.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-no.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-unknown-alt.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-unknown.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-viewlink.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-yes.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/inline-delete.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/search.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/selector-icons.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/sorting-icons.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/tooltag-add.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/tooltag-arrowright.svg -> build/lib/django/contrib/admin/static/admin/img
creating build/lib/django/contrib/admin/static/admin/img/gis
copying django/contrib/admin/static/admin/img/gis/move_vertex_off.svg -> build/lib/django/contrib/admin/static/admin/img/gis
copying django/contrib/admin/static/admin/img/gis/move_vertex_on.svg -> build/lib/django/contrib/admin/static/admin/img/gis
creating build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/SelectBox.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/SelectFilter2.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/actions.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/autocomplete.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/calendar.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/cancel.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/change_form.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/collapse.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/core.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/inlines.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/jquery.init.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/nav_sidebar.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/popup_response.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/prepopulate.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/prepopulate_init.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/urlify.js -> build/lib/django/contrib/admin/static/admin/js
creating build/lib/django/contrib/admin/static/admin/js/admin
copying django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js -> build/lib/django/contrib/admin/static/admin/js/admin
copying django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js -> build/lib/django/contrib/admin/static/admin/js/admin
creating build/lib/django/contrib/admin/static/admin/js/vendor
creating build/lib/django/contrib/admin/static/admin/js/vendor/jquery
copying django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt -> build/lib/django/contrib/admin/static/admin/js/vendor/jquery
copying django/contrib/admin/static/admin/js/vendor/jquery/jquery.js -> build/lib/django/contrib/admin/static/admin/js/vendor/jquery
copying django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js -> build/lib/django/contrib/admin/static/admin/js/vendor/jquery
creating build/lib/django/contrib/admin/static/admin/js/vendor/select2
copying django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md -> build/lib/django/contrib/admin/static/admin/js/vendor/select2
copying django/contrib/admin/static/admin/js/vendor/select2/select2.full.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2
copying django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2
creating build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
creating build/lib/django/contrib/admin/static/admin/js/vendor/xregexp
copying django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt -> build/lib/django/contrib/admin/static/admin/js/vendor/xregexp
copying django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js -> build/lib/django/contrib/admin/static/admin/js/vendor/xregexp
copying django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js -> build/lib/django/contrib/admin/static/admin/js/vendor/xregexp
creating build/lib/django/contrib/admin/templates
creating build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/404.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/500.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/actions.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/app_index.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/app_list.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/base.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/base_site.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/change_form.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/change_form_object_tools.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/change_list.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/change_list_object_tools.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/change_list_results.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/date_hierarchy.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/delete_confirmation.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/delete_selected_confirmation.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/filter.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/index.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/invalid_setup.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/login.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/nav_sidebar.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/object_history.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/pagination.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/popup_response.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/prepopulated_fields_js.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/search_form.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/submit_line.html -> build/lib/django/contrib/admin/templates/admin
creating build/lib/django/contrib/admin/templates/admin/auth
creating build/lib/django/contrib/admin/templates/admin/auth/user
copying django/contrib/admin/templates/admin/auth/user/add_form.html -> build/lib/django/contrib/admin/templates/admin/auth/user
copying django/contrib/admin/templates/admin/auth/user/change_password.html -> build/lib/django/contrib/admin/templates/admin/auth/user
creating build/lib/django/contrib/admin/templates/admin/edit_inline
copying django/contrib/admin/templates/admin/edit_inline/stacked.html -> build/lib/django/contrib/admin/templates/admin/edit_inline
copying django/contrib/admin/templates/admin/edit_inline/tabular.html -> build/lib/django/contrib/admin/templates/admin/edit_inline
creating build/lib/django/contrib/admin/templates/admin/includes
copying django/contrib/admin/templates/admin/includes/fieldset.html -> build/lib/django/contrib/admin/templates/admin/includes
copying django/contrib/admin/templates/admin/includes/object_delete_summary.html -> build/lib/django/contrib/admin/templates/admin/includes
creating build/lib/django/contrib/admin/templates/admin/widgets
copying django/contrib/admin/templates/admin/widgets/clearable_file_input.html -> build/lib/django/contrib/admin/templates/admin/widgets
copying django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html -> build/lib/django/contrib/admin/templates/admin/widgets
copying django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html -> build/lib/django/contrib/admin/templates/admin/widgets
copying django/contrib/admin/templates/admin/widgets/radio.html -> build/lib/django/contrib/admin/templates/admin/widgets
copying django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html -> build/lib/django/contrib/admin/templates/admin/widgets
copying django/contrib/admin/templates/admin/widgets/split_datetime.html -> build/lib/django/contrib/admin/templates/admin/widgets
copying django/contrib/admin/templates/admin/widgets/url.html -> build/lib/django/contrib/admin/templates/admin/widgets
creating build/lib/django/contrib/admin/templates/registration
copying django/contrib/admin/templates/registration/logged_out.html -> build/lib/django/contrib/admin/templates/registration
copying django/contrib/admin/templates/registration/password_change_done.html -> build/lib/django/contrib/admin/templates/registration
copying django/contrib/admin/templates/registration/password_change_form.html -> build/lib/django/contrib/admin/templates/registration
copying django/contrib/admin/templates/registration/password_reset_complete.html -> build/lib/django/contrib/admin/templates/registration
copying django/contrib/admin/templates/registration/password_reset_confirm.html -> build/lib/django/contrib/admin/templates/registration
copying django/contrib/admin/templates/registration/password_reset_done.html -> build/lib/django/contrib/admin/templates/registration
copying django/contrib/admin/templates/registration/password_reset_email.html -> build/lib/django/contrib/admin/templates/registration
copying django/contrib/admin/templates/registration/password_reset_form.html -> build/lib/django/contrib/admin/templates/registration
creating build/lib/django/contrib/admindocs/locale
creating build/lib/django/contrib/admindocs/locale/af
creating build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES
copying django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES
copying django/contrib/admindocs/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ar
creating build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES
copying django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES
copying django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ar_DZ
creating build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
copying django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
copying django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ast
creating build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES
copying django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES
copying django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/az
creating build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES
copying django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES
copying django/contrib/admindocs/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/be
creating build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES
copying django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES
copying django/contrib/admindocs/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/bg
creating build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES
copying django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES
copying django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/bn
creating build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES
copying django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES
copying django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/br
creating build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES
copying django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES
copying django/contrib/admindocs/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/bs
creating build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES
copying django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES
copying django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ca
creating build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES
copying django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES
copying django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/cs
creating build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES
copying django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES
copying django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/cy
creating build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES
copying django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES
copying django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/da
creating build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES
copying django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES
copying django/contrib/admindocs/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/de
creating build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES
copying django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES
copying django/contrib/admindocs/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/dsb
creating build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES
copying django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES
copying django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/el
creating build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES
copying django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES
copying django/contrib/admindocs/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/en
creating build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES
copying django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES
copying django/contrib/admindocs/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/en_AU
creating build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
copying django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
copying django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/en_GB
creating build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
copying django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
copying django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/eo
creating build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES
copying django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES
copying django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/es
creating build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES
copying django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES
copying django/contrib/admindocs/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/es_AR
creating build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
copying django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
copying django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/es_CO
creating build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
copying django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
copying django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/es_MX
creating build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
copying django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
copying django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/es_VE
creating build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
copying django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
copying django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/et
creating build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES
copying django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES
copying django/contrib/admindocs/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/eu
creating build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES
copying django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES
copying django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/fa
creating build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES
copying django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES
copying django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/fi
creating build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES
copying django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES
copying django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/fr
creating build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES
copying django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES
copying django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/fy
creating build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES
copying django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES
copying django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ga
creating build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES
copying django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES
copying django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/gd
creating build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES
copying django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES
copying django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/gl
creating build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES
copying django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES
copying django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/he
creating build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES
copying django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES
copying django/contrib/admindocs/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/hi
creating build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES
copying django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES
copying django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/hr
creating build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES
copying django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES
copying django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/hsb
creating build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES
copying django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES
copying django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/hu
creating build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES
copying django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES
copying django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ia
creating build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES
copying django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES
copying django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/id
creating build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES
copying django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES
copying django/contrib/admindocs/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/io
creating build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES
copying django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES
copying django/contrib/admindocs/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/is
creating build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES
copying django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES
copying django/contrib/admindocs/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/it
creating build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES
copying django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES
copying django/contrib/admindocs/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ja
creating build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES
copying django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES
copying django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ka
creating build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES
copying django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES
copying django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/kab
creating build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES
copying django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES
copying django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/kk
creating build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES
copying django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES
copying django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/km
creating build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES
copying django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES
copying django/contrib/admindocs/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/kn
creating build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES
copying django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES
copying django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ko
creating build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES
copying django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES
copying django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ky
creating build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES
copying django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES
copying django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/lb
creating build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES
copying django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES
copying django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/lt
creating build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES
copying django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES
copying django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/lv
creating build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES
copying django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES
copying django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/mk
creating build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES
copying django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES
copying django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ml
creating build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES
copying django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES
copying django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/mn
creating build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES
copying django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES
copying django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/mr
creating build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES
copying django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES
copying django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/my
creating build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES
copying django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES
copying django/contrib/admindocs/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/nb
creating build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES
copying django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES
copying django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ne
creating build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES
copying django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES
copying django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/nl
creating build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES
copying django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES
copying django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/nn
creating build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES
copying django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES
copying django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/os
creating build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES
copying django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES
copying django/contrib/admindocs/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/pa
creating build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES
copying django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES
copying django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/pl
creating build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES
copying django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES
copying django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/pt
creating build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES
copying django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES
copying django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/pt_BR
creating build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
copying django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
copying django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ro
creating build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES
copying django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES
copying django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ru
creating build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES
copying django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES
copying django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/sk
creating build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES
copying django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES
copying django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/sl
creating build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES
copying django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES
copying django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/sq
creating build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES
copying django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES
copying django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/sr
creating build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES
copying django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES
copying django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/sr_Latn
creating build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
copying django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
copying django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/sv
creating build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES
copying django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES
copying django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/sw
creating build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES
copying django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES
copying django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ta
creating build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES
copying django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES
copying django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/te
creating build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES
copying django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES
copying django/contrib/admindocs/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/tg
creating build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES
copying django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES
copying django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/th
creating build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES
copying django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES
copying django/contrib/admindocs/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/tr
creating build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES
copying django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES
copying django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/tt
creating build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES
copying django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES
copying django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/udm
creating build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES
copying django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES
copying django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/uk
creating build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES
copying django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES
copying django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ur
creating build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES
copying django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES
copying django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/vi
creating build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES
copying django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES
copying django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/zh_Hans
creating build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
copying django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
copying django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/zh_Hant
creating build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
copying django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
copying django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/admindocs/templates
creating build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/bookmarklets.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/missing_docutils.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/model_detail.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/model_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/template_detail.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/template_filter_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/template_tag_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/view_detail.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/view_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/auth/common-passwords.txt.gz -> build/lib/django/contrib/auth
creating build/lib/django/contrib/auth/locale
creating build/lib/django/contrib/auth/locale/af
creating build/lib/django/contrib/auth/locale/af/LC_MESSAGES
copying django/contrib/auth/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/af/LC_MESSAGES
copying django/contrib/auth/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/af/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ar
creating build/lib/django/contrib/auth/locale/ar/LC_MESSAGES
copying django/contrib/auth/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ar/LC_MESSAGES
copying django/contrib/auth/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ar_DZ
creating build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
copying django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
copying django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ast
creating build/lib/django/contrib/auth/locale/ast/LC_MESSAGES
copying django/contrib/auth/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ast/LC_MESSAGES
copying django/contrib/auth/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/az
creating build/lib/django/contrib/auth/locale/az/LC_MESSAGES
copying django/contrib/auth/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/az/LC_MESSAGES
copying django/contrib/auth/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/az/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/be
creating build/lib/django/contrib/auth/locale/be/LC_MESSAGES
copying django/contrib/auth/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/be/LC_MESSAGES
copying django/contrib/auth/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/be/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/bg
creating build/lib/django/contrib/auth/locale/bg/LC_MESSAGES
copying django/contrib/auth/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/bg/LC_MESSAGES
copying django/contrib/auth/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/bn
creating build/lib/django/contrib/auth/locale/bn/LC_MESSAGES
copying django/contrib/auth/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/bn/LC_MESSAGES
copying django/contrib/auth/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/br
creating build/lib/django/contrib/auth/locale/br/LC_MESSAGES
copying django/contrib/auth/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/br/LC_MESSAGES
copying django/contrib/auth/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/br/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/bs
creating build/lib/django/contrib/auth/locale/bs/LC_MESSAGES
copying django/contrib/auth/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/bs/LC_MESSAGES
copying django/contrib/auth/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ca
creating build/lib/django/contrib/auth/locale/ca/LC_MESSAGES
copying django/contrib/auth/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ca/LC_MESSAGES
copying django/contrib/auth/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/cs
creating build/lib/django/contrib/auth/locale/cs/LC_MESSAGES
copying django/contrib/auth/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/cs/LC_MESSAGES
copying django/contrib/auth/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/cy
creating build/lib/django/contrib/auth/locale/cy/LC_MESSAGES
copying django/contrib/auth/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/cy/LC_MESSAGES
copying django/contrib/auth/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/da
creating build/lib/django/contrib/auth/locale/da/LC_MESSAGES
copying django/contrib/auth/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/da/LC_MESSAGES
copying django/contrib/auth/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/da/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/de
creating build/lib/django/contrib/auth/locale/de/LC_MESSAGES
copying django/contrib/auth/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/de/LC_MESSAGES
copying django/contrib/auth/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/de/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/dsb
creating build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES
copying django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES
copying django/contrib/auth/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/el
creating build/lib/django/contrib/auth/locale/el/LC_MESSAGES
copying django/contrib/auth/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/el/LC_MESSAGES
copying django/contrib/auth/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/el/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/en
creating build/lib/django/contrib/auth/locale/en/LC_MESSAGES
copying django/contrib/auth/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/en/LC_MESSAGES
copying django/contrib/auth/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/en/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/en_AU
creating build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES
copying django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES
copying django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/en_GB
creating build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES
copying django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES
copying django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/eo
creating build/lib/django/contrib/auth/locale/eo/LC_MESSAGES
copying django/contrib/auth/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/eo/LC_MESSAGES
copying django/contrib/auth/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/es
creating build/lib/django/contrib/auth/locale/es/LC_MESSAGES
copying django/contrib/auth/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es/LC_MESSAGES
copying django/contrib/auth/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/es_AR
creating build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES
copying django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES
copying django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/es_CO
creating build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES
copying django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES
copying django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/es_MX
creating build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES
copying django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES
copying django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/es_VE
creating build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES
copying django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES
copying django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/et
creating build/lib/django/contrib/auth/locale/et/LC_MESSAGES
copying django/contrib/auth/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/et/LC_MESSAGES
copying django/contrib/auth/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/et/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/eu
creating build/lib/django/contrib/auth/locale/eu/LC_MESSAGES
copying django/contrib/auth/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/eu/LC_MESSAGES
copying django/contrib/auth/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/fa
creating build/lib/django/contrib/auth/locale/fa/LC_MESSAGES
copying django/contrib/auth/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fa/LC_MESSAGES
copying django/contrib/auth/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/fi
creating build/lib/django/contrib/auth/locale/fi/LC_MESSAGES
copying django/contrib/auth/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fi/LC_MESSAGES
copying django/contrib/auth/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/fr
creating build/lib/django/contrib/auth/locale/fr/LC_MESSAGES
copying django/contrib/auth/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fr/LC_MESSAGES
copying django/contrib/auth/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/fy
creating build/lib/django/contrib/auth/locale/fy/LC_MESSAGES
copying django/contrib/auth/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fy/LC_MESSAGES
copying django/contrib/auth/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ga
creating build/lib/django/contrib/auth/locale/ga/LC_MESSAGES
copying django/contrib/auth/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ga/LC_MESSAGES
copying django/contrib/auth/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/gd
creating build/lib/django/contrib/auth/locale/gd/LC_MESSAGES
copying django/contrib/auth/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/gd/LC_MESSAGES
copying django/contrib/auth/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/gl
creating build/lib/django/contrib/auth/locale/gl/LC_MESSAGES
copying django/contrib/auth/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/gl/LC_MESSAGES
copying django/contrib/auth/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/he
creating build/lib/django/contrib/auth/locale/he/LC_MESSAGES
copying django/contrib/auth/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/he/LC_MESSAGES
copying django/contrib/auth/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/he/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/hi
creating build/lib/django/contrib/auth/locale/hi/LC_MESSAGES
copying django/contrib/auth/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hi/LC_MESSAGES
copying django/contrib/auth/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/hr
creating build/lib/django/contrib/auth/locale/hr/LC_MESSAGES
copying django/contrib/auth/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hr/LC_MESSAGES
copying django/contrib/auth/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/hsb
creating build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES
copying django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES
copying django/contrib/auth/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/hu
creating build/lib/django/contrib/auth/locale/hu/LC_MESSAGES
copying django/contrib/auth/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hu/LC_MESSAGES
copying django/contrib/auth/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/hy
creating build/lib/django/contrib/auth/locale/hy/LC_MESSAGES
copying django/contrib/auth/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hy/LC_MESSAGES
copying django/contrib/auth/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ia
creating build/lib/django/contrib/auth/locale/ia/LC_MESSAGES
copying django/contrib/auth/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ia/LC_MESSAGES
copying django/contrib/auth/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/id
creating build/lib/django/contrib/auth/locale/id/LC_MESSAGES
copying django/contrib/auth/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/id/LC_MESSAGES
copying django/contrib/auth/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/id/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/io
creating build/lib/django/contrib/auth/locale/io/LC_MESSAGES
copying django/contrib/auth/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/io/LC_MESSAGES
copying django/contrib/auth/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/io/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/is
creating build/lib/django/contrib/auth/locale/is/LC_MESSAGES
copying django/contrib/auth/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/is/LC_MESSAGES
copying django/contrib/auth/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/is/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/it
creating build/lib/django/contrib/auth/locale/it/LC_MESSAGES
copying django/contrib/auth/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/it/LC_MESSAGES
copying django/contrib/auth/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/it/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ja
creating build/lib/django/contrib/auth/locale/ja/LC_MESSAGES
copying django/contrib/auth/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ja/LC_MESSAGES
copying django/contrib/auth/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ka
creating build/lib/django/contrib/auth/locale/ka/LC_MESSAGES
copying django/contrib/auth/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ka/LC_MESSAGES
copying django/contrib/auth/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/kab
creating build/lib/django/contrib/auth/locale/kab/LC_MESSAGES
copying django/contrib/auth/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/kab/LC_MESSAGES
copying django/contrib/auth/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/kab/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/kk
creating build/lib/django/contrib/auth/locale/kk/LC_MESSAGES
copying django/contrib/auth/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/kk/LC_MESSAGES
copying django/contrib/auth/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/km
creating build/lib/django/contrib/auth/locale/km/LC_MESSAGES
copying django/contrib/auth/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/km/LC_MESSAGES
copying django/contrib/auth/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/km/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/kn
creating build/lib/django/contrib/auth/locale/kn/LC_MESSAGES
copying django/contrib/auth/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/kn/LC_MESSAGES
copying django/contrib/auth/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ko
creating build/lib/django/contrib/auth/locale/ko/LC_MESSAGES
copying django/contrib/auth/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ko/LC_MESSAGES
copying django/contrib/auth/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ky
creating build/lib/django/contrib/auth/locale/ky/LC_MESSAGES
copying django/contrib/auth/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ky/LC_MESSAGES
copying django/contrib/auth/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/lb
creating build/lib/django/contrib/auth/locale/lb/LC_MESSAGES
copying django/contrib/auth/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/lb/LC_MESSAGES
copying django/contrib/auth/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/lt
creating build/lib/django/contrib/auth/locale/lt/LC_MESSAGES
copying django/contrib/auth/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/lt/LC_MESSAGES
copying django/contrib/auth/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/lv
creating build/lib/django/contrib/auth/locale/lv/LC_MESSAGES
copying django/contrib/auth/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/lv/LC_MESSAGES
copying django/contrib/auth/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/mk
creating build/lib/django/contrib/auth/locale/mk/LC_MESSAGES
copying django/contrib/auth/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/mk/LC_MESSAGES
copying django/contrib/auth/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ml
creating build/lib/django/contrib/auth/locale/ml/LC_MESSAGES
copying django/contrib/auth/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ml/LC_MESSAGES
copying django/contrib/auth/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/mn
creating build/lib/django/contrib/auth/locale/mn/LC_MESSAGES
copying django/contrib/auth/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/mn/LC_MESSAGES
copying django/contrib/auth/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/mr
creating build/lib/django/contrib/auth/locale/mr/LC_MESSAGES
copying django/contrib/auth/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/mr/LC_MESSAGES
copying django/contrib/auth/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/my
creating build/lib/django/contrib/auth/locale/my/LC_MESSAGES
copying django/contrib/auth/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/my/LC_MESSAGES
copying django/contrib/auth/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/my/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/nb
creating build/lib/django/contrib/auth/locale/nb/LC_MESSAGES
copying django/contrib/auth/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/nb/LC_MESSAGES
copying django/contrib/auth/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ne
creating build/lib/django/contrib/auth/locale/ne/LC_MESSAGES
copying django/contrib/auth/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ne/LC_MESSAGES
copying django/contrib/auth/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/nl
creating build/lib/django/contrib/auth/locale/nl/LC_MESSAGES
copying django/contrib/auth/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/nl/LC_MESSAGES
copying django/contrib/auth/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/nn
creating build/lib/django/contrib/auth/locale/nn/LC_MESSAGES
copying django/contrib/auth/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/nn/LC_MESSAGES
copying django/contrib/auth/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/os
creating build/lib/django/contrib/auth/locale/os/LC_MESSAGES
copying django/contrib/auth/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/os/LC_MESSAGES
copying django/contrib/auth/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/os/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/pa
creating build/lib/django/contrib/auth/locale/pa/LC_MESSAGES
copying django/contrib/auth/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pa/LC_MESSAGES
copying django/contrib/auth/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/pl
creating build/lib/django/contrib/auth/locale/pl/LC_MESSAGES
copying django/contrib/auth/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pl/LC_MESSAGES
copying django/contrib/auth/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/pt
creating build/lib/django/contrib/auth/locale/pt/LC_MESSAGES
copying django/contrib/auth/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pt/LC_MESSAGES
copying django/contrib/auth/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/pt_BR
creating build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES
copying django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES
copying django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ro
creating build/lib/django/contrib/auth/locale/ro/LC_MESSAGES
copying django/contrib/auth/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ro/LC_MESSAGES
copying django/contrib/auth/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ru
creating build/lib/django/contrib/auth/locale/ru/LC_MESSAGES
copying django/contrib/auth/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ru/LC_MESSAGES
copying django/contrib/auth/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/sk
creating build/lib/django/contrib/auth/locale/sk/LC_MESSAGES
copying django/contrib/auth/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sk/LC_MESSAGES
copying django/contrib/auth/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/sl
creating build/lib/django/contrib/auth/locale/sl/LC_MESSAGES
copying django/contrib/auth/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sl/LC_MESSAGES
copying django/contrib/auth/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/sq
creating build/lib/django/contrib/auth/locale/sq/LC_MESSAGES
copying django/contrib/auth/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sq/LC_MESSAGES
copying django/contrib/auth/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/sr
creating build/lib/django/contrib/auth/locale/sr/LC_MESSAGES
copying django/contrib/auth/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sr/LC_MESSAGES
copying django/contrib/auth/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/sr_Latn
creating build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
copying django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
copying django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/sv
creating build/lib/django/contrib/auth/locale/sv/LC_MESSAGES
copying django/contrib/auth/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sv/LC_MESSAGES
copying django/contrib/auth/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/sw
creating build/lib/django/contrib/auth/locale/sw/LC_MESSAGES
copying django/contrib/auth/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sw/LC_MESSAGES
copying django/contrib/auth/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ta
creating build/lib/django/contrib/auth/locale/ta/LC_MESSAGES
copying django/contrib/auth/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ta/LC_MESSAGES
copying django/contrib/auth/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/te
creating build/lib/django/contrib/auth/locale/te/LC_MESSAGES
copying django/contrib/auth/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/te/LC_MESSAGES
copying django/contrib/auth/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/te/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/tg
creating build/lib/django/contrib/auth/locale/tg/LC_MESSAGES
copying django/contrib/auth/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tg/LC_MESSAGES
copying django/contrib/auth/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/th
creating build/lib/django/contrib/auth/locale/th/LC_MESSAGES
copying django/contrib/auth/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/th/LC_MESSAGES
copying django/contrib/auth/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/th/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/tk
creating build/lib/django/contrib/auth/locale/tk/LC_MESSAGES
copying django/contrib/auth/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tk/LC_MESSAGES
copying django/contrib/auth/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tk/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/tr
creating build/lib/django/contrib/auth/locale/tr/LC_MESSAGES
copying django/contrib/auth/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tr/LC_MESSAGES
copying django/contrib/auth/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/tt
creating build/lib/django/contrib/auth/locale/tt/LC_MESSAGES
copying django/contrib/auth/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tt/LC_MESSAGES
copying django/contrib/auth/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/udm
creating build/lib/django/contrib/auth/locale/udm/LC_MESSAGES
copying django/contrib/auth/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/udm/LC_MESSAGES
copying django/contrib/auth/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/uk
creating build/lib/django/contrib/auth/locale/uk/LC_MESSAGES
copying django/contrib/auth/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/uk/LC_MESSAGES
copying django/contrib/auth/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ur
creating build/lib/django/contrib/auth/locale/ur/LC_MESSAGES
copying django/contrib/auth/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ur/LC_MESSAGES
copying django/contrib/auth/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/uz
creating build/lib/django/contrib/auth/locale/uz/LC_MESSAGES
copying django/contrib/auth/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/uz/LC_MESSAGES
copying django/contrib/auth/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/uz/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/vi
creating build/lib/django/contrib/auth/locale/vi/LC_MESSAGES
copying django/contrib/auth/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/vi/LC_MESSAGES
copying django/contrib/auth/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/zh_Hans
creating build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
copying django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
copying django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/zh_Hant
creating build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
copying django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
copying django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/auth/templates
creating build/lib/django/contrib/auth/templates/auth
creating build/lib/django/contrib/auth/templates/auth/widgets
copying django/contrib/auth/templates/auth/widgets/read_only_password_hash.html -> build/lib/django/contrib/auth/templates/auth/widgets
creating build/lib/django/contrib/auth/templates/registration
copying django/contrib/auth/templates/registration/password_reset_subject.txt -> build/lib/django/contrib/auth/templates/registration
creating build/lib/django/contrib/contenttypes/locale
creating build/lib/django/contrib/contenttypes/locale/af
creating build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES
copying django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES
copying django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ar
creating build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES
copying django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES
copying django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ar_DZ
creating build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
copying django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
copying django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ast
creating build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES
copying django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES
copying django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/az
creating build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES
copying django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES
copying django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/be
creating build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES
copying django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES
copying django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/bg
creating build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES
copying django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES
copying django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/bn
creating build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES
copying django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES
copying django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/br
creating build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES
copying django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES
copying django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/bs
creating build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES
copying django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES
copying django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ca
creating build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES
copying django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES
copying django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/cs
creating build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES
copying django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES
copying django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/cy
creating build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES
copying django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES
copying django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/da
creating build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES
copying django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES
copying django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/de
creating build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES
copying django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES
copying django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/dsb
creating build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
copying django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
copying django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/el
creating build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES
copying django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES
copying django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/en
creating build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES
copying django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES
copying django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/en_AU
creating build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
copying django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
copying django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/en_GB
creating build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
copying django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
copying django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/eo
creating build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES
copying django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES
copying django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/es
creating build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES
copying django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES
copying django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/es_AR
creating build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
copying django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
copying django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/es_CO
creating build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
copying django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
copying django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/es_MX
creating build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
copying django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
copying django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/es_VE
creating build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
copying django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
copying django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/et
creating build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES
copying django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES
copying django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/eu
creating build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES
copying django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES
copying django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/fa
creating build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES
copying django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES
copying django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/fi
creating build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES
copying django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES
copying django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/fr
creating build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES
copying django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES
copying django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/fy
creating build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES
copying django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES
copying django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ga
creating build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES
copying django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES
copying django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/gd
creating build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES
copying django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES
copying django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/gl
creating build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES
copying django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES
copying django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/he
creating build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES
copying django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES
copying django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/hi
creating build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES
copying django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES
copying django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/hr
creating build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES
copying django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES
copying django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/hsb
creating build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
copying django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
copying django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/hu
creating build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES
copying django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES
copying django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/hy
creating build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES
copying django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES
copying django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ia
creating build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES
copying django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES
copying django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/id
creating build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES
copying django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES
copying django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/io
creating build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES
copying django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES
copying django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/is
creating build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES
copying django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES
copying django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/it
creating build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES
copying django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES
copying django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ja
creating build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES
copying django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES
copying django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ka
creating build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES
copying django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES
copying django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/kk
creating build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES
copying django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES
copying django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/km
creating build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES
copying django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES
copying django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/kn
creating build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES
copying django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES
copying django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ko
creating build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES
copying django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES
copying django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ky
creating build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES
copying django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES
copying django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/lb
creating build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES
copying django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES
copying django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/lt
creating build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES
copying django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES
copying django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/lv
creating build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES
copying django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES
copying django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/mk
creating build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES
copying django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES
copying django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ml
creating build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES
copying django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES
copying django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/mn
creating build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES
copying django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES
copying django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/mr
creating build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES
copying django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES
copying django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/my
creating build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES
copying django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES
copying django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/nb
creating build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES
copying django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES
copying django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ne
creating build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES
copying django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES
copying django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/nl
creating build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES
copying django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES
copying django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/nn
creating build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES
copying django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES
copying django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/os
creating build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES
copying django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES
copying django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/pa
creating build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES
copying django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES
copying django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/pl
creating build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES
copying django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES
copying django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/pt
creating build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES
copying django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES
copying django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/pt_BR
creating build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
copying django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
copying django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ro
creating build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES
copying django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES
copying django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ru
creating build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES
copying django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES
copying django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/sk
creating build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES
copying django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES
copying django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/sl
creating build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES
copying django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES
copying django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/sq
creating build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES
copying django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES
copying django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/sr
creating build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES
copying django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES
copying django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/sr_Latn
creating build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
copying django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
copying django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/sv
creating build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES
copying django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES
copying django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/sw
creating build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES
copying django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES
copying django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ta
creating build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES
copying django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES
copying django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/te
creating build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES
copying django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES
copying django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/tg
creating build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES
copying django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES
copying django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/th
creating build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES
copying django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES
copying django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/tk
creating build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES
copying django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES
copying django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/tr
creating build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES
copying django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES
copying django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/tt
creating build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES
copying django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES
copying django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/udm
creating build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES
copying django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES
copying django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/uk
creating build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES
copying django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES
copying django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ur
creating build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES
copying django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES
copying django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/vi
creating build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES
copying django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES
copying django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/zh_Hans
creating build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
copying django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
copying django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/zh_Hant
creating build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
copying django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
copying django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale
creating build/lib/django/contrib/flatpages/locale/af
creating build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES
copying django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES
copying django/contrib/flatpages/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ar
creating build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES
copying django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES
copying django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ar_DZ
creating build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
copying django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
copying django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ast
creating build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES
copying django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES
copying django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/az
creating build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES
copying django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES
copying django/contrib/flatpages/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/be
creating build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES
copying django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES
copying django/contrib/flatpages/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/bg
creating build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES
copying django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES
copying django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/bn
creating build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES
copying django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES
copying django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/br
creating build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES
copying django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES
copying django/contrib/flatpages/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/bs
creating build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES
copying django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES
copying django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ca
creating build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES
copying django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES
copying django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/cs
creating build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES
copying django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES
copying django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/cy
creating build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES
copying django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES
copying django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/da
creating build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES
copying django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES
copying django/contrib/flatpages/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/de
creating build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES
copying django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES
copying django/contrib/flatpages/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/dsb
creating build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES
copying django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES
copying django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/el
creating build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES
copying django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES
copying django/contrib/flatpages/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/en
creating build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES
copying django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES
copying django/contrib/flatpages/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/en_AU
creating build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
copying django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
copying django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/en_GB
creating build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
copying django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
copying django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/eo
creating build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES
copying django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES
copying django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/es
creating build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES
copying django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES
copying django/contrib/flatpages/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/es_AR
creating build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
copying django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
copying django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/es_CO
creating build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
copying django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
copying django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/es_MX
creating build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
copying django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
copying django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/es_VE
creating build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
copying django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
copying django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/et
creating build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES
copying django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES
copying django/contrib/flatpages/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/eu
creating build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES
copying django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES
copying django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/fa
creating build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES
copying django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES
copying django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/fi
creating build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES
copying django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES
copying django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/fr
creating build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES
copying django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES
copying django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/fy
creating build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES
copying django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES
copying django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ga
creating build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES
copying django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES
copying django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/gd
creating build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES
copying django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES
copying django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/gl
creating build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES
copying django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES
copying django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/he
creating build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES
copying django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES
copying django/contrib/flatpages/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/hi
creating build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES
copying django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES
copying django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/hr
creating build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES
copying django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES
copying django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/hsb
creating build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES
copying django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES
copying django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/hu
creating build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES
copying django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES
copying django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/hy
creating build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES
copying django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES
copying django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ia
creating build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES
copying django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES
copying django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/id
creating build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES
copying django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES
copying django/contrib/flatpages/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/io
creating build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES
copying django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES
copying django/contrib/flatpages/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/is
creating build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES
copying django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES
copying django/contrib/flatpages/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/it
creating build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES
copying django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES
copying django/contrib/flatpages/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ja
creating build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES
copying django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES
copying django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ka
creating build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES
copying django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES
copying django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/kk
creating build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES
copying django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES
copying django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/km
creating build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES
copying django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES
copying django/contrib/flatpages/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/kn
creating build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES
copying django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES
copying django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ko
creating build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES
copying django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES
copying django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ky
creating build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES
copying django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES
copying django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/lb
creating build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES
copying django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES
copying django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/lt
creating build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES
copying django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES
copying django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/lv
creating build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES
copying django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES
copying django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/mk
creating build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES
copying django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES
copying django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ml
creating build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES
copying django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES
copying django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/mn
creating build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES
copying django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES
copying django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/mr
creating build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES
copying django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES
copying django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/my
creating build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES
copying django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES
copying django/contrib/flatpages/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/nb
creating build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES
copying django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES
copying django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ne
creating build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES
copying django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES
copying django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/nl
creating build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES
copying django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES
copying django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/nn
creating build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES
copying django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES
copying django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/os
creating build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES
copying django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES
copying django/contrib/flatpages/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/pa
creating build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES
copying django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES
copying django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/pl
creating build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES
copying django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES
copying django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/pt
creating build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES
copying django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES
copying django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/pt_BR
creating build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
copying django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
copying django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ro
creating build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES
copying django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES
copying django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ru
creating build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES
copying django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES
copying django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/sk
creating build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES
copying django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES
copying django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/sl
creating build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES
copying django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES
copying django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/sq
creating build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES
copying django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES
copying django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/sr
creating build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES
copying django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES
copying django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/sr_Latn
creating build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
copying django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
copying django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/sv
creating build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES
copying django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES
copying django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/sw
creating build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES
copying django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES
copying django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ta
creating build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES
copying django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES
copying django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/te
creating build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES
copying django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES
copying django/contrib/flatpages/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/tg
creating build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES
copying django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES
copying django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/th
creating build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES
copying django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES
copying django/contrib/flatpages/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/tk
creating build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES
copying django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES
copying django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/tr
creating build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES
copying django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES
copying django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/tt
creating build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES
copying django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES
copying django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/udm
creating build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES
copying django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES
copying django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/uk
creating build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES
copying django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES
copying django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ur
creating build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES
copying django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES
copying django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/vi
creating build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES
copying django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES
copying django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/zh_Hans
creating build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
copying django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
copying django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/zh_Hant
creating build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
copying django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
copying django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/gis/locale
creating build/lib/django/contrib/gis/locale/af
creating build/lib/django/contrib/gis/locale/af/LC_MESSAGES
copying django/contrib/gis/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/af/LC_MESSAGES
copying django/contrib/gis/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/af/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ar
creating build/lib/django/contrib/gis/locale/ar/LC_MESSAGES
copying django/contrib/gis/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ar/LC_MESSAGES
copying django/contrib/gis/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ar_DZ
creating build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
copying django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
copying django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ast
creating build/lib/django/contrib/gis/locale/ast/LC_MESSAGES
copying django/contrib/gis/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ast/LC_MESSAGES
copying django/contrib/gis/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/az
creating build/lib/django/contrib/gis/locale/az/LC_MESSAGES
copying django/contrib/gis/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/az/LC_MESSAGES
copying django/contrib/gis/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/az/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/be
creating build/lib/django/contrib/gis/locale/be/LC_MESSAGES
copying django/contrib/gis/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/be/LC_MESSAGES
copying django/contrib/gis/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/be/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/bg
creating build/lib/django/contrib/gis/locale/bg/LC_MESSAGES
copying django/contrib/gis/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/bg/LC_MESSAGES
copying django/contrib/gis/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/bn
creating build/lib/django/contrib/gis/locale/bn/LC_MESSAGES
copying django/contrib/gis/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/bn/LC_MESSAGES
copying django/contrib/gis/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/br
creating build/lib/django/contrib/gis/locale/br/LC_MESSAGES
copying django/contrib/gis/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/br/LC_MESSAGES
copying django/contrib/gis/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/br/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/bs
creating build/lib/django/contrib/gis/locale/bs/LC_MESSAGES
copying django/contrib/gis/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/bs/LC_MESSAGES
copying django/contrib/gis/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ca
creating build/lib/django/contrib/gis/locale/ca/LC_MESSAGES
copying django/contrib/gis/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ca/LC_MESSAGES
copying django/contrib/gis/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/cs
creating build/lib/django/contrib/gis/locale/cs/LC_MESSAGES
copying django/contrib/gis/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/cs/LC_MESSAGES
copying django/contrib/gis/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/cy
creating build/lib/django/contrib/gis/locale/cy/LC_MESSAGES
copying django/contrib/gis/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/cy/LC_MESSAGES
copying django/contrib/gis/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/da
creating build/lib/django/contrib/gis/locale/da/LC_MESSAGES
copying django/contrib/gis/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/da/LC_MESSAGES
copying django/contrib/gis/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/da/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/de
creating build/lib/django/contrib/gis/locale/de/LC_MESSAGES
copying django/contrib/gis/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/de/LC_MESSAGES
copying django/contrib/gis/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/de/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/dsb
creating build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES
copying django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES
copying django/contrib/gis/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/el
creating build/lib/django/contrib/gis/locale/el/LC_MESSAGES
copying django/contrib/gis/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/el/LC_MESSAGES
copying django/contrib/gis/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/el/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/en
creating build/lib/django/contrib/gis/locale/en/LC_MESSAGES
copying django/contrib/gis/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/en/LC_MESSAGES
copying django/contrib/gis/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/en/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/en_AU
creating build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES
copying django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES
copying django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/en_GB
creating build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES
copying django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES
copying django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/eo
creating build/lib/django/contrib/gis/locale/eo/LC_MESSAGES
copying django/contrib/gis/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/eo/LC_MESSAGES
copying django/contrib/gis/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/es
creating build/lib/django/contrib/gis/locale/es/LC_MESSAGES
copying django/contrib/gis/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es/LC_MESSAGES
copying django/contrib/gis/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/es_AR
creating build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES
copying django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES
copying django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/es_CO
creating build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES
copying django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES
copying django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/es_MX
creating build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES
copying django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES
copying django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/es_VE
creating build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES
copying django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES
copying django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/et
creating build/lib/django/contrib/gis/locale/et/LC_MESSAGES
copying django/contrib/gis/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/et/LC_MESSAGES
copying django/contrib/gis/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/et/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/eu
creating build/lib/django/contrib/gis/locale/eu/LC_MESSAGES
copying django/contrib/gis/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/eu/LC_MESSAGES
copying django/contrib/gis/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/fa
creating build/lib/django/contrib/gis/locale/fa/LC_MESSAGES
copying django/contrib/gis/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fa/LC_MESSAGES
copying django/contrib/gis/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/fi
creating build/lib/django/contrib/gis/locale/fi/LC_MESSAGES
copying django/contrib/gis/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fi/LC_MESSAGES
copying django/contrib/gis/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/fr
creating build/lib/django/contrib/gis/locale/fr/LC_MESSAGES
copying django/contrib/gis/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fr/LC_MESSAGES
copying django/contrib/gis/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/fy
creating build/lib/django/contrib/gis/locale/fy/LC_MESSAGES
copying django/contrib/gis/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fy/LC_MESSAGES
copying django/contrib/gis/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ga
creating build/lib/django/contrib/gis/locale/ga/LC_MESSAGES
copying django/contrib/gis/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ga/LC_MESSAGES
copying django/contrib/gis/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/gd
creating build/lib/django/contrib/gis/locale/gd/LC_MESSAGES
copying django/contrib/gis/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/gd/LC_MESSAGES
copying django/contrib/gis/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/gl
creating build/lib/django/contrib/gis/locale/gl/LC_MESSAGES
copying django/contrib/gis/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/gl/LC_MESSAGES
copying django/contrib/gis/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/he
creating build/lib/django/contrib/gis/locale/he/LC_MESSAGES
copying django/contrib/gis/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/he/LC_MESSAGES
copying django/contrib/gis/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/he/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/hi
creating build/lib/django/contrib/gis/locale/hi/LC_MESSAGES
copying django/contrib/gis/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hi/LC_MESSAGES
copying django/contrib/gis/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/hr
creating build/lib/django/contrib/gis/locale/hr/LC_MESSAGES
copying django/contrib/gis/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hr/LC_MESSAGES
copying django/contrib/gis/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/hsb
creating build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES
copying django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES
copying django/contrib/gis/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/hu
creating build/lib/django/contrib/gis/locale/hu/LC_MESSAGES
copying django/contrib/gis/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hu/LC_MESSAGES
copying django/contrib/gis/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/hy
creating build/lib/django/contrib/gis/locale/hy/LC_MESSAGES
copying django/contrib/gis/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hy/LC_MESSAGES
copying django/contrib/gis/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ia
creating build/lib/django/contrib/gis/locale/ia/LC_MESSAGES
copying django/contrib/gis/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ia/LC_MESSAGES
copying django/contrib/gis/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/id
creating build/lib/django/contrib/gis/locale/id/LC_MESSAGES
copying django/contrib/gis/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/id/LC_MESSAGES
copying django/contrib/gis/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/id/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/io
creating build/lib/django/contrib/gis/locale/io/LC_MESSAGES
copying django/contrib/gis/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/io/LC_MESSAGES
copying django/contrib/gis/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/io/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/is
creating build/lib/django/contrib/gis/locale/is/LC_MESSAGES
copying django/contrib/gis/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/is/LC_MESSAGES
copying django/contrib/gis/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/is/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/it
creating build/lib/django/contrib/gis/locale/it/LC_MESSAGES
copying django/contrib/gis/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/it/LC_MESSAGES
copying django/contrib/gis/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/it/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ja
creating build/lib/django/contrib/gis/locale/ja/LC_MESSAGES
copying django/contrib/gis/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ja/LC_MESSAGES
copying django/contrib/gis/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ka
creating build/lib/django/contrib/gis/locale/ka/LC_MESSAGES
copying django/contrib/gis/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ka/LC_MESSAGES
copying django/contrib/gis/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/kk
creating build/lib/django/contrib/gis/locale/kk/LC_MESSAGES
copying django/contrib/gis/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/kk/LC_MESSAGES
copying django/contrib/gis/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/km
creating build/lib/django/contrib/gis/locale/km/LC_MESSAGES
copying django/contrib/gis/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/km/LC_MESSAGES
copying django/contrib/gis/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/km/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/kn
creating build/lib/django/contrib/gis/locale/kn/LC_MESSAGES
copying django/contrib/gis/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/kn/LC_MESSAGES
copying django/contrib/gis/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ko
creating build/lib/django/contrib/gis/locale/ko/LC_MESSAGES
copying django/contrib/gis/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ko/LC_MESSAGES
copying django/contrib/gis/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ky
creating build/lib/django/contrib/gis/locale/ky/LC_MESSAGES
copying django/contrib/gis/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ky/LC_MESSAGES
copying django/contrib/gis/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/lb
creating build/lib/django/contrib/gis/locale/lb/LC_MESSAGES
copying django/contrib/gis/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/lb/LC_MESSAGES
copying django/contrib/gis/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/lt
creating build/lib/django/contrib/gis/locale/lt/LC_MESSAGES
copying django/contrib/gis/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/lt/LC_MESSAGES
copying django/contrib/gis/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/lv
creating build/lib/django/contrib/gis/locale/lv/LC_MESSAGES
copying django/contrib/gis/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/lv/LC_MESSAGES
copying django/contrib/gis/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/mk
creating build/lib/django/contrib/gis/locale/mk/LC_MESSAGES
copying django/contrib/gis/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/mk/LC_MESSAGES
copying django/contrib/gis/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ml
creating build/lib/django/contrib/gis/locale/ml/LC_MESSAGES
copying django/contrib/gis/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ml/LC_MESSAGES
copying django/contrib/gis/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/mn
creating build/lib/django/contrib/gis/locale/mn/LC_MESSAGES
copying django/contrib/gis/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/mn/LC_MESSAGES
copying django/contrib/gis/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/mr
creating build/lib/django/contrib/gis/locale/mr/LC_MESSAGES
copying django/contrib/gis/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/mr/LC_MESSAGES
copying django/contrib/gis/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/my
creating build/lib/django/contrib/gis/locale/my/LC_MESSAGES
copying django/contrib/gis/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/my/LC_MESSAGES
copying django/contrib/gis/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/my/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/nb
creating build/lib/django/contrib/gis/locale/nb/LC_MESSAGES
copying django/contrib/gis/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/nb/LC_MESSAGES
copying django/contrib/gis/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ne
creating build/lib/django/contrib/gis/locale/ne/LC_MESSAGES
copying django/contrib/gis/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ne/LC_MESSAGES
copying django/contrib/gis/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/nl
creating build/lib/django/contrib/gis/locale/nl/LC_MESSAGES
copying django/contrib/gis/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/nl/LC_MESSAGES
copying django/contrib/gis/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/nn
creating build/lib/django/contrib/gis/locale/nn/LC_MESSAGES
copying django/contrib/gis/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/nn/LC_MESSAGES
copying django/contrib/gis/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/os
creating build/lib/django/contrib/gis/locale/os/LC_MESSAGES
copying django/contrib/gis/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/os/LC_MESSAGES
copying django/contrib/gis/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/os/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/pa
creating build/lib/django/contrib/gis/locale/pa/LC_MESSAGES
copying django/contrib/gis/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pa/LC_MESSAGES
copying django/contrib/gis/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/pl
creating build/lib/django/contrib/gis/locale/pl/LC_MESSAGES
copying django/contrib/gis/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pl/LC_MESSAGES
copying django/contrib/gis/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/pt
creating build/lib/django/contrib/gis/locale/pt/LC_MESSAGES
copying django/contrib/gis/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pt/LC_MESSAGES
copying django/contrib/gis/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/pt_BR
creating build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES
copying django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES
copying django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ro
creating build/lib/django/contrib/gis/locale/ro/LC_MESSAGES
copying django/contrib/gis/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ro/LC_MESSAGES
copying django/contrib/gis/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ru
creating build/lib/django/contrib/gis/locale/ru/LC_MESSAGES
copying django/contrib/gis/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ru/LC_MESSAGES
copying django/contrib/gis/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/sk
creating build/lib/django/contrib/gis/locale/sk/LC_MESSAGES
copying django/contrib/gis/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sk/LC_MESSAGES
copying django/contrib/gis/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/sl
creating build/lib/django/contrib/gis/locale/sl/LC_MESSAGES
copying django/contrib/gis/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sl/LC_MESSAGES
copying django/contrib/gis/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/sq
creating build/lib/django/contrib/gis/locale/sq/LC_MESSAGES
copying django/contrib/gis/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sq/LC_MESSAGES
copying django/contrib/gis/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/sr
creating build/lib/django/contrib/gis/locale/sr/LC_MESSAGES
copying django/contrib/gis/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sr/LC_MESSAGES
copying django/contrib/gis/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/sr_Latn
creating build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
copying django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
copying django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/sv
creating build/lib/django/contrib/gis/locale/sv/LC_MESSAGES
copying django/contrib/gis/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sv/LC_MESSAGES
copying django/contrib/gis/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/sw
creating build/lib/django/contrib/gis/locale/sw/LC_MESSAGES
copying django/contrib/gis/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sw/LC_MESSAGES
copying django/contrib/gis/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ta
creating build/lib/django/contrib/gis/locale/ta/LC_MESSAGES
copying django/contrib/gis/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ta/LC_MESSAGES
copying django/contrib/gis/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/te
creating build/lib/django/contrib/gis/locale/te/LC_MESSAGES
copying django/contrib/gis/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/te/LC_MESSAGES
copying django/contrib/gis/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/te/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/tg
creating build/lib/django/contrib/gis/locale/tg/LC_MESSAGES
copying django/contrib/gis/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/tg/LC_MESSAGES
copying django/contrib/gis/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/th
creating build/lib/django/contrib/gis/locale/th/LC_MESSAGES
copying django/contrib/gis/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/th/LC_MESSAGES
copying django/contrib/gis/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/th/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/tr
creating build/lib/django/contrib/gis/locale/tr/LC_MESSAGES
copying django/contrib/gis/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/tr/LC_MESSAGES
copying django/contrib/gis/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/tt
creating build/lib/django/contrib/gis/locale/tt/LC_MESSAGES
copying django/contrib/gis/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/tt/LC_MESSAGES
copying django/contrib/gis/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/udm
creating build/lib/django/contrib/gis/locale/udm/LC_MESSAGES
copying django/contrib/gis/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/udm/LC_MESSAGES
copying django/contrib/gis/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/uk
creating build/lib/django/contrib/gis/locale/uk/LC_MESSAGES
copying django/contrib/gis/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/uk/LC_MESSAGES
copying django/contrib/gis/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ur
creating build/lib/django/contrib/gis/locale/ur/LC_MESSAGES
copying django/contrib/gis/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ur/LC_MESSAGES
copying django/contrib/gis/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/vi
creating build/lib/django/contrib/gis/locale/vi/LC_MESSAGES
copying django/contrib/gis/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/vi/LC_MESSAGES
copying django/contrib/gis/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/zh_Hans
creating build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
copying django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
copying django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/zh_Hant
creating build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
copying django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
copying django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/gis/static
creating build/lib/django/contrib/gis/static/gis
creating build/lib/django/contrib/gis/static/gis/css
copying django/contrib/gis/static/gis/css/ol3.css -> build/lib/django/contrib/gis/static/gis/css
creating build/lib/django/contrib/gis/static/gis/img
copying django/contrib/gis/static/gis/img/draw_line_off.svg -> build/lib/django/contrib/gis/static/gis/img
copying django/contrib/gis/static/gis/img/draw_line_on.svg -> build/lib/django/contrib/gis/static/gis/img
copying django/contrib/gis/static/gis/img/draw_point_off.svg -> build/lib/django/contrib/gis/static/gis/img
copying django/contrib/gis/static/gis/img/draw_point_on.svg -> build/lib/django/contrib/gis/static/gis/img
copying django/contrib/gis/static/gis/img/draw_polygon_off.svg -> build/lib/django/contrib/gis/static/gis/img
copying django/contrib/gis/static/gis/img/draw_polygon_on.svg -> build/lib/django/contrib/gis/static/gis/img
creating build/lib/django/contrib/gis/static/gis/js
copying django/contrib/gis/static/gis/js/OLMapWidget.js -> build/lib/django/contrib/gis/static/gis/js
creating build/lib/django/contrib/gis/templates
creating build/lib/django/contrib/gis/templates/gis
copying django/contrib/gis/templates/gis/openlayers-osm.html -> build/lib/django/contrib/gis/templates/gis
copying django/contrib/gis/templates/gis/openlayers.html -> build/lib/django/contrib/gis/templates/gis
creating build/lib/django/contrib/gis/templates/gis/admin
copying django/contrib/gis/templates/gis/admin/openlayers.html -> build/lib/django/contrib/gis/templates/gis/admin
copying django/contrib/gis/templates/gis/admin/openlayers.js -> build/lib/django/contrib/gis/templates/gis/admin
copying django/contrib/gis/templates/gis/admin/osm.html -> build/lib/django/contrib/gis/templates/gis/admin
copying django/contrib/gis/templates/gis/admin/osm.js -> build/lib/django/contrib/gis/templates/gis/admin
creating build/lib/django/contrib/gis/templates/gis/kml
copying django/contrib/gis/templates/gis/kml/base.kml -> build/lib/django/contrib/gis/templates/gis/kml
copying django/contrib/gis/templates/gis/kml/placemarks.kml -> build/lib/django/contrib/gis/templates/gis/kml
creating build/lib/django/contrib/humanize/locale
creating build/lib/django/contrib/humanize/locale/af
creating build/lib/django/contrib/humanize/locale/af/LC_MESSAGES
copying django/contrib/humanize/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/af/LC_MESSAGES
copying django/contrib/humanize/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/af/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ar
creating build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES
copying django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES
copying django/contrib/humanize/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ar_DZ
creating build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
copying django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
copying django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ast
creating build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES
copying django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES
copying django/contrib/humanize/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/az
creating build/lib/django/contrib/humanize/locale/az/LC_MESSAGES
copying django/contrib/humanize/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/az/LC_MESSAGES
copying django/contrib/humanize/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/az/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/be
creating build/lib/django/contrib/humanize/locale/be/LC_MESSAGES
copying django/contrib/humanize/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/be/LC_MESSAGES
copying django/contrib/humanize/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/be/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/bg
creating build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES
copying django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES
copying django/contrib/humanize/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/bn
creating build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES
copying django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES
copying django/contrib/humanize/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/br
creating build/lib/django/contrib/humanize/locale/br/LC_MESSAGES
copying django/contrib/humanize/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/br/LC_MESSAGES
copying django/contrib/humanize/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/br/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/bs
creating build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES
copying django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES
copying django/contrib/humanize/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ca
creating build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES
copying django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES
copying django/contrib/humanize/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/cs
creating build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES
copying django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES
copying django/contrib/humanize/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/cy
creating build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES
copying django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES
copying django/contrib/humanize/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/da
creating build/lib/django/contrib/humanize/locale/da/LC_MESSAGES
copying django/contrib/humanize/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/da/LC_MESSAGES
copying django/contrib/humanize/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/da/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/de
creating build/lib/django/contrib/humanize/locale/de/LC_MESSAGES
copying django/contrib/humanize/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/de/LC_MESSAGES
copying django/contrib/humanize/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/de/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/dsb
creating build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES
copying django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES
copying django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/el
creating build/lib/django/contrib/humanize/locale/el/LC_MESSAGES
copying django/contrib/humanize/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/el/LC_MESSAGES
copying django/contrib/humanize/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/el/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/en
creating build/lib/django/contrib/humanize/locale/en/LC_MESSAGES
copying django/contrib/humanize/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/en/LC_MESSAGES
copying django/contrib/humanize/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/en/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/en_AU
creating build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES
copying django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES
copying django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/en_GB
creating build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES
copying django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES
copying django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/eo
creating build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES
copying django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES
copying django/contrib/humanize/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/es
creating build/lib/django/contrib/humanize/locale/es/LC_MESSAGES
copying django/contrib/humanize/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es/LC_MESSAGES
copying django/contrib/humanize/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/es_AR
creating build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES
copying django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES
copying django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/es_CO
creating build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES
copying django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES
copying django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/es_MX
creating build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES
copying django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES
copying django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/es_VE
creating build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES
copying django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES
copying django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/et
creating build/lib/django/contrib/humanize/locale/et/LC_MESSAGES
copying django/contrib/humanize/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/et/LC_MESSAGES
copying django/contrib/humanize/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/et/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/eu
creating build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES
copying django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES
copying django/contrib/humanize/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/fa
creating build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES
copying django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES
copying django/contrib/humanize/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/fi
creating build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES
copying django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES
copying django/contrib/humanize/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/fr
creating build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES
copying django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES
copying django/contrib/humanize/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/fy
creating build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES
copying django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES
copying django/contrib/humanize/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ga
creating build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES
copying django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES
copying django/contrib/humanize/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/gd
creating build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES
copying django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES
copying django/contrib/humanize/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/gl
creating build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES
copying django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES
copying django/contrib/humanize/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/he
creating build/lib/django/contrib/humanize/locale/he/LC_MESSAGES
copying django/contrib/humanize/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/he/LC_MESSAGES
copying django/contrib/humanize/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/he/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/hi
creating build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES
copying django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES
copying django/contrib/humanize/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/hr
creating build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES
copying django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES
copying django/contrib/humanize/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/hsb
creating build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES
copying django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES
copying django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/hu
creating build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES
copying django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES
copying django/contrib/humanize/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/hy
creating build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES
copying django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES
copying django/contrib/humanize/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ia
creating build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES
copying django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES
copying django/contrib/humanize/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/id
creating build/lib/django/contrib/humanize/locale/id/LC_MESSAGES
copying django/contrib/humanize/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/id/LC_MESSAGES
copying django/contrib/humanize/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/id/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/io
creating build/lib/django/contrib/humanize/locale/io/LC_MESSAGES
copying django/contrib/humanize/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/io/LC_MESSAGES
copying django/contrib/humanize/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/io/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/is
creating build/lib/django/contrib/humanize/locale/is/LC_MESSAGES
copying django/contrib/humanize/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/is/LC_MESSAGES
copying django/contrib/humanize/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/is/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/it
creating build/lib/django/contrib/humanize/locale/it/LC_MESSAGES
copying django/contrib/humanize/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/it/LC_MESSAGES
copying django/contrib/humanize/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/it/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ja
creating build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES
copying django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES
copying django/contrib/humanize/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ka
creating build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES
copying django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES
copying django/contrib/humanize/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/kk
creating build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES
copying django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES
copying django/contrib/humanize/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/km
creating build/lib/django/contrib/humanize/locale/km/LC_MESSAGES
copying django/contrib/humanize/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/km/LC_MESSAGES
copying django/contrib/humanize/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/km/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/kn
creating build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES
copying django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES
copying django/contrib/humanize/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ko
creating build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES
copying django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES
copying django/contrib/humanize/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ky
creating build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES
copying django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES
copying django/contrib/humanize/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/lb
creating build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES
copying django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES
copying django/contrib/humanize/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/lt
creating build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES
copying django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES
copying django/contrib/humanize/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/lv
creating build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES
copying django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES
copying django/contrib/humanize/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/mk
creating build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES
copying django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES
copying django/contrib/humanize/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ml
creating build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES
copying django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES
copying django/contrib/humanize/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/mn
creating build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES
copying django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES
copying django/contrib/humanize/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/mr
creating build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES
copying django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES
copying django/contrib/humanize/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ms
creating build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES
copying django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES
copying django/contrib/humanize/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/my
creating build/lib/django/contrib/humanize/locale/my/LC_MESSAGES
copying django/contrib/humanize/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/my/LC_MESSAGES
copying django/contrib/humanize/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/my/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/nb
creating build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES
copying django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES
copying django/contrib/humanize/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ne
creating build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES
copying django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES
copying django/contrib/humanize/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/nl
creating build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES
copying django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES
copying django/contrib/humanize/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/nn
creating build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES
copying django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES
copying django/contrib/humanize/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/os
creating build/lib/django/contrib/humanize/locale/os/LC_MESSAGES
copying django/contrib/humanize/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/os/LC_MESSAGES
copying django/contrib/humanize/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/os/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/pa
creating build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES
copying django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES
copying django/contrib/humanize/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/pl
creating build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES
copying django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES
copying django/contrib/humanize/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/pt
creating build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES
copying django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES
copying django/contrib/humanize/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/pt_BR
creating build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
copying django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
copying django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ro
creating build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES
copying django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES
copying django/contrib/humanize/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ru
creating build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES
copying django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES
copying django/contrib/humanize/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/sk
creating build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES
copying django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES
copying django/contrib/humanize/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/sl
creating build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES
copying django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES
copying django/contrib/humanize/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/sq
creating build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES
copying django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES
copying django/contrib/humanize/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/sr
creating build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES
copying django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES
copying django/contrib/humanize/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/sr_Latn
creating build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
copying django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
copying django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/sv
creating build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES
copying django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES
copying django/contrib/humanize/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/sw
creating build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES
copying django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES
copying django/contrib/humanize/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ta
creating build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES
copying django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES
copying django/contrib/humanize/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/te
creating build/lib/django/contrib/humanize/locale/te/LC_MESSAGES
copying django/contrib/humanize/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/te/LC_MESSAGES
copying django/contrib/humanize/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/te/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/tg
creating build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES
copying django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES
copying django/contrib/humanize/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/th
creating build/lib/django/contrib/humanize/locale/th/LC_MESSAGES
copying django/contrib/humanize/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/th/LC_MESSAGES
copying django/contrib/humanize/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/th/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/tr
creating build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES
copying django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES
copying django/contrib/humanize/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/tt
creating build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES
copying django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES
copying django/contrib/humanize/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/udm
creating build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES
copying django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES
copying django/contrib/humanize/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/uk
creating build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES
copying django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES
copying django/contrib/humanize/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ur
creating build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES
copying django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES
copying django/contrib/humanize/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/uz
creating build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES
copying django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES
copying django/contrib/humanize/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/vi
creating build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES
copying django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES
copying django/contrib/humanize/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/zh_Hans
creating build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
copying django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
copying django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/zh_Hant
creating build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
copying django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
copying django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/postgres/jinja2
creating build/lib/django/contrib/postgres/jinja2/postgres
creating build/lib/django/contrib/postgres/jinja2/postgres/widgets
copying django/contrib/postgres/jinja2/postgres/widgets/split_array.html -> build/lib/django/contrib/postgres/jinja2/postgres/widgets
creating build/lib/django/contrib/postgres/locale
creating build/lib/django/contrib/postgres/locale/af
creating build/lib/django/contrib/postgres/locale/af/LC_MESSAGES
copying django/contrib/postgres/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/af/LC_MESSAGES
copying django/contrib/postgres/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/af/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ar
creating build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES
copying django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES
copying django/contrib/postgres/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ar_DZ
creating build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
copying django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
copying django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/az
creating build/lib/django/contrib/postgres/locale/az/LC_MESSAGES
copying django/contrib/postgres/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/az/LC_MESSAGES
copying django/contrib/postgres/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/az/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/be
creating build/lib/django/contrib/postgres/locale/be/LC_MESSAGES
copying django/contrib/postgres/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/be/LC_MESSAGES
copying django/contrib/postgres/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/be/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/bg
creating build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES
copying django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES
copying django/contrib/postgres/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ca
creating build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES
copying django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES
copying django/contrib/postgres/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/cs
creating build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES
copying django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES
copying django/contrib/postgres/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/da
creating build/lib/django/contrib/postgres/locale/da/LC_MESSAGES
copying django/contrib/postgres/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/da/LC_MESSAGES
copying django/contrib/postgres/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/da/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/de
creating build/lib/django/contrib/postgres/locale/de/LC_MESSAGES
copying django/contrib/postgres/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/de/LC_MESSAGES
copying django/contrib/postgres/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/de/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/dsb
creating build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES
copying django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES
copying django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/el
creating build/lib/django/contrib/postgres/locale/el/LC_MESSAGES
copying django/contrib/postgres/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/el/LC_MESSAGES
copying django/contrib/postgres/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/el/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/en
creating build/lib/django/contrib/postgres/locale/en/LC_MESSAGES
copying django/contrib/postgres/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/en/LC_MESSAGES
copying django/contrib/postgres/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/en/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/eo
creating build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES
copying django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES
copying django/contrib/postgres/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/es
creating build/lib/django/contrib/postgres/locale/es/LC_MESSAGES
copying django/contrib/postgres/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/es/LC_MESSAGES
copying django/contrib/postgres/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/es/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/es_AR
creating build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES
copying django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES
copying django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/es_CO
creating build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES
copying django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES
copying django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/es_MX
creating build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES
copying django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES
copying django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/et
creating build/lib/django/contrib/postgres/locale/et/LC_MESSAGES
copying django/contrib/postgres/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/et/LC_MESSAGES
copying django/contrib/postgres/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/et/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/eu
creating build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES
copying django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES
copying django/contrib/postgres/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/fa
creating build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES
copying django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES
copying django/contrib/postgres/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/fi
creating build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES
copying django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES
copying django/contrib/postgres/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/fr
creating build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES
copying django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES
copying django/contrib/postgres/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/gd
creating build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES
copying django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES
copying django/contrib/postgres/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/gl
creating build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES
copying django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES
copying django/contrib/postgres/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/he
creating build/lib/django/contrib/postgres/locale/he/LC_MESSAGES
copying django/contrib/postgres/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/he/LC_MESSAGES
copying django/contrib/postgres/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/he/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/hr
creating build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES
copying django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES
copying django/contrib/postgres/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/hsb
creating build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES
copying django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES
copying django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/hu
creating build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES
copying django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES
copying django/contrib/postgres/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/hy
creating build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES
copying django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES
copying django/contrib/postgres/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ia
creating build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES
copying django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES
copying django/contrib/postgres/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/id
creating build/lib/django/contrib/postgres/locale/id/LC_MESSAGES
copying django/contrib/postgres/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/id/LC_MESSAGES
copying django/contrib/postgres/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/id/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/is
creating build/lib/django/contrib/postgres/locale/is/LC_MESSAGES
copying django/contrib/postgres/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/is/LC_MESSAGES
copying django/contrib/postgres/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/is/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/it
creating build/lib/django/contrib/postgres/locale/it/LC_MESSAGES
copying django/contrib/postgres/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/it/LC_MESSAGES
copying django/contrib/postgres/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/it/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ja
creating build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES
copying django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES
copying django/contrib/postgres/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ka
creating build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES
copying django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES
copying django/contrib/postgres/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/kk
creating build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES
copying django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES
copying django/contrib/postgres/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ko
creating build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES
copying django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES
copying django/contrib/postgres/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ky
creating build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES
copying django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES
copying django/contrib/postgres/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/lt
creating build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES
copying django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES
copying django/contrib/postgres/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/lv
creating build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES
copying django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES
copying django/contrib/postgres/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/mk
creating build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES
copying django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES
copying django/contrib/postgres/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ml
creating build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES
copying django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES
copying django/contrib/postgres/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/mn
creating build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES
copying django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES
copying django/contrib/postgres/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/nb
creating build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES
copying django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES
copying django/contrib/postgres/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ne
creating build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES
copying django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES
copying django/contrib/postgres/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/nl
creating build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES
copying django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES
copying django/contrib/postgres/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/pl
creating build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES
copying django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES
copying django/contrib/postgres/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/pt
creating build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES
copying django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES
copying django/contrib/postgres/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/pt_BR
creating build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
copying django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
copying django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ro
creating build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES
copying django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES
copying django/contrib/postgres/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ru
creating build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES
copying django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES
copying django/contrib/postgres/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/sk
creating build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES
copying django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES
copying django/contrib/postgres/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/sl
creating build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES
copying django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES
copying django/contrib/postgres/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/sq
creating build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES
copying django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES
copying django/contrib/postgres/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/sr
creating build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES
copying django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES
copying django/contrib/postgres/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/sr_Latn
creating build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
copying django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
copying django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/sv
creating build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES
copying django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES
copying django/contrib/postgres/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/tg
creating build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES
copying django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES
copying django/contrib/postgres/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/tk
creating build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES
copying django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES
copying django/contrib/postgres/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/tr
creating build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES
copying django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES
copying django/contrib/postgres/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/uk
creating build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES
copying django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES
copying django/contrib/postgres/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/uz
creating build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES
copying django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES
copying django/contrib/postgres/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/zh_Hans
creating build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
copying django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
copying django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/zh_Hant
creating build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
copying django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
copying django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/postgres/templates
creating build/lib/django/contrib/postgres/templates/postgres
creating build/lib/django/contrib/postgres/templates/postgres/widgets
copying django/contrib/postgres/templates/postgres/widgets/split_array.html -> build/lib/django/contrib/postgres/templates/postgres/widgets
creating build/lib/django/contrib/redirects/locale
creating build/lib/django/contrib/redirects/locale/af
creating build/lib/django/contrib/redirects/locale/af/LC_MESSAGES
copying django/contrib/redirects/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/af/LC_MESSAGES
copying django/contrib/redirects/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/af/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ar
creating build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES
copying django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES
copying django/contrib/redirects/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ar_DZ
creating build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
copying django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
copying django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ast
creating build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES
copying django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES
copying django/contrib/redirects/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/az
creating build/lib/django/contrib/redirects/locale/az/LC_MESSAGES
copying django/contrib/redirects/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/az/LC_MESSAGES
copying django/contrib/redirects/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/az/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/be
creating build/lib/django/contrib/redirects/locale/be/LC_MESSAGES
copying django/contrib/redirects/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/be/LC_MESSAGES
copying django/contrib/redirects/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/be/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/bg
creating build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES
copying django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES
copying django/contrib/redirects/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/bn
creating build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES
copying django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES
copying django/contrib/redirects/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/br
creating build/lib/django/contrib/redirects/locale/br/LC_MESSAGES
copying django/contrib/redirects/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/br/LC_MESSAGES
copying django/contrib/redirects/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/br/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/bs
creating build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES
copying django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES
copying django/contrib/redirects/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ca
creating build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES
copying django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES
copying django/contrib/redirects/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/cs
creating build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES
copying django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES
copying django/contrib/redirects/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/cy
creating build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES
copying django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES
copying django/contrib/redirects/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/da
creating build/lib/django/contrib/redirects/locale/da/LC_MESSAGES
copying django/contrib/redirects/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/da/LC_MESSAGES
copying django/contrib/redirects/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/da/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/de
creating build/lib/django/contrib/redirects/locale/de/LC_MESSAGES
copying django/contrib/redirects/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/de/LC_MESSAGES
copying django/contrib/redirects/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/de/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/dsb
creating build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES
copying django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES
copying django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/el
creating build/lib/django/contrib/redirects/locale/el/LC_MESSAGES
copying django/contrib/redirects/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/el/LC_MESSAGES
copying django/contrib/redirects/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/el/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/en
creating build/lib/django/contrib/redirects/locale/en/LC_MESSAGES
copying django/contrib/redirects/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/en/LC_MESSAGES
copying django/contrib/redirects/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/en/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/en_AU
creating build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES
copying django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES
copying django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/en_GB
creating build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES
copying django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES
copying django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/eo
creating build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES
copying django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES
copying django/contrib/redirects/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/es
creating build/lib/django/contrib/redirects/locale/es/LC_MESSAGES
copying django/contrib/redirects/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es/LC_MESSAGES
copying django/contrib/redirects/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/es_AR
creating build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES
copying django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES
copying django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/es_CO
creating build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES
copying django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES
copying django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/es_MX
creating build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES
copying django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES
copying django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/es_VE
creating build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES
copying django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES
copying django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/et
creating build/lib/django/contrib/redirects/locale/et/LC_MESSAGES
copying django/contrib/redirects/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/et/LC_MESSAGES
copying django/contrib/redirects/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/et/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/eu
creating build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES
copying django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES
copying django/contrib/redirects/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/fa
creating build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES
copying django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES
copying django/contrib/redirects/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/fi
creating build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES
copying django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES
copying django/contrib/redirects/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/fr
creating build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES
copying django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES
copying django/contrib/redirects/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/fy
creating build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES
copying django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES
copying django/contrib/redirects/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ga
creating build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES
copying django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES
copying django/contrib/redirects/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/gd
creating build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES
copying django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES
copying django/contrib/redirects/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/gl
creating build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES
copying django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES
copying django/contrib/redirects/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/he
creating build/lib/django/contrib/redirects/locale/he/LC_MESSAGES
copying django/contrib/redirects/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/he/LC_MESSAGES
copying django/contrib/redirects/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/he/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/hi
creating build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES
copying django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES
copying django/contrib/redirects/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/hr
creating build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES
copying django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES
copying django/contrib/redirects/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/hsb
creating build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES
copying django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES
copying django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/hu
creating build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES
copying django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES
copying django/contrib/redirects/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/hy
creating build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES
copying django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES
copying django/contrib/redirects/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ia
creating build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES
copying django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES
copying django/contrib/redirects/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/id
creating build/lib/django/contrib/redirects/locale/id/LC_MESSAGES
copying django/contrib/redirects/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/id/LC_MESSAGES
copying django/contrib/redirects/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/id/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/io
creating build/lib/django/contrib/redirects/locale/io/LC_MESSAGES
copying django/contrib/redirects/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/io/LC_MESSAGES
copying django/contrib/redirects/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/io/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/is
creating build/lib/django/contrib/redirects/locale/is/LC_MESSAGES
copying django/contrib/redirects/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/is/LC_MESSAGES
copying django/contrib/redirects/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/is/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/it
creating build/lib/django/contrib/redirects/locale/it/LC_MESSAGES
copying django/contrib/redirects/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/it/LC_MESSAGES
copying django/contrib/redirects/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/it/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ja
creating build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES
copying django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES
copying django/contrib/redirects/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ka
creating build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES
copying django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES
copying django/contrib/redirects/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/kab
creating build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES
copying django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES
copying django/contrib/redirects/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/kk
creating build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES
copying django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES
copying django/contrib/redirects/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/km
creating build/lib/django/contrib/redirects/locale/km/LC_MESSAGES
copying django/contrib/redirects/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/km/LC_MESSAGES
copying django/contrib/redirects/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/km/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/kn
creating build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES
copying django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES
copying django/contrib/redirects/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ko
creating build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES
copying django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES
copying django/contrib/redirects/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ky
creating build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES
copying django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES
copying django/contrib/redirects/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/lb
creating build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES
copying django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES
copying django/contrib/redirects/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/lt
creating build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES
copying django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES
copying django/contrib/redirects/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/lv
creating build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES
copying django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES
copying django/contrib/redirects/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/mk
creating build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES
copying django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES
copying django/contrib/redirects/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ml
creating build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES
copying django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES
copying django/contrib/redirects/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/mn
creating build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES
copying django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES
copying django/contrib/redirects/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/mr
creating build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES
copying django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES
copying django/contrib/redirects/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/my
creating build/lib/django/contrib/redirects/locale/my/LC_MESSAGES
copying django/contrib/redirects/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/my/LC_MESSAGES
copying django/contrib/redirects/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/my/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/nb
creating build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES
copying django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES
copying django/contrib/redirects/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ne
creating build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES
copying django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES
copying django/contrib/redirects/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/nl
creating build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES
copying django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES
copying django/contrib/redirects/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/nn
creating build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES
copying django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES
copying django/contrib/redirects/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/os
creating build/lib/django/contrib/redirects/locale/os/LC_MESSAGES
copying django/contrib/redirects/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/os/LC_MESSAGES
copying django/contrib/redirects/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/os/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/pa
creating build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES
copying django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES
copying django/contrib/redirects/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/pl
creating build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES
copying django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES
copying django/contrib/redirects/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/pt
creating build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES
copying django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES
copying django/contrib/redirects/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/pt_BR
creating build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
copying django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
copying django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ro
creating build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES
copying django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES
copying django/contrib/redirects/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ru
creating build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES
copying django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES
copying django/contrib/redirects/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/sk
creating build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES
copying django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES
copying django/contrib/redirects/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/sl
creating build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES
copying django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES
copying django/contrib/redirects/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/sq
creating build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES
copying django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES
copying django/contrib/redirects/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/sr
creating build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES
copying django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES
copying django/contrib/redirects/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/sr_Latn
creating build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
copying django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
copying django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/sv
creating build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES
copying django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES
copying django/contrib/redirects/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/sw
creating build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES
copying django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES
copying django/contrib/redirects/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ta
creating build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES
copying django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES
copying django/contrib/redirects/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/te
creating build/lib/django/contrib/redirects/locale/te/LC_MESSAGES
copying django/contrib/redirects/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/te/LC_MESSAGES
copying django/contrib/redirects/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/te/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/tg
creating build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES
copying django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES
copying django/contrib/redirects/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/th
creating build/lib/django/contrib/redirects/locale/th/LC_MESSAGES
copying django/contrib/redirects/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/th/LC_MESSAGES
copying django/contrib/redirects/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/th/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/tk
creating build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES
copying django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES
copying django/contrib/redirects/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/tr
creating build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES
copying django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES
copying django/contrib/redirects/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/tt
creating build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES
copying django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES
copying django/contrib/redirects/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/udm
creating build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES
copying django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES
copying django/contrib/redirects/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/uk
creating build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES
copying django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES
copying django/contrib/redirects/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ur
creating build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES
copying django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES
copying django/contrib/redirects/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/uz
creating build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES
copying django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES
copying django/contrib/redirects/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/vi
creating build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES
copying django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES
copying django/contrib/redirects/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/zh_Hans
creating build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
copying django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
copying django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/zh_Hant
creating build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
copying django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
copying django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale
creating build/lib/django/contrib/sessions/locale/af
creating build/lib/django/contrib/sessions/locale/af/LC_MESSAGES
copying django/contrib/sessions/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/af/LC_MESSAGES
copying django/contrib/sessions/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/af/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ar
creating build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES
copying django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES
copying django/contrib/sessions/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ar_DZ
creating build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
copying django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
copying django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ast
creating build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES
copying django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES
copying django/contrib/sessions/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/az
creating build/lib/django/contrib/sessions/locale/az/LC_MESSAGES
copying django/contrib/sessions/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/az/LC_MESSAGES
copying django/contrib/sessions/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/az/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/be
creating build/lib/django/contrib/sessions/locale/be/LC_MESSAGES
copying django/contrib/sessions/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/be/LC_MESSAGES
copying django/contrib/sessions/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/be/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/bg
creating build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES
copying django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES
copying django/contrib/sessions/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/bn
creating build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES
copying django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES
copying django/contrib/sessions/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/br
creating build/lib/django/contrib/sessions/locale/br/LC_MESSAGES
copying django/contrib/sessions/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/br/LC_MESSAGES
copying django/contrib/sessions/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/br/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/bs
creating build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES
copying django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES
copying django/contrib/sessions/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ca
creating build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES
copying django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES
copying django/contrib/sessions/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/cs
creating build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES
copying django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES
copying django/contrib/sessions/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/cy
creating build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES
copying django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES
copying django/contrib/sessions/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/da
creating build/lib/django/contrib/sessions/locale/da/LC_MESSAGES
copying django/contrib/sessions/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/da/LC_MESSAGES
copying django/contrib/sessions/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/da/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/de
creating build/lib/django/contrib/sessions/locale/de/LC_MESSAGES
copying django/contrib/sessions/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/de/LC_MESSAGES
copying django/contrib/sessions/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/de/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/dsb
creating build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES
copying django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES
copying django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/el
creating build/lib/django/contrib/sessions/locale/el/LC_MESSAGES
copying django/contrib/sessions/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/el/LC_MESSAGES
copying django/contrib/sessions/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/el/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/en
creating build/lib/django/contrib/sessions/locale/en/LC_MESSAGES
copying django/contrib/sessions/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/en/LC_MESSAGES
copying django/contrib/sessions/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/en/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/en_AU
creating build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES
copying django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES
copying django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/en_GB
creating build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES
copying django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES
copying django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/eo
creating build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES
copying django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES
copying django/contrib/sessions/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/es
creating build/lib/django/contrib/sessions/locale/es/LC_MESSAGES
copying django/contrib/sessions/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es/LC_MESSAGES
copying django/contrib/sessions/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/es_AR
creating build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES
copying django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES
copying django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/es_CO
creating build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES
copying django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES
copying django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/es_MX
creating build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES
copying django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES
copying django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/es_VE
creating build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES
copying django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES
copying django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/et
creating build/lib/django/contrib/sessions/locale/et/LC_MESSAGES
copying django/contrib/sessions/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/et/LC_MESSAGES
copying django/contrib/sessions/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/et/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/eu
creating build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES
copying django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES
copying django/contrib/sessions/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/fa
creating build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES
copying django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES
copying django/contrib/sessions/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/fi
creating build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES
copying django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES
copying django/contrib/sessions/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/fr
creating build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES
copying django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES
copying django/contrib/sessions/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/fy
creating build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES
copying django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES
copying django/contrib/sessions/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ga
creating build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES
copying django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES
copying django/contrib/sessions/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/gd
creating build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES
copying django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES
copying django/contrib/sessions/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/gl
creating build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES
copying django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES
copying django/contrib/sessions/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/he
creating build/lib/django/contrib/sessions/locale/he/LC_MESSAGES
copying django/contrib/sessions/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/he/LC_MESSAGES
copying django/contrib/sessions/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/he/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/hi
creating build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES
copying django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES
copying django/contrib/sessions/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/hr
creating build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES
copying django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES
copying django/contrib/sessions/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/hsb
creating build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES
copying django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES
copying django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/hu
creating build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES
copying django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES
copying django/contrib/sessions/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/hy
creating build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES
copying django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES
copying django/contrib/sessions/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ia
creating build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES
copying django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES
copying django/contrib/sessions/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/id
creating build/lib/django/contrib/sessions/locale/id/LC_MESSAGES
copying django/contrib/sessions/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/id/LC_MESSAGES
copying django/contrib/sessions/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/id/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/io
creating build/lib/django/contrib/sessions/locale/io/LC_MESSAGES
copying django/contrib/sessions/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/io/LC_MESSAGES
copying django/contrib/sessions/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/io/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/is
creating build/lib/django/contrib/sessions/locale/is/LC_MESSAGES
copying django/contrib/sessions/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/is/LC_MESSAGES
copying django/contrib/sessions/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/is/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/it
creating build/lib/django/contrib/sessions/locale/it/LC_MESSAGES
copying django/contrib/sessions/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/it/LC_MESSAGES
copying django/contrib/sessions/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/it/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ja
creating build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES
copying django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES
copying django/contrib/sessions/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ka
creating build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES
copying django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES
copying django/contrib/sessions/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/kab
creating build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES
copying django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES
copying django/contrib/sessions/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/kk
creating build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES
copying django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES
copying django/contrib/sessions/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/km
creating build/lib/django/contrib/sessions/locale/km/LC_MESSAGES
copying django/contrib/sessions/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/km/LC_MESSAGES
copying django/contrib/sessions/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/km/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/kn
creating build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES
copying django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES
copying django/contrib/sessions/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ko
creating build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES
copying django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES
copying django/contrib/sessions/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ky
creating build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES
copying django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES
copying django/contrib/sessions/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/lb
creating build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES
copying django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES
copying django/contrib/sessions/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/lt
creating build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES
copying django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES
copying django/contrib/sessions/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/lv
creating build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES
copying django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES
copying django/contrib/sessions/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/mk
creating build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES
copying django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES
copying django/contrib/sessions/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ml
creating build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES
copying django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES
copying django/contrib/sessions/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/mn
creating build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES
copying django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES
copying django/contrib/sessions/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/mr
creating build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES
copying django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES
copying django/contrib/sessions/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/my
creating build/lib/django/contrib/sessions/locale/my/LC_MESSAGES
copying django/contrib/sessions/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/my/LC_MESSAGES
copying django/contrib/sessions/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/my/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/nb
creating build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES
copying django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES
copying django/contrib/sessions/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ne
creating build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES
copying django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES
copying django/contrib/sessions/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/nl
creating build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES
copying django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES
copying django/contrib/sessions/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/nn
creating build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES
copying django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES
copying django/contrib/sessions/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/os
creating build/lib/django/contrib/sessions/locale/os/LC_MESSAGES
copying django/contrib/sessions/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/os/LC_MESSAGES
copying django/contrib/sessions/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/os/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/pa
creating build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES
copying django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES
copying django/contrib/sessions/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/pl
creating build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES
copying django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES
copying django/contrib/sessions/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/pt
creating build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES
copying django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES
copying django/contrib/sessions/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/pt_BR
creating build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
copying django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
copying django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ro
creating build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES
copying django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES
copying django/contrib/sessions/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ru
creating build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES
copying django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES
copying django/contrib/sessions/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/sk
creating build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES
copying django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES
copying django/contrib/sessions/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/sl
creating build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES
copying django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES
copying django/contrib/sessions/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/sq
creating build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES
copying django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES
copying django/contrib/sessions/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/sr
creating build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES
copying django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES
copying django/contrib/sessions/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/sr_Latn
creating build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
copying django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
copying django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/sv
creating build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES
copying django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES
copying django/contrib/sessions/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/sw
creating build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES
copying django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES
copying django/contrib/sessions/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ta
creating build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES
copying django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES
copying django/contrib/sessions/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/te
creating build/lib/django/contrib/sessions/locale/te/LC_MESSAGES
copying django/contrib/sessions/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/te/LC_MESSAGES
copying django/contrib/sessions/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/te/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/tg
creating build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES
copying django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES
copying django/contrib/sessions/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/th
creating build/lib/django/contrib/sessions/locale/th/LC_MESSAGES
copying django/contrib/sessions/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/th/LC_MESSAGES
copying django/contrib/sessions/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/th/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/tk
creating build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES
copying django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES
copying django/contrib/sessions/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/tr
creating build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES
copying django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES
copying django/contrib/sessions/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/tt
creating build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES
copying django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES
copying django/contrib/sessions/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/udm
creating build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES
copying django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES
copying django/contrib/sessions/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/uk
creating build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES
copying django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES
copying django/contrib/sessions/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ur
creating build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES
copying django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES
copying django/contrib/sessions/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/uz
creating build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES
copying django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES
copying django/contrib/sessions/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/vi
creating build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES
copying django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES
copying django/contrib/sessions/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/zh_Hans
creating build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
copying django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
copying django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/zh_Hant
creating build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
copying django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
copying django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/sitemaps/templates
copying django/contrib/sitemaps/templates/sitemap.xml -> build/lib/django/contrib/sitemaps/templates
copying django/contrib/sitemaps/templates/sitemap_index.xml -> build/lib/django/contrib/sitemaps/templates
creating build/lib/django/contrib/sites/locale
creating build/lib/django/contrib/sites/locale/af
creating build/lib/django/contrib/sites/locale/af/LC_MESSAGES
copying django/contrib/sites/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/af/LC_MESSAGES
copying django/contrib/sites/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/af/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ar
creating build/lib/django/contrib/sites/locale/ar/LC_MESSAGES
copying django/contrib/sites/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ar/LC_MESSAGES
copying django/contrib/sites/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ar_DZ
creating build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
copying django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
copying django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ast
creating build/lib/django/contrib/sites/locale/ast/LC_MESSAGES
copying django/contrib/sites/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ast/LC_MESSAGES
copying django/contrib/sites/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/az
creating build/lib/django/contrib/sites/locale/az/LC_MESSAGES
copying django/contrib/sites/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/az/LC_MESSAGES
copying django/contrib/sites/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/az/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/be
creating build/lib/django/contrib/sites/locale/be/LC_MESSAGES
copying django/contrib/sites/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/be/LC_MESSAGES
copying django/contrib/sites/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/be/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/bg
creating build/lib/django/contrib/sites/locale/bg/LC_MESSAGES
copying django/contrib/sites/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/bg/LC_MESSAGES
copying django/contrib/sites/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/bn
creating build/lib/django/contrib/sites/locale/bn/LC_MESSAGES
copying django/contrib/sites/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/bn/LC_MESSAGES
copying django/contrib/sites/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/br
creating build/lib/django/contrib/sites/locale/br/LC_MESSAGES
copying django/contrib/sites/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/br/LC_MESSAGES
copying django/contrib/sites/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/br/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/bs
creating build/lib/django/contrib/sites/locale/bs/LC_MESSAGES
copying django/contrib/sites/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/bs/LC_MESSAGES
copying django/contrib/sites/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ca
creating build/lib/django/contrib/sites/locale/ca/LC_MESSAGES
copying django/contrib/sites/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ca/LC_MESSAGES
copying django/contrib/sites/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/cs
creating build/lib/django/contrib/sites/locale/cs/LC_MESSAGES
copying django/contrib/sites/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/cs/LC_MESSAGES
copying django/contrib/sites/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/cy
creating build/lib/django/contrib/sites/locale/cy/LC_MESSAGES
copying django/contrib/sites/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/cy/LC_MESSAGES
copying django/contrib/sites/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/da
creating build/lib/django/contrib/sites/locale/da/LC_MESSAGES
copying django/contrib/sites/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/da/LC_MESSAGES
copying django/contrib/sites/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/da/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/de
creating build/lib/django/contrib/sites/locale/de/LC_MESSAGES
copying django/contrib/sites/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/de/LC_MESSAGES
copying django/contrib/sites/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/de/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/dsb
creating build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES
copying django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES
copying django/contrib/sites/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/el
creating build/lib/django/contrib/sites/locale/el/LC_MESSAGES
copying django/contrib/sites/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/el/LC_MESSAGES
copying django/contrib/sites/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/el/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/en
creating build/lib/django/contrib/sites/locale/en/LC_MESSAGES
copying django/contrib/sites/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/en/LC_MESSAGES
copying django/contrib/sites/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/en/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/en_AU
creating build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES
copying django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES
copying django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/en_GB
creating build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES
copying django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES
copying django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/eo
creating build/lib/django/contrib/sites/locale/eo/LC_MESSAGES
copying django/contrib/sites/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/eo/LC_MESSAGES
copying django/contrib/sites/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/es
creating build/lib/django/contrib/sites/locale/es/LC_MESSAGES
copying django/contrib/sites/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es/LC_MESSAGES
copying django/contrib/sites/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/es_AR
creating build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES
copying django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES
copying django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/es_CO
creating build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES
copying django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES
copying django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/es_MX
creating build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES
copying django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES
copying django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/es_VE
creating build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES
copying django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES
copying django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/et
creating build/lib/django/contrib/sites/locale/et/LC_MESSAGES
copying django/contrib/sites/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/et/LC_MESSAGES
copying django/contrib/sites/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/et/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/eu
creating build/lib/django/contrib/sites/locale/eu/LC_MESSAGES
copying django/contrib/sites/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/eu/LC_MESSAGES
copying django/contrib/sites/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/fa
creating build/lib/django/contrib/sites/locale/fa/LC_MESSAGES
copying django/contrib/sites/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fa/LC_MESSAGES
copying django/contrib/sites/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/fi
creating build/lib/django/contrib/sites/locale/fi/LC_MESSAGES
copying django/contrib/sites/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fi/LC_MESSAGES
copying django/contrib/sites/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/fr
creating build/lib/django/contrib/sites/locale/fr/LC_MESSAGES
copying django/contrib/sites/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fr/LC_MESSAGES
copying django/contrib/sites/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/fy
creating build/lib/django/contrib/sites/locale/fy/LC_MESSAGES
copying django/contrib/sites/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fy/LC_MESSAGES
copying django/contrib/sites/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ga
creating build/lib/django/contrib/sites/locale/ga/LC_MESSAGES
copying django/contrib/sites/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ga/LC_MESSAGES
copying django/contrib/sites/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/gd
creating build/lib/django/contrib/sites/locale/gd/LC_MESSAGES
copying django/contrib/sites/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/gd/LC_MESSAGES
copying django/contrib/sites/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/gl
creating build/lib/django/contrib/sites/locale/gl/LC_MESSAGES
copying django/contrib/sites/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/gl/LC_MESSAGES
copying django/contrib/sites/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/he
creating build/lib/django/contrib/sites/locale/he/LC_MESSAGES
copying django/contrib/sites/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/he/LC_MESSAGES
copying django/contrib/sites/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/he/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/hi
creating build/lib/django/contrib/sites/locale/hi/LC_MESSAGES
copying django/contrib/sites/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hi/LC_MESSAGES
copying django/contrib/sites/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/hr
creating build/lib/django/contrib/sites/locale/hr/LC_MESSAGES
copying django/contrib/sites/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hr/LC_MESSAGES
copying django/contrib/sites/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/hsb
creating build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES
copying django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES
copying django/contrib/sites/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/hu
creating build/lib/django/contrib/sites/locale/hu/LC_MESSAGES
copying django/contrib/sites/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hu/LC_MESSAGES
copying django/contrib/sites/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/hy
creating build/lib/django/contrib/sites/locale/hy/LC_MESSAGES
copying django/contrib/sites/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hy/LC_MESSAGES
copying django/contrib/sites/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ia
creating build/lib/django/contrib/sites/locale/ia/LC_MESSAGES
copying django/contrib/sites/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ia/LC_MESSAGES
copying django/contrib/sites/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/id
creating build/lib/django/contrib/sites/locale/id/LC_MESSAGES
copying django/contrib/sites/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/id/LC_MESSAGES
copying django/contrib/sites/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/id/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/io
creating build/lib/django/contrib/sites/locale/io/LC_MESSAGES
copying django/contrib/sites/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/io/LC_MESSAGES
copying django/contrib/sites/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/io/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/is
creating build/lib/django/contrib/sites/locale/is/LC_MESSAGES
copying django/contrib/sites/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/is/LC_MESSAGES
copying django/contrib/sites/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/is/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/it
creating build/lib/django/contrib/sites/locale/it/LC_MESSAGES
copying django/contrib/sites/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/it/LC_MESSAGES
copying django/contrib/sites/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/it/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ja
creating build/lib/django/contrib/sites/locale/ja/LC_MESSAGES
copying django/contrib/sites/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ja/LC_MESSAGES
copying django/contrib/sites/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ka
creating build/lib/django/contrib/sites/locale/ka/LC_MESSAGES
copying django/contrib/sites/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ka/LC_MESSAGES
copying django/contrib/sites/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/kab
creating build/lib/django/contrib/sites/locale/kab/LC_MESSAGES
copying django/contrib/sites/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/kab/LC_MESSAGES
copying django/contrib/sites/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/kab/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/kk
creating build/lib/django/contrib/sites/locale/kk/LC_MESSAGES
copying django/contrib/sites/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/kk/LC_MESSAGES
copying django/contrib/sites/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/km
creating build/lib/django/contrib/sites/locale/km/LC_MESSAGES
copying django/contrib/sites/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/km/LC_MESSAGES
copying django/contrib/sites/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/km/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/kn
creating build/lib/django/contrib/sites/locale/kn/LC_MESSAGES
copying django/contrib/sites/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/kn/LC_MESSAGES
copying django/contrib/sites/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ko
creating build/lib/django/contrib/sites/locale/ko/LC_MESSAGES
copying django/contrib/sites/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ko/LC_MESSAGES
copying django/contrib/sites/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ky
creating build/lib/django/contrib/sites/locale/ky/LC_MESSAGES
copying django/contrib/sites/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ky/LC_MESSAGES
copying django/contrib/sites/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/lb
creating build/lib/django/contrib/sites/locale/lb/LC_MESSAGES
copying django/contrib/sites/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/lb/LC_MESSAGES
copying django/contrib/sites/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/lt
creating build/lib/django/contrib/sites/locale/lt/LC_MESSAGES
copying django/contrib/sites/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/lt/LC_MESSAGES
copying django/contrib/sites/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/lv
creating build/lib/django/contrib/sites/locale/lv/LC_MESSAGES
copying django/contrib/sites/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/lv/LC_MESSAGES
copying django/contrib/sites/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/mk
creating build/lib/django/contrib/sites/locale/mk/LC_MESSAGES
copying django/contrib/sites/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/mk/LC_MESSAGES
copying django/contrib/sites/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ml
creating build/lib/django/contrib/sites/locale/ml/LC_MESSAGES
copying django/contrib/sites/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ml/LC_MESSAGES
copying django/contrib/sites/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/mn
creating build/lib/django/contrib/sites/locale/mn/LC_MESSAGES
copying django/contrib/sites/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/mn/LC_MESSAGES
copying django/contrib/sites/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/mr
creating build/lib/django/contrib/sites/locale/mr/LC_MESSAGES
copying django/contrib/sites/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/mr/LC_MESSAGES
copying django/contrib/sites/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/my
creating build/lib/django/contrib/sites/locale/my/LC_MESSAGES
copying django/contrib/sites/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/my/LC_MESSAGES
copying django/contrib/sites/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/my/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/nb
creating build/lib/django/contrib/sites/locale/nb/LC_MESSAGES
copying django/contrib/sites/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/nb/LC_MESSAGES
copying django/contrib/sites/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ne
creating build/lib/django/contrib/sites/locale/ne/LC_MESSAGES
copying django/contrib/sites/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ne/LC_MESSAGES
copying django/contrib/sites/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/nl
creating build/lib/django/contrib/sites/locale/nl/LC_MESSAGES
copying django/contrib/sites/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/nl/LC_MESSAGES
copying django/contrib/sites/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/nn
creating build/lib/django/contrib/sites/locale/nn/LC_MESSAGES
copying django/contrib/sites/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/nn/LC_MESSAGES
copying django/contrib/sites/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/os
creating build/lib/django/contrib/sites/locale/os/LC_MESSAGES
copying django/contrib/sites/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/os/LC_MESSAGES
copying django/contrib/sites/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/os/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/pa
creating build/lib/django/contrib/sites/locale/pa/LC_MESSAGES
copying django/contrib/sites/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pa/LC_MESSAGES
copying django/contrib/sites/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/pl
creating build/lib/django/contrib/sites/locale/pl/LC_MESSAGES
copying django/contrib/sites/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pl/LC_MESSAGES
copying django/contrib/sites/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/pt
creating build/lib/django/contrib/sites/locale/pt/LC_MESSAGES
copying django/contrib/sites/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pt/LC_MESSAGES
copying django/contrib/sites/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/pt_BR
creating build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES
copying django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES
copying django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ro
creating build/lib/django/contrib/sites/locale/ro/LC_MESSAGES
copying django/contrib/sites/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ro/LC_MESSAGES
copying django/contrib/sites/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ru
creating build/lib/django/contrib/sites/locale/ru/LC_MESSAGES
copying django/contrib/sites/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ru/LC_MESSAGES
copying django/contrib/sites/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/sk
creating build/lib/django/contrib/sites/locale/sk/LC_MESSAGES
copying django/contrib/sites/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sk/LC_MESSAGES
copying django/contrib/sites/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/sl
creating build/lib/django/contrib/sites/locale/sl/LC_MESSAGES
copying django/contrib/sites/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sl/LC_MESSAGES
copying django/contrib/sites/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/sq
creating build/lib/django/contrib/sites/locale/sq/LC_MESSAGES
copying django/contrib/sites/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sq/LC_MESSAGES
copying django/contrib/sites/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/sr
creating build/lib/django/contrib/sites/locale/sr/LC_MESSAGES
copying django/contrib/sites/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sr/LC_MESSAGES
copying django/contrib/sites/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/sr_Latn
creating build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
copying django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
copying django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/sv
creating build/lib/django/contrib/sites/locale/sv/LC_MESSAGES
copying django/contrib/sites/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sv/LC_MESSAGES
copying django/contrib/sites/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/sw
creating build/lib/django/contrib/sites/locale/sw/LC_MESSAGES
copying django/contrib/sites/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sw/LC_MESSAGES
copying django/contrib/sites/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ta
creating build/lib/django/contrib/sites/locale/ta/LC_MESSAGES
copying django/contrib/sites/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ta/LC_MESSAGES
copying django/contrib/sites/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/te
creating build/lib/django/contrib/sites/locale/te/LC_MESSAGES
copying django/contrib/sites/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/te/LC_MESSAGES
copying django/contrib/sites/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/te/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/tg
creating build/lib/django/contrib/sites/locale/tg/LC_MESSAGES
copying django/contrib/sites/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tg/LC_MESSAGES
copying django/contrib/sites/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/th
creating build/lib/django/contrib/sites/locale/th/LC_MESSAGES
copying django/contrib/sites/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/th/LC_MESSAGES
copying django/contrib/sites/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/th/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/tk
creating build/lib/django/contrib/sites/locale/tk/LC_MESSAGES
copying django/contrib/sites/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tk/LC_MESSAGES
copying django/contrib/sites/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tk/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/tr
creating build/lib/django/contrib/sites/locale/tr/LC_MESSAGES
copying django/contrib/sites/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tr/LC_MESSAGES
copying django/contrib/sites/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/tt
creating build/lib/django/contrib/sites/locale/tt/LC_MESSAGES
copying django/contrib/sites/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tt/LC_MESSAGES
copying django/contrib/sites/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/udm
creating build/lib/django/contrib/sites/locale/udm/LC_MESSAGES
copying django/contrib/sites/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/udm/LC_MESSAGES
copying django/contrib/sites/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/uk
creating build/lib/django/contrib/sites/locale/uk/LC_MESSAGES
copying django/contrib/sites/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/uk/LC_MESSAGES
copying django/contrib/sites/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ur
creating build/lib/django/contrib/sites/locale/ur/LC_MESSAGES
copying django/contrib/sites/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ur/LC_MESSAGES
copying django/contrib/sites/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/uz
creating build/lib/django/contrib/sites/locale/uz/LC_MESSAGES
copying django/contrib/sites/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/uz/LC_MESSAGES
copying django/contrib/sites/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/uz/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/vi
creating build/lib/django/contrib/sites/locale/vi/LC_MESSAGES
copying django/contrib/sites/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/vi/LC_MESSAGES
copying django/contrib/sites/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/zh_Hans
creating build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
copying django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
copying django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/zh_Hant
creating build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
copying django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
copying django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
copying django/contrib/gis/gdal/LICENSE -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/geos/LICENSE -> build/lib/django/contrib/gis/geos
running build_scripts
creating build/scripts-3.10
copying and adjusting django/bin/django-admin.py -> build/scripts-3.10
changing mode of build/scripts-3.10/django-admin.py from 644 to 755
installing to build/bdist.netbsd-9.0-i386/wheel
running install
running install_lib
creating build/bdist.netbsd-9.0-i386
creating build/bdist.netbsd-9.0-i386/wheel
creating build/bdist.netbsd-9.0-i386/wheel/django
copying build/lib/django/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django
copying build/lib/django/__main__.py -> build/bdist.netbsd-9.0-i386/wheel/./django
copying build/lib/django/shortcuts.py -> build/bdist.netbsd-9.0-i386/wheel/./django
creating build/bdist.netbsd-9.0-i386/wheel/django/apps
copying build/lib/django/apps/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/apps
copying build/lib/django/apps/config.py -> build/bdist.netbsd-9.0-i386/wheel/./django/apps
copying build/lib/django/apps/registry.py -> build/bdist.netbsd-9.0-i386/wheel/./django/apps
creating build/bdist.netbsd-9.0-i386/wheel/django/conf
copying build/lib/django/conf/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf
copying build/lib/django/conf/global_settings.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale
copying build/lib/django/conf/locale/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ar
copying build/lib/django/conf/locale/ar/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ar
copying build/lib/django/conf/locale/ar/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ar
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ar/LC_MESSAGES
copying build/lib/django/conf/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ar/LC_MESSAGES
copying build/lib/django/conf/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ar/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ar_DZ
copying build/lib/django/conf/locale/ar_DZ/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ar_DZ
copying build/lib/django/conf/locale/ar_DZ/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ar_DZ
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/conf/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/conf/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ar_DZ/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/az
copying build/lib/django/conf/locale/az/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/az
copying build/lib/django/conf/locale/az/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/az
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/az/LC_MESSAGES
copying build/lib/django/conf/locale/az/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/az/LC_MESSAGES
copying build/lib/django/conf/locale/az/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/az/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/bg
copying build/lib/django/conf/locale/bg/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/bg
copying build/lib/django/conf/locale/bg/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/bg
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/bg/LC_MESSAGES
copying build/lib/django/conf/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/bg/LC_MESSAGES
copying build/lib/django/conf/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/bg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/bn
copying build/lib/django/conf/locale/bn/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/bn
copying build/lib/django/conf/locale/bn/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/bn
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/bn/LC_MESSAGES
copying build/lib/django/conf/locale/bn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/bn/LC_MESSAGES
copying build/lib/django/conf/locale/bn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/bn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/bs
copying build/lib/django/conf/locale/bs/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/bs
copying build/lib/django/conf/locale/bs/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/bs
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/bs/LC_MESSAGES
copying build/lib/django/conf/locale/bs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/bs/LC_MESSAGES
copying build/lib/django/conf/locale/bs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/bs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ca
copying build/lib/django/conf/locale/ca/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ca
copying build/lib/django/conf/locale/ca/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ca
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ca/LC_MESSAGES
copying build/lib/django/conf/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ca/LC_MESSAGES
copying build/lib/django/conf/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ca/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/cs
copying build/lib/django/conf/locale/cs/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/cs
copying build/lib/django/conf/locale/cs/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/cs
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/cs/LC_MESSAGES
copying build/lib/django/conf/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/cs/LC_MESSAGES
copying build/lib/django/conf/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/cs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/cy
copying build/lib/django/conf/locale/cy/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/cy
copying build/lib/django/conf/locale/cy/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/cy
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/cy/LC_MESSAGES
copying build/lib/django/conf/locale/cy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/cy/LC_MESSAGES
copying build/lib/django/conf/locale/cy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/cy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/da
copying build/lib/django/conf/locale/da/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/da
copying build/lib/django/conf/locale/da/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/da
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/da/LC_MESSAGES
copying build/lib/django/conf/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/da/LC_MESSAGES
copying build/lib/django/conf/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/da/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/de
copying build/lib/django/conf/locale/de/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/de
copying build/lib/django/conf/locale/de/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/de
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/de/LC_MESSAGES
copying build/lib/django/conf/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/de/LC_MESSAGES
copying build/lib/django/conf/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/de/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/de_CH
copying build/lib/django/conf/locale/de_CH/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/de_CH
copying build/lib/django/conf/locale/de_CH/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/de_CH
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/el
copying build/lib/django/conf/locale/el/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/el
copying build/lib/django/conf/locale/el/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/el
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/el/LC_MESSAGES
copying build/lib/django/conf/locale/el/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/el/LC_MESSAGES
copying build/lib/django/conf/locale/el/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/el/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/en
copying build/lib/django/conf/locale/en/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/en
copying build/lib/django/conf/locale/en/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/en
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/en/LC_MESSAGES
copying build/lib/django/conf/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/en/LC_MESSAGES
copying build/lib/django/conf/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/en/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/en_AU
copying build/lib/django/conf/locale/en_AU/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/en_AU
copying build/lib/django/conf/locale/en_AU/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/en_AU
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/en_AU/LC_MESSAGES
copying build/lib/django/conf/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/en_AU/LC_MESSAGES
copying build/lib/django/conf/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/en_AU/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/en_GB
copying build/lib/django/conf/locale/en_GB/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/en_GB
copying build/lib/django/conf/locale/en_GB/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/en_GB
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/en_GB/LC_MESSAGES
copying build/lib/django/conf/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/en_GB/LC_MESSAGES
copying build/lib/django/conf/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/en_GB/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/eo
copying build/lib/django/conf/locale/eo/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/eo
copying build/lib/django/conf/locale/eo/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/eo
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/eo/LC_MESSAGES
copying build/lib/django/conf/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/eo/LC_MESSAGES
copying build/lib/django/conf/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/eo/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/es
copying build/lib/django/conf/locale/es/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es
copying build/lib/django/conf/locale/es/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/es/LC_MESSAGES
copying build/lib/django/conf/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es/LC_MESSAGES
copying build/lib/django/conf/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/es_AR
copying build/lib/django/conf/locale/es_AR/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_AR
copying build/lib/django/conf/locale/es_AR/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_AR
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/es_AR/LC_MESSAGES
copying build/lib/django/conf/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_AR/LC_MESSAGES
copying build/lib/django/conf/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_AR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/es_CO
copying build/lib/django/conf/locale/es_CO/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_CO
copying build/lib/django/conf/locale/es_CO/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_CO
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/es_CO/LC_MESSAGES
copying build/lib/django/conf/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_CO/LC_MESSAGES
copying build/lib/django/conf/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_CO/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/es_MX
copying build/lib/django/conf/locale/es_MX/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_MX
copying build/lib/django/conf/locale/es_MX/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_MX
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/es_MX/LC_MESSAGES
copying build/lib/django/conf/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_MX/LC_MESSAGES
copying build/lib/django/conf/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_MX/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/es_NI
copying build/lib/django/conf/locale/es_NI/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_NI
copying build/lib/django/conf/locale/es_NI/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_NI
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/es_PR
copying build/lib/django/conf/locale/es_PR/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_PR
copying build/lib/django/conf/locale/es_PR/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_PR
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/et
copying build/lib/django/conf/locale/et/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/et
copying build/lib/django/conf/locale/et/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/et
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/et/LC_MESSAGES
copying build/lib/django/conf/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/et/LC_MESSAGES
copying build/lib/django/conf/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/et/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/eu
copying build/lib/django/conf/locale/eu/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/eu
copying build/lib/django/conf/locale/eu/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/eu
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/eu/LC_MESSAGES
copying build/lib/django/conf/locale/eu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/eu/LC_MESSAGES
copying build/lib/django/conf/locale/eu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/eu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/fa
copying build/lib/django/conf/locale/fa/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/fa
copying build/lib/django/conf/locale/fa/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/fa
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/fa/LC_MESSAGES
copying build/lib/django/conf/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/fa/LC_MESSAGES
copying build/lib/django/conf/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/fa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/fi
copying build/lib/django/conf/locale/fi/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/fi
copying build/lib/django/conf/locale/fi/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/fi
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/fi/LC_MESSAGES
copying build/lib/django/conf/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/fi/LC_MESSAGES
copying build/lib/django/conf/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/fi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/fr
copying build/lib/django/conf/locale/fr/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/fr
copying build/lib/django/conf/locale/fr/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/fr
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/fr/LC_MESSAGES
copying build/lib/django/conf/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/fr/LC_MESSAGES
copying build/lib/django/conf/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/fr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/fy
copying build/lib/django/conf/locale/fy/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/fy
copying build/lib/django/conf/locale/fy/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/fy
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/fy/LC_MESSAGES
copying build/lib/django/conf/locale/fy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/fy/LC_MESSAGES
copying build/lib/django/conf/locale/fy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/fy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ga
copying build/lib/django/conf/locale/ga/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ga
copying build/lib/django/conf/locale/ga/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ga
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ga/LC_MESSAGES
copying build/lib/django/conf/locale/ga/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ga/LC_MESSAGES
copying build/lib/django/conf/locale/ga/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ga/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/gd
copying build/lib/django/conf/locale/gd/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/gd
copying build/lib/django/conf/locale/gd/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/gd
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/gd/LC_MESSAGES
copying build/lib/django/conf/locale/gd/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/gd/LC_MESSAGES
copying build/lib/django/conf/locale/gd/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/gd/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/gl
copying build/lib/django/conf/locale/gl/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/gl
copying build/lib/django/conf/locale/gl/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/gl
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/gl/LC_MESSAGES
copying build/lib/django/conf/locale/gl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/gl/LC_MESSAGES
copying build/lib/django/conf/locale/gl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/gl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/he
copying build/lib/django/conf/locale/he/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/he
copying build/lib/django/conf/locale/he/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/he
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/he/LC_MESSAGES
copying build/lib/django/conf/locale/he/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/he/LC_MESSAGES
copying build/lib/django/conf/locale/he/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/he/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/hi
copying build/lib/django/conf/locale/hi/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/hi
copying build/lib/django/conf/locale/hi/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/hi
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/hi/LC_MESSAGES
copying build/lib/django/conf/locale/hi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/hi/LC_MESSAGES
copying build/lib/django/conf/locale/hi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/hi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/hr
copying build/lib/django/conf/locale/hr/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/hr
copying build/lib/django/conf/locale/hr/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/hr
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/hr/LC_MESSAGES
copying build/lib/django/conf/locale/hr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/hr/LC_MESSAGES
copying build/lib/django/conf/locale/hr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/hr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/hu
copying build/lib/django/conf/locale/hu/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/hu
copying build/lib/django/conf/locale/hu/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/hu
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/hu/LC_MESSAGES
copying build/lib/django/conf/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/hu/LC_MESSAGES
copying build/lib/django/conf/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/hu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/id
copying build/lib/django/conf/locale/id/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/id
copying build/lib/django/conf/locale/id/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/id
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/id/LC_MESSAGES
copying build/lib/django/conf/locale/id/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/id/LC_MESSAGES
copying build/lib/django/conf/locale/id/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/id/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ig
copying build/lib/django/conf/locale/ig/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ig
copying build/lib/django/conf/locale/ig/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ig
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ig/LC_MESSAGES
copying build/lib/django/conf/locale/ig/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ig/LC_MESSAGES
copying build/lib/django/conf/locale/ig/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ig/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/is
copying build/lib/django/conf/locale/is/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/is
copying build/lib/django/conf/locale/is/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/is
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/is/LC_MESSAGES
copying build/lib/django/conf/locale/is/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/is/LC_MESSAGES
copying build/lib/django/conf/locale/is/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/is/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/it
copying build/lib/django/conf/locale/it/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/it
copying build/lib/django/conf/locale/it/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/it
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/it/LC_MESSAGES
copying build/lib/django/conf/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/it/LC_MESSAGES
copying build/lib/django/conf/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/it/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ja
copying build/lib/django/conf/locale/ja/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ja
copying build/lib/django/conf/locale/ja/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ja
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ja/LC_MESSAGES
copying build/lib/django/conf/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ja/LC_MESSAGES
copying build/lib/django/conf/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ja/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ka
copying build/lib/django/conf/locale/ka/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ka
copying build/lib/django/conf/locale/ka/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ka
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ka/LC_MESSAGES
copying build/lib/django/conf/locale/ka/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ka/LC_MESSAGES
copying build/lib/django/conf/locale/ka/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ka/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/km
copying build/lib/django/conf/locale/km/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/km
copying build/lib/django/conf/locale/km/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/km
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/km/LC_MESSAGES
copying build/lib/django/conf/locale/km/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/km/LC_MESSAGES
copying build/lib/django/conf/locale/km/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/km/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/kn
copying build/lib/django/conf/locale/kn/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/kn
copying build/lib/django/conf/locale/kn/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/kn
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/kn/LC_MESSAGES
copying build/lib/django/conf/locale/kn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/kn/LC_MESSAGES
copying build/lib/django/conf/locale/kn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/kn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ko
copying build/lib/django/conf/locale/ko/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ko
copying build/lib/django/conf/locale/ko/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ko
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ko/LC_MESSAGES
copying build/lib/django/conf/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ko/LC_MESSAGES
copying build/lib/django/conf/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ko/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ky
copying build/lib/django/conf/locale/ky/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ky
copying build/lib/django/conf/locale/ky/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ky
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ky/LC_MESSAGES
copying build/lib/django/conf/locale/ky/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ky/LC_MESSAGES
copying build/lib/django/conf/locale/ky/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ky/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/lt
copying build/lib/django/conf/locale/lt/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/lt
copying build/lib/django/conf/locale/lt/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/lt
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/lt/LC_MESSAGES
copying build/lib/django/conf/locale/lt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/lt/LC_MESSAGES
copying build/lib/django/conf/locale/lt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/lt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/lv
copying build/lib/django/conf/locale/lv/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/lv
copying build/lib/django/conf/locale/lv/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/lv
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/lv/LC_MESSAGES
copying build/lib/django/conf/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/lv/LC_MESSAGES
copying build/lib/django/conf/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/lv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/mk
copying build/lib/django/conf/locale/mk/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/mk
copying build/lib/django/conf/locale/mk/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/mk
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/mk/LC_MESSAGES
copying build/lib/django/conf/locale/mk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/mk/LC_MESSAGES
copying build/lib/django/conf/locale/mk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/mk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ml
copying build/lib/django/conf/locale/ml/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ml
copying build/lib/django/conf/locale/ml/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ml
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ml/LC_MESSAGES
copying build/lib/django/conf/locale/ml/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ml/LC_MESSAGES
copying build/lib/django/conf/locale/ml/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ml/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/mn
copying build/lib/django/conf/locale/mn/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/mn
copying build/lib/django/conf/locale/mn/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/mn
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/mn/LC_MESSAGES
copying build/lib/django/conf/locale/mn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/mn/LC_MESSAGES
copying build/lib/django/conf/locale/mn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/mn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/nb
copying build/lib/django/conf/locale/nb/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/nb
copying build/lib/django/conf/locale/nb/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/nb
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/nb/LC_MESSAGES
copying build/lib/django/conf/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/nb/LC_MESSAGES
copying build/lib/django/conf/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/nb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/nl
copying build/lib/django/conf/locale/nl/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/nl
copying build/lib/django/conf/locale/nl/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/nl
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/nl/LC_MESSAGES
copying build/lib/django/conf/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/nl/LC_MESSAGES
copying build/lib/django/conf/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/nl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/nn
copying build/lib/django/conf/locale/nn/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/nn
copying build/lib/django/conf/locale/nn/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/nn
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/nn/LC_MESSAGES
copying build/lib/django/conf/locale/nn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/nn/LC_MESSAGES
copying build/lib/django/conf/locale/nn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/nn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/pl
copying build/lib/django/conf/locale/pl/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/pl
copying build/lib/django/conf/locale/pl/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/pl
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/pl/LC_MESSAGES
copying build/lib/django/conf/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/pl/LC_MESSAGES
copying build/lib/django/conf/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/pl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/pt
copying build/lib/django/conf/locale/pt/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/pt
copying build/lib/django/conf/locale/pt/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/pt
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/pt/LC_MESSAGES
copying build/lib/django/conf/locale/pt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/pt/LC_MESSAGES
copying build/lib/django/conf/locale/pt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/pt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/pt_BR
copying build/lib/django/conf/locale/pt_BR/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/pt_BR
copying build/lib/django/conf/locale/pt_BR/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/pt_BR
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/pt_BR/LC_MESSAGES
copying build/lib/django/conf/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/pt_BR/LC_MESSAGES
copying build/lib/django/conf/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/pt_BR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ro
copying build/lib/django/conf/locale/ro/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ro
copying build/lib/django/conf/locale/ro/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ro
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ro/LC_MESSAGES
copying build/lib/django/conf/locale/ro/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ro/LC_MESSAGES
copying build/lib/django/conf/locale/ro/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ro/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ru
copying build/lib/django/conf/locale/ru/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ru
copying build/lib/django/conf/locale/ru/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ru
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ru/LC_MESSAGES
copying build/lib/django/conf/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ru/LC_MESSAGES
copying build/lib/django/conf/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ru/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/sk
copying build/lib/django/conf/locale/sk/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sk
copying build/lib/django/conf/locale/sk/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sk
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/sk/LC_MESSAGES
copying build/lib/django/conf/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sk/LC_MESSAGES
copying build/lib/django/conf/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/sl
copying build/lib/django/conf/locale/sl/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sl
copying build/lib/django/conf/locale/sl/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sl
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/sl/LC_MESSAGES
copying build/lib/django/conf/locale/sl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sl/LC_MESSAGES
copying build/lib/django/conf/locale/sl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/sq
copying build/lib/django/conf/locale/sq/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sq
copying build/lib/django/conf/locale/sq/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sq
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/sq/LC_MESSAGES
copying build/lib/django/conf/locale/sq/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sq/LC_MESSAGES
copying build/lib/django/conf/locale/sq/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sq/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/sr
copying build/lib/django/conf/locale/sr/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sr
copying build/lib/django/conf/locale/sr/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sr
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/sr/LC_MESSAGES
copying build/lib/django/conf/locale/sr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sr/LC_MESSAGES
copying build/lib/django/conf/locale/sr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/sr_Latn
copying build/lib/django/conf/locale/sr_Latn/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sr_Latn
copying build/lib/django/conf/locale/sr_Latn/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sr_Latn
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/conf/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/conf/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sr_Latn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/sv
copying build/lib/django/conf/locale/sv/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sv
copying build/lib/django/conf/locale/sv/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sv
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/sv/LC_MESSAGES
copying build/lib/django/conf/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sv/LC_MESSAGES
copying build/lib/django/conf/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ta
copying build/lib/django/conf/locale/ta/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ta
copying build/lib/django/conf/locale/ta/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ta
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ta/LC_MESSAGES
copying build/lib/django/conf/locale/ta/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ta/LC_MESSAGES
copying build/lib/django/conf/locale/ta/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ta/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/te
copying build/lib/django/conf/locale/te/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/te
copying build/lib/django/conf/locale/te/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/te
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/te/LC_MESSAGES
copying build/lib/django/conf/locale/te/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/te/LC_MESSAGES
copying build/lib/django/conf/locale/te/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/te/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/tg
copying build/lib/django/conf/locale/tg/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/tg
copying build/lib/django/conf/locale/tg/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/tg
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/tg/LC_MESSAGES
copying build/lib/django/conf/locale/tg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/tg/LC_MESSAGES
copying build/lib/django/conf/locale/tg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/tg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/th
copying build/lib/django/conf/locale/th/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/th
copying build/lib/django/conf/locale/th/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/th
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/th/LC_MESSAGES
copying build/lib/django/conf/locale/th/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/th/LC_MESSAGES
copying build/lib/django/conf/locale/th/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/th/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/tk
copying build/lib/django/conf/locale/tk/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/tk
copying build/lib/django/conf/locale/tk/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/tk
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/tk/LC_MESSAGES
copying build/lib/django/conf/locale/tk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/tk/LC_MESSAGES
copying build/lib/django/conf/locale/tk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/tk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/tr
copying build/lib/django/conf/locale/tr/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/tr
copying build/lib/django/conf/locale/tr/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/tr
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/tr/LC_MESSAGES
copying build/lib/django/conf/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/tr/LC_MESSAGES
copying build/lib/django/conf/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/tr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/uk
copying build/lib/django/conf/locale/uk/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/uk
copying build/lib/django/conf/locale/uk/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/uk
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/uk/LC_MESSAGES
copying build/lib/django/conf/locale/uk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/uk/LC_MESSAGES
copying build/lib/django/conf/locale/uk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/uk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/uz
copying build/lib/django/conf/locale/uz/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/uz
copying build/lib/django/conf/locale/uz/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/uz
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/uz/LC_MESSAGES
copying build/lib/django/conf/locale/uz/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/uz/LC_MESSAGES
copying build/lib/django/conf/locale/uz/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/uz/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/vi
copying build/lib/django/conf/locale/vi/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/vi
copying build/lib/django/conf/locale/vi/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/vi
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/vi/LC_MESSAGES
copying build/lib/django/conf/locale/vi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/vi/LC_MESSAGES
copying build/lib/django/conf/locale/vi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/vi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/zh_Hans
copying build/lib/django/conf/locale/zh_Hans/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/zh_Hans
copying build/lib/django/conf/locale/zh_Hans/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/zh_Hans
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/conf/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/conf/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/zh_Hans/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/zh_Hant
copying build/lib/django/conf/locale/zh_Hant/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/zh_Hant
copying build/lib/django/conf/locale/zh_Hant/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/zh_Hant
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/conf/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/conf/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/zh_Hant/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/af
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/af/LC_MESSAGES
copying build/lib/django/conf/locale/af/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/af/LC_MESSAGES
copying build/lib/django/conf/locale/af/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/af/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ast
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ast/LC_MESSAGES
copying build/lib/django/conf/locale/ast/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ast/LC_MESSAGES
copying build/lib/django/conf/locale/ast/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ast/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/be
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/be/LC_MESSAGES
copying build/lib/django/conf/locale/be/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/be/LC_MESSAGES
copying build/lib/django/conf/locale/be/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/be/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/br
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/br/LC_MESSAGES
copying build/lib/django/conf/locale/br/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/br/LC_MESSAGES
copying build/lib/django/conf/locale/br/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/br/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/dsb
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/dsb/LC_MESSAGES
copying build/lib/django/conf/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/dsb/LC_MESSAGES
copying build/lib/django/conf/locale/dsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/dsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/es_VE
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/es_VE/LC_MESSAGES
copying build/lib/django/conf/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_VE/LC_MESSAGES
copying build/lib/django/conf/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/es_VE/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/hsb
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/hsb/LC_MESSAGES
copying build/lib/django/conf/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/hsb/LC_MESSAGES
copying build/lib/django/conf/locale/hsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/hsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/hy
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/hy/LC_MESSAGES
copying build/lib/django/conf/locale/hy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/hy/LC_MESSAGES
copying build/lib/django/conf/locale/hy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/hy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ia
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ia/LC_MESSAGES
copying build/lib/django/conf/locale/ia/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ia/LC_MESSAGES
copying build/lib/django/conf/locale/ia/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ia/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/io
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/io/LC_MESSAGES
copying build/lib/django/conf/locale/io/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/io/LC_MESSAGES
copying build/lib/django/conf/locale/io/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/io/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/kab
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/kab/LC_MESSAGES
copying build/lib/django/conf/locale/kab/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/kab/LC_MESSAGES
copying build/lib/django/conf/locale/kab/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/kab/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/kk
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/kk/LC_MESSAGES
copying build/lib/django/conf/locale/kk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/kk/LC_MESSAGES
copying build/lib/django/conf/locale/kk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/kk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/lb
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/lb/LC_MESSAGES
copying build/lib/django/conf/locale/lb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/lb/LC_MESSAGES
copying build/lib/django/conf/locale/lb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/lb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/mr
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/mr/LC_MESSAGES
copying build/lib/django/conf/locale/mr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/mr/LC_MESSAGES
copying build/lib/django/conf/locale/mr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/mr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/my
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/my/LC_MESSAGES
copying build/lib/django/conf/locale/my/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/my/LC_MESSAGES
copying build/lib/django/conf/locale/my/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/my/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ne
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ne/LC_MESSAGES
copying build/lib/django/conf/locale/ne/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ne/LC_MESSAGES
copying build/lib/django/conf/locale/ne/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ne/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/os
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/os/LC_MESSAGES
copying build/lib/django/conf/locale/os/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/os/LC_MESSAGES
copying build/lib/django/conf/locale/os/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/os/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/pa
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/pa/LC_MESSAGES
copying build/lib/django/conf/locale/pa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/pa/LC_MESSAGES
copying build/lib/django/conf/locale/pa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/pa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/sw
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/sw/LC_MESSAGES
copying build/lib/django/conf/locale/sw/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sw/LC_MESSAGES
copying build/lib/django/conf/locale/sw/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/sw/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/tt
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/tt/LC_MESSAGES
copying build/lib/django/conf/locale/tt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/tt/LC_MESSAGES
copying build/lib/django/conf/locale/tt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/tt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/udm
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/udm/LC_MESSAGES
copying build/lib/django/conf/locale/udm/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/udm/LC_MESSAGES
copying build/lib/django/conf/locale/udm/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/udm/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ur
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/locale/ur/LC_MESSAGES
copying build/lib/django/conf/locale/ur/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ur/LC_MESSAGES
copying build/lib/django/conf/locale/ur/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/locale/ur/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/urls
copying build/lib/django/conf/urls/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/urls
copying build/lib/django/conf/urls/i18n.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/urls
copying build/lib/django/conf/urls/static.py -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/urls
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/app_template
copying build/lib/django/conf/app_template/__init__.py-tpl -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/app_template
copying build/lib/django/conf/app_template/admin.py-tpl -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/app_template
copying build/lib/django/conf/app_template/apps.py-tpl -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/app_template
copying build/lib/django/conf/app_template/models.py-tpl -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/app_template
copying build/lib/django/conf/app_template/tests.py-tpl -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/app_template
copying build/lib/django/conf/app_template/views.py-tpl -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/app_template
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/app_template/migrations
copying build/lib/django/conf/app_template/migrations/__init__.py-tpl -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/app_template/migrations
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/project_template
copying build/lib/django/conf/project_template/manage.py-tpl -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/project_template
creating build/bdist.netbsd-9.0-i386/wheel/django/conf/project_template/project_name
copying build/lib/django/conf/project_template/project_name/__init__.py-tpl -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/project_template/project_name
copying build/lib/django/conf/project_template/project_name/asgi.py-tpl -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/project_template/project_name
copying build/lib/django/conf/project_template/project_name/settings.py-tpl -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/project_template/project_name
copying build/lib/django/conf/project_template/project_name/urls.py-tpl -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/project_template/project_name
copying build/lib/django/conf/project_template/project_name/wsgi.py-tpl -> build/bdist.netbsd-9.0-i386/wheel/./django/conf/project_template/project_name
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib
copying build/lib/django/contrib/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin
copying build/lib/django/contrib/admin/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin
copying build/lib/django/contrib/admin/actions.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin
copying build/lib/django/contrib/admin/apps.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin
copying build/lib/django/contrib/admin/checks.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin
copying build/lib/django/contrib/admin/decorators.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin
copying build/lib/django/contrib/admin/exceptions.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin
copying build/lib/django/contrib/admin/filters.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin
copying build/lib/django/contrib/admin/forms.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin
copying build/lib/django/contrib/admin/helpers.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin
copying build/lib/django/contrib/admin/models.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin
copying build/lib/django/contrib/admin/options.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin
copying build/lib/django/contrib/admin/sites.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin
copying build/lib/django/contrib/admin/tests.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin
copying build/lib/django/contrib/admin/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin
copying build/lib/django/contrib/admin/widgets.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/migrations
copying build/lib/django/contrib/admin/migrations/0001_initial.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/migrations
copying build/lib/django/contrib/admin/migrations/0002_logentry_remove_auto_add.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/migrations
copying build/lib/django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/migrations
copying build/lib/django/contrib/admin/migrations/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/migrations
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/templatetags
copying build/lib/django/contrib/admin/templatetags/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templatetags
copying build/lib/django/contrib/admin/templatetags/admin_list.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templatetags
copying build/lib/django/contrib/admin/templatetags/admin_modify.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templatetags
copying build/lib/django/contrib/admin/templatetags/admin_urls.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templatetags
copying build/lib/django/contrib/admin/templatetags/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templatetags
copying build/lib/django/contrib/admin/templatetags/log.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templatetags
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/views
copying build/lib/django/contrib/admin/views/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/views
copying build/lib/django/contrib/admin/views/autocomplete.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/views
copying build/lib/django/contrib/admin/views/decorators.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/views
copying build/lib/django/contrib/admin/views/main.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/views
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/af
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/af/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/af/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/af/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/af/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/af/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/am
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/am/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/am/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/am/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/am/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/am/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ar
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ar/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ar_DZ
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ar_DZ/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ast
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ast/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/az
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/az/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/az/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/az/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/az/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/az/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/be
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/be/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/be/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/be/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/be/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/be/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/bg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/bg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/bn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/bn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/br
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/br/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/br/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/br/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/br/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/br/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/bs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/bs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ca
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ca/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/cs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/cs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/cy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/cy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/da
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/da/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/da/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/da/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/da/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/da/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/de
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/de/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/de/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/de/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/de/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/de/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/dsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/dsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/el
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/el/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/el/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/el/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/el/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/el/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/en
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/en/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/en/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/en/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/en/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/en/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/en_AU
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/en_AU/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/en_GB
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/en_GB/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/eo
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/eo/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/es
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/es/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/es_AR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es_AR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/es_CO
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es_CO/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/es_MX
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es_MX/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/es_VE
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/es_VE/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/et
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/et/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/et/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/et/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/et/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/et/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/eu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/eu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/fa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/fa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/fi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/fi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/fr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/fr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/fy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/fy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ga
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ga/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/gd
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/gd/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/gl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/gl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/he
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/he/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/he/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/he/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/he/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/he/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/hi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/hr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/hsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/hu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/hy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/hy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ia
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ia/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/id
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/id/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/id/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/id/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/id/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/id/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/io
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/io/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/io/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/io/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/io/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/io/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/is
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/is/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/is/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/is/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/is/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/is/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/it
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/it/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/it/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/it/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/it/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/it/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ja
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ja/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ka
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ka/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/kab
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/kab/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/kk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/kk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/km
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/km/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/km/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/km/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/km/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/km/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/kn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/kn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ko
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ko/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ky
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ky/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/lb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/lb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/lt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/lt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/lv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/lv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/mk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/mk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ml
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ml/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/mn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/mn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/mr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/mr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/my
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/my/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/my/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/my/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/my/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/my/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/nb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/nb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ne
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ne/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/nl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/nl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/nn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/nn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/os
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/os/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/os/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/os/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/os/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/os/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/pa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/pa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/pl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/pl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/pt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/pt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/pt_BR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/pt_BR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ro
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ro/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ru
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ru/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/sk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/sl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/sq
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sq/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/sr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/sr_Latn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sr_Latn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/sv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/sw
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/sw/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ta
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ta/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/te
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/te/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/te/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/te/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/te/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/te/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/tg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/tg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/th
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/th/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/th/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/th/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/th/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/th/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/tr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/tr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/tt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/tt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/udm
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/udm/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/uk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/uk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ur
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/ur/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/uz
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/uz/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/vi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/vi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/zh_Hans
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/zh_Hans/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/zh_Hant
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/locale/zh_Hant/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/static
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/static/admin
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/autocomplete.css -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/base.css -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/changelists.css -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/dashboard.css -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/fonts.css -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/forms.css -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/login.css -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/nav_sidebar.css -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/responsive.css -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/responsive_rtl.css -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/rtl.css -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/widgets.css -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/css
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/static/admin/css/vendor
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/static/admin/css/vendor/select2
copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/css/vendor/select2
copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/select2.css -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/css/vendor/select2
copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/select2.min.css -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/css/vendor/select2
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/static/admin/fonts
copying build/lib/django/contrib/admin/static/admin/fonts/LICENSE.txt -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/fonts
copying build/lib/django/contrib/admin/static/admin/fonts/README.txt -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/fonts
copying build/lib/django/contrib/admin/static/admin/fonts/Roboto-Bold-webfont.woff -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/fonts
copying build/lib/django/contrib/admin/static/admin/fonts/Roboto-Light-webfont.woff -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/fonts
copying build/lib/django/contrib/admin/static/admin/fonts/Roboto-Regular-webfont.woff -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/fonts
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/LICENSE -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/README.txt -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/calendar-icons.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-addlink.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-alert.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-calendar.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-changelink.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-clock.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-deletelink.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-no.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-unknown-alt.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-unknown.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-viewlink.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-yes.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/inline-delete.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/search.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/selector-icons.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/sorting-icons.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/tooltag-add.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/tooltag-arrowright.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/static/admin/img/gis
copying build/lib/django/contrib/admin/static/admin/img/gis/move_vertex_off.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img/gis
copying build/lib/django/contrib/admin/static/admin/img/gis/move_vertex_on.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/img/gis
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/SelectBox.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/SelectFilter2.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/actions.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/autocomplete.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/calendar.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/cancel.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/change_form.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/collapse.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/core.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/inlines.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/jquery.init.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/nav_sidebar.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/popup_response.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/prepopulate.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/prepopulate_init.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/urlify.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/static/admin/js/admin
copying build/lib/django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/admin
copying build/lib/django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/admin
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/static/admin/js/vendor
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/static/admin/js/vendor/jquery
copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/jquery
copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/jquery.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/jquery
copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/jquery
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/static/admin/js/vendor/select2
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/select2.full.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/static/admin/js/vendor/xregexp
copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/xregexp
copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/xregexp
copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/static/admin/js/vendor/xregexp
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/templates
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/404.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/500.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/actions.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/app_index.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/app_list.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/base.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/base_site.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/change_form.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/change_form_object_tools.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/change_list.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/change_list_object_tools.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/change_list_results.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/date_hierarchy.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/delete_confirmation.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/delete_selected_confirmation.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/filter.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/index.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/invalid_setup.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/login.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/nav_sidebar.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/object_history.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/pagination.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/popup_response.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/prepopulated_fields_js.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/search_form.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/submit_line.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/templates/admin/auth
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/templates/admin/auth/user
copying build/lib/django/contrib/admin/templates/admin/auth/user/add_form.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin/auth/user
copying build/lib/django/contrib/admin/templates/admin/auth/user/change_password.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin/auth/user
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/templates/admin/edit_inline
copying build/lib/django/contrib/admin/templates/admin/edit_inline/stacked.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin/edit_inline
copying build/lib/django/contrib/admin/templates/admin/edit_inline/tabular.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin/edit_inline
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/templates/admin/includes
copying build/lib/django/contrib/admin/templates/admin/includes/fieldset.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin/includes
copying build/lib/django/contrib/admin/templates/admin/includes/object_delete_summary.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin/includes
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/templates/admin/widgets
copying build/lib/django/contrib/admin/templates/admin/widgets/clearable_file_input.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin/widgets
copying build/lib/django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin/widgets
copying build/lib/django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin/widgets
copying build/lib/django/contrib/admin/templates/admin/widgets/radio.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin/widgets
copying build/lib/django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin/widgets
copying build/lib/django/contrib/admin/templates/admin/widgets/split_datetime.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin/widgets
copying build/lib/django/contrib/admin/templates/admin/widgets/url.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/admin/widgets
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admin/templates/registration
copying build/lib/django/contrib/admin/templates/registration/logged_out.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/registration
copying build/lib/django/contrib/admin/templates/registration/password_change_done.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/registration
copying build/lib/django/contrib/admin/templates/registration/password_change_form.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/registration
copying build/lib/django/contrib/admin/templates/registration/password_reset_complete.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/registration
copying build/lib/django/contrib/admin/templates/registration/password_reset_confirm.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/registration
copying build/lib/django/contrib/admin/templates/registration/password_reset_done.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/registration
copying build/lib/django/contrib/admin/templates/registration/password_reset_email.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/registration
copying build/lib/django/contrib/admin/templates/registration/password_reset_form.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admin/templates/registration
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs
copying build/lib/django/contrib/admindocs/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs
copying build/lib/django/contrib/admindocs/apps.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs
copying build/lib/django/contrib/admindocs/middleware.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs
copying build/lib/django/contrib/admindocs/urls.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs
copying build/lib/django/contrib/admindocs/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs
copying build/lib/django/contrib/admindocs/views.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/af
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/af/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/af/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/af/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ar
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ar/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ar_DZ
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ast
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ast/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/az
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/az/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/az/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/az/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/be
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/be/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/be/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/be/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/bg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/bg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/bn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/bn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/br
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/br/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/br/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/br/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/bs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/bs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ca
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ca/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/cs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/cs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/cy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/cy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/da
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/da/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/da/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/da/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/de
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/de/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/de/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/de/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/dsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/dsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/el
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/el/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/el/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/el/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/en
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/en/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/en/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/en/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/en_AU
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/en_AU/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/en_GB
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/en_GB/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/eo
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/eo/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/es
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/es/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/es/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/es/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/es_AR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/es_AR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/es_CO
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/es_CO/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/es_MX
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/es_MX/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/es_VE
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/es_VE/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/et
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/et/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/et/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/et/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/eu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/eu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/fa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/fa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/fi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/fi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/fr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/fr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/fy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/fy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ga
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ga/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/gd
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/gd/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/gl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/gl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/he
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/he/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/he/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/he/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/hi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/hi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/hr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/hr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/hsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/hsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/hu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/hu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ia
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ia/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/id
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/id/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/id/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/id/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/io
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/io/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/io/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/io/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/is
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/is/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/is/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/is/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/it
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/it/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/it/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/it/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ja
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ja/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ka
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ka/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/kab
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/kab/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/kk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/kk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/km
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/km/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/km/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/km/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/kn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/kn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ko
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ko/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ky
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ky/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/lb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/lb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/lt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/lt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/lv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/lv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/mk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/mk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ml
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ml/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/mn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/mn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/mr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/mr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/my
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/my/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/my/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/my/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/nb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/nb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ne
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ne/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/nl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/nl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/nn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/nn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/os
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/os/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/os/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/os/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/pa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/pa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/pl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/pl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/pt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/pt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/pt_BR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ro
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ro/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ru
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ru/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/sk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/sk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/sl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/sl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/sq
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/sq/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/sr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/sr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/sr_Latn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/sv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/sv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/sw
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/sw/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ta
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ta/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/te
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/te/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/te/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/te/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/tg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/tg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/th
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/th/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/th/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/th/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/tr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/tr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/tt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/tt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/udm
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/udm/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/uk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/uk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ur
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/ur/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/vi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/vi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/zh_Hans
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/zh_Hant
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/templates
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/bookmarklets.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/index.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/missing_docutils.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/model_detail.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/model_index.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/template_detail.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/template_filter_index.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/template_tag_index.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/view_detail.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/view_index.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/admindocs/templates/admin_doc
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/admin.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/apps.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/backends.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/base_user.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/checks.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/context_processors.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/decorators.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/forms.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/hashers.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/middleware.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/mixins.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/models.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/password_validation.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/signals.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/tokens.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/urls.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/validators.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
copying build/lib/django/contrib/auth/views.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/handlers
copying build/lib/django/contrib/auth/handlers/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/handlers
copying build/lib/django/contrib/auth/handlers/modwsgi.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/handlers
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/management
copying build/lib/django/contrib/auth/management/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/management
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/management/commands
copying build/lib/django/contrib/auth/management/commands/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/management/commands
copying build/lib/django/contrib/auth/management/commands/changepassword.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/management/commands
copying build/lib/django/contrib/auth/management/commands/createsuperuser.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/management/commands
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0001_initial.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0002_alter_permission_name_max_length.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0003_alter_user_email_max_length.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0004_alter_user_username_opts.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0005_alter_user_last_login_null.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0006_require_contenttypes_0002.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0008_alter_user_username_max_length.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0010_alter_group_name_max_length.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0011_update_proxy_permissions.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/migrations
copying build/lib/django/contrib/auth/common-passwords.txt.gz -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/af
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/af/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/af/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/af/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/af/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/af/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ar
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ar/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ar_DZ
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ar_DZ/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ast
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ast/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ast/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ast/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/az
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/az/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/az/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/az/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/az/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/az/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/be
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/be/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/be/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/be/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/be/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/be/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/bg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/bg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/bn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/bn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/bn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/bn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/br
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/br/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/br/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/br/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/br/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/br/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/bs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/bs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/bs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/bs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ca
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ca/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/cs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/cs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/cy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/cy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/cy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/cy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/da
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/da/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/da/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/da/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/de
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/de/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/de/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/de/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/dsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/dsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/el
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/el/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/el/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/el/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/el/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/el/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/en
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/en/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/en/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/en/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/en_AU
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/en_AU/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/en_GB
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/en_GB/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/eo
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/eo/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/es
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/es/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/es/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/es/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/es_AR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/es_AR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/es_CO
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/es_CO/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/es_MX
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/es_MX/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/es_VE
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/es_VE/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/et
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/et/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/et/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/et/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/eu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/eu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/eu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/eu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/fa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/fa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/fi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/fi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/fr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/fr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/fy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/fy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/fy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/fy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ga
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ga/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ga/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ga/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/gd
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/gd/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/gd/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/gd/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/gl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/gl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/gl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/gl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/he
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/he/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/he/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/he/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/he/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/he/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/hi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/hi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/hr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/hr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/hsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/hsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/hu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/hu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/hy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/hy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ia
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ia/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ia/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ia/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/id
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/id/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/id/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/id/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/id/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/id/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/io
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/io/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/io/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/io/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/io/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/io/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/is
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/is/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/is/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/is/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/is/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/is/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/it
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/it/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/it/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/it/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ja
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ja/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ka
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ka/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ka/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ka/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/kab
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/kab/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/kab/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/kab/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/kk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/kk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/kk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/kk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/km
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/km/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/km/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/km/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/km/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/km/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/kn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/kn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/kn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/kn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ko
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ko/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ky
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ky/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ky/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ky/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/lb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/lb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/lb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/lb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/lt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/lt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/lt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/lt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/lv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/lv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/mk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/mk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/mk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/mk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ml
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ml/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ml/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ml/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/mn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/mn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/mn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/mn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/mr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/mr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/mr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/mr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/my
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/my/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/my/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/my/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/my/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/my/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/nb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/nb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ne
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ne/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ne/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ne/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/nl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/nl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/nn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/nn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/nn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/nn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/os
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/os/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/os/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/os/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/os/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/os/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/pa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/pa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/pa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/pa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/pl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/pl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/pt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/pt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/pt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/pt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/pt_BR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/pt_BR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ro
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ro/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ro/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ro/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ru
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ru/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/sk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/sk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/sl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/sl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/sq
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sq/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sq/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/sq/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/sr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/sr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/sr_Latn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/sr_Latn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/sv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/sv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/sw
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sw/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sw/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/sw/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ta
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ta/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ta/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ta/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/te
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/te/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/te/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/te/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/te/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/te/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/tg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/tg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/tg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/tg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/th
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/th/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/th/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/th/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/th/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/th/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/tk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/tk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/tk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/tk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/tr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/tr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/tt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/tt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/tt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/tt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/udm
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/udm/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/udm/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/udm/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/uk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/uk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/uk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/uk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ur
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ur/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ur/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/ur/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/uz
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/uz/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/uz/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/uz/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/vi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/vi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/vi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/vi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/zh_Hans
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/zh_Hans/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/zh_Hant
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/locale/zh_Hant/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/templates
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/templates/auth
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/templates/auth/widgets
copying build/lib/django/contrib/auth/templates/auth/widgets/read_only_password_hash.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/templates/auth/widgets
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/auth/templates/registration
copying build/lib/django/contrib/auth/templates/registration/password_reset_subject.txt -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/auth/templates/registration
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes
copying build/lib/django/contrib/contenttypes/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes
copying build/lib/django/contrib/contenttypes/admin.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes
copying build/lib/django/contrib/contenttypes/apps.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes
copying build/lib/django/contrib/contenttypes/checks.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes
copying build/lib/django/contrib/contenttypes/fields.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes
copying build/lib/django/contrib/contenttypes/forms.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes
copying build/lib/django/contrib/contenttypes/models.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes
copying build/lib/django/contrib/contenttypes/views.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/management
copying build/lib/django/contrib/contenttypes/management/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/management
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/management/commands
copying build/lib/django/contrib/contenttypes/management/commands/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/management/commands
copying build/lib/django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/management/commands
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/migrations
copying build/lib/django/contrib/contenttypes/migrations/0001_initial.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/migrations
copying build/lib/django/contrib/contenttypes/migrations/0002_remove_content_type_name.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/migrations
copying build/lib/django/contrib/contenttypes/migrations/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/migrations
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/af
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/af/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/af/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/af/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ar
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ar/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ar_DZ
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ast
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ast/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/az
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/az/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/az/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/az/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/be
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/be/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/be/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/be/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/bg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/bg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/bn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/bn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/br
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/br/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/br/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/br/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/bs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/bs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ca
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ca/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/cs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/cs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/cy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/cy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/da
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/da/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/da/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/da/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/de
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/de/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/de/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/de/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/dsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/dsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/el
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/el/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/el/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/el/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/en
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/en/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/en/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/en/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/en_AU
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/en_GB
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/eo
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/eo/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/es
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/es/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/es/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/es/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/es_AR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/es_CO
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/es_MX
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/es_VE
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/et
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/et/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/et/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/et/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/eu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/eu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/fa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/fa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/fi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/fi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/fr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/fr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/fy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/fy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ga
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ga/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/gd
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/gd/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/gl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/gl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/he
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/he/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/he/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/he/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/hi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/hi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/hr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/hr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/hsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/hsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/hu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/hu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/hy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/hy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ia
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ia/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/id
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/id/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/id/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/id/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/io
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/io/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/io/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/io/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/is
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/is/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/is/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/is/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/it
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/it/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/it/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/it/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ja
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ja/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ka
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ka/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/kk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/kk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/km
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/km/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/km/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/km/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/kn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/kn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ko
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ko/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ky
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ky/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/lb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/lb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/lt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/lt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/lv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/lv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/mk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/mk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ml
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ml/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/mn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/mn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/mr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/mr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/my
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/my/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/my/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/my/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/nb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/nb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ne
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ne/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/nl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/nl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/nn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/nn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/os
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/os/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/os/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/os/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/pa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/pa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/pl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/pl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/pt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/pt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/pt_BR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ro
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ro/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ru
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ru/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/sk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/sk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/sl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/sl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/sq
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/sq/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/sr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/sr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/sr_Latn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/sv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/sv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/sw
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/sw/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ta
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ta/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/te
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/te/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/te/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/te/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/tg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/tg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/th
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/th/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/th/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/th/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/tk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/tk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/tr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/tr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/tt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/tt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/udm
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/udm/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/uk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/uk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ur
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/ur/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/vi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/vi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/zh_Hans
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/zh_Hant
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages
copying build/lib/django/contrib/flatpages/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages
copying build/lib/django/contrib/flatpages/admin.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages
copying build/lib/django/contrib/flatpages/apps.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages
copying build/lib/django/contrib/flatpages/forms.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages
copying build/lib/django/contrib/flatpages/middleware.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages
copying build/lib/django/contrib/flatpages/models.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages
copying build/lib/django/contrib/flatpages/sitemaps.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages
copying build/lib/django/contrib/flatpages/urls.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages
copying build/lib/django/contrib/flatpages/views.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/migrations
copying build/lib/django/contrib/flatpages/migrations/0001_initial.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/migrations
copying build/lib/django/contrib/flatpages/migrations/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/migrations
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/templatetags
copying build/lib/django/contrib/flatpages/templatetags/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/templatetags
copying build/lib/django/contrib/flatpages/templatetags/flatpages.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/templatetags
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/af
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/af/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/af/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/af/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ar
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ar/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ar_DZ
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ast
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ast/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/az
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/az/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/az/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/az/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/be
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/be/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/be/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/be/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/bg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/bg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/bn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/bn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/br
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/br/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/br/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/br/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/bs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/bs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ca
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ca/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/cs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/cs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/cy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/cy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/da
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/da/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/da/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/da/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/de
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/de/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/de/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/de/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/dsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/dsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/el
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/el/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/el/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/el/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/en
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/en/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/en/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/en/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/en_AU
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/en_AU/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/en_GB
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/en_GB/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/eo
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/eo/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/es
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/es/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/es/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/es/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/es_AR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/es_AR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/es_CO
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/es_CO/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/es_MX
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/es_MX/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/es_VE
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/es_VE/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/et
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/et/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/et/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/et/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/eu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/eu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/fa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/fa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/fi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/fi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/fr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/fr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/fy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/fy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ga
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ga/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/gd
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/gd/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/gl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/gl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/he
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/he/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/he/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/he/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/hi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/hi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/hr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/hr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/hsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/hsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/hu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/hu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/hy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/hy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ia
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ia/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/id
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/id/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/id/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/id/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/io
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/io/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/io/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/io/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/is
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/is/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/is/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/is/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/it
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/it/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/it/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/it/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ja
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ja/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ka
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ka/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/kk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/kk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/km
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/km/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/km/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/km/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/kn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/kn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ko
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ko/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ky
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ky/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/lb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/lb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/lt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/lt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/lv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/lv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/mk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/mk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ml
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ml/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/mn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/mn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/mr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/mr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/my
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/my/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/my/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/my/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/nb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/nb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ne
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ne/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/nl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/nl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/nn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/nn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/os
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/os/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/os/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/os/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/pa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/pa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/pl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/pl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/pt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/pt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/pt_BR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ro
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ro/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ru
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ru/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/sk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/sk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/sl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/sl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/sq
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/sq/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/sr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/sr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/sr_Latn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/sv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/sv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/sw
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/sw/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ta
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ta/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/te
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/te/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/te/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/te/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/tg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/tg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/th
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/th/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/th/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/th/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/tk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/tk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/tr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/tr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/tt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/tt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/udm
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/udm/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/uk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/uk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ur
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/ur/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/vi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/vi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/zh_Hans
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/zh_Hant
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis
copying build/lib/django/contrib/gis/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis
copying build/lib/django/contrib/gis/apps.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis
copying build/lib/django/contrib/gis/feeds.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis
copying build/lib/django/contrib/gis/geometry.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis
copying build/lib/django/contrib/gis/measure.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis
copying build/lib/django/contrib/gis/ptr.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis
copying build/lib/django/contrib/gis/shortcuts.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis
copying build/lib/django/contrib/gis/views.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/admin
copying build/lib/django/contrib/gis/admin/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/admin
copying build/lib/django/contrib/gis/admin/options.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/admin
copying build/lib/django/contrib/gis/admin/widgets.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/admin
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/db
copying build/lib/django/contrib/gis/db/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/db/backends
copying build/lib/django/contrib/gis/db/backends/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends
copying build/lib/django/contrib/gis/db/backends/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/db/backends/base
copying build/lib/django/contrib/gis/db/backends/base/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/base
copying build/lib/django/contrib/gis/db/backends/base/adapter.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/base
copying build/lib/django/contrib/gis/db/backends/base/features.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/base
copying build/lib/django/contrib/gis/db/backends/base/models.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/base
copying build/lib/django/contrib/gis/db/backends/base/operations.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/base
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/db/backends/mysql
copying build/lib/django/contrib/gis/db/backends/mysql/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/mysql
copying build/lib/django/contrib/gis/db/backends/mysql/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/mysql
copying build/lib/django/contrib/gis/db/backends/mysql/features.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/mysql
copying build/lib/django/contrib/gis/db/backends/mysql/introspection.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/mysql
copying build/lib/django/contrib/gis/db/backends/mysql/operations.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/mysql
copying build/lib/django/contrib/gis/db/backends/mysql/schema.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/mysql
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/db/backends/oracle
copying build/lib/django/contrib/gis/db/backends/oracle/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/oracle
copying build/lib/django/contrib/gis/db/backends/oracle/adapter.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/oracle
copying build/lib/django/contrib/gis/db/backends/oracle/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/oracle
copying build/lib/django/contrib/gis/db/backends/oracle/features.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/oracle
copying build/lib/django/contrib/gis/db/backends/oracle/introspection.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/oracle
copying build/lib/django/contrib/gis/db/backends/oracle/models.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/oracle
copying build/lib/django/contrib/gis/db/backends/oracle/operations.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/oracle
copying build/lib/django/contrib/gis/db/backends/oracle/schema.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/oracle
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/adapter.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/const.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/features.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/introspection.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/models.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/operations.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/pgraster.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/schema.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/postgis
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/adapter.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/client.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/features.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/introspection.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/models.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/operations.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/schema.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/backends/spatialite
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/db/models
copying build/lib/django/contrib/gis/db/models/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/models
copying build/lib/django/contrib/gis/db/models/aggregates.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/models
copying build/lib/django/contrib/gis/db/models/fields.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/models
copying build/lib/django/contrib/gis/db/models/functions.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/models
copying build/lib/django/contrib/gis/db/models/lookups.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/models
copying build/lib/django/contrib/gis/db/models/proxy.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/models
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/db/models/sql
copying build/lib/django/contrib/gis/db/models/sql/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/models/sql
copying build/lib/django/contrib/gis/db/models/sql/conversion.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/db/models/sql
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/forms
copying build/lib/django/contrib/gis/forms/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/forms
copying build/lib/django/contrib/gis/forms/fields.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/forms
copying build/lib/django/contrib/gis/forms/widgets.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/forms
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/datasource.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/driver.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/envelope.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/error.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/feature.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/field.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/geometries.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/geomtype.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/layer.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/libgdal.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/srs.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/gdal/prototypes
copying build/lib/django/contrib/gis/gdal/prototypes/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal/prototypes
copying build/lib/django/contrib/gis/gdal/prototypes/ds.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal/prototypes
copying build/lib/django/contrib/gis/gdal/prototypes/errcheck.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal/prototypes
copying build/lib/django/contrib/gis/gdal/prototypes/generation.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal/prototypes
copying build/lib/django/contrib/gis/gdal/prototypes/geom.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal/prototypes
copying build/lib/django/contrib/gis/gdal/prototypes/raster.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal/prototypes
copying build/lib/django/contrib/gis/gdal/prototypes/srs.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal/prototypes
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/gdal/raster
copying build/lib/django/contrib/gis/gdal/raster/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal/raster
copying build/lib/django/contrib/gis/gdal/raster/band.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal/raster
copying build/lib/django/contrib/gis/gdal/raster/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal/raster
copying build/lib/django/contrib/gis/gdal/raster/const.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal/raster
copying build/lib/django/contrib/gis/gdal/raster/source.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal/raster
copying build/lib/django/contrib/gis/gdal/LICENSE -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/gdal
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/geoip2
copying build/lib/django/contrib/gis/geoip2/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geoip2
copying build/lib/django/contrib/gis/geoip2/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geoip2
copying build/lib/django/contrib/gis/geoip2/resources.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geoip2
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/collections.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/coordseq.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/error.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/factory.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/geometry.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/io.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/libgeos.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/linestring.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/mutable_list.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/point.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/polygon.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/prepared.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/coordseq.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/errcheck.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/geom.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/io.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/misc.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/predicates.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/prepared.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/threadsafe.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/topology.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/LICENSE -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/geos
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/management
copying build/lib/django/contrib/gis/management/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/management
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/management/commands
copying build/lib/django/contrib/gis/management/commands/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/management/commands
copying build/lib/django/contrib/gis/management/commands/inspectdb.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/management/commands
copying build/lib/django/contrib/gis/management/commands/ogrinspect.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/management/commands
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/serializers
copying build/lib/django/contrib/gis/serializers/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/serializers
copying build/lib/django/contrib/gis/serializers/geojson.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/serializers
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/sitemaps
copying build/lib/django/contrib/gis/sitemaps/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/sitemaps
copying build/lib/django/contrib/gis/sitemaps/kml.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/sitemaps
copying build/lib/django/contrib/gis/sitemaps/views.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/sitemaps
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/utils
copying build/lib/django/contrib/gis/utils/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/utils
copying build/lib/django/contrib/gis/utils/layermapping.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/utils
copying build/lib/django/contrib/gis/utils/ogrinfo.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/utils
copying build/lib/django/contrib/gis/utils/ogrinspect.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/utils
copying build/lib/django/contrib/gis/utils/srs.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/utils
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/af
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/af/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/af/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/af/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/af/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/af/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ar
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ar/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ar_DZ
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ar_DZ/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ast
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ast/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ast/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ast/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/az
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/az/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/az/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/az/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/az/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/az/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/be
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/be/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/be/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/be/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/be/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/be/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/bg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/bg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/bn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/bn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/bn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/bn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/br
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/br/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/br/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/br/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/br/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/br/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/bs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/bs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/bs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/bs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ca
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ca/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/cs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/cs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/cy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/cy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/cy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/cy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/da
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/da/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/da/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/da/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/de
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/de/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/de/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/de/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/dsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/dsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/el
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/el/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/el/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/el/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/el/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/el/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/en
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/en/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/en/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/en/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/en_AU
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/en_AU/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/en_GB
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/en_GB/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/eo
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/eo/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/es
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/es/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/es/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/es/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/es_AR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/es_AR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/es_CO
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/es_CO/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/es_MX
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/es_MX/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/es_VE
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/es_VE/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/et
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/et/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/et/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/et/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/eu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/eu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/eu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/eu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/fa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/fa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/fi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/fi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/fr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/fr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/fy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/fy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/fy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/fy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ga
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ga/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ga/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ga/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/gd
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/gd/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/gd/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/gd/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/gl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/gl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/gl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/gl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/he
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/he/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/he/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/he/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/he/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/he/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/hi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/hi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/hr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/hr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/hsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/hsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/hu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/hu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/hy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/hy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ia
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ia/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ia/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ia/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/id
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/id/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/id/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/id/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/id/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/id/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/io
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/io/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/io/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/io/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/io/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/io/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/is
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/is/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/is/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/is/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/is/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/is/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/it
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/it/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/it/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/it/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ja
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ja/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ka
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ka/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ka/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ka/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/kk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/kk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/kk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/kk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/km
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/km/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/km/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/km/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/km/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/km/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/kn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/kn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/kn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/kn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ko
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ko/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ky
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ky/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ky/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ky/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/lb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/lb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/lb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/lb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/lt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/lt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/lt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/lt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/lv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/lv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/mk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/mk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/mk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/mk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ml
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ml/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ml/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ml/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/mn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/mn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/mn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/mn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/mr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/mr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/mr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/mr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/my
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/my/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/my/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/my/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/my/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/my/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/nb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/nb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ne
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ne/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ne/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ne/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/nl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/nl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/nn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/nn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/nn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/nn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/os
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/os/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/os/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/os/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/os/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/os/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/pa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/pa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/pa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/pa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/pl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/pl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/pt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/pt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/pt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/pt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/pt_BR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/pt_BR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ro
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ro/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ro/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ro/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ru
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ru/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/sk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/sk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/sl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/sl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/sq
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sq/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sq/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/sq/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/sr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/sr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/sr_Latn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/sr_Latn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/sv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/sv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/sw
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sw/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sw/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/sw/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ta
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ta/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ta/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ta/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/te
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/te/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/te/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/te/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/te/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/te/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/tg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/tg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/tg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/tg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/th
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/th/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/th/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/th/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/th/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/th/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/tr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/tr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/tt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/tt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/tt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/tt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/udm
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/udm/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/udm/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/udm/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/uk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/uk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/uk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/uk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ur
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ur/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ur/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/ur/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/vi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/vi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/vi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/vi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/zh_Hans
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/zh_Hans/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/zh_Hant
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/locale/zh_Hant/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/static
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/static/gis
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/static/gis/css
copying build/lib/django/contrib/gis/static/gis/css/ol3.css -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/static/gis/css
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/static/gis/img
copying build/lib/django/contrib/gis/static/gis/img/draw_line_off.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/static/gis/img
copying build/lib/django/contrib/gis/static/gis/img/draw_line_on.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/static/gis/img
copying build/lib/django/contrib/gis/static/gis/img/draw_point_off.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/static/gis/img
copying build/lib/django/contrib/gis/static/gis/img/draw_point_on.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/static/gis/img
copying build/lib/django/contrib/gis/static/gis/img/draw_polygon_off.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/static/gis/img
copying build/lib/django/contrib/gis/static/gis/img/draw_polygon_on.svg -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/static/gis/img
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/static/gis/js
copying build/lib/django/contrib/gis/static/gis/js/OLMapWidget.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/static/gis/js
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/templates
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/templates/gis
copying build/lib/django/contrib/gis/templates/gis/openlayers-osm.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/templates/gis
copying build/lib/django/contrib/gis/templates/gis/openlayers.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/templates/gis
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/templates/gis/admin
copying build/lib/django/contrib/gis/templates/gis/admin/openlayers.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/templates/gis/admin
copying build/lib/django/contrib/gis/templates/gis/admin/openlayers.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/templates/gis/admin
copying build/lib/django/contrib/gis/templates/gis/admin/osm.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/templates/gis/admin
copying build/lib/django/contrib/gis/templates/gis/admin/osm.js -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/templates/gis/admin
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/gis/templates/gis/kml
copying build/lib/django/contrib/gis/templates/gis/kml/base.kml -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/templates/gis/kml
copying build/lib/django/contrib/gis/templates/gis/kml/placemarks.kml -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/gis/templates/gis/kml
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize
copying build/lib/django/contrib/humanize/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize
copying build/lib/django/contrib/humanize/apps.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/templatetags
copying build/lib/django/contrib/humanize/templatetags/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/templatetags
copying build/lib/django/contrib/humanize/templatetags/humanize.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/templatetags
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/af
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/af/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/af/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/af/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/af/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/af/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ar
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ar/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ar_DZ
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ast
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ast/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/az
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/az/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/az/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/az/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/az/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/az/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/be
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/be/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/be/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/be/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/be/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/be/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/bg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/bg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/bn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/bn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/br
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/br/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/br/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/br/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/br/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/br/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/bs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/bs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ca
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ca/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/cs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/cs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/cy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/cy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/da
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/da/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/da/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/da/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/de
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/de/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/de/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/de/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/dsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/dsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/el
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/el/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/el/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/el/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/el/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/el/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/en
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/en/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/en/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/en/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/en_AU
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/en_AU/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/en_GB
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/en_GB/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/eo
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/eo/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/es
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/es/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/es/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/es/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/es_AR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/es_AR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/es_CO
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/es_CO/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/es_MX
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/es_MX/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/es_VE
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/es_VE/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/et
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/et/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/et/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/et/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/eu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/eu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/fa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/fa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/fi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/fi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/fr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/fr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/fy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/fy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ga
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ga/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/gd
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/gd/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/gl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/gl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/he
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/he/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/he/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/he/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/he/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/he/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/hi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/hi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/hr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/hr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/hsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/hsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/hu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/hu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/hy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/hy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ia
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ia/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/id
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/id/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/id/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/id/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/id/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/id/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/io
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/io/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/io/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/io/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/io/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/io/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/is
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/is/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/is/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/is/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/is/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/is/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/it
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/it/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/it/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/it/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ja
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ja/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ka
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ka/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/kk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/kk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/km
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/km/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/km/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/km/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/km/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/km/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/kn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/kn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ko
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ko/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ky
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ky/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/lb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/lb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/lt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/lt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/lv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/lv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/mk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/mk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ml
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ml/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/mn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/mn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/mr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/mr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ms
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ms/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/my
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/my/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/my/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/my/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/my/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/my/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/nb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/nb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ne
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ne/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/nl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/nl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/nn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/nn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/os
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/os/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/os/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/os/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/os/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/os/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/pa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/pa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/pl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/pl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/pt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/pt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/pt_BR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/pt_BR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ro
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ro/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ru
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ru/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/sk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/sk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/sl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/sl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/sq
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/sq/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/sr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/sr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/sr_Latn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/sv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/sv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/sw
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/sw/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ta
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ta/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/te
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/te/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/te/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/te/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/te/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/te/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/tg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/tg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/th
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/th/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/th/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/th/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/th/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/th/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/tr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/tr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/tt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/tt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/udm
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/udm/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/uk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/uk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ur
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/ur/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/uz
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/uz/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/vi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/vi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/zh_Hans
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/zh_Hant
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/messages
copying build/lib/django/contrib/messages/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/messages
copying build/lib/django/contrib/messages/api.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/messages
copying build/lib/django/contrib/messages/apps.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/messages
copying build/lib/django/contrib/messages/constants.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/messages
copying build/lib/django/contrib/messages/context_processors.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/messages
copying build/lib/django/contrib/messages/middleware.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/messages
copying build/lib/django/contrib/messages/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/messages
copying build/lib/django/contrib/messages/views.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/messages
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/messages/storage
copying build/lib/django/contrib/messages/storage/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/messages/storage
copying build/lib/django/contrib/messages/storage/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/messages/storage
copying build/lib/django/contrib/messages/storage/cookie.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/messages/storage
copying build/lib/django/contrib/messages/storage/fallback.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/messages/storage
copying build/lib/django/contrib/messages/storage/session.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/messages/storage
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres
copying build/lib/django/contrib/postgres/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres
copying build/lib/django/contrib/postgres/apps.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres
copying build/lib/django/contrib/postgres/constraints.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres
copying build/lib/django/contrib/postgres/functions.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres
copying build/lib/django/contrib/postgres/indexes.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres
copying build/lib/django/contrib/postgres/lookups.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres
copying build/lib/django/contrib/postgres/operations.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres
copying build/lib/django/contrib/postgres/search.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres
copying build/lib/django/contrib/postgres/serializers.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres
copying build/lib/django/contrib/postgres/signals.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres
copying build/lib/django/contrib/postgres/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres
copying build/lib/django/contrib/postgres/validators.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/aggregates
copying build/lib/django/contrib/postgres/aggregates/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/aggregates
copying build/lib/django/contrib/postgres/aggregates/general.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/aggregates
copying build/lib/django/contrib/postgres/aggregates/mixins.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/aggregates
copying build/lib/django/contrib/postgres/aggregates/statistics.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/aggregates
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/fields
copying build/lib/django/contrib/postgres/fields/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/fields
copying build/lib/django/contrib/postgres/fields/array.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/fields
copying build/lib/django/contrib/postgres/fields/citext.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/fields
copying build/lib/django/contrib/postgres/fields/hstore.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/fields
copying build/lib/django/contrib/postgres/fields/jsonb.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/fields
copying build/lib/django/contrib/postgres/fields/ranges.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/fields
copying build/lib/django/contrib/postgres/fields/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/fields
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/forms
copying build/lib/django/contrib/postgres/forms/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/forms
copying build/lib/django/contrib/postgres/forms/array.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/forms
copying build/lib/django/contrib/postgres/forms/hstore.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/forms
copying build/lib/django/contrib/postgres/forms/jsonb.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/forms
copying build/lib/django/contrib/postgres/forms/ranges.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/forms
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/jinja2
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/jinja2/postgres
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/jinja2/postgres/widgets
copying build/lib/django/contrib/postgres/jinja2/postgres/widgets/split_array.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/jinja2/postgres/widgets
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/af
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/af/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/af/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/af/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/af/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/af/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ar
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ar/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ar_DZ
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/az
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/az/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/az/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/az/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/az/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/az/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/be
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/be/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/be/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/be/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/be/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/be/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/bg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/bg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ca
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ca/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/cs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/cs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/da
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/da/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/da/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/da/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/de
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/de/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/de/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/de/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/dsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/dsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/el
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/el/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/el/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/el/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/el/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/el/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/en
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/en/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/en/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/en/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/eo
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/eo/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/es
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/es/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/es/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/es/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/es_AR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/es_AR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/es_CO
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/es_CO/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/es_MX
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/es_MX/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/et
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/et/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/et/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/et/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/eu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/eu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/fa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/fa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/fi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/fi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/fr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/fr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/gd
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/gd/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/gl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/gl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/he
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/he/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/he/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/he/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/he/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/he/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/hr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/hr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/hsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/hsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/hu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/hu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/hy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/hy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ia
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ia/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/id
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/id/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/id/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/id/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/id/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/id/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/is
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/is/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/is/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/is/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/is/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/is/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/it
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/it/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/it/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/it/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ja
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ja/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ka
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ka/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/kk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/kk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ko
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ko/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ky
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ky/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/lt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/lt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/lv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/lv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/mk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/mk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ml
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ml/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/mn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/mn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/nb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/nb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ne
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ne/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/nl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/nl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/pl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/pl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/pt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/pt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/pt_BR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/pt_BR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ro
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ro/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ru
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/ru/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/sk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/sk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/sl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/sl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/sq
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/sq/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/sr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/sr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/sr_Latn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/sv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/sv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/tg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/tg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/tk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/tk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/tr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/tr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/uk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/uk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/uz
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/uz/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/zh_Hans
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/zh_Hant
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/templates
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/templates/postgres
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/postgres/templates/postgres/widgets
copying build/lib/django/contrib/postgres/templates/postgres/widgets/split_array.html -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/postgres/templates/postgres/widgets
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects
copying build/lib/django/contrib/redirects/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects
copying build/lib/django/contrib/redirects/admin.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects
copying build/lib/django/contrib/redirects/apps.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects
copying build/lib/django/contrib/redirects/middleware.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects
copying build/lib/django/contrib/redirects/models.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/migrations
copying build/lib/django/contrib/redirects/migrations/0001_initial.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/migrations
copying build/lib/django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/migrations
copying build/lib/django/contrib/redirects/migrations/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/migrations
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/af
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/af/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/af/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/af/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/af/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/af/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ar
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ar/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ar_DZ
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ast
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ast/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/az
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/az/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/az/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/az/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/az/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/az/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/be
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/be/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/be/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/be/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/be/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/be/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/bg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/bg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/bn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/bn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/br
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/br/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/br/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/br/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/br/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/br/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/bs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/bs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ca
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ca/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/cs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/cs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/cy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/cy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/da
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/da/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/da/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/da/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/de
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/de/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/de/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/de/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/dsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/dsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/el
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/el/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/el/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/el/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/el/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/el/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/en
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/en/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/en/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/en/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/en_AU
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/en_AU/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/en_GB
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/en_GB/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/eo
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/eo/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/es
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/es/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/es/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/es/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/es_AR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/es_AR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/es_CO
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/es_CO/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/es_MX
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/es_MX/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/es_VE
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/es_VE/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/et
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/et/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/et/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/et/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/eu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/eu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/fa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/fa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/fi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/fi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/fr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/fr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/fy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/fy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ga
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ga/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/gd
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/gd/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/gl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/gl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/he
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/he/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/he/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/he/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/he/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/he/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/hi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/hi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/hr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/hr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/hsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/hsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/hu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/hu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/hy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/hy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ia
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ia/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/id
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/id/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/id/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/id/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/id/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/id/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/io
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/io/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/io/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/io/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/io/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/io/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/is
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/is/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/is/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/is/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/is/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/is/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/it
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/it/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/it/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/it/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ja
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ja/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ka
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ka/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/kab
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/kab/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/kk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/kk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/km
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/km/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/km/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/km/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/km/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/km/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/kn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/kn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ko
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ko/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ky
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ky/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/lb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/lb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/lt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/lt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/lv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/lv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/mk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/mk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ml
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ml/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/mn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/mn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/mr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/mr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/my
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/my/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/my/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/my/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/my/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/my/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/nb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/nb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ne
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ne/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/nl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/nl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/nn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/nn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/os
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/os/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/os/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/os/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/os/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/os/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/pa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/pa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/pl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/pl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/pt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/pt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/pt_BR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/pt_BR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ro
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ro/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ru
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ru/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/sk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/sk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/sl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/sl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/sq
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/sq/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/sr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/sr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/sr_Latn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/sv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/sv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/sw
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/sw/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ta
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ta/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/te
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/te/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/te/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/te/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/te/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/te/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/tg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/tg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/th
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/th/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/th/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/th/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/th/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/th/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/tk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/tk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/tr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/tr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/tt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/tt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/udm
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/udm/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/uk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/uk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ur
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/ur/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/uz
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/uz/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/vi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/vi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/zh_Hans
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/zh_Hant
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions
copying build/lib/django/contrib/sessions/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions
copying build/lib/django/contrib/sessions/apps.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions
copying build/lib/django/contrib/sessions/base_session.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions
copying build/lib/django/contrib/sessions/exceptions.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions
copying build/lib/django/contrib/sessions/middleware.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions
copying build/lib/django/contrib/sessions/models.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions
copying build/lib/django/contrib/sessions/serializers.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/backends
copying build/lib/django/contrib/sessions/backends/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/backends
copying build/lib/django/contrib/sessions/backends/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/backends
copying build/lib/django/contrib/sessions/backends/cache.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/backends
copying build/lib/django/contrib/sessions/backends/cached_db.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/backends
copying build/lib/django/contrib/sessions/backends/db.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/backends
copying build/lib/django/contrib/sessions/backends/file.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/backends
copying build/lib/django/contrib/sessions/backends/signed_cookies.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/backends
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/management
copying build/lib/django/contrib/sessions/management/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/management
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/management/commands
copying build/lib/django/contrib/sessions/management/commands/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/management/commands
copying build/lib/django/contrib/sessions/management/commands/clearsessions.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/management/commands
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/migrations
copying build/lib/django/contrib/sessions/migrations/0001_initial.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/migrations
copying build/lib/django/contrib/sessions/migrations/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/migrations
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/af
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/af/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/af/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/af/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/af/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/af/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ar
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ar/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ar_DZ
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ast
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ast/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/az
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/az/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/az/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/az/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/az/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/az/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/be
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/be/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/be/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/be/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/be/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/be/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/bg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/bg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/bn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/bn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/br
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/br/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/br/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/br/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/br/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/br/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/bs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/bs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ca
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ca/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/cs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/cs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/cy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/cy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/da
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/da/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/da/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/da/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/de
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/de/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/de/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/de/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/dsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/dsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/el
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/el/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/el/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/el/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/el/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/el/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/en
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/en/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/en/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/en/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/en_AU
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/en_AU/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/en_GB
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/en_GB/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/eo
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/eo/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/es
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/es/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/es/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/es/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/es_AR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/es_AR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/es_CO
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/es_CO/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/es_MX
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/es_MX/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/es_VE
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/es_VE/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/et
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/et/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/et/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/et/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/eu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/eu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/fa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/fa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/fi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/fi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/fr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/fr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/fy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/fy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ga
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ga/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/gd
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/gd/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/gl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/gl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/he
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/he/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/he/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/he/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/he/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/he/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/hi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/hi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/hr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/hr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/hsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/hsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/hu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/hu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/hy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/hy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ia
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ia/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/id
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/id/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/id/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/id/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/id/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/id/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/io
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/io/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/io/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/io/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/io/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/io/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/is
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/is/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/is/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/is/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/is/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/is/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/it
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/it/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/it/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/it/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ja
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ja/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ka
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ka/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/kab
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/kab/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/kk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/kk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/km
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/km/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/km/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/km/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/km/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/km/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/kn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/kn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ko
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ko/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ky
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ky/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/lb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/lb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/lt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/lt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/lv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/lv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/mk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/mk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ml
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ml/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/mn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/mn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/mr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/mr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/my
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/my/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/my/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/my/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/my/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/my/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/nb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/nb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ne
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ne/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/nl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/nl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/nn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/nn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/os
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/os/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/os/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/os/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/os/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/os/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/pa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/pa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/pl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/pl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/pt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/pt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/pt_BR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/pt_BR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ro
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ro/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ru
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ru/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/sk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/sk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/sl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/sl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/sq
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/sq/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/sr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/sr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/sr_Latn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/sv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/sv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/sw
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/sw/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ta
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ta/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/te
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/te/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/te/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/te/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/te/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/te/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/tg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/tg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/th
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/th/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/th/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/th/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/th/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/th/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/tk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/tk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/tr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/tr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/tt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/tt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/udm
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/udm/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/uk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/uk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ur
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/ur/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/uz
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/uz/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/vi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/vi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/zh_Hans
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/zh_Hant
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sitemaps
copying build/lib/django/contrib/sitemaps/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sitemaps
copying build/lib/django/contrib/sitemaps/apps.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sitemaps
copying build/lib/django/contrib/sitemaps/views.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sitemaps
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sitemaps/management
copying build/lib/django/contrib/sitemaps/management/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sitemaps/management
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sitemaps/management/commands
copying build/lib/django/contrib/sitemaps/management/commands/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sitemaps/management/commands
copying build/lib/django/contrib/sitemaps/management/commands/ping_google.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sitemaps/management/commands
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sitemaps/templates
copying build/lib/django/contrib/sitemaps/templates/sitemap.xml -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sitemaps/templates
copying build/lib/django/contrib/sitemaps/templates/sitemap_index.xml -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sitemaps/templates
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites
copying build/lib/django/contrib/sites/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites
copying build/lib/django/contrib/sites/admin.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites
copying build/lib/django/contrib/sites/apps.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites
copying build/lib/django/contrib/sites/checks.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites
copying build/lib/django/contrib/sites/management.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites
copying build/lib/django/contrib/sites/managers.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites
copying build/lib/django/contrib/sites/middleware.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites
copying build/lib/django/contrib/sites/models.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites
copying build/lib/django/contrib/sites/requests.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites
copying build/lib/django/contrib/sites/shortcuts.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/migrations
copying build/lib/django/contrib/sites/migrations/0001_initial.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/migrations
copying build/lib/django/contrib/sites/migrations/0002_alter_domain_unique.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/migrations
copying build/lib/django/contrib/sites/migrations/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/migrations
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/af
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/af/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/af/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/af/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/af/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/af/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ar
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ar/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ar_DZ
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ar_DZ/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ast
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ast/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ast/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ast/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/az
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/az/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/az/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/az/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/az/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/az/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/be
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/be/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/be/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/be/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/be/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/be/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/bg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/bg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/bn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/bn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/bn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/bn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/br
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/br/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/br/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/br/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/br/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/br/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/bs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/bs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/bs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/bs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ca
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ca/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/cs
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/cs/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/cy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/cy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/cy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/cy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/da
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/da/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/da/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/da/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/de
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/de/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/de/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/de/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/dsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/dsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/el
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/el/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/el/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/el/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/el/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/el/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/en
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/en/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/en/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/en/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/en_AU
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/en_AU/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/en_GB
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/en_GB/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/eo
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/eo/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/es
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/es/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/es/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/es/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/es_AR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/es_AR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/es_CO
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/es_CO/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/es_MX
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/es_MX/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/es_VE
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/es_VE/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/et
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/et/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/et/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/et/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/eu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/eu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/eu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/eu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/fa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/fa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/fi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/fi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/fr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/fr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/fy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/fy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/fy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/fy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ga
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ga/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ga/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ga/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/gd
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/gd/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/gd/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/gd/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/gl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/gl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/gl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/gl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/he
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/he/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/he/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/he/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/he/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/he/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/hi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/hi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/hr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/hr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/hsb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/hsb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/hu
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/hu/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/hy
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hy/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hy/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/hy/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ia
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ia/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ia/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ia/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/id
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/id/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/id/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/id/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/id/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/id/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/io
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/io/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/io/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/io/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/io/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/io/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/is
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/is/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/is/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/is/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/is/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/is/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/it
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/it/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/it/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/it/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ja
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ja/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ka
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ka/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ka/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ka/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/kab
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/kab/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/kab/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/kab/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/kk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/kk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/kk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/kk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/km
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/km/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/km/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/km/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/km/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/km/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/kn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/kn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/kn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/kn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ko
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ko/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ky
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ky/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ky/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ky/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/lb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/lb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/lb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/lb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/lt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/lt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/lt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/lt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/lv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/lv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/mk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/mk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/mk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/mk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ml
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ml/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ml/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ml/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/mn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/mn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/mn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/mn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/mr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/mr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/mr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/mr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/my
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/my/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/my/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/my/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/my/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/my/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/nb
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/nb/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ne
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ne/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ne/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ne/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/nl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/nl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/nn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/nn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/nn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/nn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/os
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/os/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/os/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/os/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/os/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/os/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/pa
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/pa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/pa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/pa/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/pl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/pl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/pt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/pt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/pt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/pt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/pt_BR
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/pt_BR/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ro
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ro/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ro/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ro/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ru
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ru/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/sk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/sk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/sl
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/sl/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/sq
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sq/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sq/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/sq/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/sr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/sr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/sr_Latn
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/sr_Latn/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/sv
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/sv/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/sw
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sw/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sw/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/sw/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ta
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ta/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ta/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ta/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/te
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/te/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/te/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/te/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/te/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/te/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/tg
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/tg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/tg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/tg/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/th
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/th/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/th/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/th/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/th/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/th/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/tk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/tk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/tk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/tk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/tr
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/tr/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/tt
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/tt/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/tt/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/tt/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/udm
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/udm/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/udm/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/udm/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/uk
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/uk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/uk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/uk/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ur
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ur/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ur/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/ur/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/uz
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/uz/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/uz/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/uz/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/vi
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/vi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/vi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/vi/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/zh_Hans
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/zh_Hans/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/zh_Hant
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/sites/locale/zh_Hant/LC_MESSAGES
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/apps.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/checks.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/finders.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/handlers.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/storage.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/testing.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/urls.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/views.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/staticfiles
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/staticfiles/management
copying build/lib/django/contrib/staticfiles/management/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/staticfiles/management
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/staticfiles/management/commands
copying build/lib/django/contrib/staticfiles/management/commands/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/staticfiles/management/commands
copying build/lib/django/contrib/staticfiles/management/commands/collectstatic.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/staticfiles/management/commands
copying build/lib/django/contrib/staticfiles/management/commands/findstatic.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/staticfiles/management/commands
copying build/lib/django/contrib/staticfiles/management/commands/runserver.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/staticfiles/management/commands
creating build/bdist.netbsd-9.0-i386/wheel/django/contrib/syndication
copying build/lib/django/contrib/syndication/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/syndication
copying build/lib/django/contrib/syndication/apps.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/syndication
copying build/lib/django/contrib/syndication/views.py -> build/bdist.netbsd-9.0-i386/wheel/./django/contrib/syndication
creating build/bdist.netbsd-9.0-i386/wheel/django/core
copying build/lib/django/core/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core
copying build/lib/django/core/asgi.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core
copying build/lib/django/core/exceptions.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core
copying build/lib/django/core/paginator.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core
copying build/lib/django/core/signals.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core
copying build/lib/django/core/signing.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core
copying build/lib/django/core/validators.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core
copying build/lib/django/core/wsgi.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core
creating build/bdist.netbsd-9.0-i386/wheel/django/core/cache
copying build/lib/django/core/cache/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/cache
copying build/lib/django/core/cache/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/cache
creating build/bdist.netbsd-9.0-i386/wheel/django/core/cache/backends
copying build/lib/django/core/cache/backends/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/cache/backends
copying build/lib/django/core/cache/backends/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/cache/backends
copying build/lib/django/core/cache/backends/db.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/cache/backends
copying build/lib/django/core/cache/backends/dummy.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/cache/backends
copying build/lib/django/core/cache/backends/filebased.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/cache/backends
copying build/lib/django/core/cache/backends/locmem.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/cache/backends
copying build/lib/django/core/cache/backends/memcached.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/cache/backends
creating build/bdist.netbsd-9.0-i386/wheel/django/core/checks
copying build/lib/django/core/checks/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/checks
copying build/lib/django/core/checks/async_checks.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/checks
copying build/lib/django/core/checks/caches.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/checks
copying build/lib/django/core/checks/database.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/checks
copying build/lib/django/core/checks/messages.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/checks
copying build/lib/django/core/checks/model_checks.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/checks
copying build/lib/django/core/checks/registry.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/checks
copying build/lib/django/core/checks/templates.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/checks
copying build/lib/django/core/checks/translation.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/checks
copying build/lib/django/core/checks/urls.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/checks
creating build/bdist.netbsd-9.0-i386/wheel/django/core/checks/compatibility
copying build/lib/django/core/checks/compatibility/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/checks/compatibility
creating build/bdist.netbsd-9.0-i386/wheel/django/core/checks/security
copying build/lib/django/core/checks/security/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/checks/security
copying build/lib/django/core/checks/security/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/checks/security
copying build/lib/django/core/checks/security/csrf.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/checks/security
copying build/lib/django/core/checks/security/sessions.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/checks/security
creating build/bdist.netbsd-9.0-i386/wheel/django/core/files
copying build/lib/django/core/files/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/files
copying build/lib/django/core/files/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/files
copying build/lib/django/core/files/images.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/files
copying build/lib/django/core/files/locks.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/files
copying build/lib/django/core/files/move.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/files
copying build/lib/django/core/files/storage.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/files
copying build/lib/django/core/files/temp.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/files
copying build/lib/django/core/files/uploadedfile.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/files
copying build/lib/django/core/files/uploadhandler.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/files
copying build/lib/django/core/files/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/files
creating build/bdist.netbsd-9.0-i386/wheel/django/core/handlers
copying build/lib/django/core/handlers/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/handlers
copying build/lib/django/core/handlers/asgi.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/handlers
copying build/lib/django/core/handlers/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/handlers
copying build/lib/django/core/handlers/exception.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/handlers
copying build/lib/django/core/handlers/wsgi.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/handlers
creating build/bdist.netbsd-9.0-i386/wheel/django/core/mail
copying build/lib/django/core/mail/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/mail
copying build/lib/django/core/mail/message.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/mail
copying build/lib/django/core/mail/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/mail
creating build/bdist.netbsd-9.0-i386/wheel/django/core/mail/backends
copying build/lib/django/core/mail/backends/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/mail/backends
copying build/lib/django/core/mail/backends/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/mail/backends
copying build/lib/django/core/mail/backends/console.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/mail/backends
copying build/lib/django/core/mail/backends/dummy.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/mail/backends
copying build/lib/django/core/mail/backends/filebased.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/mail/backends
copying build/lib/django/core/mail/backends/locmem.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/mail/backends
copying build/lib/django/core/mail/backends/smtp.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/mail/backends
creating build/bdist.netbsd-9.0-i386/wheel/django/core/management
copying build/lib/django/core/management/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management
copying build/lib/django/core/management/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management
copying build/lib/django/core/management/color.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management
copying build/lib/django/core/management/sql.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management
copying build/lib/django/core/management/templates.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management
copying build/lib/django/core/management/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management
creating build/bdist.netbsd-9.0-i386/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/check.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/compilemessages.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/createcachetable.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/dbshell.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/diffsettings.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/dumpdata.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/flush.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/inspectdb.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/loaddata.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/makemessages.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/makemigrations.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/migrate.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/runserver.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/sendtestemail.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/shell.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/showmigrations.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/sqlflush.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/sqlmigrate.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/sqlsequencereset.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/squashmigrations.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/startapp.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/startproject.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/test.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
copying build/lib/django/core/management/commands/testserver.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/management/commands
creating build/bdist.netbsd-9.0-i386/wheel/django/core/serializers
copying build/lib/django/core/serializers/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/serializers
copying build/lib/django/core/serializers/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/serializers
copying build/lib/django/core/serializers/json.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/serializers
copying build/lib/django/core/serializers/jsonl.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/serializers
copying build/lib/django/core/serializers/python.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/serializers
copying build/lib/django/core/serializers/pyyaml.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/serializers
copying build/lib/django/core/serializers/xml_serializer.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/serializers
creating build/bdist.netbsd-9.0-i386/wheel/django/core/servers
copying build/lib/django/core/servers/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/servers
copying build/lib/django/core/servers/basehttp.py -> build/bdist.netbsd-9.0-i386/wheel/./django/core/servers
creating build/bdist.netbsd-9.0-i386/wheel/django/db
copying build/lib/django/db/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db
copying build/lib/django/db/transaction.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db
copying build/lib/django/db/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db
creating build/bdist.netbsd-9.0-i386/wheel/django/db/backends
copying build/lib/django/db/backends/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends
copying build/lib/django/db/backends/ddl_references.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends
copying build/lib/django/db/backends/signals.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends
copying build/lib/django/db/backends/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends
creating build/bdist.netbsd-9.0-i386/wheel/django/db/backends/base
copying build/lib/django/db/backends/base/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/base
copying build/lib/django/db/backends/base/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/base
copying build/lib/django/db/backends/base/client.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/base
copying build/lib/django/db/backends/base/creation.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/base
copying build/lib/django/db/backends/base/features.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/base
copying build/lib/django/db/backends/base/introspection.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/base
copying build/lib/django/db/backends/base/operations.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/base
copying build/lib/django/db/backends/base/schema.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/base
copying build/lib/django/db/backends/base/validation.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/base
creating build/bdist.netbsd-9.0-i386/wheel/django/db/backends/dummy
copying build/lib/django/db/backends/dummy/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/dummy
copying build/lib/django/db/backends/dummy/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/dummy
copying build/lib/django/db/backends/dummy/features.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/dummy
creating build/bdist.netbsd-9.0-i386/wheel/django/db/backends/mysql
copying build/lib/django/db/backends/mysql/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/mysql
copying build/lib/django/db/backends/mysql/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/mysql
copying build/lib/django/db/backends/mysql/client.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/mysql
copying build/lib/django/db/backends/mysql/compiler.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/mysql
copying build/lib/django/db/backends/mysql/creation.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/mysql
copying build/lib/django/db/backends/mysql/features.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/mysql
copying build/lib/django/db/backends/mysql/introspection.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/mysql
copying build/lib/django/db/backends/mysql/operations.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/mysql
copying build/lib/django/db/backends/mysql/schema.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/mysql
copying build/lib/django/db/backends/mysql/validation.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/mysql
creating build/bdist.netbsd-9.0-i386/wheel/django/db/backends/oracle
copying build/lib/django/db/backends/oracle/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/oracle
copying build/lib/django/db/backends/oracle/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/oracle
copying build/lib/django/db/backends/oracle/client.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/oracle
copying build/lib/django/db/backends/oracle/creation.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/oracle
copying build/lib/django/db/backends/oracle/features.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/oracle
copying build/lib/django/db/backends/oracle/functions.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/oracle
copying build/lib/django/db/backends/oracle/introspection.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/oracle
copying build/lib/django/db/backends/oracle/operations.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/oracle
copying build/lib/django/db/backends/oracle/schema.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/oracle
copying build/lib/django/db/backends/oracle/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/oracle
copying build/lib/django/db/backends/oracle/validation.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/oracle
creating build/bdist.netbsd-9.0-i386/wheel/django/db/backends/postgresql
copying build/lib/django/db/backends/postgresql/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/postgresql
copying build/lib/django/db/backends/postgresql/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/postgresql
copying build/lib/django/db/backends/postgresql/client.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/postgresql
copying build/lib/django/db/backends/postgresql/creation.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/postgresql
copying build/lib/django/db/backends/postgresql/features.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/postgresql
copying build/lib/django/db/backends/postgresql/introspection.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/postgresql
copying build/lib/django/db/backends/postgresql/operations.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/postgresql
copying build/lib/django/db/backends/postgresql/schema.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/postgresql
creating build/bdist.netbsd-9.0-i386/wheel/django/db/backends/sqlite3
copying build/lib/django/db/backends/sqlite3/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/sqlite3
copying build/lib/django/db/backends/sqlite3/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/sqlite3
copying build/lib/django/db/backends/sqlite3/client.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/sqlite3
copying build/lib/django/db/backends/sqlite3/creation.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/sqlite3
copying build/lib/django/db/backends/sqlite3/features.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/sqlite3
copying build/lib/django/db/backends/sqlite3/introspection.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/sqlite3
copying build/lib/django/db/backends/sqlite3/operations.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/sqlite3
copying build/lib/django/db/backends/sqlite3/schema.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/backends/sqlite3
creating build/bdist.netbsd-9.0-i386/wheel/django/db/migrations
copying build/lib/django/db/migrations/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations
copying build/lib/django/db/migrations/autodetector.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations
copying build/lib/django/db/migrations/exceptions.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations
copying build/lib/django/db/migrations/executor.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations
copying build/lib/django/db/migrations/graph.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations
copying build/lib/django/db/migrations/loader.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations
copying build/lib/django/db/migrations/migration.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations
copying build/lib/django/db/migrations/optimizer.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations
copying build/lib/django/db/migrations/questioner.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations
copying build/lib/django/db/migrations/recorder.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations
copying build/lib/django/db/migrations/serializer.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations
copying build/lib/django/db/migrations/state.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations
copying build/lib/django/db/migrations/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations
copying build/lib/django/db/migrations/writer.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations
creating build/bdist.netbsd-9.0-i386/wheel/django/db/migrations/operations
copying build/lib/django/db/migrations/operations/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations/operations
copying build/lib/django/db/migrations/operations/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations/operations
copying build/lib/django/db/migrations/operations/fields.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations/operations
copying build/lib/django/db/migrations/operations/models.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations/operations
copying build/lib/django/db/migrations/operations/special.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations/operations
copying build/lib/django/db/migrations/operations/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/migrations/operations
creating build/bdist.netbsd-9.0-i386/wheel/django/db/models
copying build/lib/django/db/models/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models
copying build/lib/django/db/models/aggregates.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models
copying build/lib/django/db/models/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models
copying build/lib/django/db/models/constants.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models
copying build/lib/django/db/models/constraints.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models
copying build/lib/django/db/models/deletion.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models
copying build/lib/django/db/models/enums.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models
copying build/lib/django/db/models/expressions.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models
copying build/lib/django/db/models/indexes.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models
copying build/lib/django/db/models/lookups.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models
copying build/lib/django/db/models/manager.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models
copying build/lib/django/db/models/options.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models
copying build/lib/django/db/models/query.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models
copying build/lib/django/db/models/query_utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models
copying build/lib/django/db/models/signals.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models
copying build/lib/django/db/models/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models
creating build/bdist.netbsd-9.0-i386/wheel/django/db/models/fields
copying build/lib/django/db/models/fields/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/fields
copying build/lib/django/db/models/fields/files.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/fields
copying build/lib/django/db/models/fields/json.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/fields
copying build/lib/django/db/models/fields/mixins.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/fields
copying build/lib/django/db/models/fields/proxy.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/fields
copying build/lib/django/db/models/fields/related.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/fields
copying build/lib/django/db/models/fields/related_descriptors.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/fields
copying build/lib/django/db/models/fields/related_lookups.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/fields
copying build/lib/django/db/models/fields/reverse_related.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/fields
creating build/bdist.netbsd-9.0-i386/wheel/django/db/models/functions
copying build/lib/django/db/models/functions/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/functions
copying build/lib/django/db/models/functions/comparison.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/functions
copying build/lib/django/db/models/functions/datetime.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/functions
copying build/lib/django/db/models/functions/math.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/functions
copying build/lib/django/db/models/functions/mixins.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/functions
copying build/lib/django/db/models/functions/text.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/functions
copying build/lib/django/db/models/functions/window.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/functions
creating build/bdist.netbsd-9.0-i386/wheel/django/db/models/sql
copying build/lib/django/db/models/sql/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/sql
copying build/lib/django/db/models/sql/compiler.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/sql
copying build/lib/django/db/models/sql/constants.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/sql
copying build/lib/django/db/models/sql/datastructures.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/sql
copying build/lib/django/db/models/sql/query.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/sql
copying build/lib/django/db/models/sql/subqueries.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/sql
copying build/lib/django/db/models/sql/where.py -> build/bdist.netbsd-9.0-i386/wheel/./django/db/models/sql
creating build/bdist.netbsd-9.0-i386/wheel/django/dispatch
copying build/lib/django/dispatch/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/dispatch
copying build/lib/django/dispatch/dispatcher.py -> build/bdist.netbsd-9.0-i386/wheel/./django/dispatch
copying build/lib/django/dispatch/license.txt -> build/bdist.netbsd-9.0-i386/wheel/./django/dispatch
creating build/bdist.netbsd-9.0-i386/wheel/django/forms
copying build/lib/django/forms/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/forms
copying build/lib/django/forms/boundfield.py -> build/bdist.netbsd-9.0-i386/wheel/./django/forms
copying build/lib/django/forms/fields.py -> build/bdist.netbsd-9.0-i386/wheel/./django/forms
copying build/lib/django/forms/forms.py -> build/bdist.netbsd-9.0-i386/wheel/./django/forms
copying build/lib/django/forms/formsets.py -> build/bdist.netbsd-9.0-i386/wheel/./django/forms
copying build/lib/django/forms/models.py -> build/bdist.netbsd-9.0-i386/wheel/./django/forms
copying build/lib/django/forms/renderers.py -> build/bdist.netbsd-9.0-i386/wheel/./django/forms
copying build/lib/django/forms/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/forms
copying build/lib/django/forms/widgets.py -> build/bdist.netbsd-9.0-i386/wheel/./django/forms
creating build/bdist.netbsd-9.0-i386/wheel/django/forms/jinja2
creating build/bdist.netbsd-9.0-i386/wheel/django/forms/jinja2/django
creating build/bdist.netbsd-9.0-i386/wheel/django/forms/jinja2/django/forms
creating build/bdist.netbsd-9.0-i386/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/attrs.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox_option.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox_select.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/clearable_file_input.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/date.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/datetime.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/email.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/file.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/hidden.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/input.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/input_option.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/multiple_hidden.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/multiple_input.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/multiwidget.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/number.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/password.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/radio.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/radio_option.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/select.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/select_date.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/select_option.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/splitdatetime.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/splithiddendatetime.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/text.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/textarea.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/time.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/url.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/jinja2/django/forms/widgets
creating build/bdist.netbsd-9.0-i386/wheel/django/forms/templates
creating build/bdist.netbsd-9.0-i386/wheel/django/forms/templates/django
creating build/bdist.netbsd-9.0-i386/wheel/django/forms/templates/django/forms
creating build/bdist.netbsd-9.0-i386/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/attrs.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/checkbox.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/checkbox_option.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/checkbox_select.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/clearable_file_input.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/date.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/datetime.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/email.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/file.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/hidden.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/input.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/input_option.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/multiple_hidden.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/multiple_input.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/multiwidget.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/number.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/password.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/radio.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/radio_option.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/select.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/select_date.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/select_option.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/splitdatetime.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/splithiddendatetime.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/text.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/textarea.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/time.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/url.html -> build/bdist.netbsd-9.0-i386/wheel/./django/forms/templates/django/forms/widgets
creating build/bdist.netbsd-9.0-i386/wheel/django/http
copying build/lib/django/http/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/http
copying build/lib/django/http/cookie.py -> build/bdist.netbsd-9.0-i386/wheel/./django/http
copying build/lib/django/http/multipartparser.py -> build/bdist.netbsd-9.0-i386/wheel/./django/http
copying build/lib/django/http/request.py -> build/bdist.netbsd-9.0-i386/wheel/./django/http
copying build/lib/django/http/response.py -> build/bdist.netbsd-9.0-i386/wheel/./django/http
creating build/bdist.netbsd-9.0-i386/wheel/django/middleware
copying build/lib/django/middleware/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/middleware
copying build/lib/django/middleware/cache.py -> build/bdist.netbsd-9.0-i386/wheel/./django/middleware
copying build/lib/django/middleware/clickjacking.py -> build/bdist.netbsd-9.0-i386/wheel/./django/middleware
copying build/lib/django/middleware/common.py -> build/bdist.netbsd-9.0-i386/wheel/./django/middleware
copying build/lib/django/middleware/csrf.py -> build/bdist.netbsd-9.0-i386/wheel/./django/middleware
copying build/lib/django/middleware/gzip.py -> build/bdist.netbsd-9.0-i386/wheel/./django/middleware
copying build/lib/django/middleware/http.py -> build/bdist.netbsd-9.0-i386/wheel/./django/middleware
copying build/lib/django/middleware/locale.py -> build/bdist.netbsd-9.0-i386/wheel/./django/middleware
copying build/lib/django/middleware/security.py -> build/bdist.netbsd-9.0-i386/wheel/./django/middleware
creating build/bdist.netbsd-9.0-i386/wheel/django/template
copying build/lib/django/template/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template
copying build/lib/django/template/autoreload.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template
copying build/lib/django/template/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template
copying build/lib/django/template/context.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template
copying build/lib/django/template/context_processors.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template
copying build/lib/django/template/defaultfilters.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template
copying build/lib/django/template/defaulttags.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template
copying build/lib/django/template/engine.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template
copying build/lib/django/template/exceptions.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template
copying build/lib/django/template/library.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template
copying build/lib/django/template/loader.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template
copying build/lib/django/template/loader_tags.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template
copying build/lib/django/template/response.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template
copying build/lib/django/template/smartif.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template
copying build/lib/django/template/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template
creating build/bdist.netbsd-9.0-i386/wheel/django/template/backends
copying build/lib/django/template/backends/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template/backends
copying build/lib/django/template/backends/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template/backends
copying build/lib/django/template/backends/django.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template/backends
copying build/lib/django/template/backends/dummy.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template/backends
copying build/lib/django/template/backends/jinja2.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template/backends
copying build/lib/django/template/backends/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template/backends
creating build/bdist.netbsd-9.0-i386/wheel/django/template/loaders
copying build/lib/django/template/loaders/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template/loaders
copying build/lib/django/template/loaders/app_directories.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template/loaders
copying build/lib/django/template/loaders/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template/loaders
copying build/lib/django/template/loaders/cached.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template/loaders
copying build/lib/django/template/loaders/filesystem.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template/loaders
copying build/lib/django/template/loaders/locmem.py -> build/bdist.netbsd-9.0-i386/wheel/./django/template/loaders
creating build/bdist.netbsd-9.0-i386/wheel/django/templatetags
copying build/lib/django/templatetags/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/templatetags
copying build/lib/django/templatetags/cache.py -> build/bdist.netbsd-9.0-i386/wheel/./django/templatetags
copying build/lib/django/templatetags/i18n.py -> build/bdist.netbsd-9.0-i386/wheel/./django/templatetags
copying build/lib/django/templatetags/l10n.py -> build/bdist.netbsd-9.0-i386/wheel/./django/templatetags
copying build/lib/django/templatetags/static.py -> build/bdist.netbsd-9.0-i386/wheel/./django/templatetags
copying build/lib/django/templatetags/tz.py -> build/bdist.netbsd-9.0-i386/wheel/./django/templatetags
creating build/bdist.netbsd-9.0-i386/wheel/django/test
copying build/lib/django/test/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/test
copying build/lib/django/test/client.py -> build/bdist.netbsd-9.0-i386/wheel/./django/test
copying build/lib/django/test/html.py -> build/bdist.netbsd-9.0-i386/wheel/./django/test
copying build/lib/django/test/runner.py -> build/bdist.netbsd-9.0-i386/wheel/./django/test
copying build/lib/django/test/selenium.py -> build/bdist.netbsd-9.0-i386/wheel/./django/test
copying build/lib/django/test/signals.py -> build/bdist.netbsd-9.0-i386/wheel/./django/test
copying build/lib/django/test/testcases.py -> build/bdist.netbsd-9.0-i386/wheel/./django/test
copying build/lib/django/test/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/test
creating build/bdist.netbsd-9.0-i386/wheel/django/urls
copying build/lib/django/urls/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/urls
copying build/lib/django/urls/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/urls
copying build/lib/django/urls/conf.py -> build/bdist.netbsd-9.0-i386/wheel/./django/urls
copying build/lib/django/urls/converters.py -> build/bdist.netbsd-9.0-i386/wheel/./django/urls
copying build/lib/django/urls/exceptions.py -> build/bdist.netbsd-9.0-i386/wheel/./django/urls
copying build/lib/django/urls/resolvers.py -> build/bdist.netbsd-9.0-i386/wheel/./django/urls
copying build/lib/django/urls/utils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/urls
creating build/bdist.netbsd-9.0-i386/wheel/django/utils
copying build/lib/django/utils/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/_os.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/archive.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/asyncio.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/autoreload.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/baseconv.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/cache.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/connection.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/crypto.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/datastructures.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/dateformat.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/dateparse.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/dates.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/datetime_safe.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/deconstruct.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/decorators.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/deprecation.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/duration.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/encoding.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/feedgenerator.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/formats.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/functional.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/hashable.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/html.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/http.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/inspect.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/ipv6.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/itercompat.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/jslex.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/log.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/lorem_ipsum.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/module_loading.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/numberformat.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/regex_helper.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/safestring.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/termcolors.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/text.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/timesince.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/timezone.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/topological_sort.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/tree.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/version.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
copying build/lib/django/utils/xmlutils.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils
creating build/bdist.netbsd-9.0-i386/wheel/django/utils/translation
copying build/lib/django/utils/translation/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils/translation
copying build/lib/django/utils/translation/reloader.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils/translation
copying build/lib/django/utils/translation/template.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils/translation
copying build/lib/django/utils/translation/trans_null.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils/translation
copying build/lib/django/utils/translation/trans_real.py -> build/bdist.netbsd-9.0-i386/wheel/./django/utils/translation
creating build/bdist.netbsd-9.0-i386/wheel/django/views
copying build/lib/django/views/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views
copying build/lib/django/views/csrf.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views
copying build/lib/django/views/debug.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views
copying build/lib/django/views/defaults.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views
copying build/lib/django/views/i18n.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views
copying build/lib/django/views/static.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views
creating build/bdist.netbsd-9.0-i386/wheel/django/views/decorators
copying build/lib/django/views/decorators/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views/decorators
copying build/lib/django/views/decorators/cache.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views/decorators
copying build/lib/django/views/decorators/clickjacking.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views/decorators
copying build/lib/django/views/decorators/common.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views/decorators
copying build/lib/django/views/decorators/csrf.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views/decorators
copying build/lib/django/views/decorators/debug.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views/decorators
copying build/lib/django/views/decorators/gzip.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views/decorators
copying build/lib/django/views/decorators/http.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views/decorators
copying build/lib/django/views/decorators/vary.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views/decorators
creating build/bdist.netbsd-9.0-i386/wheel/django/views/generic
copying build/lib/django/views/generic/__init__.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views/generic
copying build/lib/django/views/generic/base.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views/generic
copying build/lib/django/views/generic/dates.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views/generic
copying build/lib/django/views/generic/detail.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views/generic
copying build/lib/django/views/generic/edit.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views/generic
copying build/lib/django/views/generic/list.py -> build/bdist.netbsd-9.0-i386/wheel/./django/views/generic
creating build/bdist.netbsd-9.0-i386/wheel/django/views/templates
copying build/lib/django/views/templates/default_urlconf.html -> build/bdist.netbsd-9.0-i386/wheel/./django/views/templates
copying build/lib/django/views/templates/technical_404.html -> build/bdist.netbsd-9.0-i386/wheel/./django/views/templates
copying build/lib/django/views/templates/technical_500.html -> build/bdist.netbsd-9.0-i386/wheel/./django/views/templates
copying build/lib/django/views/templates/technical_500.txt -> build/bdist.netbsd-9.0-i386/wheel/./django/views/templates
creating build/bdist.netbsd-9.0-i386/wheel/django/bin
copying build/lib/django/bin/django-admin.py -> build/bdist.netbsd-9.0-i386/wheel/./django/bin
running install_egg_info
Copying Django.egg-info to build/bdist.netbsd-9.0-i386/wheel/./Django-3.2.25-py3.10.egg-info
running install_scripts
creating build/bdist.netbsd-9.0-i386/wheel/Django-3.2.25.data
creating build/bdist.netbsd-9.0-i386/wheel/Django-3.2.25.data/scripts
copying build/scripts-3.10/django-admin.py -> build/bdist.netbsd-9.0-i386/wheel/Django-3.2.25.data/scripts
changing mode of build/bdist.netbsd-9.0-i386/wheel/Django-3.2.25.data/scripts/django-admin.py to 755
creating build/bdist.netbsd-9.0-i386/wheel/Django-3.2.25.dist-info/WHEEL
creating '/pbulk/work/www/py-django3/work/Django-3.2.25/dist/.tmp-g0fnaljo/Django-3.2.25-py3-none-any.whl' and adding 'build/bdist.netbsd-9.0-i386/wheel' to it
adding 'Django-3.2.25.data/scripts/django-admin.py'
adding 'django/__init__.py'
adding 'django/__main__.py'
adding 'django/shortcuts.py'
adding 'django/apps/__init__.py'
adding 'django/apps/config.py'
adding 'django/apps/registry.py'
adding 'django/bin/django-admin.py'
adding 'django/conf/__init__.py'
adding 'django/conf/global_settings.py'
adding 'django/conf/app_template/__init__.py-tpl'
adding 'django/conf/app_template/admin.py-tpl'
adding 'django/conf/app_template/apps.py-tpl'
adding 'django/conf/app_template/models.py-tpl'
adding 'django/conf/app_template/tests.py-tpl'
adding 'django/conf/app_template/views.py-tpl'
adding 'django/conf/app_template/migrations/__init__.py-tpl'
adding 'django/conf/locale/__init__.py'
adding 'django/conf/locale/af/LC_MESSAGES/django.mo'
adding 'django/conf/locale/af/LC_MESSAGES/django.po'
adding 'django/conf/locale/ar/__init__.py'
adding 'django/conf/locale/ar/formats.py'
adding 'django/conf/locale/ar/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ar/LC_MESSAGES/django.po'
adding 'django/conf/locale/ar_DZ/__init__.py'
adding 'django/conf/locale/ar_DZ/formats.py'
adding 'django/conf/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/conf/locale/ast/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ast/LC_MESSAGES/django.po'
adding 'django/conf/locale/az/__init__.py'
adding 'django/conf/locale/az/formats.py'
adding 'django/conf/locale/az/LC_MESSAGES/django.mo'
adding 'django/conf/locale/az/LC_MESSAGES/django.po'
adding 'django/conf/locale/be/LC_MESSAGES/django.mo'
adding 'django/conf/locale/be/LC_MESSAGES/django.po'
adding 'django/conf/locale/bg/__init__.py'
adding 'django/conf/locale/bg/formats.py'
adding 'django/conf/locale/bg/LC_MESSAGES/django.mo'
adding 'django/conf/locale/bg/LC_MESSAGES/django.po'
adding 'django/conf/locale/bn/__init__.py'
adding 'django/conf/locale/bn/formats.py'
adding 'django/conf/locale/bn/LC_MESSAGES/django.mo'
adding 'django/conf/locale/bn/LC_MESSAGES/django.po'
adding 'django/conf/locale/br/LC_MESSAGES/django.mo'
adding 'django/conf/locale/br/LC_MESSAGES/django.po'
adding 'django/conf/locale/bs/__init__.py'
adding 'django/conf/locale/bs/formats.py'
adding 'django/conf/locale/bs/LC_MESSAGES/django.mo'
adding 'django/conf/locale/bs/LC_MESSAGES/django.po'
adding 'django/conf/locale/ca/__init__.py'
adding 'django/conf/locale/ca/formats.py'
adding 'django/conf/locale/ca/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ca/LC_MESSAGES/django.po'
adding 'django/conf/locale/cs/__init__.py'
adding 'django/conf/locale/cs/formats.py'
adding 'django/conf/locale/cs/LC_MESSAGES/django.mo'
adding 'django/conf/locale/cs/LC_MESSAGES/django.po'
adding 'django/conf/locale/cy/__init__.py'
adding 'django/conf/locale/cy/formats.py'
adding 'django/conf/locale/cy/LC_MESSAGES/django.mo'
adding 'django/conf/locale/cy/LC_MESSAGES/django.po'
adding 'django/conf/locale/da/__init__.py'
adding 'django/conf/locale/da/formats.py'
adding 'django/conf/locale/da/LC_MESSAGES/django.mo'
adding 'django/conf/locale/da/LC_MESSAGES/django.po'
adding 'django/conf/locale/de/__init__.py'
adding 'django/conf/locale/de/formats.py'
adding 'django/conf/locale/de/LC_MESSAGES/django.mo'
adding 'django/conf/locale/de/LC_MESSAGES/django.po'
adding 'django/conf/locale/de_CH/__init__.py'
adding 'django/conf/locale/de_CH/formats.py'
adding 'django/conf/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/conf/locale/dsb/LC_MESSAGES/django.po'
adding 'django/conf/locale/el/__init__.py'
adding 'django/conf/locale/el/formats.py'
adding 'django/conf/locale/el/LC_MESSAGES/django.mo'
adding 'django/conf/locale/el/LC_MESSAGES/django.po'
adding 'django/conf/locale/en/__init__.py'
adding 'django/conf/locale/en/formats.py'
adding 'django/conf/locale/en/LC_MESSAGES/django.mo'
adding 'django/conf/locale/en/LC_MESSAGES/django.po'
adding 'django/conf/locale/en_AU/__init__.py'
adding 'django/conf/locale/en_AU/formats.py'
adding 'django/conf/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/conf/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/conf/locale/en_GB/__init__.py'
adding 'django/conf/locale/en_GB/formats.py'
adding 'django/conf/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/conf/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/conf/locale/eo/__init__.py'
adding 'django/conf/locale/eo/formats.py'
adding 'django/conf/locale/eo/LC_MESSAGES/django.mo'
adding 'django/conf/locale/eo/LC_MESSAGES/django.po'
adding 'django/conf/locale/es/__init__.py'
adding 'django/conf/locale/es/formats.py'
adding 'django/conf/locale/es/LC_MESSAGES/django.mo'
adding 'django/conf/locale/es/LC_MESSAGES/django.po'
adding 'django/conf/locale/es_AR/__init__.py'
adding 'django/conf/locale/es_AR/formats.py'
adding 'django/conf/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/conf/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/conf/locale/es_CO/__init__.py'
adding 'django/conf/locale/es_CO/formats.py'
adding 'django/conf/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/conf/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/conf/locale/es_MX/__init__.py'
adding 'django/conf/locale/es_MX/formats.py'
adding 'django/conf/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/conf/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/conf/locale/es_NI/__init__.py'
adding 'django/conf/locale/es_NI/formats.py'
adding 'django/conf/locale/es_PR/__init__.py'
adding 'django/conf/locale/es_PR/formats.py'
adding 'django/conf/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/conf/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/conf/locale/et/__init__.py'
adding 'django/conf/locale/et/formats.py'
adding 'django/conf/locale/et/LC_MESSAGES/django.mo'
adding 'django/conf/locale/et/LC_MESSAGES/django.po'
adding 'django/conf/locale/eu/__init__.py'
adding 'django/conf/locale/eu/formats.py'
adding 'django/conf/locale/eu/LC_MESSAGES/django.mo'
adding 'django/conf/locale/eu/LC_MESSAGES/django.po'
adding 'django/conf/locale/fa/__init__.py'
adding 'django/conf/locale/fa/formats.py'
adding 'django/conf/locale/fa/LC_MESSAGES/django.mo'
adding 'django/conf/locale/fa/LC_MESSAGES/django.po'
adding 'django/conf/locale/fi/__init__.py'
adding 'django/conf/locale/fi/formats.py'
adding 'django/conf/locale/fi/LC_MESSAGES/django.mo'
adding 'django/conf/locale/fi/LC_MESSAGES/django.po'
adding 'django/conf/locale/fr/__init__.py'
adding 'django/conf/locale/fr/formats.py'
adding 'django/conf/locale/fr/LC_MESSAGES/django.mo'
adding 'django/conf/locale/fr/LC_MESSAGES/django.po'
adding 'django/conf/locale/fy/__init__.py'
adding 'django/conf/locale/fy/formats.py'
adding 'django/conf/locale/fy/LC_MESSAGES/django.mo'
adding 'django/conf/locale/fy/LC_MESSAGES/django.po'
adding 'django/conf/locale/ga/__init__.py'
adding 'django/conf/locale/ga/formats.py'
adding 'django/conf/locale/ga/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ga/LC_MESSAGES/django.po'
adding 'django/conf/locale/gd/__init__.py'
adding 'django/conf/locale/gd/formats.py'
adding 'django/conf/locale/gd/LC_MESSAGES/django.mo'
adding 'django/conf/locale/gd/LC_MESSAGES/django.po'
adding 'django/conf/locale/gl/__init__.py'
adding 'django/conf/locale/gl/formats.py'
adding 'django/conf/locale/gl/LC_MESSAGES/django.mo'
adding 'django/conf/locale/gl/LC_MESSAGES/django.po'
adding 'django/conf/locale/he/__init__.py'
adding 'django/conf/locale/he/formats.py'
adding 'django/conf/locale/he/LC_MESSAGES/django.mo'
adding 'django/conf/locale/he/LC_MESSAGES/django.po'
adding 'django/conf/locale/hi/__init__.py'
adding 'django/conf/locale/hi/formats.py'
adding 'django/conf/locale/hi/LC_MESSAGES/django.mo'
adding 'django/conf/locale/hi/LC_MESSAGES/django.po'
adding 'django/conf/locale/hr/__init__.py'
adding 'django/conf/locale/hr/formats.py'
adding 'django/conf/locale/hr/LC_MESSAGES/django.mo'
adding 'django/conf/locale/hr/LC_MESSAGES/django.po'
adding 'django/conf/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/conf/locale/hsb/LC_MESSAGES/django.po'
adding 'django/conf/locale/hu/__init__.py'
adding 'django/conf/locale/hu/formats.py'
adding 'django/conf/locale/hu/LC_MESSAGES/django.mo'
adding 'django/conf/locale/hu/LC_MESSAGES/django.po'
adding 'django/conf/locale/hy/LC_MESSAGES/django.mo'
adding 'django/conf/locale/hy/LC_MESSAGES/django.po'
adding 'django/conf/locale/ia/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ia/LC_MESSAGES/django.po'
adding 'django/conf/locale/id/__init__.py'
adding 'django/conf/locale/id/formats.py'
adding 'django/conf/locale/id/LC_MESSAGES/django.mo'
adding 'django/conf/locale/id/LC_MESSAGES/django.po'
adding 'django/conf/locale/ig/__init__.py'
adding 'django/conf/locale/ig/formats.py'
adding 'django/conf/locale/ig/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ig/LC_MESSAGES/django.po'
adding 'django/conf/locale/io/LC_MESSAGES/django.mo'
adding 'django/conf/locale/io/LC_MESSAGES/django.po'
adding 'django/conf/locale/is/__init__.py'
adding 'django/conf/locale/is/formats.py'
adding 'django/conf/locale/is/LC_MESSAGES/django.mo'
adding 'django/conf/locale/is/LC_MESSAGES/django.po'
adding 'django/conf/locale/it/__init__.py'
adding 'django/conf/locale/it/formats.py'
adding 'django/conf/locale/it/LC_MESSAGES/django.mo'
adding 'django/conf/locale/it/LC_MESSAGES/django.po'
adding 'django/conf/locale/ja/__init__.py'
adding 'django/conf/locale/ja/formats.py'
adding 'django/conf/locale/ja/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ja/LC_MESSAGES/django.po'
adding 'django/conf/locale/ka/__init__.py'
adding 'django/conf/locale/ka/formats.py'
adding 'django/conf/locale/ka/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ka/LC_MESSAGES/django.po'
adding 'django/conf/locale/kab/LC_MESSAGES/django.mo'
adding 'django/conf/locale/kab/LC_MESSAGES/django.po'
adding 'django/conf/locale/kk/LC_MESSAGES/django.mo'
adding 'django/conf/locale/kk/LC_MESSAGES/django.po'
adding 'django/conf/locale/km/__init__.py'
adding 'django/conf/locale/km/formats.py'
adding 'django/conf/locale/km/LC_MESSAGES/django.mo'
adding 'django/conf/locale/km/LC_MESSAGES/django.po'
adding 'django/conf/locale/kn/__init__.py'
adding 'django/conf/locale/kn/formats.py'
adding 'django/conf/locale/kn/LC_MESSAGES/django.mo'
adding 'django/conf/locale/kn/LC_MESSAGES/django.po'
adding 'django/conf/locale/ko/__init__.py'
adding 'django/conf/locale/ko/formats.py'
adding 'django/conf/locale/ko/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ko/LC_MESSAGES/django.po'
adding 'django/conf/locale/ky/__init__.py'
adding 'django/conf/locale/ky/formats.py'
adding 'django/conf/locale/ky/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ky/LC_MESSAGES/django.po'
adding 'django/conf/locale/lb/LC_MESSAGES/django.mo'
adding 'django/conf/locale/lb/LC_MESSAGES/django.po'
adding 'django/conf/locale/lt/__init__.py'
adding 'django/conf/locale/lt/formats.py'
adding 'django/conf/locale/lt/LC_MESSAGES/django.mo'
adding 'django/conf/locale/lt/LC_MESSAGES/django.po'
adding 'django/conf/locale/lv/__init__.py'
adding 'django/conf/locale/lv/formats.py'
adding 'django/conf/locale/lv/LC_MESSAGES/django.mo'
adding 'django/conf/locale/lv/LC_MESSAGES/django.po'
adding 'django/conf/locale/mk/__init__.py'
adding 'django/conf/locale/mk/formats.py'
adding 'django/conf/locale/mk/LC_MESSAGES/django.mo'
adding 'django/conf/locale/mk/LC_MESSAGES/django.po'
adding 'django/conf/locale/ml/__init__.py'
adding 'django/conf/locale/ml/formats.py'
adding 'django/conf/locale/ml/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ml/LC_MESSAGES/django.po'
adding 'django/conf/locale/mn/__init__.py'
adding 'django/conf/locale/mn/formats.py'
adding 'django/conf/locale/mn/LC_MESSAGES/django.mo'
adding 'django/conf/locale/mn/LC_MESSAGES/django.po'
adding 'django/conf/locale/mr/LC_MESSAGES/django.mo'
adding 'django/conf/locale/mr/LC_MESSAGES/django.po'
adding 'django/conf/locale/my/LC_MESSAGES/django.mo'
adding 'django/conf/locale/my/LC_MESSAGES/django.po'
adding 'django/conf/locale/nb/__init__.py'
adding 'django/conf/locale/nb/formats.py'
adding 'django/conf/locale/nb/LC_MESSAGES/django.mo'
adding 'django/conf/locale/nb/LC_MESSAGES/django.po'
adding 'django/conf/locale/ne/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ne/LC_MESSAGES/django.po'
adding 'django/conf/locale/nl/__init__.py'
adding 'django/conf/locale/nl/formats.py'
adding 'django/conf/locale/nl/LC_MESSAGES/django.mo'
adding 'django/conf/locale/nl/LC_MESSAGES/django.po'
adding 'django/conf/locale/nn/__init__.py'
adding 'django/conf/locale/nn/formats.py'
adding 'django/conf/locale/nn/LC_MESSAGES/django.mo'
adding 'django/conf/locale/nn/LC_MESSAGES/django.po'
adding 'django/conf/locale/os/LC_MESSAGES/django.mo'
adding 'django/conf/locale/os/LC_MESSAGES/django.po'
adding 'django/conf/locale/pa/LC_MESSAGES/django.mo'
adding 'django/conf/locale/pa/LC_MESSAGES/django.po'
adding 'django/conf/locale/pl/__init__.py'
adding 'django/conf/locale/pl/formats.py'
adding 'django/conf/locale/pl/LC_MESSAGES/django.mo'
adding 'django/conf/locale/pl/LC_MESSAGES/django.po'
adding 'django/conf/locale/pt/__init__.py'
adding 'django/conf/locale/pt/formats.py'
adding 'django/conf/locale/pt/LC_MESSAGES/django.mo'
adding 'django/conf/locale/pt/LC_MESSAGES/django.po'
adding 'django/conf/locale/pt_BR/__init__.py'
adding 'django/conf/locale/pt_BR/formats.py'
adding 'django/conf/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/conf/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/conf/locale/ro/__init__.py'
adding 'django/conf/locale/ro/formats.py'
adding 'django/conf/locale/ro/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ro/LC_MESSAGES/django.po'
adding 'django/conf/locale/ru/__init__.py'
adding 'django/conf/locale/ru/formats.py'
adding 'django/conf/locale/ru/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ru/LC_MESSAGES/django.po'
adding 'django/conf/locale/sk/__init__.py'
adding 'django/conf/locale/sk/formats.py'
adding 'django/conf/locale/sk/LC_MESSAGES/django.mo'
adding 'django/conf/locale/sk/LC_MESSAGES/django.po'
adding 'django/conf/locale/sl/__init__.py'
adding 'django/conf/locale/sl/formats.py'
adding 'django/conf/locale/sl/LC_MESSAGES/django.mo'
adding 'django/conf/locale/sl/LC_MESSAGES/django.po'
adding 'django/conf/locale/sq/__init__.py'
adding 'django/conf/locale/sq/formats.py'
adding 'django/conf/locale/sq/LC_MESSAGES/django.mo'
adding 'django/conf/locale/sq/LC_MESSAGES/django.po'
adding 'django/conf/locale/sr/__init__.py'
adding 'django/conf/locale/sr/formats.py'
adding 'django/conf/locale/sr/LC_MESSAGES/django.mo'
adding 'django/conf/locale/sr/LC_MESSAGES/django.po'
adding 'django/conf/locale/sr_Latn/__init__.py'
adding 'django/conf/locale/sr_Latn/formats.py'
adding 'django/conf/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/conf/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/conf/locale/sv/__init__.py'
adding 'django/conf/locale/sv/formats.py'
adding 'django/conf/locale/sv/LC_MESSAGES/django.mo'
adding 'django/conf/locale/sv/LC_MESSAGES/django.po'
adding 'django/conf/locale/sw/LC_MESSAGES/django.mo'
adding 'django/conf/locale/sw/LC_MESSAGES/django.po'
adding 'django/conf/locale/ta/__init__.py'
adding 'django/conf/locale/ta/formats.py'
adding 'django/conf/locale/ta/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ta/LC_MESSAGES/django.po'
adding 'django/conf/locale/te/__init__.py'
adding 'django/conf/locale/te/formats.py'
adding 'django/conf/locale/te/LC_MESSAGES/django.mo'
adding 'django/conf/locale/te/LC_MESSAGES/django.po'
adding 'django/conf/locale/tg/__init__.py'
adding 'django/conf/locale/tg/formats.py'
adding 'django/conf/locale/tg/LC_MESSAGES/django.mo'
adding 'django/conf/locale/tg/LC_MESSAGES/django.po'
adding 'django/conf/locale/th/__init__.py'
adding 'django/conf/locale/th/formats.py'
adding 'django/conf/locale/th/LC_MESSAGES/django.mo'
adding 'django/conf/locale/th/LC_MESSAGES/django.po'
adding 'django/conf/locale/tk/__init__.py'
adding 'django/conf/locale/tk/formats.py'
adding 'django/conf/locale/tk/LC_MESSAGES/django.mo'
adding 'django/conf/locale/tk/LC_MESSAGES/django.po'
adding 'django/conf/locale/tr/__init__.py'
adding 'django/conf/locale/tr/formats.py'
adding 'django/conf/locale/tr/LC_MESSAGES/django.mo'
adding 'django/conf/locale/tr/LC_MESSAGES/django.po'
adding 'django/conf/locale/tt/LC_MESSAGES/django.mo'
adding 'django/conf/locale/tt/LC_MESSAGES/django.po'
adding 'django/conf/locale/udm/LC_MESSAGES/django.mo'
adding 'django/conf/locale/udm/LC_MESSAGES/django.po'
adding 'django/conf/locale/uk/__init__.py'
adding 'django/conf/locale/uk/formats.py'
adding 'django/conf/locale/uk/LC_MESSAGES/django.mo'
adding 'django/conf/locale/uk/LC_MESSAGES/django.po'
adding 'django/conf/locale/ur/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ur/LC_MESSAGES/django.po'
adding 'django/conf/locale/uz/__init__.py'
adding 'django/conf/locale/uz/formats.py'
adding 'django/conf/locale/uz/LC_MESSAGES/django.mo'
adding 'django/conf/locale/uz/LC_MESSAGES/django.po'
adding 'django/conf/locale/vi/__init__.py'
adding 'django/conf/locale/vi/formats.py'
adding 'django/conf/locale/vi/LC_MESSAGES/django.mo'
adding 'django/conf/locale/vi/LC_MESSAGES/django.po'
adding 'django/conf/locale/zh_Hans/__init__.py'
adding 'django/conf/locale/zh_Hans/formats.py'
adding 'django/conf/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/conf/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/conf/locale/zh_Hant/__init__.py'
adding 'django/conf/locale/zh_Hant/formats.py'
adding 'django/conf/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/conf/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/conf/project_template/manage.py-tpl'
adding 'django/conf/project_template/project_name/__init__.py-tpl'
adding 'django/conf/project_template/project_name/asgi.py-tpl'
adding 'django/conf/project_template/project_name/settings.py-tpl'
adding 'django/conf/project_template/project_name/urls.py-tpl'
adding 'django/conf/project_template/project_name/wsgi.py-tpl'
adding 'django/conf/urls/__init__.py'
adding 'django/conf/urls/i18n.py'
adding 'django/conf/urls/static.py'
adding 'django/contrib/__init__.py'
adding 'django/contrib/admin/__init__.py'
adding 'django/contrib/admin/actions.py'
adding 'django/contrib/admin/apps.py'
adding 'django/contrib/admin/checks.py'
adding 'django/contrib/admin/decorators.py'
adding 'django/contrib/admin/exceptions.py'
adding 'django/contrib/admin/filters.py'
adding 'django/contrib/admin/forms.py'
adding 'django/contrib/admin/helpers.py'
adding 'django/contrib/admin/models.py'
adding 'django/contrib/admin/options.py'
adding 'django/contrib/admin/sites.py'
adding 'django/contrib/admin/tests.py'
adding 'django/contrib/admin/utils.py'
adding 'django/contrib/admin/widgets.py'
adding 'django/contrib/admin/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/am/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/am/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/kab/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/kab/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/uz/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/uz/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/migrations/0001_initial.py'
adding 'django/contrib/admin/migrations/0002_logentry_remove_auto_add.py'
adding 'django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py'
adding 'django/contrib/admin/migrations/__init__.py'
adding 'django/contrib/admin/static/admin/css/autocomplete.css'
adding 'django/contrib/admin/static/admin/css/base.css'
adding 'django/contrib/admin/static/admin/css/changelists.css'
adding 'django/contrib/admin/static/admin/css/dashboard.css'
adding 'django/contrib/admin/static/admin/css/fonts.css'
adding 'django/contrib/admin/static/admin/css/forms.css'
adding 'django/contrib/admin/static/admin/css/login.css'
adding 'django/contrib/admin/static/admin/css/nav_sidebar.css'
adding 'django/contrib/admin/static/admin/css/responsive.css'
adding 'django/contrib/admin/static/admin/css/responsive_rtl.css'
adding 'django/contrib/admin/static/admin/css/rtl.css'
adding 'django/contrib/admin/static/admin/css/widgets.css'
adding 'django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md'
adding 'django/contrib/admin/static/admin/css/vendor/select2/select2.css'
adding 'django/contrib/admin/static/admin/css/vendor/select2/select2.min.css'
adding 'django/contrib/admin/static/admin/fonts/LICENSE.txt'
adding 'django/contrib/admin/static/admin/fonts/README.txt'
adding 'django/contrib/admin/static/admin/fonts/Roboto-Bold-webfont.woff'
adding 'django/contrib/admin/static/admin/fonts/Roboto-Light-webfont.woff'
adding 'django/contrib/admin/static/admin/fonts/Roboto-Regular-webfont.woff'
adding 'django/contrib/admin/static/admin/img/LICENSE'
adding 'django/contrib/admin/static/admin/img/README.txt'
adding 'django/contrib/admin/static/admin/img/calendar-icons.svg'
adding 'django/contrib/admin/static/admin/img/icon-addlink.svg'
adding 'django/contrib/admin/static/admin/img/icon-alert.svg'
adding 'django/contrib/admin/static/admin/img/icon-calendar.svg'
adding 'django/contrib/admin/static/admin/img/icon-changelink.svg'
adding 'django/contrib/admin/static/admin/img/icon-clock.svg'
adding 'django/contrib/admin/static/admin/img/icon-deletelink.svg'
adding 'django/contrib/admin/static/admin/img/icon-no.svg'
adding 'django/contrib/admin/static/admin/img/icon-unknown-alt.svg'
adding 'django/contrib/admin/static/admin/img/icon-unknown.svg'
adding 'django/contrib/admin/static/admin/img/icon-viewlink.svg'
adding 'django/contrib/admin/static/admin/img/icon-yes.svg'
adding 'django/contrib/admin/static/admin/img/inline-delete.svg'
adding 'django/contrib/admin/static/admin/img/search.svg'
adding 'django/contrib/admin/static/admin/img/selector-icons.svg'
adding 'django/contrib/admin/static/admin/img/sorting-icons.svg'
adding 'django/contrib/admin/static/admin/img/tooltag-add.svg'
adding 'django/contrib/admin/static/admin/img/tooltag-arrowright.svg'
adding 'django/contrib/admin/static/admin/img/gis/move_vertex_off.svg'
adding 'django/contrib/admin/static/admin/img/gis/move_vertex_on.svg'
adding 'django/contrib/admin/static/admin/js/SelectBox.js'
adding 'django/contrib/admin/static/admin/js/SelectFilter2.js'
adding 'django/contrib/admin/static/admin/js/actions.js'
adding 'django/contrib/admin/static/admin/js/autocomplete.js'
adding 'django/contrib/admin/static/admin/js/calendar.js'
adding 'django/contrib/admin/static/admin/js/cancel.js'
adding 'django/contrib/admin/static/admin/js/change_form.js'
adding 'django/contrib/admin/static/admin/js/collapse.js'
adding 'django/contrib/admin/static/admin/js/core.js'
adding 'django/contrib/admin/static/admin/js/inlines.js'
adding 'django/contrib/admin/static/admin/js/jquery.init.js'
adding 'django/contrib/admin/static/admin/js/nav_sidebar.js'
adding 'django/contrib/admin/static/admin/js/popup_response.js'
adding 'django/contrib/admin/static/admin/js/prepopulate.js'
adding 'django/contrib/admin/static/admin/js/prepopulate_init.js'
adding 'django/contrib/admin/static/admin/js/urlify.js'
adding 'django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js'
adding 'django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js'
adding 'django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt'
adding 'django/contrib/admin/static/admin/js/vendor/jquery/jquery.js'
adding 'django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md'
adding 'django/contrib/admin/static/admin/js/vendor/select2/select2.full.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js'
adding 'django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt'
adding 'django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js'
adding 'django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js'
adding 'django/contrib/admin/templates/admin/404.html'
adding 'django/contrib/admin/templates/admin/500.html'
adding 'django/contrib/admin/templates/admin/actions.html'
adding 'django/contrib/admin/templates/admin/app_index.html'
adding 'django/contrib/admin/templates/admin/app_list.html'
adding 'django/contrib/admin/templates/admin/base.html'
adding 'django/contrib/admin/templates/admin/base_site.html'
adding 'django/contrib/admin/templates/admin/change_form.html'
adding 'django/contrib/admin/templates/admin/change_form_object_tools.html'
adding 'django/contrib/admin/templates/admin/change_list.html'
adding 'django/contrib/admin/templates/admin/change_list_object_tools.html'
adding 'django/contrib/admin/templates/admin/change_list_results.html'
adding 'django/contrib/admin/templates/admin/date_hierarchy.html'
adding 'django/contrib/admin/templates/admin/delete_confirmation.html'
adding 'django/contrib/admin/templates/admin/delete_selected_confirmation.html'
adding 'django/contrib/admin/templates/admin/filter.html'
adding 'django/contrib/admin/templates/admin/index.html'
adding 'django/contrib/admin/templates/admin/invalid_setup.html'
adding 'django/contrib/admin/templates/admin/login.html'
adding 'django/contrib/admin/templates/admin/nav_sidebar.html'
adding 'django/contrib/admin/templates/admin/object_history.html'
adding 'django/contrib/admin/templates/admin/pagination.html'
adding 'django/contrib/admin/templates/admin/popup_response.html'
adding 'django/contrib/admin/templates/admin/prepopulated_fields_js.html'
adding 'django/contrib/admin/templates/admin/search_form.html'
adding 'django/contrib/admin/templates/admin/submit_line.html'
adding 'django/contrib/admin/templates/admin/auth/user/add_form.html'
adding 'django/contrib/admin/templates/admin/auth/user/change_password.html'
adding 'django/contrib/admin/templates/admin/edit_inline/stacked.html'
adding 'django/contrib/admin/templates/admin/edit_inline/tabular.html'
adding 'django/contrib/admin/templates/admin/includes/fieldset.html'
adding 'django/contrib/admin/templates/admin/includes/object_delete_summary.html'
adding 'django/contrib/admin/templates/admin/widgets/clearable_file_input.html'
adding 'django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html'
adding 'django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html'
adding 'django/contrib/admin/templates/admin/widgets/radio.html'
adding 'django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html'
adding 'django/contrib/admin/templates/admin/widgets/split_datetime.html'
adding 'django/contrib/admin/templates/admin/widgets/url.html'
adding 'django/contrib/admin/templates/registration/logged_out.html'
adding 'django/contrib/admin/templates/registration/password_change_done.html'
adding 'django/contrib/admin/templates/registration/password_change_form.html'
adding 'django/contrib/admin/templates/registration/password_reset_complete.html'
adding 'django/contrib/admin/templates/registration/password_reset_confirm.html'
adding 'django/contrib/admin/templates/registration/password_reset_done.html'
adding 'django/contrib/admin/templates/registration/password_reset_email.html'
adding 'django/contrib/admin/templates/registration/password_reset_form.html'
adding 'django/contrib/admin/templatetags/__init__.py'
adding 'django/contrib/admin/templatetags/admin_list.py'
adding 'django/contrib/admin/templatetags/admin_modify.py'
adding 'django/contrib/admin/templatetags/admin_urls.py'
adding 'django/contrib/admin/templatetags/base.py'
adding 'django/contrib/admin/templatetags/log.py'
adding 'django/contrib/admin/views/__init__.py'
adding 'django/contrib/admin/views/autocomplete.py'
adding 'django/contrib/admin/views/decorators.py'
adding 'django/contrib/admin/views/main.py'
adding 'django/contrib/admindocs/__init__.py'
adding 'django/contrib/admindocs/apps.py'
adding 'django/contrib/admindocs/middleware.py'
adding 'django/contrib/admindocs/urls.py'
adding 'django/contrib/admindocs/utils.py'
adding 'django/contrib/admindocs/views.py'
adding 'django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/templates/admin_doc/bookmarklets.html'
adding 'django/contrib/admindocs/templates/admin_doc/index.html'
adding 'django/contrib/admindocs/templates/admin_doc/missing_docutils.html'
adding 'django/contrib/admindocs/templates/admin_doc/model_detail.html'
adding 'django/contrib/admindocs/templates/admin_doc/model_index.html'
adding 'django/contrib/admindocs/templates/admin_doc/template_detail.html'
adding 'django/contrib/admindocs/templates/admin_doc/template_filter_index.html'
adding 'django/contrib/admindocs/templates/admin_doc/template_tag_index.html'
adding 'django/contrib/admindocs/templates/admin_doc/view_detail.html'
adding 'django/contrib/admindocs/templates/admin_doc/view_index.html'
adding 'django/contrib/auth/__init__.py'
adding 'django/contrib/auth/admin.py'
adding 'django/contrib/auth/apps.py'
adding 'django/contrib/auth/backends.py'
adding 'django/contrib/auth/base_user.py'
adding 'django/contrib/auth/checks.py'
adding 'django/contrib/auth/common-passwords.txt.gz'
adding 'django/contrib/auth/context_processors.py'
adding 'django/contrib/auth/decorators.py'
adding 'django/contrib/auth/forms.py'
adding 'django/contrib/auth/hashers.py'
adding 'django/contrib/auth/middleware.py'
adding 'django/contrib/auth/mixins.py'
adding 'django/contrib/auth/models.py'
adding 'django/contrib/auth/password_validation.py'
adding 'django/contrib/auth/signals.py'
adding 'django/contrib/auth/tokens.py'
adding 'django/contrib/auth/urls.py'
adding 'django/contrib/auth/validators.py'
adding 'django/contrib/auth/views.py'
adding 'django/contrib/auth/handlers/__init__.py'
adding 'django/contrib/auth/handlers/modwsgi.py'
adding 'django/contrib/auth/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/kab/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/kab/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/tk/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/tk/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/uz/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/uz/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/auth/management/__init__.py'
adding 'django/contrib/auth/management/commands/__init__.py'
adding 'django/contrib/auth/management/commands/changepassword.py'
adding 'django/contrib/auth/management/commands/createsuperuser.py'
adding 'django/contrib/auth/migrations/0001_initial.py'
adding 'django/contrib/auth/migrations/0002_alter_permission_name_max_length.py'
adding 'django/contrib/auth/migrations/0003_alter_user_email_max_length.py'
adding 'django/contrib/auth/migrations/0004_alter_user_username_opts.py'
adding 'django/contrib/auth/migrations/0005_alter_user_last_login_null.py'
adding 'django/contrib/auth/migrations/0006_require_contenttypes_0002.py'
adding 'django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py'
adding 'django/contrib/auth/migrations/0008_alter_user_username_max_length.py'
adding 'django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py'
adding 'django/contrib/auth/migrations/0010_alter_group_name_max_length.py'
adding 'django/contrib/auth/migrations/0011_update_proxy_permissions.py'
adding 'django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py'
adding 'django/contrib/auth/migrations/__init__.py'
adding 'django/contrib/auth/templates/auth/widgets/read_only_password_hash.html'
adding 'django/contrib/auth/templates/registration/password_reset_subject.txt'
adding 'django/contrib/contenttypes/__init__.py'
adding 'django/contrib/contenttypes/admin.py'
adding 'django/contrib/contenttypes/apps.py'
adding 'django/contrib/contenttypes/checks.py'
adding 'django/contrib/contenttypes/fields.py'
adding 'django/contrib/contenttypes/forms.py'
adding 'django/contrib/contenttypes/models.py'
adding 'django/contrib/contenttypes/views.py'
adding 'django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/management/__init__.py'
adding 'django/contrib/contenttypes/management/commands/__init__.py'
adding 'django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py'
adding 'django/contrib/contenttypes/migrations/0001_initial.py'
adding 'django/contrib/contenttypes/migrations/0002_remove_content_type_name.py'
adding 'django/contrib/contenttypes/migrations/__init__.py'
adding 'django/contrib/flatpages/__init__.py'
adding 'django/contrib/flatpages/admin.py'
adding 'django/contrib/flatpages/apps.py'
adding 'django/contrib/flatpages/forms.py'
adding 'django/contrib/flatpages/middleware.py'
adding 'django/contrib/flatpages/models.py'
adding 'django/contrib/flatpages/sitemaps.py'
adding 'django/contrib/flatpages/urls.py'
adding 'django/contrib/flatpages/views.py'
adding 'django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/migrations/0001_initial.py'
adding 'django/contrib/flatpages/migrations/__init__.py'
adding 'django/contrib/flatpages/templatetags/__init__.py'
adding 'django/contrib/flatpages/templatetags/flatpages.py'
adding 'django/contrib/gis/__init__.py'
adding 'django/contrib/gis/apps.py'
adding 'django/contrib/gis/feeds.py'
adding 'django/contrib/gis/geometry.py'
adding 'django/contrib/gis/measure.py'
adding 'django/contrib/gis/ptr.py'
adding 'django/contrib/gis/shortcuts.py'
adding 'django/contrib/gis/views.py'
adding 'django/contrib/gis/admin/__init__.py'
adding 'django/contrib/gis/admin/options.py'
adding 'django/contrib/gis/admin/widgets.py'
adding 'django/contrib/gis/db/__init__.py'
adding 'django/contrib/gis/db/backends/__init__.py'
adding 'django/contrib/gis/db/backends/utils.py'
adding 'django/contrib/gis/db/backends/base/__init__.py'
adding 'django/contrib/gis/db/backends/base/adapter.py'
adding 'django/contrib/gis/db/backends/base/features.py'
adding 'django/contrib/gis/db/backends/base/models.py'
adding 'django/contrib/gis/db/backends/base/operations.py'
adding 'django/contrib/gis/db/backends/mysql/__init__.py'
adding 'django/contrib/gis/db/backends/mysql/base.py'
adding 'django/contrib/gis/db/backends/mysql/features.py'
adding 'django/contrib/gis/db/backends/mysql/introspection.py'
adding 'django/contrib/gis/db/backends/mysql/operations.py'
adding 'django/contrib/gis/db/backends/mysql/schema.py'
adding 'django/contrib/gis/db/backends/oracle/__init__.py'
adding 'django/contrib/gis/db/backends/oracle/adapter.py'
adding 'django/contrib/gis/db/backends/oracle/base.py'
adding 'django/contrib/gis/db/backends/oracle/features.py'
adding 'django/contrib/gis/db/backends/oracle/introspection.py'
adding 'django/contrib/gis/db/backends/oracle/models.py'
adding 'django/contrib/gis/db/backends/oracle/operations.py'
adding 'django/contrib/gis/db/backends/oracle/schema.py'
adding 'django/contrib/gis/db/backends/postgis/__init__.py'
adding 'django/contrib/gis/db/backends/postgis/adapter.py'
adding 'django/contrib/gis/db/backends/postgis/base.py'
adding 'django/contrib/gis/db/backends/postgis/const.py'
adding 'django/contrib/gis/db/backends/postgis/features.py'
adding 'django/contrib/gis/db/backends/postgis/introspection.py'
adding 'django/contrib/gis/db/backends/postgis/models.py'
adding 'django/contrib/gis/db/backends/postgis/operations.py'
adding 'django/contrib/gis/db/backends/postgis/pgraster.py'
adding 'django/contrib/gis/db/backends/postgis/schema.py'
adding 'django/contrib/gis/db/backends/spatialite/__init__.py'
adding 'django/contrib/gis/db/backends/spatialite/adapter.py'
adding 'django/contrib/gis/db/backends/spatialite/base.py'
adding 'django/contrib/gis/db/backends/spatialite/client.py'
adding 'django/contrib/gis/db/backends/spatialite/features.py'
adding 'django/contrib/gis/db/backends/spatialite/introspection.py'
adding 'django/contrib/gis/db/backends/spatialite/models.py'
adding 'django/contrib/gis/db/backends/spatialite/operations.py'
adding 'django/contrib/gis/db/backends/spatialite/schema.py'
adding 'django/contrib/gis/db/models/__init__.py'
adding 'django/contrib/gis/db/models/aggregates.py'
adding 'django/contrib/gis/db/models/fields.py'
adding 'django/contrib/gis/db/models/functions.py'
adding 'django/contrib/gis/db/models/lookups.py'
adding 'django/contrib/gis/db/models/proxy.py'
adding 'django/contrib/gis/db/models/sql/__init__.py'
adding 'django/contrib/gis/db/models/sql/conversion.py'
adding 'django/contrib/gis/forms/__init__.py'
adding 'django/contrib/gis/forms/fields.py'
adding 'django/contrib/gis/forms/widgets.py'
adding 'django/contrib/gis/gdal/LICENSE'
adding 'django/contrib/gis/gdal/__init__.py'
adding 'django/contrib/gis/gdal/base.py'
adding 'django/contrib/gis/gdal/datasource.py'
adding 'django/contrib/gis/gdal/driver.py'
adding 'django/contrib/gis/gdal/envelope.py'
adding 'django/contrib/gis/gdal/error.py'
adding 'django/contrib/gis/gdal/feature.py'
adding 'django/contrib/gis/gdal/field.py'
adding 'django/contrib/gis/gdal/geometries.py'
adding 'django/contrib/gis/gdal/geomtype.py'
adding 'django/contrib/gis/gdal/layer.py'
adding 'django/contrib/gis/gdal/libgdal.py'
adding 'django/contrib/gis/gdal/srs.py'
adding 'django/contrib/gis/gdal/prototypes/__init__.py'
adding 'django/contrib/gis/gdal/prototypes/ds.py'
adding 'django/contrib/gis/gdal/prototypes/errcheck.py'
adding 'django/contrib/gis/gdal/prototypes/generation.py'
adding 'django/contrib/gis/gdal/prototypes/geom.py'
adding 'django/contrib/gis/gdal/prototypes/raster.py'
adding 'django/contrib/gis/gdal/prototypes/srs.py'
adding 'django/contrib/gis/gdal/raster/__init__.py'
adding 'django/contrib/gis/gdal/raster/band.py'
adding 'django/contrib/gis/gdal/raster/base.py'
adding 'django/contrib/gis/gdal/raster/const.py'
adding 'django/contrib/gis/gdal/raster/source.py'
adding 'django/contrib/gis/geoip2/__init__.py'
adding 'django/contrib/gis/geoip2/base.py'
adding 'django/contrib/gis/geoip2/resources.py'
adding 'django/contrib/gis/geos/LICENSE'
adding 'django/contrib/gis/geos/__init__.py'
adding 'django/contrib/gis/geos/base.py'
adding 'django/contrib/gis/geos/collections.py'
adding 'django/contrib/gis/geos/coordseq.py'
adding 'django/contrib/gis/geos/error.py'
adding 'django/contrib/gis/geos/factory.py'
adding 'django/contrib/gis/geos/geometry.py'
adding 'django/contrib/gis/geos/io.py'
adding 'django/contrib/gis/geos/libgeos.py'
adding 'django/contrib/gis/geos/linestring.py'
adding 'django/contrib/gis/geos/mutable_list.py'
adding 'django/contrib/gis/geos/point.py'
adding 'django/contrib/gis/geos/polygon.py'
adding 'django/contrib/gis/geos/prepared.py'
adding 'django/contrib/gis/geos/prototypes/__init__.py'
adding 'django/contrib/gis/geos/prototypes/coordseq.py'
adding 'django/contrib/gis/geos/prototypes/errcheck.py'
adding 'django/contrib/gis/geos/prototypes/geom.py'
adding 'django/contrib/gis/geos/prototypes/io.py'
adding 'django/contrib/gis/geos/prototypes/misc.py'
adding 'django/contrib/gis/geos/prototypes/predicates.py'
adding 'django/contrib/gis/geos/prototypes/prepared.py'
adding 'django/contrib/gis/geos/prototypes/threadsafe.py'
adding 'django/contrib/gis/geos/prototypes/topology.py'
adding 'django/contrib/gis/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/gis/management/__init__.py'
adding 'django/contrib/gis/management/commands/__init__.py'
adding 'django/contrib/gis/management/commands/inspectdb.py'
adding 'django/contrib/gis/management/commands/ogrinspect.py'
adding 'django/contrib/gis/serializers/__init__.py'
adding 'django/contrib/gis/serializers/geojson.py'
adding 'django/contrib/gis/sitemaps/__init__.py'
adding 'django/contrib/gis/sitemaps/kml.py'
adding 'django/contrib/gis/sitemaps/views.py'
adding 'django/contrib/gis/static/gis/css/ol3.css'
adding 'django/contrib/gis/static/gis/img/draw_line_off.svg'
adding 'django/contrib/gis/static/gis/img/draw_line_on.svg'
adding 'django/contrib/gis/static/gis/img/draw_point_off.svg'
adding 'django/contrib/gis/static/gis/img/draw_point_on.svg'
adding 'django/contrib/gis/static/gis/img/draw_polygon_off.svg'
adding 'django/contrib/gis/static/gis/img/draw_polygon_on.svg'
adding 'django/contrib/gis/static/gis/js/OLMapWidget.js'
adding 'django/contrib/gis/templates/gis/openlayers-osm.html'
adding 'django/contrib/gis/templates/gis/openlayers.html'
adding 'django/contrib/gis/templates/gis/admin/openlayers.html'
adding 'django/contrib/gis/templates/gis/admin/openlayers.js'
adding 'django/contrib/gis/templates/gis/admin/osm.html'
adding 'django/contrib/gis/templates/gis/admin/osm.js'
adding 'django/contrib/gis/templates/gis/kml/base.kml'
adding 'django/contrib/gis/templates/gis/kml/placemarks.kml'
adding 'django/contrib/gis/utils/__init__.py'
adding 'django/contrib/gis/utils/layermapping.py'
adding 'django/contrib/gis/utils/ogrinfo.py'
adding 'django/contrib/gis/utils/ogrinspect.py'
adding 'django/contrib/gis/utils/srs.py'
adding 'django/contrib/humanize/__init__.py'
adding 'django/contrib/humanize/apps.py'
adding 'django/contrib/humanize/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ms/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/uz/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/templatetags/__init__.py'
adding 'django/contrib/humanize/templatetags/humanize.py'
adding 'django/contrib/messages/__init__.py'
adding 'django/contrib/messages/api.py'
adding 'django/contrib/messages/apps.py'
adding 'django/contrib/messages/constants.py'
adding 'django/contrib/messages/context_processors.py'
adding 'django/contrib/messages/middleware.py'
adding 'django/contrib/messages/utils.py'
adding 'django/contrib/messages/views.py'
adding 'django/contrib/messages/storage/__init__.py'
adding 'django/contrib/messages/storage/base.py'
adding 'django/contrib/messages/storage/cookie.py'
adding 'django/contrib/messages/storage/fallback.py'
adding 'django/contrib/messages/storage/session.py'
adding 'django/contrib/postgres/__init__.py'
adding 'django/contrib/postgres/apps.py'
adding 'django/contrib/postgres/constraints.py'
adding 'django/contrib/postgres/functions.py'
adding 'django/contrib/postgres/indexes.py'
adding 'django/contrib/postgres/lookups.py'
adding 'django/contrib/postgres/operations.py'
adding 'django/contrib/postgres/search.py'
adding 'django/contrib/postgres/serializers.py'
adding 'django/contrib/postgres/signals.py'
adding 'django/contrib/postgres/utils.py'
adding 'django/contrib/postgres/validators.py'
adding 'django/contrib/postgres/aggregates/__init__.py'
adding 'django/contrib/postgres/aggregates/general.py'
adding 'django/contrib/postgres/aggregates/mixins.py'
adding 'django/contrib/postgres/aggregates/statistics.py'
adding 'django/contrib/postgres/fields/__init__.py'
adding 'django/contrib/postgres/fields/array.py'
adding 'django/contrib/postgres/fields/citext.py'
adding 'django/contrib/postgres/fields/hstore.py'
adding 'django/contrib/postgres/fields/jsonb.py'
adding 'django/contrib/postgres/fields/ranges.py'
adding 'django/contrib/postgres/fields/utils.py'
adding 'django/contrib/postgres/forms/__init__.py'
adding 'django/contrib/postgres/forms/array.py'
adding 'django/contrib/postgres/forms/hstore.py'
adding 'django/contrib/postgres/forms/jsonb.py'
adding 'django/contrib/postgres/forms/ranges.py'
adding 'django/contrib/postgres/jinja2/postgres/widgets/split_array.html'
adding 'django/contrib/postgres/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/tk/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/uz/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/templates/postgres/widgets/split_array.html'
adding 'django/contrib/redirects/__init__.py'
adding 'django/contrib/redirects/admin.py'
adding 'django/contrib/redirects/apps.py'
adding 'django/contrib/redirects/middleware.py'
adding 'django/contrib/redirects/models.py'
adding 'django/contrib/redirects/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/kab/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/tk/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/uz/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/migrations/0001_initial.py'
adding 'django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py'
adding 'django/contrib/redirects/migrations/__init__.py'
adding 'django/contrib/sessions/__init__.py'
adding 'django/contrib/sessions/apps.py'
adding 'django/contrib/sessions/base_session.py'
adding 'django/contrib/sessions/exceptions.py'
adding 'django/contrib/sessions/middleware.py'
adding 'django/contrib/sessions/models.py'
adding 'django/contrib/sessions/serializers.py'
adding 'django/contrib/sessions/backends/__init__.py'
adding 'django/contrib/sessions/backends/base.py'
adding 'django/contrib/sessions/backends/cache.py'
adding 'django/contrib/sessions/backends/cached_db.py'
adding 'django/contrib/sessions/backends/db.py'
adding 'django/contrib/sessions/backends/file.py'
adding 'django/contrib/sessions/backends/signed_cookies.py'
adding 'django/contrib/sessions/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/kab/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/tk/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/uz/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/management/__init__.py'
adding 'django/contrib/sessions/management/commands/__init__.py'
adding 'django/contrib/sessions/management/commands/clearsessions.py'
adding 'django/contrib/sessions/migrations/0001_initial.py'
adding 'django/contrib/sessions/migrations/__init__.py'
adding 'django/contrib/sitemaps/__init__.py'
adding 'django/contrib/sitemaps/apps.py'
adding 'django/contrib/sitemaps/views.py'
adding 'django/contrib/sitemaps/management/__init__.py'
adding 'django/contrib/sitemaps/management/commands/__init__.py'
adding 'django/contrib/sitemaps/management/commands/ping_google.py'
adding 'django/contrib/sitemaps/templates/sitemap.xml'
adding 'django/contrib/sitemaps/templates/sitemap_index.xml'
adding 'django/contrib/sites/__init__.py'
adding 'django/contrib/sites/admin.py'
adding 'django/contrib/sites/apps.py'
adding 'django/contrib/sites/checks.py'
adding 'django/contrib/sites/management.py'
adding 'django/contrib/sites/managers.py'
adding 'django/contrib/sites/middleware.py'
adding 'django/contrib/sites/models.py'
adding 'django/contrib/sites/requests.py'
adding 'django/contrib/sites/shortcuts.py'
adding 'django/contrib/sites/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/kab/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/kab/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/tk/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/tk/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/uz/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/uz/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/sites/migrations/0001_initial.py'
adding 'django/contrib/sites/migrations/0002_alter_domain_unique.py'
adding 'django/contrib/sites/migrations/__init__.py'
adding 'django/contrib/staticfiles/__init__.py'
adding 'django/contrib/staticfiles/apps.py'
adding 'django/contrib/staticfiles/checks.py'
adding 'django/contrib/staticfiles/finders.py'
adding 'django/contrib/staticfiles/handlers.py'
adding 'django/contrib/staticfiles/storage.py'
adding 'django/contrib/staticfiles/testing.py'
adding 'django/contrib/staticfiles/urls.py'
adding 'django/contrib/staticfiles/utils.py'
adding 'django/contrib/staticfiles/views.py'
adding 'django/contrib/staticfiles/management/__init__.py'
adding 'django/contrib/staticfiles/management/commands/__init__.py'
adding 'django/contrib/staticfiles/management/commands/collectstatic.py'
adding 'django/contrib/staticfiles/management/commands/findstatic.py'
adding 'django/contrib/staticfiles/management/commands/runserver.py'
adding 'django/contrib/syndication/__init__.py'
adding 'django/contrib/syndication/apps.py'
adding 'django/contrib/syndication/views.py'
adding 'django/core/__init__.py'
adding 'django/core/asgi.py'
adding 'django/core/exceptions.py'
adding 'django/core/paginator.py'
adding 'django/core/signals.py'
adding 'django/core/signing.py'
adding 'django/core/validators.py'
adding 'django/core/wsgi.py'
adding 'django/core/cache/__init__.py'
adding 'django/core/cache/utils.py'
adding 'django/core/cache/backends/__init__.py'
adding 'django/core/cache/backends/base.py'
adding 'django/core/cache/backends/db.py'
adding 'django/core/cache/backends/dummy.py'
adding 'django/core/cache/backends/filebased.py'
adding 'django/core/cache/backends/locmem.py'
adding 'django/core/cache/backends/memcached.py'
adding 'django/core/checks/__init__.py'
adding 'django/core/checks/async_checks.py'
adding 'django/core/checks/caches.py'
adding 'django/core/checks/database.py'
adding 'django/core/checks/messages.py'
adding 'django/core/checks/model_checks.py'
adding 'django/core/checks/registry.py'
adding 'django/core/checks/templates.py'
adding 'django/core/checks/translation.py'
adding 'django/core/checks/urls.py'
adding 'django/core/checks/compatibility/__init__.py'
adding 'django/core/checks/security/__init__.py'
adding 'django/core/checks/security/base.py'
adding 'django/core/checks/security/csrf.py'
adding 'django/core/checks/security/sessions.py'
adding 'django/core/files/__init__.py'
adding 'django/core/files/base.py'
adding 'django/core/files/images.py'
adding 'django/core/files/locks.py'
adding 'django/core/files/move.py'
adding 'django/core/files/storage.py'
adding 'django/core/files/temp.py'
adding 'django/core/files/uploadedfile.py'
adding 'django/core/files/uploadhandler.py'
adding 'django/core/files/utils.py'
adding 'django/core/handlers/__init__.py'
adding 'django/core/handlers/asgi.py'
adding 'django/core/handlers/base.py'
adding 'django/core/handlers/exception.py'
adding 'django/core/handlers/wsgi.py'
adding 'django/core/mail/__init__.py'
adding 'django/core/mail/message.py'
adding 'django/core/mail/utils.py'
adding 'django/core/mail/backends/__init__.py'
adding 'django/core/mail/backends/base.py'
adding 'django/core/mail/backends/console.py'
adding 'django/core/mail/backends/dummy.py'
adding 'django/core/mail/backends/filebased.py'
adding 'django/core/mail/backends/locmem.py'
adding 'django/core/mail/backends/smtp.py'
adding 'django/core/management/__init__.py'
adding 'django/core/management/base.py'
adding 'django/core/management/color.py'
adding 'django/core/management/sql.py'
adding 'django/core/management/templates.py'
adding 'django/core/management/utils.py'
adding 'django/core/management/commands/__init__.py'
adding 'django/core/management/commands/check.py'
adding 'django/core/management/commands/compilemessages.py'
adding 'django/core/management/commands/createcachetable.py'
adding 'django/core/management/commands/dbshell.py'
adding 'django/core/management/commands/diffsettings.py'
adding 'django/core/management/commands/dumpdata.py'
adding 'django/core/management/commands/flush.py'
adding 'django/core/management/commands/inspectdb.py'
adding 'django/core/management/commands/loaddata.py'
adding 'django/core/management/commands/makemessages.py'
adding 'django/core/management/commands/makemigrations.py'
adding 'django/core/management/commands/migrate.py'
adding 'django/core/management/commands/runserver.py'
adding 'django/core/management/commands/sendtestemail.py'
adding 'django/core/management/commands/shell.py'
adding 'django/core/management/commands/showmigrations.py'
adding 'django/core/management/commands/sqlflush.py'
adding 'django/core/management/commands/sqlmigrate.py'
adding 'django/core/management/commands/sqlsequencereset.py'
adding 'django/core/management/commands/squashmigrations.py'
adding 'django/core/management/commands/startapp.py'
adding 'django/core/management/commands/startproject.py'
adding 'django/core/management/commands/test.py'
adding 'django/core/management/commands/testserver.py'
adding 'django/core/serializers/__init__.py'
adding 'django/core/serializers/base.py'
adding 'django/core/serializers/json.py'
adding 'django/core/serializers/jsonl.py'
adding 'django/core/serializers/python.py'
adding 'django/core/serializers/pyyaml.py'
adding 'django/core/serializers/xml_serializer.py'
adding 'django/core/servers/__init__.py'
adding 'django/core/servers/basehttp.py'
adding 'django/db/__init__.py'
adding 'django/db/transaction.py'
adding 'django/db/utils.py'
adding 'django/db/backends/__init__.py'
adding 'django/db/backends/ddl_references.py'
adding 'django/db/backends/signals.py'
adding 'django/db/backends/utils.py'
adding 'django/db/backends/base/__init__.py'
adding 'django/db/backends/base/base.py'
adding 'django/db/backends/base/client.py'
adding 'django/db/backends/base/creation.py'
adding 'django/db/backends/base/features.py'
adding 'django/db/backends/base/introspection.py'
adding 'django/db/backends/base/operations.py'
adding 'django/db/backends/base/schema.py'
adding 'django/db/backends/base/validation.py'
adding 'django/db/backends/dummy/__init__.py'
adding 'django/db/backends/dummy/base.py'
adding 'django/db/backends/dummy/features.py'
adding 'django/db/backends/mysql/__init__.py'
adding 'django/db/backends/mysql/base.py'
adding 'django/db/backends/mysql/client.py'
adding 'django/db/backends/mysql/compiler.py'
adding 'django/db/backends/mysql/creation.py'
adding 'django/db/backends/mysql/features.py'
adding 'django/db/backends/mysql/introspection.py'
adding 'django/db/backends/mysql/operations.py'
adding 'django/db/backends/mysql/schema.py'
adding 'django/db/backends/mysql/validation.py'
adding 'django/db/backends/oracle/__init__.py'
adding 'django/db/backends/oracle/base.py'
adding 'django/db/backends/oracle/client.py'
adding 'django/db/backends/oracle/creation.py'
adding 'django/db/backends/oracle/features.py'
adding 'django/db/backends/oracle/functions.py'
adding 'django/db/backends/oracle/introspection.py'
adding 'django/db/backends/oracle/operations.py'
adding 'django/db/backends/oracle/schema.py'
adding 'django/db/backends/oracle/utils.py'
adding 'django/db/backends/oracle/validation.py'
adding 'django/db/backends/postgresql/__init__.py'
adding 'django/db/backends/postgresql/base.py'
adding 'django/db/backends/postgresql/client.py'
adding 'django/db/backends/postgresql/creation.py'
adding 'django/db/backends/postgresql/features.py'
adding 'django/db/backends/postgresql/introspection.py'
adding 'django/db/backends/postgresql/operations.py'
adding 'django/db/backends/postgresql/schema.py'
adding 'django/db/backends/sqlite3/__init__.py'
adding 'django/db/backends/sqlite3/base.py'
adding 'django/db/backends/sqlite3/client.py'
adding 'django/db/backends/sqlite3/creation.py'
adding 'django/db/backends/sqlite3/features.py'
adding 'django/db/backends/sqlite3/introspection.py'
adding 'django/db/backends/sqlite3/operations.py'
adding 'django/db/backends/sqlite3/schema.py'
adding 'django/db/migrations/__init__.py'
adding 'django/db/migrations/autodetector.py'
adding 'django/db/migrations/exceptions.py'
adding 'django/db/migrations/executor.py'
adding 'django/db/migrations/graph.py'
adding 'django/db/migrations/loader.py'
adding 'django/db/migrations/migration.py'
adding 'django/db/migrations/optimizer.py'
adding 'django/db/migrations/questioner.py'
adding 'django/db/migrations/recorder.py'
adding 'django/db/migrations/serializer.py'
adding 'django/db/migrations/state.py'
adding 'django/db/migrations/utils.py'
adding 'django/db/migrations/writer.py'
adding 'django/db/migrations/operations/__init__.py'
adding 'django/db/migrations/operations/base.py'
adding 'django/db/migrations/operations/fields.py'
adding 'django/db/migrations/operations/models.py'
adding 'django/db/migrations/operations/special.py'
adding 'django/db/migrations/operations/utils.py'
adding 'django/db/models/__init__.py'
adding 'django/db/models/aggregates.py'
adding 'django/db/models/base.py'
adding 'django/db/models/constants.py'
adding 'django/db/models/constraints.py'
adding 'django/db/models/deletion.py'
adding 'django/db/models/enums.py'
adding 'django/db/models/expressions.py'
adding 'django/db/models/indexes.py'
adding 'django/db/models/lookups.py'
adding 'django/db/models/manager.py'
adding 'django/db/models/options.py'
adding 'django/db/models/query.py'
adding 'django/db/models/query_utils.py'
adding 'django/db/models/signals.py'
adding 'django/db/models/utils.py'
adding 'django/db/models/fields/__init__.py'
adding 'django/db/models/fields/files.py'
adding 'django/db/models/fields/json.py'
adding 'django/db/models/fields/mixins.py'
adding 'django/db/models/fields/proxy.py'
adding 'django/db/models/fields/related.py'
adding 'django/db/models/fields/related_descriptors.py'
adding 'django/db/models/fields/related_lookups.py'
adding 'django/db/models/fields/reverse_related.py'
adding 'django/db/models/functions/__init__.py'
adding 'django/db/models/functions/comparison.py'
adding 'django/db/models/functions/datetime.py'
adding 'django/db/models/functions/math.py'
adding 'django/db/models/functions/mixins.py'
adding 'django/db/models/functions/text.py'
adding 'django/db/models/functions/window.py'
adding 'django/db/models/sql/__init__.py'
adding 'django/db/models/sql/compiler.py'
adding 'django/db/models/sql/constants.py'
adding 'django/db/models/sql/datastructures.py'
adding 'django/db/models/sql/query.py'
adding 'django/db/models/sql/subqueries.py'
adding 'django/db/models/sql/where.py'
adding 'django/dispatch/__init__.py'
adding 'django/dispatch/dispatcher.py'
adding 'django/dispatch/license.txt'
adding 'django/forms/__init__.py'
adding 'django/forms/boundfield.py'
adding 'django/forms/fields.py'
adding 'django/forms/forms.py'
adding 'django/forms/formsets.py'
adding 'django/forms/models.py'
adding 'django/forms/renderers.py'
adding 'django/forms/utils.py'
adding 'django/forms/widgets.py'
adding 'django/forms/jinja2/django/forms/widgets/attrs.html'
adding 'django/forms/jinja2/django/forms/widgets/checkbox.html'
adding 'django/forms/jinja2/django/forms/widgets/checkbox_option.html'
adding 'django/forms/jinja2/django/forms/widgets/checkbox_select.html'
adding 'django/forms/jinja2/django/forms/widgets/clearable_file_input.html'
adding 'django/forms/jinja2/django/forms/widgets/date.html'
adding 'django/forms/jinja2/django/forms/widgets/datetime.html'
adding 'django/forms/jinja2/django/forms/widgets/email.html'
adding 'django/forms/jinja2/django/forms/widgets/file.html'
adding 'django/forms/jinja2/django/forms/widgets/hidden.html'
adding 'django/forms/jinja2/django/forms/widgets/input.html'
adding 'django/forms/jinja2/django/forms/widgets/input_option.html'
adding 'django/forms/jinja2/django/forms/widgets/multiple_hidden.html'
adding 'django/forms/jinja2/django/forms/widgets/multiple_input.html'
adding 'django/forms/jinja2/django/forms/widgets/multiwidget.html'
adding 'django/forms/jinja2/django/forms/widgets/number.html'
adding 'django/forms/jinja2/django/forms/widgets/password.html'
adding 'django/forms/jinja2/django/forms/widgets/radio.html'
adding 'django/forms/jinja2/django/forms/widgets/radio_option.html'
adding 'django/forms/jinja2/django/forms/widgets/select.html'
adding 'django/forms/jinja2/django/forms/widgets/select_date.html'
adding 'django/forms/jinja2/django/forms/widgets/select_option.html'
adding 'django/forms/jinja2/django/forms/widgets/splitdatetime.html'
adding 'django/forms/jinja2/django/forms/widgets/splithiddendatetime.html'
adding 'django/forms/jinja2/django/forms/widgets/text.html'
adding 'django/forms/jinja2/django/forms/widgets/textarea.html'
adding 'django/forms/jinja2/django/forms/widgets/time.html'
adding 'django/forms/jinja2/django/forms/widgets/url.html'
adding 'django/forms/templates/django/forms/widgets/attrs.html'
adding 'django/forms/templates/django/forms/widgets/checkbox.html'
adding 'django/forms/templates/django/forms/widgets/checkbox_option.html'
adding 'django/forms/templates/django/forms/widgets/checkbox_select.html'
adding 'django/forms/templates/django/forms/widgets/clearable_file_input.html'
adding 'django/forms/templates/django/forms/widgets/date.html'
adding 'django/forms/templates/django/forms/widgets/datetime.html'
adding 'django/forms/templates/django/forms/widgets/email.html'
adding 'django/forms/templates/django/forms/widgets/file.html'
adding 'django/forms/templates/django/forms/widgets/hidden.html'
adding 'django/forms/templates/django/forms/widgets/input.html'
adding 'django/forms/templates/django/forms/widgets/input_option.html'
adding 'django/forms/templates/django/forms/widgets/multiple_hidden.html'
adding 'django/forms/templates/django/forms/widgets/multiple_input.html'
adding 'django/forms/templates/django/forms/widgets/multiwidget.html'
adding 'django/forms/templates/django/forms/widgets/number.html'
adding 'django/forms/templates/django/forms/widgets/password.html'
adding 'django/forms/templates/django/forms/widgets/radio.html'
adding 'django/forms/templates/django/forms/widgets/radio_option.html'
adding 'django/forms/templates/django/forms/widgets/select.html'
adding 'django/forms/templates/django/forms/widgets/select_date.html'
adding 'django/forms/templates/django/forms/widgets/select_option.html'
adding 'django/forms/templates/django/forms/widgets/splitdatetime.html'
adding 'django/forms/templates/django/forms/widgets/splithiddendatetime.html'
adding 'django/forms/templates/django/forms/widgets/text.html'
adding 'django/forms/templates/django/forms/widgets/textarea.html'
adding 'django/forms/templates/django/forms/widgets/time.html'
adding 'django/forms/templates/django/forms/widgets/url.html'
adding 'django/http/__init__.py'
adding 'django/http/cookie.py'
adding 'django/http/multipartparser.py'
adding 'django/http/request.py'
adding 'django/http/response.py'
adding 'django/middleware/__init__.py'
adding 'django/middleware/cache.py'
adding 'django/middleware/clickjacking.py'
adding 'django/middleware/common.py'
adding 'django/middleware/csrf.py'
adding 'django/middleware/gzip.py'
adding 'django/middleware/http.py'
adding 'django/middleware/locale.py'
adding 'django/middleware/security.py'
adding 'django/template/__init__.py'
adding 'django/template/autoreload.py'
adding 'django/template/base.py'
adding 'django/template/context.py'
adding 'django/template/context_processors.py'
adding 'django/template/defaultfilters.py'
adding 'django/template/defaulttags.py'
adding 'django/template/engine.py'
adding 'django/template/exceptions.py'
adding 'django/template/library.py'
adding 'django/template/loader.py'
adding 'django/template/loader_tags.py'
adding 'django/template/response.py'
adding 'django/template/smartif.py'
adding 'django/template/utils.py'
adding 'django/template/backends/__init__.py'
adding 'django/template/backends/base.py'
adding 'django/template/backends/django.py'
adding 'django/template/backends/dummy.py'
adding 'django/template/backends/jinja2.py'
adding 'django/template/backends/utils.py'
adding 'django/template/loaders/__init__.py'
adding 'django/template/loaders/app_directories.py'
adding 'django/template/loaders/base.py'
adding 'django/template/loaders/cached.py'
adding 'django/template/loaders/filesystem.py'
adding 'django/template/loaders/locmem.py'
adding 'django/templatetags/__init__.py'
adding 'django/templatetags/cache.py'
adding 'django/templatetags/i18n.py'
adding 'django/templatetags/l10n.py'
adding 'django/templatetags/static.py'
adding 'django/templatetags/tz.py'
adding 'django/test/__init__.py'
adding 'django/test/client.py'
adding 'django/test/html.py'
adding 'django/test/runner.py'
adding 'django/test/selenium.py'
adding 'django/test/signals.py'
adding 'django/test/testcases.py'
adding 'django/test/utils.py'
adding 'django/urls/__init__.py'
adding 'django/urls/base.py'
adding 'django/urls/conf.py'
adding 'django/urls/converters.py'
adding 'django/urls/exceptions.py'
adding 'django/urls/resolvers.py'
adding 'django/urls/utils.py'
adding 'django/utils/__init__.py'
adding 'django/utils/_os.py'
adding 'django/utils/archive.py'
adding 'django/utils/asyncio.py'
adding 'django/utils/autoreload.py'
adding 'django/utils/baseconv.py'
adding 'django/utils/cache.py'
adding 'django/utils/connection.py'
adding 'django/utils/crypto.py'
adding 'django/utils/datastructures.py'
adding 'django/utils/dateformat.py'
adding 'django/utils/dateparse.py'
adding 'django/utils/dates.py'
adding 'django/utils/datetime_safe.py'
adding 'django/utils/deconstruct.py'
adding 'django/utils/decorators.py'
adding 'django/utils/deprecation.py'
adding 'django/utils/duration.py'
adding 'django/utils/encoding.py'
adding 'django/utils/feedgenerator.py'
adding 'django/utils/formats.py'
adding 'django/utils/functional.py'
adding 'django/utils/hashable.py'
adding 'django/utils/html.py'
adding 'django/utils/http.py'
adding 'django/utils/inspect.py'
adding 'django/utils/ipv6.py'
adding 'django/utils/itercompat.py'
adding 'django/utils/jslex.py'
adding 'django/utils/log.py'
adding 'django/utils/lorem_ipsum.py'
adding 'django/utils/module_loading.py'
adding 'django/utils/numberformat.py'
adding 'django/utils/regex_helper.py'
adding 'django/utils/safestring.py'
adding 'django/utils/termcolors.py'
adding 'django/utils/text.py'
adding 'django/utils/timesince.py'
adding 'django/utils/timezone.py'
adding 'django/utils/topological_sort.py'
adding 'django/utils/tree.py'
adding 'django/utils/version.py'
adding 'django/utils/xmlutils.py'
adding 'django/utils/translation/__init__.py'
adding 'django/utils/translation/reloader.py'
adding 'django/utils/translation/template.py'
adding 'django/utils/translation/trans_null.py'
adding 'django/utils/translation/trans_real.py'
adding 'django/views/__init__.py'
adding 'django/views/csrf.py'
adding 'django/views/debug.py'
adding 'django/views/defaults.py'
adding 'django/views/i18n.py'
adding 'django/views/static.py'
adding 'django/views/decorators/__init__.py'
adding 'django/views/decorators/cache.py'
adding 'django/views/decorators/clickjacking.py'
adding 'django/views/decorators/common.py'
adding 'django/views/decorators/csrf.py'
adding 'django/views/decorators/debug.py'
adding 'django/views/decorators/gzip.py'
adding 'django/views/decorators/http.py'
adding 'django/views/decorators/vary.py'
adding 'django/views/generic/__init__.py'
adding 'django/views/generic/base.py'
adding 'django/views/generic/dates.py'
adding 'django/views/generic/detail.py'
adding 'django/views/generic/edit.py'
adding 'django/views/generic/list.py'
adding 'django/views/templates/default_urlconf.html'
adding 'django/views/templates/technical_404.html'
adding 'django/views/templates/technical_500.html'
adding 'django/views/templates/technical_500.txt'
adding 'Django-3.2.25.dist-info/AUTHORS'
adding 'Django-3.2.25.dist-info/LICENSE'
adding 'Django-3.2.25.dist-info/LICENSE.python'
adding 'Django-3.2.25.dist-info/METADATA'
adding 'Django-3.2.25.dist-info/WHEEL'
adding 'Django-3.2.25.dist-info/entry_points.txt'
adding 'Django-3.2.25.dist-info/top_level.txt'
adding 'Django-3.2.25.dist-info/RECORD'
removing build/bdist.netbsd-9.0-i386/wheel
Successfully built Django-3.2.25-py3-none-any.whl